Business Process Architecture: Jochen Boeder SAT Knowledge Transfer

Business Process
Architecture
Kick-off Architecture Training, November 25/26, 2004
Jochen Boeder
SAT Knowledge Transfer
ESA Service Composition & Orchestration
PEOPLE PRODUCTIVITY
ANALYTICS/REPORTING
SERVICE COMPOSITION
& ORCHESTRATION
SAP NetWeaver
Enterprise
SERVICE Services
ENABLEMENT Repository
SAP’s Enterprise Partner

Services Services
Business Objects, Components,
and Engines
Bus.
Legacy
Partner
LIFE-CYCLE MGMT
 SAP AG 2004, Kick-off Bangalore, Business Process Architecture, Jochen Böder / 2

Introduction
Business Process Modeling
Business Process Architecture
Consequences for Development

Process Integration Architecture - Objectives
Objectives & Benefits

 Reusable processes in different scenarios
 Flexible deployment options
 Flexible process enhancements and adaptation
 Transparency of business processes
 Model-based, process-oriented development process
Design principles
 Loosely coupled B2B and A2A processes
 Message-based and
 Event-driven process integration
 Model driven
 Separation of business logic from process logic
 Error forward recovery

Introduction

What is Process Modeling and why are we doing it?
Process Modeling is a formal methodology to describe

business scenarios and processes at SAP
Key Goals
 Transparency of the main process building blocks and their
interactions – incl. Processes and Services
 Model driven development process
 Models linked with software implementation
 Model based scoping and implementation process
 Define a unified methodology used in all SAP Solutions from
business level modeling to service modeling

Vision: Unified Modeling Environment
Meta Model
Business-level
Models
Process Configuration
Models
Process Execution SAP NETWEAVER

Models Enterprise Services
Repository
One single Repository!

Design Time: Layers in Modeling Environment
Unified Modeling Environment

Focus on business
level and how Business Scenario,
Process,
customer implements Process Step Business Level Model Process-Oriented
View
solution, refers directly
to ESA Process Model
Turning process-oriented Application Scenario,

view into ESA Process ESA Process Model
object-oriented
view
Business Objects
Static, 1:1 A2A & B2B Services ESA Object & Object-Oriented
representation of Process Agents
repository content
Messages Services Catalog View
Enterprise
Services
Repository

Overview: Modeling in Platform
KEY MESSAGE
The ESA Process Models are available in ARIS today. Content for these models is
currently in development for the Business Process Platform. The Process Map
represents the Process Integration Content of the Business Process Platform.
Process Map Business Activity

Processing Scenario Variant Model
(View on Process Map)
Personnel
Opportunity Administration
Processing
Supply to Production Demand Planning Sales Contract

Quotation
Processing
Sales Order
Production Procurement Sales Delivery
Purchase Contract
Delivery Schedule Schedule
Sales Contract Service Contract Quotation
Processing Processing Processing
Management Management Processing
Delivery from
Production Sales Order Sales Order
RFQ Processing Service Request
Quotation RFQ Processing Quotation
Supply Planning at at Customer Processing
Processing ... Processing Purchase Order
Supplier Sales Order
A Supply Planning Processing at
A Processing
Customer
Sales Scheduling Procurement
Internal Requirement Sales Scheduling
Release Processing Scheduling Release Supply Planning
Processing Release Processing
at Supplier Processing A
Purchase
Project
Processing
Requirement Procurement Inbound Delivery
Processing Scheduling Release Outbound Delivery
at Customer Processing at
Processing
Customer
Personnel Times
Sales Order Purchase Order
Processing at
Purchase Order Sales Order
Processing at
Service Order Management A
Processing Processing Processing
Supplier Customer
A
A A
Supplier Invoice
Customer Invoice
Service Confirmation Goods and Service
Outbound Delivery
Inbound Delivery Outbound Delivery
Inbound Delivery
Service Confirmation
Goods and Service Processing at
Processing at Processing at Confirmation at Processing
at Supplier Confirmation
Supplier
Processing Processing
Customer
Processing
Customer Customer
A
A A A
A
A Due Item Processing
Customer Invoice Supplier Invoice

Supplier Invoice Customer Invoice
Processing at Processing at
Processing Processing
Supplier Customer
Return Processing
A A
Payment Processing
A Payment Processing
at Business Partner
Accounting
Payment processing Bank statement
A Document
A Payment Processing
Payment Processing at house bank creation at bank
at Business Partner Processing
Accounting
A Document
Processing
at house bank creation at bank
ESA Process Model
Process Interaction Model

Scenario Variant: Plan Driven Procurement
draft
Process
Supply Planning Interaction (drill
down in Accounting
detailed model) A Document
Processing
ESA Process
(drill down in Purchase
Requirement
detailed model) Processing
Sales Order
Purchase Order
A Processing at
Processing
Supplier
ESA Process
Outbound Delivery at B2B Partner
Inbound Delivery
Processing at
Processing
Supplier
Customer Invoice
Supplier Invoice
A Processing at
Processing
Supplier
Payment Payment Processing

A
Processing at Business Partner

at house bank creation at bank Topic relevant part
Detail of a Node (ESA Process)
BO centric view: Business Object, it’s A2A & B2B Services, Process Agents
as a single modeling entity (represents a reuse block for building business scenarios)

Detail of a Connection: 1:1 Link to Repository Content
Process Interaction Model
Process Process
Outbound Inbound
Interface Interface
Business Outbound Inbound Business

Object Process Operation XI Operation Process Object
Agent message Agent
Process Interaction Model: PurchaseOrderIntegration
Process: PurchaseOrderProcessing Process: SalesOrderProcessing

Business Object: PurchaseOrder Business Object: SalesOrder
Outbound Process Agent: Inbound Process Agent:
- Name: PurchaseOrderProcessing - Name: SalesOrderProcessing
Outbound Interface: PurchaseOrderRequest_out Inbound Interface: PurchaseOrderRequest_in
Operation: PurchaseOrderRequest_out Operation: PurchaseOrderRequest_in

Logical Metamodel: Process – Business Objects – Services
Process Model Business Object Model Service Description

(based on WSDL & XSD)
Application Scenario
* * Service
1..*
0..1 * *
0..1
ESA Process 0..1 Business Object
1
*
2 Root 1
Service Interface
Node 1 1..*
* 1..*
*
* 0..1 2 1
Process Interaction Business Object Node
Source 2 1..*
* * *
& Target
Node Operation
*
Some detail omitted Input
(Mapping of Operations Output
between two Processes) Fault
1..*
Key 1
Data 1 Data Type
*
Definition: XML Schema
Association (binary)
*
Sales Order *
Processing Inclusion
Composition
Outb. Delivery
Processing

Introduction

Process Integration Architecture - Overview
ESA Process Interaction Model (Process Modeling)
Process Process
Outbound Inbound
Interface Interface
Object Process Agent Operation XI message Operation Process Agent Object
Business Application Business Application

Service Layer Process Layer Process Layer Service Layer
Business Logic Process Logic Process Logic Business Logic
Workflow
Event Event
Start Manager Process Agent
Exception WF
Manager
Business
Event Business
async Outbound Event
Proxy
Process Agent
async Process A
Process Agent Proxy
Process C
Exception
Outbound async async
Proxy Proxy Inbound
Process Agent
Process Agent
Process B
End
Process Integration Process Integration
Persistence Persistence
Sending Receiving
SAP XI Business Business
SAP XI
Document Document
Data Flow Central SAP XI

Routing, Mapping, …

Process Integration Architecture - Outbound processing
Process Process
Outbound Inbound
Interface Interface

Workflow
Event Event
Exception WF
Manager
Business
Event Business
Proxy
Process Agent
async Process A
Process Agent Proxy
Process C
Exception
Proxy Proxy Inbound
Process Agent
Process Agent
Process B
End
Process Agent for Process Integration Process Integration
Outbound Processing Persistence Persistence
Sending Receiving
SAP XI
Document Document


Transactional Behaviour - Outbound
Outbound
User Interaction or Automatic Execution Framework Process Agent
start modify 1 modify 2 push/trigger before save after commit end

save button save save work
LUW
raise business
events „saved“
loop at business
events „saved“
check objects update process logic of

business logic & services objects outbound process agent

Event
Manager
Outbound async
Process Agent A PROXY
Outbound async
Process Agent B PROXY
Business
Event Outbound async
Process Agent C PROXY
Business
Object Task:
Identify registered process agents
Call registered process agents at transactional point
“after_save”
Input:
Business Object type; Business Event type “saved”
Uses:
Registration information (configurable)
Output:
Activated process agents

Outbound Process Agent - Details
async
Outbound Proxy
Process Agent
Responsibili
Process Process
Condition ty Message Proxy Call
Persistence
Relevance Evaluation Determinatio Assembly and Logging
Evaluation
n
Business
Event
Business
Object Process model /
MOM
configuration
Process Integration Persistence
Role of Outbound Process Agent

 Mediator between business object(s) and subsequent process
 Only carriers of process integration logic

Process Integration Architecture - Outbound processing
Process Process
Outbound Inbound
Interface Interface

Workflow
Event Event
Exception WF
Manager
Business
Event Business
Proxy
Process Agent
async Process A
Process Agent Proxy
Process C
Exception
Proxy Proxy Inbound
Process Agent
Process Agent
Process B
End
Persistence Persistence Process Agent for
Sending Receiving
Inbound Processing
SAP XI
Document Document


Transactional Behaviour - Inbound
Outbound
XI Proxy Inbound Process Agent Framework
Process Agent
start modify 1 modify 2 trigger save before save after commit after
button save save work commitend
LUW
raise business
events „saved“
loop at business
events saved
process logic of
check objects update
business logic outbound process
& services objects
agents

Inbound Process Agent - Details
async
Proxy Inbound
Process Agent
Exception
event
Exception handling
Check Mapping to Modify Message

Sequence Check
message Business Business Save release and
handling before save
content Object Object logging
Process model /
configuration Business
Object(s)
Process Integration Persistence
Role of Inbound Process Agent

 Decoupling of message transfer from message processing for short, robust
transactions
 Reuse of business object core services
 Uniform, push driven exception handling
Error and Conflict Handling: Motivation
Motivation
 Mainly asynchronous, loosely coupled programming model
 No (or only few) cross component early validation
 No common database transaction
 No technical error resolution possible e.g. no rollback
 Risk of problems during inbound processing increases
Errors must be resolved on business level
Advanced error handling & resolution concept required
Active information about error situations of person in charge
Proper Error and Conflict Handling is Key

Classification of Errors and Conflicts
Errors in message structure or data format
Errors in data conversion
Errors at message processing
Error in subsequent business logic
Conflicts with exceeded process milestones
Conflicts with deadlines
Conflicts by business exception
Conflicts by violation of business data integrity
Conflicts by violation of business protocoll

Error Handling: Error Propagation
Push driven error propagation

 Responsibility determination based on
Exception  Business Object responsible
WF  Message content
Exception
event  Person / team determined done via MOM
 Creation of task for person in charge
Error Handling: Manual Error Processing
* Sample UI provided by team ‘Business Process Renovation’

Error handling: Basic principles
Error forward recovery

 Errors are resolved at business level, not on technical level
 Applications are responsible for error processing, not XI
High quality of error messages by applications needed

 Basis for proper analysis and automatic resolution strategies
Sophisticated trouble shooting UI for error resolution needed

 Detailed analysis within familiar environment of person in charge
 Dedicated features for error processing needed
Sophisticated error resolution needed

 To minimize effort for customers
 Definition of automatic resolution strategies based on symptom and
cause

Process Integration Architecture - Process Integration Persistence
Business Business
Application Application
Business Business
Process Process
A B

Service Layer Process Layer Process Layer Service Layer Keeps state of the
integration process
Workflow
Basis for use cases

Start
Event
Manager Process Agent
Event
Manager
 Process decisions
Exception WF
Business
Event async Outbound
Business
Event
 Common monitoring
Proxy
Process Agent
Process Agent
async
Proxy
Process A
 Message
Process C
Exception
choreography
Process Agent Proxy Proxy Inbound
Process Agent
 Sequencing
Process B
End
 Consistency tools
Sending Receiving
SAP XI
Document Document
Central SAP XI

Further Process Agents
Business Business
Application Application
Business Business
Process Process

Workflow Workflow
Process Agents for
Workflow integrating
Event
Manager Process Agent Process Agent
Event
Manager
Business Objects with
Workflow
for Workflow for Workflow
Business
Event Business
Process Agent async async Process Agent Event
Proxy Proxy
for Outbound for Outbound
Integration Integration
Process Agent async async Process AgentException

for Inbound
Integration
Proxy Proxy
for Inbound
Integration
Process Agents for
Process Agent sync
Proxy
sync
Proxy
Process Agent synchronous Integration
for sync. for sync.
Integration Integration used for synchronous
Process Integration Process Integration cross component
communication
Sending Receiving
SAP XI
Document Document
Central SAP XI

Flexible Deployment: One-System-Solution
Workflow
Event Event
Exception WF
Manager
Business
Event Business
Event
async Inbound
async Proxy
Process Agent Process Agent
Proxy
Process C Process B
Exception
Proxy Proxy Inbound
Process Agent
Process Agent
Process B
End
History History
Receiving
SAP XI Business
Document
LUW 1 LUW 2
One system solution
 Application architecture follows distributed solution
 ‘Short cut’ purely handled by infrastructure

Introduction

Tasks for Development
1.
Business Process Business Process
Outbound Inbound
Interface Interface

2 Registry
2. 4. 4. 2.
4 Relevance
Event 5 Conditions
Start Manager 3 Process Variant
Business
Event 6 Responsibility 4 Error Handling
7 Message 5 Service call

1 Outbound 3 async 2 async 1 Inbound
Process Agent PROXY PROXY Process Agent
End
Process Process
Integration Integration
3. SAP XI
Integration Scenario Connection Data Types
Outbound Mapping Inbound
Interface Interface …
Content Object
What can development do now?
Specification of Process Agents:

 Modeling of business processes
 Definition of conditions
 Identification of possible errors and conflicts

Contacts / Further Information
Process
Design
Process Contact: Günter Pecht-Seibert
Modeling
Contact: Stefan Kaetker Interface
Modeling/PIC
Contact: Michael Seubert
Vienna Portal at ESA -> Cross-Topics -> Business Process – Modeling

Business Process - Integration

Business Process Architecture: Jochen Boeder SAT Knowledge Transfer

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Business Process Architecture: Jochen Boeder SAT Knowledge Transfer

Hochgeladen von

Copyright:

Verfügbare Formate

Business Process

Kick-off Architecture Training, November 25/26, 2004

SAP’s Enterprise Partner

 SAP AG 2004, Kick-off Bangalore, Business Process Architecture, Jochen Böder / 2

Business Process Modeling

Business Process Architecture

Consequences for Development

Objectives & Benefits

 SAP AG 2004, Kick-off Bangalore, Business Process Architecture, Jochen Böder / 4

Business Process Modeling

Business Process Architecture

Consequences for Development

Process Modeling is a formal methodology to describe

 SAP AG 2004, Kick-off Bangalore, Business Process Architecture, Jochen Böder / 6

Process Execution SAP NETWEAVER

One single Repository!

 SAP AG 2004, Kick-off Bangalore, Business Process Architecture, Jochen Böder / 7

Unified Modeling Environment

Turning process-oriented Application Scenario,

 SAP AG 2004, Kick-off Bangalore, Business Process Architecture, Jochen Böder / 8

Process Map Business Activity

Supply to Production Demand Planning Sales Contract

A Due Item Processing

Customer Invoice Supplier Invoice

A Due Item Processing

ESA Process Model

Process Interaction Model

 SAP AG 2004, Kick-off Bangalore, Business Process Architecture, Jochen Böder / 9

A Due Item Processing

Payment Payment Processing

Payment processing Bank statement

 SAP AG 2004, Kick-off Bangalore, Business Process Architecture, Jochen Böder / 11

Process Interaction Model

Business Outbound Inbound Business

Process Interaction Model: PurchaseOrderIntegration

Process: PurchaseOrderProcessing Process: SalesOrderProcessing

 SAP AG 2004, Kick-off Bangalore, Business Process Architecture, Jochen Böder / 12

Process Model Business Object Model Service Description

 SAP AG 2004, Kick-off Bangalore, Business Process Architecture, Jochen Böder / 13

Business Process Modeling

Business Process Architecture

Consequences for Development

Business Application Business Application

Data Flow Central SAP XI

 SAP AG 2004, Kick-off Bangalore, Business Process Architecture, Jochen Böder / 15

Business Application Business Application

Data Flow Central SAP XI

 SAP AG 2004, Kick-off Bangalore, Business Process Architecture, Jochen Böder / 16

start modify 1 modify 2 push/trigger before save after commit end

check objects update process logic of

 SAP AG 2004, Kick-off Bangalore, Business Process Architecture, Jochen Böder / 17

 SAP AG 2004, Kick-off Bangalore, Business Process Architecture, Jochen Böder / 18

Process Integration Persistence

Role of Outbound Process Agent

 SAP AG 2004, Kick-off Bangalore, Business Process Architecture, Jochen Böder / 19

Business Application Business Application

Data Flow Central SAP XI

 SAP AG 2004, Kick-off Bangalore, Business Process Architecture, Jochen Böder / 20

 SAP AG 2004, Kick-off Bangalore, Business Process Architecture, Jochen Böder / 21

Check Mapping to Modify Message

Role of Inbound Process Agent

Errors must be resolved on business level