SAP Business ByDesign Studio

Transcription

1 SAP ByDesign Studio

2 SAP ByDesign : Requirements can change our Solution can be adapted accordingly. Scoping and fine-tuning of the complete solution Optimize and extend the solution during runtime Make us of a comprehensive development environment

3 SAP ByDesign Introduction ByD Deployment: ByD Architecture SAP focuses on the Core Scenarios of the SAP ByDesign solution (SaaS) and provides with a comprehensive Platform from both a technical and a commercial point of view. (Micro) Vertical Solutions Mashups Forms & Reports Add-on Solutiuons Partner Extensions Development Environment Integrated Software & Services ByDesign Platform

4 Define Object Generate & Tune UI Excel Upload Generate Reports Add Approval Task Design Print Form Integrate with BYD Generate Web Services Calculated Extension Fields Configuration Tracing Lifecycle Management

5 SAP ByDesign Introduction ByD Deployment Architecture User Interface Work Center Transactional UI Service-oriented architecture: Persistence Database and Search Engine Object Create Read Update Delete Core Services standardize the access to business objects like SQL standardizes access to database tables

6 SAP ByDesign Introduction ByD Deployment Architecture User Work Interface Center Transactional UI Analytical UI UI Form Service Integration Mail (iform) Message Type Object Message Type Task Print, Fax, Mail Web Service Connection (external/interal) Service Interface Application Logic Service Interface Extension

7 Developers Desktop SAP ByDesign Introduction ByD Deployment: Environment ByDesign Hosted Development System SAP Content Repository Partner Content Develop Browser Deplo y Runtime Test

8 Definition Object A business object is an entity of significance to a business. In ByDesign business objects Encapsulate business logic and business data Act as service consumer and provider Are accessible exclusively through a standardized set of (core) services Are described by a business object model which defines: Structure Type of the attributes Aspects of the behavior Service interfaces Transaction Documents Purchase Order Customer Invoice Master Data Objects Partner Dunning Strategy Sales Order Accounting Document Product Configuration Objects Accounting Principle Note: In our context business object means the type and not the instance! object: purchase order object instance: purchase order with ID 32452

9 Refinement of an Object Model: Compositions and Associations The internal structure of a business object is described by its components (object nodes) Nodes are compositions with cardinality are related via a strict hierarchical relationship (no n:m relationship) A separate node exposes semantics and business understanding represents a logical / semantic group of elements that can be treated as a group even if the elements could be assigned directly to the higher-level node: SalesOrderItemProduct: (Product, category, batch) Elements (attributes) in one node can Bonus be mandatory Entitlement or optional. Elements Bonus Planwith cardinality larger than 1 require a separate node. Sales Order Root Root Root 1..n Item Party 1..n Product ID Quantity Party Role Code Party ID 0..n Product Bonus Rule Product ID Product Bonus

10 Object Node Operations objects nodes offer services (operations), which can be accessed via interfaces. Operations and their implementation are generated from the BO definition logic is added in script coding. Script coding may call operations from other business object nodes Query Retrieve Modify Action Save BO-Joins (Create,Update, Delete) Script Coding (AfterModify) (applicationdefined) Script Coding (Action) Script Coding (BeforeSave) Object Buffer and Lock Handler Database and Search Engine

11 Definition Integration Scenario Customer Relationship Management Human Capital Management Sales Order Processing Sales Order Query Bonus Management Bonus Entitlement Bonus Plan Message-based interaction Request Response Compensation Management Employee Compensation Agreement Process Interaction: Defines the interaction between business objects in different deployment units Foundation Employee Material Deployment Unit: A software package that can be operated with the foundation layer, isolated from other deployment units. It contains a set of process components.

12 The Object and its Relationships Customer Relationship Management Human Capital Management Sales Order Processing Sales Order [0..n] [0..n] Bonus Management Bonus Entitlement [0..n] [0..n] Bonus Plan 1 [0..1] Compensation Management Employee Compensation Agreement [0..n] [0..n] Foundation 1 Employee [0..n] Material

13 Servic Interac UI-driven Transactional UI Transactional UI Separate transactional sessions UI Navigation Object 1 Transactional UI Object 1 Object 2 Object 2 No interaction between business objects One direction UI-driven or process driven One common transactional session Changes only allowed if both BOs are in the same deployment unit, or in foundation One direction Direct BO Interaction Object 1 Request Response Object 2 UI-driven or process driven Separate transactional sessions For BOs in different deployment units Two directions

14 UI Interaction Model/ UI Floor Plans The following floor plans are available in ByD: Work Center (WC), Control Center (CC): An area where an employee can perform the typical tasks or functions that they are responsible for within an enterprise. The Control Center is a dedicates work center that is the central starting point for all business activities Object Work List (OWL) Quick Activity (QA), Fact Sheet (FS), Object Instance (OI) For viewing and maintaining the key properties of an object and for viewing the the full set of properties of a business object. The employee can switch back and forth between different views

15 UI Interaction Model OWL Bonus Rule OWL Bonus Plan OWL Bonus Entitlement New Edit New Edit New Edit FS Sales Order QA / OI / FS Bonus Rule QA / OI / FS Bonus Plan QA / OI / FS Bonus Entitlement Display Create Display Display OVS Product Find Find New: Opens an empty floor plan, creates a new object Find Display Create: Creates an object with reference Display OVS Bonus Rule OVS Employee FS Employee FS Product

16 SAP ByDesign ABSL Part I Core/ Global Data Types Namespaces SAP data types are located in namespace: For rapid prototyping you may also use namespace: SAP GDT Catalog can be accessed in SDN: Identifier Use to identify a business object, or business concept: element ID : Identifier;

17 SAP ByDesign ABSL Part I Core/ Global Data Types element SomeAmount : Amount; element SomeQuantity : Quantity; element Name : LANGUAGEIDEPENTENT_SHORT_Name; element StartDate : Date; Strings element Name : LANGUAGEINDEPENDENT_SHORT_Name; element Description : LANGUAGEINDEPENDENT_Description; The lenght of the cahracter field is defined by the prefixes Short (10 char), Medium (40), Long (80), Extended (255).

18 NumberValue, Amount, Quantity, Measure SAP ByDesign ABSL Part I Core/ Global Data Types element SomeNumberValue : NumberValue; element SomeAmount : Amount; element SomeQuantity : Quantity; element SomeMeasure : Measure; Ratio, Percent element SomeRatio : Ratio; element SomePercent : Percent; Boolean element SomeIndicator : Indicatior;

19 SAP ByDesign ABSL Part I Core/ Global Data Types Date and Time element SomeDate : Date; element SomeDateTime: :GLOBAL_DateTime; There are the following re-use services for getting date and time: this.lastchangedate = Context.GetCurrentDate(); this.lastchangedatetime = Context.GetCurrentDateTime(); Codes element PriorityCode : PriorityCode; element ReleaseStatusCode : ReleaseStatusCode; element ApprovalStatusCode : ApprovalStatusCode;