SAP NetWeaver - Cross-Component Business Process Management With XI 3 (1) .0

Cross-Component Business Process Management with SAP Exchange Infrastructure Jerome Delune
SAP Labs, LLC
Learning Objectives
As a result of this presentation, you will be able to:

Understand three pillars of SAP Business Process
Management
Understand the cross-component BPM within SAP XI
SAP AG 2003, BPI202_US, George Yu / 2
Agenda
Driving process integration: BPM@SAP Cross-component BPM in XI 3.0: functions and features Process patterns Outlook and summary
Todays Grown Integration Landscapes

Business Partners
SAP SAP SAP SAP other Integration Solution SAP
3rd party
B2B B2B Tool Tool EAI EAI Tool Tool hard hard coded coded mainframe application
SAP
B2B Tool
Business Partner Application
Adapter
3rd Party 3rd Party
3rd Party
Marketplace
Integration with SAP Exchange Infrastructure (SAP XI)

SAP NetWeaver
SAP SAP SAP SAP XI SAP XI
3rd party
other Integration Solution
Business Partners
SAP
SAP
SAP XI SAP
mainframe application
RosettaNet Middleware
3rd Party
3rd Party 3rd Party
Marketplace
Process Driven Integration Solution

Business Partners
SAP SAP SAP
SAP Business Workflow
SAP other Integration SAP XI Solution

3rd party
3rd party BPMS Message Oriented Middleware 3rd party WfMS mainframe application
SAP
SAP
3rd Party
3rd Party 3rd Party Programmed Workflow
Marketplace
BPMS: Business Process Management System WfMS: Workflow Management System

Integration with SAP Exchange Infrastructure (SAP XI)

SAP NetWeaver
SAP SAP SAP
Business Partners
SAP ccBPM SAP XI

3rd party
SAP
ccBPM SAP
mainframe application
3rd Party
3rd Party 3rd Party Programmed Workflow
Marketplace
Business Process Management (BPM)

SAP NetWeaver BPM
A comprehensive BPM solution
Ad-hoc Workflow
Team-driven processes Spontaneous events Collaboration
Ad-hoc Workflow controls teamdriven processes Cross-Component BPM controls inter-application processes Business Workflow controls intraapplication processes
Cross-Component BPM
Design, execute and monitor automated processes across applications and systems Stateful interaction model Cross application execution
Business Workflow
Design, execute and monitor processes within applications Apply standard business rules Business events Human interaction
BPM in SAP NetWeaver 04

SAP NetWeaver
PEOPLE Multi channel access Portal Collaboration INFORMATION Knowledge Mgmt Business Intelligence Master Data Mgmt PROCESS Integration Broker Business Process Mgmt Ad-hoc Workflow
Business Process Management
UWL
SAP EP
Human Interaction Collaboration
SAP BI Cross-Component BPM
SAP XI m m
Inter-Application Process Automation
w
APPLICATION J2EE ABAP DB and OS Abstraction
ERP alert CRM
SRM
3rd party WMS
3rd party ERP
Intra-Application Process Automation
m = Message/ Document w = Workitem

= Adapter
BPM & Composite Applications

SAP NetWeaver
PEOPLE Multi channel access Portal Collaboration INFORMATION Knowledge Mgmt Business Intelligence Master Data Mgmt PROCESS Integration Broker Business Process Mgmt
Business Application Process Management Composite Framework Guided Procedures

Ad-hoc Workflow
xApp
UWL
SAP EP
Human Interaction Collaboration
SAP BI Cross-Component BPM
SAP XI m m
Inter-Application Process Automation
w
APPLICATION J2EE ABAP DB and OS Abstraction
ERP alert CRM
SRM
3rd party WMS
3rd party ERP
Intra-Application Process Automation
m = Message/ Document w = Workitem

= Adapter
Agenda
Orchestrating the Message Choreography

Service choreography between systems using stateful interactions
System System A A Process Process Definition Definition System System B B
Design & Configuration
Send Receive
Send
Receive Send
Execution
Cross-Component BPM Architecture Overview

Integration Builder
Integration Directory
Business Process (Configuration) Routing Rules Process / Message Store (References)
Integration Server
Business Process Engine
Process Execution Correlation Handling
Process Editor
3 Message Routing 1 Mapping Channel Det. 4
Business Process (Definition)

Abstract
Integration Engine Adapter Engine
Interfaces
Message
Integration Repository
Business Process Anatomy

Contains Graphical Process Builder Business Process object is incorporated in a namespace, identified by a name
Integration Directory
Contains a reference to its originating repository process Can only be deployed not created in the directory Does not contain a process definition
Routing and Mapping

Business process is a source or target and can be addressed like any Business System
BPM runtime extends Business Workflow runtime

Business Process Engine to execute processes adhering to standards Proven, scalable, robust technology Integral part of SAP XIs Integration Server
Business Process and Business Scenario

Scenario Component View
Product A Product A Product B Product Template
Send Receive
Process
Process
IF1 IF2
IF1 IF2
back to initiator
Send
IF...
IF...
Business Process is integrated in Business Scenario Choreography

One process per swimlane Navigation from swimlane to the process description
One action per interface of the process

An action is derivable from an interface Consistency checks between process and scenario
Cross-Component BPM / Business Workflow

Workflow Domain Cross-Component BPM Domain Workflow Domain
Application System 11 Application System

Workflow1
Application Org.Mgmt. User Mgmt.
* * * *
Integration Server
Process

Workflow3
* * *
Integration Engine
* * * *

Workflow2
* * * *
Business Process as Repository Object
Header
Birds view Edit area
Property area
Output area
Object area
Modeling Business Processes

Trigger processes
Via messages Schedules
Modeling elements
Receive messages and trigger process / step Send messages Transformation

Merge messages Split messages
Receiver determination Conditions Process flow elements such as: switch, assign, parallel, wait, Deadlines (including deadline handler) Exceptions (including exception handler)
ccBPM - Process Step-Types

MESSAGING RELEVANT RECEIVE SEND TRANSFORMATION (merge, split) RECEIVER DETERMINATION PROCESS FLOW CONTROL RELEVANT CONTAINER-OPERATION CONTROL (deadlines, exceptions, alerts) WHILE LOOP FORK BLOCK
Block
CK BLO LE MP EXA
EMPTY WAIT SWITCH
Correlations
Correlation Handling
Routing of messages (Business Documents) to process instances Dependencies rely on business data (e.g. Message ID, Order ID, Business Partner ID, Company Code) Correlations define these dependencies
SAP NetWeaver: Business Process Content

Integration Builder Integration Directory
Business Process (Configuration) Process Editor
SAP Business Process Content

XI scenario & process pattern templates (XI 3.0) SAP solution process content (delivered with SAP solutions)
SAP Solutions Industry Standards XI Process Patterns Workflow Templates Patterns
References
Industry standard content (as e.g. RosettaNet)
Business Process (Definition)
Monitoring and Administration

Technical monitoring
Entry from message view (Integration Engine) Entry from process view (Business Process Engine) Navigation between the monitoring tools
Integration in Monitoring Infrastructure

Process Engine Component Test (Runtime Workbench) Alerts SAP CCMS integration
Open Standards Support

Support for open standards
BPEL4WS 1.1 (BPM in SAP XI 3.0)
Active participation in standards, e.g.:

Advance BPEL4WS 1.1 together with IBM, BEA and Microsoft
Graphical Process Builder

Supports process design adhering to standards Import/ export of standard process descriptions
Cross-Component BPM adheres to evolving future standards via a pluggable import/export-interface concept .
Agenda
Business Process Patterns and Flavors

Collect flavors (to trigger the process end)
Payload triggered Time triggered Message triggered
Serialize flavors (how to perform send & receive)

One-message-triggered All-message-triggered
Multicast flavors (how to perform the send & receive)

In a sequence In parallel (ParForEach)
Collect Motivation
Systems sends an arbitrary number of messages to a process Collect all messages
End of collect cannot be determined at definition time, e,.g.
Collect Collect Collect
50 messages until a certain time has passed until a termination message arrives
Merge messages to a new message Send new message
Flavors
Flavor = Different possibilities to end collect
1. Payload triggered end of collecting

Specify overall number of messages in each message
2. Time triggered end of collecting

E.g. collect 24 hours
3. Message triggered end of collecting

Collect messages until termination message arrives
Flavor 1 Payload triggered end of collecting

Process Process
Container A type LIF1 AT type LIF1 * B type LIF2 C type int Correlations MyCorrelation ID type int Add 1 to C Append A to AT Process Interface LIF1 in LIF2 out Until C = A.number Transformation Merge AT into B Send message on B Loop
Receive messages on A
Is triggering Refers to two correlations
Instantiate Correlation
z Use M.Id to fill correlation-element Id (the first receive instantiates)
Receive message on A
Using Correlation
z Use M.Id to fill correlation-element Id
Add 1 to C Append message on A to AT Loop until C = A.number Merge messages on AT into new message on B Send message on B
Flavor 2 Time triggered end of collecting

Process Process
Container A type LIF1 AT type LIF1 * B type LIF2 C type int Correlations MyCorrelation ID type int Append A To AT Process Interface LIF1 in LIF2 out Until C <> C Block Loop Timeout Exception
z Use M.Id to fill correlation-element Id the first receive instantiates)
Receive A
Using Correlation
Append message on A to AT Loop until C <> C (infinite loop) Timeout occurs and fires an exception
Exception is cached and ends the block (normally)
Transformation Merge AT into B Send message on B
Merge messages on AT into new message on B Send message on B
Flavor 3 Message triggered end of collecting

Process Process
Container A type LIF1 AT type LIF1 * B type LIF2 C type int D type LIF3 Correlations MyCorrelation ID type int Append A To AT Until C <> C Fork
Loop
Receive A Receive D
Using Correlation
Append message on A to AT Loop until C <> C (infinite loop) Receive message on D (completion message)
Process Interface LIF1 in LIF2 out LIF3 in
1 of 2 branches
Ends the parallel section (1 of 2)
Transformation Merge AT into B Send message on B
Merge messages on AT into new message on B Send message on B
Serialization Motivation
Several systems send independently different messages to one target system
The messages must be submitted in a certain order to the target system
Receive all (different) messages Send messages out in a specific order verifying the acknowledgements
Flavors
Flavor = Different possibilities to perform the send and receive operations
1. One (special) message as triggering message

All others correlate to the first one
2. All messages as possible triggering messages

Each message correlates with each other
Flavor 1 One message as triggering message

Process Process
Container A type LIF1 B type LIF2 C type LIF3 Receive message on A Receive message on B Receive message on C
Is triggering Instantiate Correlation
Use
M.Id to fill correlationelement Id
Correlations MyCorrelation ID type int
Receive message on B
Using Correlation
Use
Process Interface LIF1 in/out LIF2 in/out LIF3 in/out Send message on A
Receive message on C
Using Correlation
Use
Send message on B Send message on C
Send message using acknowledgements on A, B, C
Flavor 2 All messages as triggering messages

Process Process
Container A type LIF1 B type LIF2 C type LIF3 Rec. A Rec. B Rec. C Fork
Use M.Id to fill correlation-element Id Use M.Id to fill correlation-element Id
Using Correlation
Correlations 3 of 3 branches MyCorrelation ID type int
Using Correlation
Process Interface LIF1 in/out LIF2 in/out LIF3 in/out Send message on A
Send message on B Send message on C
Using Correlation
Send message using acknowledgements on A, B, C

Multicast Motivation
Systems send a message out to an at definition time unknown number of receivers
Receivers are specified via Configuration in Integration Directory
Determine receivers for a given message (e.g. PurchaseOrder) Loop over table of receivers (in parallel or sequential) and send given message to receiver Wait for the business Response (e.g. PurchaseOrderConfirm)
Flavors
Flavor = Different possibilities to perform the send and receive operations
1. Send to all receivers in a sequence

Use ForEach (Block)
2. Send to all receivers in parallel

Use ParForEach (Block)
Flavor 1 Send to All Receivers in Sequence

Process Process
Container A type LIF1 B type LIF2 R type Rec. RT type Rec.* Block Correlations MyCorrelation ID type int Get Receive r R of Receiver-list RT Send message on A Receive message on B Receive message on A Receiver Determination
Receive message (e.g. PO) on A

Is triggering
Do Receiver Determination for A

All Receivers configured in the directory are in RT
Start ForEach Block Get Receiver R out of the list of receivers RT Send message on A (e.g. PO)
Process Interface LIF1 in/out LIF2 in
Use M.Id to fill correlation-element Id
Until R is empty
Receive message (e.g. POResponse) on B

Using Correlation
Until R is empty
Flavor 2 Send to all Receivers in Parallel

Process Process
Container A type LIF1 B type LIF2 R type Rec. RT type Rec.* Block Correlations MyCorrelation ID type int Get Receive r R of Receiver-list RT Send message on A Receive message on B Receive message on A Receiver Determination
Receive message (e.g. PO) on A

Is triggering
Do Receiver Determination for A

All Receivers configured in the directory are in RT
Start ParForEach Get Receiver R out of the list of receivers RT Send message on A (e.g. PO)
Process Interface LIF1 in/out LIF2 out
Receive message (e.g. POResponse) on B

Using Correlation
Until all responses from all branches are received

Agenda
Current Process Modeling Approaches

Value Potential Business Benefits
OEM
Importer
Dealer
Business Benefits
Value Potential $ 800 per vehicle** From 75 to 35 days** 5.1%*** 27.2%***
Business View
Business blueprinting Project planning High-level executive model
Up to 50% 2 months - 2 weeks* $ 250 per vehicle** Up to 14%**
Reduced delivery times Cost advantage via online sales Reduction in Supply Chain Costs Reduced inventories
Vehicle Specification/ Search Request via Internet
Cost advantage via online sales Reduced days supply inventory Customer SelfInformation Interactive configuration
Scenario Maps/ Solution Maps

Vehicle Locating and Allocation Reservation Planning Order Processing
Speed up buying
Collect information about customer requirements and preferences Improved market intelligence
Consistent Dealer Database Online information to customer reduces time of communication Pooled data on cars available Visibility of tracking status Speed up handing over of vehicle Increased customer satisfaction
Production Production
Order Tracking Order Tracking
7.5%*** 12.6%***
Shipment Tracking
Management/ Business Analyst
Faster reaction to market trends Increased customer satisfaction Increased planning security and quality
Transport Control Goods Receipt Processing
5.5%***
Static Implementation View

Implementation information Component view Process configuration model
Business Scenarios
Business Analyst/ Developer
Dynamic Implementation View

Executable processes State engine Process execution model
Business Processes
IT Specialist/ Developer
High Level Procedural Model

ARIS for SAP NetWeaver
Company View Business View Component View
ARIS Process Modeling

Company View Component View Process Content
SAP Solution Manager

Component View
Service Infrastructure
BPM Operational Services Solution Monitoring Service Level Reporting SAP Process Content
Process Configuration Model
SAP XI
Business Scenario
Process Integration
Model & execute automated processes across & within applications Process Integration Content
Process Execution Model
SAP NetWeaver
Business Process
SAP Applications
Workflow
SAP SAP xApp
Non-SAP
powered by SAP NetWeaver
Components Composites Engines Business objects
Evolution To A Unified Modeling Environment

Unified Modeling Environment Based on ONE Meta Model One Process Repository Different Views and Roles One Look & Feel Business View Value Chain Diagrams Component Diagrams Business Blueprinting Static Implementation View Process Configuration Model Dynamic Implementation View Process Execution Model
Static Implementation View
Unified Modeling
Meta-Model Business View
Dynamic Implementation View
Process Repository
Unified Business Process Management

Unified Modeling Environment Model driven Implementation as far as possible One common Repository SAP Execution Applications & Composites, SAP XI & Workflow Business Objects Monitoring Technical Process Monitoring Business Activity Monitoring
One Architecture for workflow and automated processes

Modeling Design
Process logic decoupled from applications

Process Configuration
Business Activity Monitoring
BPM
Flexible process design & configuration

Process Execution
Process Monitoring
Integrated in SAP NetWeaver Unified approach for A2A and B2B Integration
Business Activities Business Events Enterprise Services Business Objects
Open Standards Support
Business Process Management @ SAP
SAP NetWeaver
TM
offers a comprehensive BPM solution
Cross-Component BPM controls inter-application processes Business Workflow controls intra-application processes Ad-hoc workflow controls ad-hoc processes
Three pillars of BPM expedite process integration Three pillars of BPM share services Synergies of the SAP NetWeaver stack
TM
Questions?
Q&A
Copyright 2003 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express
permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other
software vendors.
Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of
Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,
OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix and Informix Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.
ORACLE is a registered trademark of ORACLE Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and
other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C, World Wide Web Consortium,
Massachusetts Institute of Technology.

JAVA is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT is a registered trademark of Sun Microsystems, Inc., used under license for technology invented
and implemented by Netscape.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, R/3, mySAP, mySAP.com, xApps, xApp and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.
Copyright 2003 SAP AG. Alle Rechte vorbehalten

Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher
Form auch immer, ohne die aus-drckliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen knnen ohne vorherige Ankn-digung gendert werden.
Die von SAP AG oder deren Vertriebsfirmen angebotenen Softwareprodukte knnen Softwarekomponenten auch
anderer Softwarehersteller enthalten.

Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint und SQL Server sind eingetragene Marken der
Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390,
OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix und Informix Dynamic ServerTM sind Marken der IBM Corporation in den USA und/oder anderen Lndern.
ORACLE ist eine eingetragene Marke der ORACLE Corporation. UNIX, X/Open, OSF/1 und Motif sind eingetragene Marken der Open Group. Citrix, das Citrix-Logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin und
andere hier erwhnte Namen von Citrix-Produkten sind Marken von Citrix Systems, Inc.
HTML, DHTML, XML, XHTML sind Marken oder eingetragene Marken des W3C, World Wide Web Consortium,
Massachusetts Institute of Technology.

JAVA ist eine eingetragene Marke der Sun Microsystems, Inc. JAVASCRIPT ist eine eingetragene Marke der Sun Microsystems, Inc., verwendet unter der Lizenz der von
Netscape entwickelten und implementierten Technologie.

MarketSet und Enterprise Buyer sind gemeinsame Marken von SAP AG und Commerce One. SAP, R/3, mySAP, mySAP.com, xApps, xApp und weitere im Text erwhnte SAP-Produkte und Dienstleistungen
sowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderen Lndern weltweit. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen.

SAP NetWeaver - Cross-Component Business Process Management With XI 3 (1) .0

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

SAP NetWeaver - Cross-Component Business Process Management With XI 3 (1) .0

Încărcat de

Drepturi de autor:

Formate disponibile

Cross-Component Business Process Management with SAP Exchange Infrastructure Jerome Delune

SAP Labs, LLC

As a result of this presentation, you will be able to:

SAP AG 2003, BPI202_US, George Yu / 2

SAP AG 2003, BPI202_US, George Yu / 3

Todays Grown Integration Landscapes

Business Partner Application

SAP AG 2003, BPI202_US, George Yu / 4

Integration with SAP Exchange Infrastructure (SAP XI)

Business Partner Application

3rd Party 3rd Party

SAP AG 2003, BPI202_US, George Yu / 5

Process Driven Integration Solution

SAP other Integration SAP XI Solution

Business Partner Application

3rd Party 3rd Party Programmed Workflow

BPMS: Business Process Management System WfMS: Workflow Management System

Integration with SAP Exchange Infrastructure (SAP XI)

SAP ccBPM SAP XI

other Integration Solution

Business Partner Application

3rd Party 3rd Party Programmed Workflow

SAP AG 2003, BPI202_US, George Yu / 7

Business Process Management (BPM)

SAP AG 2003, BPI202_US, George Yu / 8

BPM in SAP NetWeaver 04

Business Process Management

Human Interaction Collaboration

SAP BI Cross-Component BPM

ERP alert CRM

3rd party WMS

3rd party ERP

Intra-Application Process Automation

m = Message/ Document w = Workitem

SAP Business Workflow

BPM & Composite Applications

Business Application Process Management Composite Framework Guided Procedures

Human Interaction Collaboration

SAP BI Cross-Component BPM

ERP alert CRM

3rd party WMS

3rd party ERP

Intra-Application Process Automation

m = Message/ Document w = Workitem

SAP Business Workflow

SAP AG 2003, BPI202_US, George Yu / 11

Orchestrating the Message Choreography

Design & Configuration

SAP AG 2003, BPI202_US, George Yu / 12

Cross-Component BPM Architecture Overview

3 Message Routing 1 Mapping Channel Det. 4

Business Process (Definition)

Integration Engine Adapter Engine

SAP AG 2003, BPI202_US, George Yu / 13

Business Process Anatomy

Routing and Mapping

BPM runtime extends Business Workflow runtime

SAP AG 2003, BPI202_US, George Yu / 14

Business Process and Business Scenario

Business Process is integrated in Business Scenario Choreography

One action per interface of the process

SAP AG 2003, BPI202_US, George Yu / 15