bam - settiung up a milestone monitoring process

7/30/2019 BAM - Settiung Up a Milestone Monitoring Process

http://slidepdf.com/reader/full/bam-settiung-up-a-milestone-monitoring-process 1/18

1

Business Activity Monitoring –

Setting up a Milestone

Monitoring Process

SAP NetWeaver Product Management inBusiness Process Management

sample

for a pi

cture

in the t

itle slid

e



2

Monitoring Process Definition

Standards

Monitoring Process Definit ion Standards

Business Process Execution Language for Web Services - BPEL4WS 1.1(specification/already adopted)

Web Services Business Process Execution Language - WS-BPEL 2.0(specification/preview/implementation)

SAP is

A leader in BPEL standard adoption

A driver of the BPEL standard

SAP was one of the companies who proposed the OASIS WS-BPEL TechnicalCommittee

SAP works together with IBM on two significant BPEL extensions

Monitoring Event Standards

No known Monitoring Event standard yet

Can easily be introduced (Monitoring Events are SAP NetWeaver ProcessIntegration messages)

©SAP 2008 /



3

Process Milestone Monitoring

©SAP 2008 /

Process Milestone Monitoring Event-based monitoring of key process milestones Subscription and handling of business process events BPM modeling (BPEL) Building consistent business process instances across different application system Providing rich business context information Basis for process efficiency analysis



4

Setting up a Milestone Monitoring Process

Use Case: Sales Order Monitoring

GoodsReceipt

Sales Order Purchase

Order

SAP NetWeaver

Instances of process milestones

Event Resolut ion Dashboard

Alert

SAP CRM SAP ERP SAP ERP

BI Process Efficiency Analysis

Alert:

Consistency Check: If the goods receipt quantity does not match the quantity

ordered then an alert should be raised on the dashboard.

©SAP 2008 /

With this use case we want to demonstrate the main steps of defining a monitoring processin SAP NetWeaver Process Integration.



5

Design and Configuration

Alert

Server

CRM

Asy nc h. Ab str act MI

CRM_Sales_Order_Event

(MT: CRM_Sales_Order

DT: CRM_Sales_Order )

Asy nc h. Ab str act MI

ERP_Purchase_Order_

Event

(MT:

ERP_Purchase_Order

DT:

ERP_Purchase_Order)

Synch. Abstract MI

ERP_Purchase_Order_

Item_Event

(MT:

ERP_Purchase_Order

DT:

ERP_Purchase_Order)

Asy nch . Abs tract MI

ERP_Goods_Receipt_

Event

(MT:

ERP_Goods_Reciept

DT:

ERP_Goods_Receipt)

Condition

StepTransformation

Step (Message

Mapping:

Aler tCon text )

Asy nch . Abs tract M I

BAM_Alert_Event

(MT: BAM_Alert

DT: BAM_Alert)

Start

Asy nch . Out bou nd MI

CRM_Sales_Order_Message

(MT: CRM_Sales_Order

DT: CRM_Sales_Order)


ERP_Purchase_Order_

Message

(MT:

ERP_Purchase_Order DT:

ERP_Purchase_Order)

= Message and Interface Mapping

Synch. Inbound MI

ERP_Purchase_Order_

Item_Message

(MT:

ERP_Purchase_Order DT:

ERP_Purchase_Order)


ERP_Goods_Receipt_

Message

(MT:

ERP_Goods_RecieptDT:

ERP_Goods_Receipt)

Asy nch . Inboun d MI

BAM_Alert_Message

(MT: BAM_Alert

DT: BAM_Alert)

PI Process

Engine

PI IntegrationEngine

Sales Order Outbound Proxy Purchase Order

Outbound ProxyPurchase Order Item

Inbound Proxy

Goods Receipt

Outbound Proxy Aler t Inbou nd Pr oxy

ERP

= Message = Message / Process Flow

Legend: MI = Message Interface

MT = Message Type

DT = Data Type©SAP 2008 /

Need to define the following objects in cross-component Business Process Management(ccBPM) powered by SAP NetWeaver PI:

Data type: CRM sales order Purchase order Goods receipt BAM Alert

Message type:

CRM sales order Purchase order Goods receipt BAM Alert

Message Interface:

CRM sales order message (outbound asyn.) CRM sales order event (abstract asyn.) Purchase Order Message (outbound asyn) Purchase Order Event (abstract asyn) Purchase Order Item Message (inbound syn) Purchase Order Item Event (abstract syn) Goods Receipt Message (outbound asyn) Goods Receipt Event (abstract asyn) BAM Alert Message (inbound asyn)

BAM Alert Event (abstract asyn)



6

Defining Data Type

©SAP 2008 /



7

Defining Message Interface

©SAP 2008 /



8

Defining Mapping Objects

©SAP 2008 /



9

Defining Milestone Monitoring Process

©SAP 2008 /

The Business Activity Monitoring (BAM) sales order process should be defined as aMonitoring Process.

This process consists of:

Three steps as follows:– receiving sales order– receiving purchase order– sending purchase order item

One step group:– receiving goods receipt– transformation (alert context mapping)– BAM alerting

Condition statement: if PO quantity does not match goods receipt quantity, then raise an alert.



10

Configuration: Generating a Proxy

©SAP 2008 /

In order to generate a proxy:

Switch to the configuration part of Enterprise Service Repository

Assigning system to receiver determination, interface determination, and generatingproxies.



11

Technical Details - Monitoring Process Definition

New Modeling Concepts for BAM

Extended conditions and expressions

Configurable Parameters

Language dependent texts

Step Groups

User Decisions

Alert Categor ies

Driving WS BPEL 2.0 standard

Extends BAM and ccBPM

BPEL4WS 1.1 standard adoption

KPI lookup via extended mappings

©SAP 2008 /

Here is an overview of the new features that are delivered with SAP NetWeaver PI 7.1:

Basic extensions

Process types allow fine granular check services depending on the process type (integration, monitoring, etc.)

Language dependent text for all modeling elements allows better documentation for all SAP delivered processes

Configurable parameters allow new concepts such as parameterization in general (see conditions) and user decision

Step Groups for speeding up process modeling

User Interaction

User Decisions

Alert Categories

Conditions and expressions

Extended capabilities

Advanced User Interface

Standards

Monitoring process definition standards BPEL4WS 1.1 (specification/already adopted) WS BPEL 2.0 (specification/preview/implementation)

SAP is A leader in BPEL standard adoption A driver of the BPEL standard

– SAP was one of the companies who proposed of the OASIS WS-BPEL Technical Committee– SAP works together with IBM on two significant BPEL Extensions

Monitoring Event Standards No known Monitoring Event standard yet Can easily be introduced (Monitoring Events are PI messages)



12

Monitoring Process Definition

Typical Pattern (Receive, Project and throw Alert)

Typical Pattern of monitoring process:

Receiving

Project (Transformation)

Alerting

This pattern can be defined as step group to speed up BAM process definition.

Label (Receive)

MessageStarting

Mode

Act ivat e Correlati onsCorrelation-Variables…

Label (Transformation)

Link t o Interface-MappingInbound-Variables…Outbound-Variables…

Label (Switch)

Branch1Branch-nameCondition

Label (Control)

Mode Aler t

Aler t-Categ ory Aler t-Variables…

Step Group

Design

©SAP 2008 /

This pattern is not delivered to customers, however customers can easily define this stepgroup for monitoring process.

This typical ‘BAM’step group consists of three steps:

Receiving

Project (Transformation)

Alerting with a condition statement



13

User Decisions

Generic user decision during the execution of an Integration Process

Deadline occurs, or an alert is thrown, option needed to directly interact

Provide decision gateway and outcomes of the user decision, and use the IntegrationDirectory for responsibility determination

Uses container elements type “agent”from the configurable parameters

Language dependent texts for end-user display enriched with variables

©SAP 2008 /

Use the new step type “User Decision”to enable a user to decide which branch of aprocess flow is to be executed.

For each decision option a branch is entered.

At runtime the user will be notified by a dialog work item in the workflow inbox.

To define the text, which will be displayed for the user, it is possible to use local variables.At runtime these variables will be replaced with the current data from the process.

Within “User Decision”you will use the introduced “Configurable Parameters”todetermine which user is to be notified at runtime. You therefore use the configurable

parameter type “Agent”.



14

Extended Conditions and Expressions

Define conditions to control processing depending on the result of the condition

The condition editor supports the definition of the condition

Insert comments to ensure that conditions remain clear and easy to understand

Drag and drop and

context

sensitive help

Condition Editor provides all back-end

functionality and is reusable by all

ESR components

©SAP 2008 /

With the help of conditions customers are able to control the flow of a process.

Depending on the result of the defined condition, the process will be executed in thedefined way.

Use the step type “Switch”and use “Condition”in the properties.

In the integrated Condition Editor customers can formulate logical conditions.



15

Data EnrichmentModeling Using Mapping Lookup Mechanism

Lookups should be defined within interface mapping

Remote Function Call (RFC) channel can be defined concretely in the standardtransformation step

Use the standard transformationstep for lookups

Submit channel to be usedwith the mapping

Define container elements on

adapter metadata that can befilled with concrete channels during

configuration

©SAP 2008 /

KPI lookup could be used within the BAM scenario.

Customers can, for example, define the condition statement so that if delivery is delayed formore than five hours and if the customer is an A-customer then an alert is raised.

In this example customers can use the KPI lookup mechanism to get the data from BI (Keyfigure customer classification = A).

Detailed lookup mechanism (J ava coding) should be defined within interface mapping.When defining the process, the concrete Remote Function Call (RFC) channel must bespecified.



16

Alert Categories

Creating alert categories directly in the Integration Process

Designing Integration Process and alerts at the same time

Define alerts in IntegrationBuilder design

Use alerts in control steps

Having full access to thecontainer-elementsof the alert category

©SAP 2008 /

Now an alert category can be created within the Integration Builder instead of withtransaction ALERTCATDEF, however alert recipients have to be defined with transactionALERTCATDEF. In the control step alerts can be defined with full access to the containerelements of the alert category.



17

Summary

Process Monitoring definition co-operates standards.

Process Monitoring is a special category, which can bedefined within ccBPM. It subscribes and handles businessevents and correlates them into a consistent business processinstance.

Process Monitoring provides rich business related context.

Process Monitoring instances are the data basis for ProcessEfficiency Analysis.

Typical BAM pattern (Receive, Project and Throw alert) canbe modeled as a step group for speeding up process modeling.

©SAP 2008 /

Process Monitoring is a speciall category which can be defined within ccBPM. It mainlyconsists of ‚receive‘ process steps. From technical perspective, there is no differencebetween monitoring process and integration process.

So in this case, if customers are familiar with ccBPM, then they will be able to set up amonitoring process with the aspect of BAM.



Copyright 2008 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 changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

SAP , R/3, mySAP , mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdgeand other SAP products and services mentioned herein as well as theirrespective 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 andassociated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This documentcontains only intended strategies, developments, and functionalities of the SAP®product and is not intended to be binding upon SAP to any particular course of business, product strategy,and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy orcompleteness of the information, text, graphics, links, orother items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitationshall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information thatyou may access through the use of hot links contained in thesematerials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfältigung dieser P ublikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durchSAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.

SAP , R/3, mySAP, mySAP .com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Servicessowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderenVereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmtenGeschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiertnicht dieRichtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, wederausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zwecksowie für die Gewährleistung der Nichtverletzung geltenden Rechts.

SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendungdieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.

Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinkszugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen überInternetseiten Dritter ab.

Alle Rechte vorbehalten.

bam - settiung up a milestone monitoring process

Documents