sap netweaver - cross-component business process management with xi 3[1].0

7/29/2019 SAP NetWeaver - Cross-Component Business Process Management With XI 3[1].0

1/49

Cross-Component BusinessProcess Management w ithSAP Exchange Infrastructure

Jerome DeluneSAP Labs, LLC


2/49

SAP AG 2003, BPI202_US, George Yu /2

Learning Objectives

As a result of this presentat ion, you w illbe able to: Understand three pillars of SAP Business Process

Management

Understand the cross-component BPM within SAP XI


3/49


Agenda

Driving process integration: BPM@SAP

Cross-component BPM in XI 3.0: functions and features

Process patterns

Outlook and summary


4/49 SAP AG 2003, BPI202_US, George Yu /4

Todays Grow n Integrat ion Landscapes

Business Partners

hard

coded

hard

coded

EAI

Tool

EAI

Tool

3rd

Party

3rd

Party3rd

Party

B2B

Tool

B2 B

Tool

SAP

SAP

mainframeapplication

SAP

SAP

SAP

Marketplace

Business PartnerApplication

3rdparty

SAP

other IntegrationSolution

B2B Tool

Adapter



Integrat ion w ith SAP Exchange I nfrastruct ure (SAP XI )

Business Partners

3rd

Party

3rd

Party3rd

Party

SAP

SAP


SAP

Marketplace


3rdparty

SAP

RosettaNetMiddleware

SAP

SAP


SAP Net Weaver

SAP XI


SAP XI

SAP XI



Process Driven Integrat ion Solut ion

Business Partners

3rd

Party

3rd

Party

SAP

SAP


SAP

Marketplace


3rdparty

SAP


Message

Oriented

Middleware

SAP

SAP

SAP XIother IntegrationSolution

3rd

Party

3rd party WfMS

3rd party BPMS

SAP Business

Workflow

Programmed

WorkflowBPMS: Business Process Management System

WfMS: Workflow Management System



Integrat ion w ith SAP Exchange I nfrastruct ure (SAP XI )

Business Partners

3rd

Party

3rd

Party3rd

Party

SAP

SAP


SAP

Marketplace


3rdparty

SAP


SAP

SAP


SAP Net Weaver

SAP XI


ccBPM

ccBPM

SAP Business

Workflow

Programmed

Workflow



Business Process Management (BPM)

Ad-hoc Workflow Team-driven processes

Spontaneous events

Collaboration

Cross-Component BPM

Design, execute and monitor

automated processes across

applications and systems

Stateful interaction model

Cross application execution

Business Workflow

Design, execute and monitorprocesses within applications

Apply standard business rules

Business events

Human interaction

SAP NetWeaver BPM A comprehensive BPM solution

Ad-hoc Workflow controls team-

driven processes

Cross-Component BPM controlsinter-application processes

Business Workflow controls intra-

application processes



SAP NetWeaver

PEOPLE

Multi channel access

Portal

Collaboration

INFORMATION

PROCESS

Integration Broker

Business Process Mgmt

APPLICATION

Knowledge Mgmt

Business Intelligence

Master Data Mgmt

J2EE

ABAP

DB and OS Abstraction

Business Process Management

BPM in SAP NetWeaver 04

UWL

SAP BI

ERP CRM SRM3rd party

WMS

3rd party

ERP

SAP EPmm

Ad-hoc Workflow

Cross-Component BPM

SAP XI

SAP Business Workflow

m

wm

m = Message/ Document

w = Workitem

Human Interaction

Collaboration

Inter-Application

Process Automation

m

alertIntra-Application

Process Automation

= Adapter



SAP NetWeaver

PEOPLE

Multi channel access

Portal

Collaboration

INFORMATION

PROCESS

Integration Broker

Business Process Mgmt

APPLICATION

Knowledge Mgmt

Business Intelligence

Master Data Mgmt

J2EE

ABAP

DB and OS Abstraction

Business Process Management

BPM & Composite Applicat ions

UWL

SAP BI

ERP CRM SRM3rd party

WMS

3rd party

ERP

SAP EPmm

= Adapter

Ad-hoc Workflow

Cross-Component BPM

SAP XI

SAP Business Workflow

m

wm

m = Message/ Document

w = Workitem

Intra-Application

Process Automation

Human Interaction

Collaboration

Inter-Application

Process Automation

m

alert

Composite Application Framew ork

Guided Procedures xApp


11/49


Agenda



Process patterns

Outlook and summary


12/49


Orchestrat ing the Message Choreography

Service choreography between systems

using stateful interactions

SendReceive

Send

Send

Receive

Send

Process DefinitionProcess DefinitionSystem ASystem A System BSystem B

Design&

Configuration

Execution

C C t BPM A hit t O i


13/49


Cross-Component BPM Architecture Overview

Integration Server

Integration Engine

Process / Message Store

Integration

Repository

Abstract

Interfaces

Integration

Directory

Business Process

(Configuration)

Routing Rules

Business Process Engine

Adapter Engine

Routing

Correlation

Handling

Integration Builder

Process

Editor

Business Process(Definition)

(References)

Messa

ge

M

essage

23

1

4MappingChannel

Det.

Process

Execution

B i P A t


14/49


Business Process Anatomy

Integration Repository

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

B i P d B i S i


15/49


Business Process and Business Scenario

Product

A

IF1

IF...

Product

A

Scenario Component ViewProduct

B

Product

Template

IF2

Process Send

back to initiator

Process

Receive

Send

IF1

IF2

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


16/49


Cross-Component BPM / Business Workflow

Workflow Domain Workflow DomainCross-Component BPM Domain

Integration Server

Integration

Engine

Process

*

*

*

*

Application System 1Application System 1

Org.Mgmt.

Workflow1

*

*

*

*

Application

User Mgmt. Application System 3Application System 3

Org.Mgmt.

Workflow3

*

*

*

*

Application

User Mgmt.

Application System 2Application System 2

Org.Mgmt.

Workflow2

*

*

*

*

Application

User Mgmt.

Business Process as Repository Object


17/49





18/49



Output area Object area

Header

Birdsview

Propertyarea

Edit area



19/49



Modeling Business Processes


20/49


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


21/49


ccBPM Process Step Types

MESSAGING RELEVANTRECEIVE Block

SEND

TRANSFORMATION (merge, split) BLOCKEXAMPL

ERECEIVER DETERMINATION

PROCESS FLOW CONT ROL RELEVANTCONTAINER-OPERATION

CONTROL (deadlines, exceptions, alerts)

WHILE LOOP EMPTY

WAITFORK

BLOCK SWITCH

Correlations


22/49


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


23/49


SAP NetWeaver: Business Process Content

Integration

Directory

Integration

RepositoryProcessEditor

Integration Builder

Business Process

(Configuration)

Business Process

(Definition)

References

SAP Business Process Content XI scenario & process pattern

templates (XI 3.0)

SAP solution process content

(delivered with SAP solutions) Industry standard content

(as e.g. RosettaNet)

IndustryStandards

SAP

Solutions

Patterns

XI Process

Patterns

Workflow

Templates

Monitoring and Administrat ion


24/49


o to g a d d st at o

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


25/49


p pp

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 toevolving future standards via apluggable import/export-interface

concept .

Agenda


26/49


g



Process patterns

Outlook and summary

Business Process Patterns and Flavors


27/49


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)

Collec t Motivation


28/49


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 50 messages

Collect until a certain time has passed

Collect until a termination message arrives

Merge messages to a new message

Send new message

Flavors


29/49


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 collect ing


30/49


ProcessProcess

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)

Using Correlationz 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 newmessage on B

Send message on B

Receive

message on A

Add 1 to

C

Append A

to AT

Until

C = A.number

Container

A type LIF1AT type LIF1 *B type LIF2C type int

Correlations

MyCorrelationID type int

Transformation

Merge AT into B

Send

message on B

Process

Interface

LIF1 inLIF2 out

Flavor 2 Time triggered end of collec ting


31/49


ProcessProcess

BlockLoop


Is triggering

Refers to two correlations


z Use M.Id to fill correlation-elementId the first receive instantiates)

Using Correlation

z Use M.Id to fill correlation-elementId


Loop until C C (infinite loop)Timeout occurs and fires anexception

Exception is cached and ends the

block (normally)


Send message on B

Receive A

Append A

To AT

Until

C C

Container

A type LIF1AT type LIF1 *B type LIF2C type int

Correlations


Transformation

Merge AT into B

Send

message on B

Process

Interface

LIF1 inLIF2 out

Timeout Exception

Flavor 3 Message triggered end of collec ting


32/49


ProcessProcess

Fork

Loop


Is triggering

Refers to two correlations



Using Correlation



Loop until C C (infinite loop)

Receive message on D (completionmessage)

Ends the parallel section (1 of 2)


Send message on B

Receive A

Append A

To AT

UntilC C

Container

A type LIF1AT type LIF1 *B type LIF2C type intD type LIF3

Correlations


Transformation

Merge AT into B

Send

message on B

Process

Interface

LIF1 inLIF2 out

LIF3 in

1 of 2 branches

Receive D

Serializat ion Motivat ion


33/49


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


34/49


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 t riggering message


35/49


ProcessProcess Receive message on A

Is triggering Instantiate Correlation

Use M.Id to fill correlation-element Id

Receive message on B Using Correlation


Receive message on C

Using Correlation


Send message usingacknowledgements on A, B, C

Receive

message on A

Container

A type LIF1B type LIF2C type LIF3

Correlations


Send

message on C

Process

Interface

LIF1 in/outLIF2 in/outLIF3 in/out

Receive

message on B

Receive

message on C

Send

message on B

Send

message on A

Flavor 2 All messages as triggering messages


36/49


ProcessProcess

Fork

Receive message on A

Is triggering



Using Correlation



Is triggering



Using Correlation Use M.Id to fill correlation-element Id


Is triggering



Using Correlation


Send message usingacknowledgements on A, B, C

Rec. A

Container

A type LIF1B type LIF2C type LIF3

Correlations


Process

Interface

LIF1 in/outLIF2 in/out

LIF3 in/out

3 of 3 branches

Rec. B Rec. C

Send

message on C

Send

message on B

Send

message on A

Multicast Motivation


37/49


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


38/49


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


39/49


ProcessProcess

Block

Receive message (e.g. PO) on A

Is triggering

Do Receiver Determination for A

All Receivers configured in thedirectory are in RT

Start ForEach Block

Get Receiver R out of the list ofreceivers RT

Send message on A (e.g. PO)


Use M.Id to fill correlation-elementId

Receive message (e.g. PO-Response) on B

Using Correlation

Use M.Id to fill correlation-element

Id

Until R is empty

Receive

message on A

Until R is empty

Container

A type LIF1B type LIF2R type Rec.RT type Rec.*

Correlations


Process

Interface

LIF1 in/outLIF2 in

Receive

message on B

Receiver

Determination

Sendmessage on A

Get Receive r R of

Receiver-list RT

Flavor 2 Send to all Receivers in Parallel


40/49


ProcessProcess

Block

Receive message (e.g. PO) on A

Is triggering

Do Receiver Determination for A

All Receivers configured in thedirectory are in RT

Start ParForEach

Get Receiver R out of the list ofreceivers RT

Send message on A (e.g. PO) Instantiate Correlation


Receive message (e.g. PO-Response) on B

Using Correlation


Until all responses from allbranches are received

Receive

message on AContainer

A type LIF1B type LIF2R type Rec.RT type Rec.*

Correlations


Process

Interface

LIF1 in/outLIF2 out

Receive

message on B

Receiver

Determination

Sendmessage on A

Get Receive r R of

Receiver-list RT

Agenda


41/49




Process patterns

Outlook and summary

Current Process Modeling Approaches


42/49


Business View

Business blueprinting

Project planning

High-level executive model

Cost advantagevia online sales

Reduced dayssupply inventory

Customer Self-Information

Interactiveconfiguration

Speed up buying

Consistent DealerDatabase

Online informa-tion to customerreduces time ofcommunication

Pooled data oncars available

Visibility oftracking status

Speed uphanding overof vehicle

Increasedcustomer

satisfaction

OEM Dealer Importer

ProductionProduction

ReservationPlanning

Goods Receipt

Processing

Vehicle Specification/

Search Request

via Internet

Shipment

Tracking

Transport

Control

Vehicle

Locating and

Allocation

Order

Processing

Order TrackingOrder Tracking

Value

Potential

Value

Potential

$ 800 pervehicle**

From 75 to35 days**

5.1%***

27.2%***

7.5%***

12.6%***

5.5%***

Up to 50%2 months- 2 weeks*

$ 250 pervehicle**

Up to14%**

Business Benefits Business Benefits

Reduced deliverytimes

Cost advantagevia online sales

Reduction inSupply ChainCosts

Reducedinventories

Collectinformation aboutcustomerrequirements andpreferences

Improved marketintelligence

Faster reaction tomarket trends

Increasedcustomersatisfaction

Increasedplanning security

and quality

Management/

Business Analyst

Scenario Maps/ Solution Maps

IT Specialist/

Developer

Dynamic Implementat ion View

Executable processes

State engine

Process execution model

Business Processes

Business Analyst/

Developer

Stat ic Implementat ion View

Implementation information

Component view

Process configuration model

Business Sce narios

High Level Procedural Model


43/49


SAP XI

Company View

ARISARIS for SAP NetWeaverfor SAP NetWeaver

SAP Solution Manager

SAPNetWeaverProcessExecution

Model

Business View

Process

Configuration

Model

SAPSAP

ARIS

Process Modeling

Company View

Component View

Process Content

SAP Applica t ions Components

Composites

Engines Business objects

Non-SAP

Business

Scenario

Process Integrat ion

Model & execute automated

processes across & within

applications

Process Integration Content

xApp

Service Infrastruct ure

BPM Operational Services

Solution Monitoring

Service Level Reporting

SAP Process Content

powered by SAP NetWeaver

Workflow

Business

Process

Component

View

Component

View

Evolution To A Unified Modeling Environment


44/49


Unified ModelingEnvironment

Based on ONE Meta Model

One Process Repository

Different Views and RolesOne Look & Feel

Business ViewValue Chain DiagramsComponent DiagramsBusiness Blueprinting

Static Implementation ViewProcess ConfigurationModel

Dynamic ImplementationViewProcess Execution Model

Unified ModelingBusiness

View

Static

Implementation

View

Dynamic

ImplementationView

Meta-Model

Process

Reposito

ry

Unified Business Process Management


45/49


One Architecture forworkflow and

automated processes

Process logicdecoupled fromapplications

Flexible processdesign &configuration

Integrated inSAP NetWeaver

Unified approach forA2A and B2BIntegration

Open StandardsSupport

Unified ModelingEnvironment

Model drivenImplementation asfar as possible

One commonRepository

SAP ExecutionApplications& Composites,

SAP XI & WorkflowBusiness Objects

MonitoringTechnical ProcessMonitoring

Business Activity

Monitoring

ProcessConfiguration

Modeling

Design

Process

Monitoring

Process

Execution

BusinessActivity Monitoring

BPM

Business Events

Business Objects

Enterprise Services

Business Activities


46/49

Questions?


48/49


No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission 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 othersoftware vendors.

Microsoft, WINDOWS, NT, EXCEL, Word, PowerPointand SQL Serverare registered trademarks ofMicrosoft 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, Informixand InformixDynamic 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 Motifare registered trademarks of the Open Group.

Citrix, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWinand

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.

J AVAis a registered trademark of Sun Microsystems, Inc.

J AVASCRIPT 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 astheir respective logos are trademarks or registered trademarks of SAP AG in Germany and in several othercountries all over the world. All other product and service names mentioned are the trademarks of their respectivecompanies.

Copyright 2003 SAP AG. Alle Rechte vorbehalten


49/49


Weitergabe und Vervielfltigung dieser Publikationoder von Teilen daraus sind, zu welchemZweckund in welcherForm auch immer, ohne die aus-drckliche schriftliche GenehmigungdurchSAP AG nichtgestattet. In dieser

Publikation enthaltene Informationen knnenohne vorherige Ankn-digung gendertwerden. Die von SAP AG oder deren Vertriebsfirmen angebotenenSoftwareprodukte knnenSoftwarekomponenten auch

anderer Softwarehersteller enthalten.

Microsoft, WINDOWS, NT, EXCEL, Word, PowerPointund SQL Serversindeingetragene Marken derMicrosoft 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, Informixund InformixDynamic ServerTM sindMarken der IBM Corporation in den USA und/oder anderen Lndern.

ORACLE isteineeingetragene Marke der ORACLE Corporation.

UNIX, X/Open, OSF/1und Motifsindeingetragene Marken der Open Group.

Citrix, das Citrix-Logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWinundanderehier erwhnte Namen von Citrix-Produkten sind Marken von Citrix Systems, Inc.

HTML, DHTML, XML, XHTML sindMarkenoder eingetragene Marken des W3C, World Wide Web Consortium,Massachusetts Institute of Technology.

J AVA ist eine eingetragene Marke der Sun Microsystems, Inc.

J AVASCRIPT isteine eingetragene Markeder Sun Microsystems, Inc., verwendetunterder Lizenz der vonNetscape entwickelten und implementierten Technologie.

MarketSet und Enterprise Buyer sindgemeinsame Marken von SAP AG und Commerce One.

SAP, R/3, mySAP, mySAP.com, xApps, xApp und weitere imText erwhnte SAP-Produkte und Dienstleistungensowie die entsprechenden Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und anderenLndern weltweit. Alle anderen Namen von Produkten und Dienstleistungen sind Marken der jeweiligen Firmen.