SAP® Business ByDesign™: Business Requirements can change – our Solution can be adapted accordingly.
Optimize and
extend the solution
during runtime
Make us of a
comprehensive
development
environment
Scoping and
fine-tuning of the
complete solution
SAP Business ByDesign™
Introduction ByD Deployment: ByD Architecture
•SAP focuses on the Core Scenarios
of the SAP Business ByDesign
solution (SaaS) and provides with a
comprehensive Platform from both a
technical and a commercial point of
view.
Partner Extensions
Development
Environment
ByDesign Platform
(Micro) Vertical Solutions
Mashups
Integrated
Software
& Services
Add-on
Solutiuons
Forms &
Reports
Design Print Form
Generate Reports
Generate Web Services
Define Business Object Generate & Tune UI Excel Upload
TracingCalculated Extension Fields Business Configuration
Integrate with BYD
Lifecycle Management
Add Approval Task
SAP Business ByDesign™
Introduction ByD Deployment Architecture
Persistence
Database and
Search Engine
Work
Center
Business
Object
Transactional UIUser
InterfaceService-oriented
architecture:
Core Services
standardize the access
to business objects like
SQL standardizes
access to database
tables• Create
• Read
• Update
• Delete
SAP Business ByDesign™Introduction ByD Deployment Architecture
Work
CenterUser
Interface Transactional UI Analytical UI
Business
Object
Service
Interface
Service
Interface
Business
TaskMail
(iForm)
Service
Integration
Application
Business Logic
Print,
Fax,
Form
Message
Type
Analytical UI
Extension
Web Service
Connection
(external/interal)
Message
Type
SAP Business ByDesign™Introduction ByD Deployment: Environment
Developers Desktop
Hosted Development
System
Bu
sin
ess
ByD
esig
n
Stu
dio
Bro
wser
RepositorySAP Content
__________________________
_______
______________________
Partner Content
__________________________
_______
Runtime
Develo
p
Test
Deplo
y
Definition “Business Object”
•“A business object is an entity of significance to a business.”
•In Business 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
Sales
OrderPurchase
Order
Customer
Invoice
Product
Accounting
Document
Business
Partner
Accounting
Principle
Dunning
Strategy
Business Transaction Documents
Master Data Objects
Business Configuration Objects
Note: In our context business object means the type and
not the instance!
Business object: purchase order
Business object instance: purchase order with ID 32452
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 be mandatory or optional. Elements with cardinality larger than
1 require a separate node.
Sales Order
Root
Item1..n
Party1..n
Bonus Entitlement
Root
Bonus Plan
Root
Product
Bonus
Rule
0..n
• Product ID
• Quantity
• …
• Party Role Code
• Party ID
• Product ID
• Product Bonus
• …
Business Object Node Operations
Business objects nodes offer services (operations), which can be accessed via
interfaces. Operations and their implementation are generated from the BO definition
Business logic is added in script coding. Script coding may call operations from other
business object nodes
Query Retrieve Save
Database and Search Engine
Business Object Buffer and Lock Handler
Script Coding
(AfterModify)Script Coding(Action)
Script Coding
(BeforeSave)
BO-Joins
Modify(Create,Update,
Delete)
Action(application-
defined)
Definition “Integration Scenario ”
Sales Order Processing
Sales
Order
Customer Relationship Management
Bonus
Plan
Bonus
Entitlement
Bonus
Management
Employee
Compensation
Agreement
Compensation
Management
Foundation
Employee Material
Human Capital Management
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.
Process Interaction: Defines the
interaction between business
objects in different deployment
units
Query
Request
Response
Message-based
interaction
The Business Object and its Relationships
Sales Order Processing
Sales
Order
Customer Relationship Management
Bonus
Plan
Bonus
Entitlement
Bonus Management
Employee
Compensation
Agreement
Compensation
Management
Foundation
Employee Material
Human Capital Management
[0..n] [0..n]
[0..n] 1
1
[0..n] [0..n]
[0..n]
[0..1]
[0..n]
Business
Object 2
Business
Object 1
UI N
avig
atio
n
Business
Object 1
Business
Object 2
Dire
ct B
O In
tera
ctio
n
Business
Object 2
Business
Object 1
Se
rvic
e
Inte
rac
tion
Request
Response
Transactional UI Transactional UI
Transactional UI
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
UI-driven or process driven
Separate transactional sessions
For BOs in different deployment units
Two directions
UI-driven
Separate transactional
sessions
No interaction between
business objects
One direction
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
UI Interaction Model
OWL
Bonus Rule
QA / OI / FS
Bonus Rule
OWL
Bonus Plan
QA / OI / FS
Bonus Plan
OVS
Bonus Rule
OVS
Employee
FS
Employee
OWL
Bonus
Entitlement
QA / OI / FS
Bonus
Entitlement
FS
Sales Order
Display
FS
ProductOVS
Product
Display
Create
New
Edit
New
Edit
New
Edit
DisplayFind
Find
Display
DisplayFind
Create:
Creates an
object with
reference
New: Opens an empty floor plan, creates a new object
SAP Business ByDesign™ABSL Part I – Core/ Global Data Types
Namespaces
•SAP data types are located in namespace: http://sap.com/xi/AP/Common/GDT
•For rapid prototyping you may also use namespace: http://sap.com/xi/BASIS/Global
•SAP GDT Catalog can be accessed in SDN:
•http://wiki.sdn.sap.com/wiki/display/GDT/SAP+Global+Data+Type+Catalog
Identifier
•Use to identify a business object, or business concept:
•element ID : Identifier;
SAP Business 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).
SAP Business ByDesign™ABSL Part I – Core/ Global Data Types
NumberValue, Amount, Quantity, Measure
•element SomeNumberValue : NumberValue;
•element SomeAmount : Amount;
•element SomeQuantity : Quantity;
•element SomeMeasure : Measure;
Ratio, Percent
•element SomeRatio : Ratio;
•element SomePercent : Percent;
Boolean
•element SomeIndicator : Indicatior;
SAP Business ByDesign™
ABSL Part I – Core/ Global Data Types
Date and Time
•element SomeDate : Date;
•element SomeDateTime:http://sap.com/xi/BASIS/Global”: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;