globalizing local business events

7/27/2019 Globalizing Local Business Events

http://slidepdf.com/reader/full/globalizing-local-business-events 1/53

SAP NetWeaver Process Integration 7.1 1

SAP NetWeaver Process Integration 7.1

Business Activity Monitoring: Globalizing Local BusinessEvents–Event to Resolution

SAP NetWeaver Regional Implementation Group

SAP Netweaver Process Integration

December 2007




Benefits

This document shows you a development example for Business ActivityMonitoring




1. Introduction

2. System Overview

3. Development Step by Step

Agenda




1. Introduction

2. System Overview


Agenda




Main Customer Challenges

I am not aware of significant business needs that are relevant for me before it is toolate.

Events are not actionable today – Is this just another wave of notifications that we

have to deal with?

Events are not tangible for business users – What kinds o f business events are

managed in my landscape today?

Where and how do I set up new scenarios?

Missing “ chattiness” of today’s applications and systems – Events remain unnoticed

or without suf ficient context.

The unknown – Do event-driven archi tectures affect my service-oriented arch itecture(SOA) strategy? What kind of event management capabilit ies do I really need?




Evolution of Business Process and Event

Management

1995

2002

2004

TODAY

SAP BusinessWorkflow/

Events

SAP PIUWL/ ccBPM

Business Process Management

Business Task ManagementBusiness Activity Monitoring Infrastructure

…SAP Reference

Model

SAP NetWeaver




Leveraging Enterprise Services and Business Events

Business Activity Monitoring (BAM)

Business ActivityMonitoring

A f ramework (technical infrastruc ture)

that enables users to

Act on signif icant events and take

the correct action in the right work

context

Monitor , measure, and improve the

efficiency of business processes

mySAP Business Suite

Event InfrastructureEvent Infrastructure

Alert

Milestone Monitoring PI

Event Resolution Cockpit

Non-SAP

Process

Efficiency

BI

Servi ce Bu si ness Obj ect Event




1. Introduction

2. System Overview


Agenda




Status

Business Activity Monitoring (BAM)

mySAP Non-SAP

(2) Milestone Monitoring (PI)

Deliver Goods

CreateOpportunity

Place Order Create

Lead Aler t

Event

Manager

Event

F i l t er

Event

Handler

(3) Process Efficiency (BI)

Process Data Marts*

Process-centric BICockpits*

(1) Event Resolution (GP)

Alerting & resolution context

Availab le as of SAP_Basis 620

Availab le as of PI 7.1 (PI 3.0)

Prototype

Process Analysis

as StandardBusiness Content Availab le as of BI

7.0

BAM combines existing and new functionality into a consistent framework for SAP,ISV’s and customers




Use Case Sales Order Monitoring

GoodsReceipt

Sales Order Purchase

Order

SAP NetWeaver

Instances of process milestones

Event Resolution Dashboard

Aler t

SAP CRM SAP ERP SAP ERP

Alert:

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

quantity then an alert should be raised to the Dashboard.

BI Process Efficiency Analysis




System Component View

PI BI

Alert Server Visual Composer

UWL

Guided Procedures

SAP NetWeaver 7.0SAP NetWeaver Portal

ERPCRMIn this example

PI and alert server

are on the same box




System Connectivity View




Runtime – Event Resolution: UWL Entry Point




Runtime – Event Resolution: Dashboard




Runtime – Event Resolution: Problem Analysis

& Resolution




Runtime – Process Efficiency Dashboard




1. Introduction

2. System Overview


1. Step 1: PI

2. Step 2: CRM

3. Step 3: ERP

4. Step 4: Alert Server

5. Step 5: Guided Procedures

6. Step 6: BI7. Step 7: Visual Composer

Agenda




1. Introduction

2. System Overview


1. Step 1: PI

2. Step 2: CRM

3. Step 3: ERP




Agenda




STEP 1: PI Design & Configuration

Asyn ch. Abs tract MICRM_Sales_Order_Event

(MT: CRM_Sales_Order

DT: CRM_Sales_Order)

MI = Message Interface

MT = Message Type

DT = Data Type

Asyn ch. Abs tract MI

ERP_Purchase_Order_

Event(MT:

ERP_Purchase_Order DT:

ERP_Purchase_Order)

Synch. Abstract MIERP_Purchase_Order_

Item_Event

(MT:ERP_Purchase_Order

DT:ERP_Purchase_Order)

Asyn ch. Abs tract MIERP_Goods_Receipt_

Event

(MT:ERP_Goods_Reciept

DT:ERP_Goods_Receipt)

Condition

StepTransformation

Step (MessageMapping:

Aler tCon text )

Asyn ch. Abs tract MI

BAM_Alert_Event(MT: BAM_Alert

DT: BAM_Alert)

Start

End

Asyn ch. Outboun d MI

CRM_Sales_Order_Message

(MT: CRM_Sales_Order DT: CRM_Sales_Order)

Asyn ch. Outboun d MIERP_Purchase_Order_

Message(MT:

ERP_Purchase_Order DT:

ERP_Purchase_Order)

= Message and Interface Mapping

Synch. Inbound MIERP_Purchase_Order_

Item_Message

(MT:ERP_Purchase_Order

DT:ERP_Purchase_Order)

Asyn ch. Outboun d MI

ERP_Goods_Receipt_ Message(MT:

ERP_Goods_RecieptDT:

ERP_Goods_Receipt)

Asyn ch. Inbo und MI

BAM_Alert_Message(MT: BAM_Alert

DT: BAM_Alert)

PI ProcessEngine

PI Integration

Engine

Sales Order Outbound Proxy Purchase Order

Outbound ProxyPurchase Order ItemInbound Proxy

Goods ReceiptOutbound Proxy

Aler t In boun d Prox y

ERP Aler t

Server

CRM

Legend:

= Message = Message/ Process Flow




STEP 1: PI Data Types




STEP 1: PI Monitoring Process




STEP 1: PI Configuration




1. Introduction

2. System Overview


1. Step 1: PI

2. Step 2: CRM

3. Step 3: ERP




Agenda




STEP 2: CRM Event Enabling

Transaction Code SWED




STEP 2: CRM Event Linkage

Transaction Code SWF_BAM




1. Introduction

2. System Overview


1. Step 1: PI

2. Step 2: CRM

3. Step 3: ERP




Agenda




STEP 3: ERP PO Event Enabling I

Customizing - Transaction Code SPRO SAP Reference IMGMaterials Management

Purchasing

Messages

Output Control

Messages Types

Defines Messages Typesfor Purchaser OrderMaintain Message Types for PO




STEP 3: ERP PO Event Enabling II




STEP 3: ERP PO Event Enabling III




STEP 3: ERP PO Event Enabling IV

Customizing - Transaction Code SPRO SAP Reference IMGMaterials Management

Purchasing

Messages

Output Control

Messages Types

Defines Messages Types forPurchaser Order Fine-Tuned Control: Purchase Order




STEP 3: ERP PO Event Enabling V

Customizing - Transaction Code SPRO SAP Reference IMG Materials Management

Purchasing

Messages

Output Control

Messages Types

Message Determination Schemas Define Message Schema for Purchase OrderMaintain Message Determination Schema: PurchaseOrder




STEP 3: ERP PO Event Enabling VI

Master Data - Transaction Code MN04




STEP 3: ERP PO Business Object

Enhancement I

Business Object Builder - Transaction Code SWO1 New Object Type ZZBUS2012

Enhancement of BUS2012 with attribute PurchaseOrderDetails.OurReference (field EKKO-UNSEZ)to get the correlation to the CRM Sales Order

Source of the attribute: virtual

Program of the attribute:GET_PROPERTY OURREFERENCE CHANGING CONTAINER.

data l_unsez like ekko-unsez.

select single unsez from ekko into l_unsez where

ebeln = OBJECT-KEY-PURCHASEORDER.OBJECT-OURREFERENCE = l_unsez.

SWC_SET_ELEMENT CONTAINER 'OurReference' OBJECT-OURREFERENCE.

END_PROPERTY.




STEP 3: ERP PO Business Object

Enhancement II

Delegation - Transaction Code SWO6




STEP 3: ERP PO Event Linkage

Transaction Code SWF_BAM




STEP 3: ERP PO Item Look-up

Transaction Code SPROXY

method ZNW_II_ERP_PURCHASE_ORDER_ITEM~EXECUTE_SYNCHRONOUS.data l_menge type ekpo-menge.output =input.select single matnr from ekpointo output-ERP_PURCHASE_ORDER-MATERIAL where EBELN =input-

ERP_PURCHASE_ORDER-ID and ebelp ='00010'.select single mengefrom ekpointo l_menge where EBELN =input-ERP_PURCHASE_ORDER-ID and ebelp='00010'.output-ERP_PURCHASE_ORDER-ORDER_QUAN =l_menge.select single werks from ekpo into output-ERP_PURCHASE_ORDER-PLANT where EBELN =input-

ERP_PURCHASE_ORDER-ID and ebelp ='00010'.select single meins from ekpo into output-ERP_PURCHASE_ORDER-unit where EBELN =input-ERP_PURCHASE_ORDER-ID

and ebelp='00010'.endmethod.




STEP 3: ERP GR – Enhancement

Implementation

Transaction Code

SE19




1. Introduction

2. System Overview


1. Step 1: PI

2. Step 2: CRM

3. Step 3: ERP




Agenda




STEP 4: Alert Server – Alert Category I

Transaction Code ALRTCATDEF




STEP 4: Alert Server – Alert Category II




STEP 4: Alert Server – Alert Category III




STEP 4: Alert Server – Alert Proxy




STEP 4: Alert Server – Alert API

method ZNW_II_BAM_ALERT_MESSAGE~EXECUTE_ASYNCHRONOUS.

*** **** INSERT IMPLEMENTATION HERE **** ***

data: l_r_cnt type ref to IF_SWF_CNT_CONTAINER.

l_r_cnt = cl_swf_cnt_factory=>create( ).

Call method l_r_cnt->element_set

EXPORTING

name = 'so'

value = input-bam_alert-sales_date-object_id.

…

CALL FUNCTION 'SALRT_CREATE_API'EXPORTINGip_category =

'BAM_ALERT_GR'IP_WAIT_ON_COMMIT = ''ii_container =l_r_cnt

* IMPORTING

* ep_alert_Id = l_IdtablesIT_RECIPIENTS =

EXCEPTIONSALERT_CATEGORY_UNKNOWN =1ALERT_NO_RECIPIENTS = 2ALERT_ERROR_UNKNOWN =3DESTINATION_UNDEFINED =4COMMUNICATION_FAILURE =5SYSTEM_FAILURE = 6.




STEP 5: Guided Procedures – Event Resolution

Design Time




1. Introduction

2. System Overview


1. Step 1: PI

2. Step 2: CRM

3. Step 3: ERP




Agenda




STEP 6: BI – Process Data Extraction PI BI




1. Introduction

2. System Overview


1. Step 1: PI

2. Step 2: CRM

3. Step 3: ERP




Agenda




STEP 7: VC – Process Efficiency Dashboard




BPM With SAP NetWeaver – Roadmap

Highlights

2007

Process

Transparency

& Flexibility

2009/10Themes do not correspond to releases

End-to-end

BusinessProcess

Further SOA

Delivery

Built-in Process

Flexibility

Composition

Accelerator

Out-of-the box access tobusiness semantics via

Enterprise Services

Repository (ESR)

Enterprise Modeling to

plan standardization andupgrades

SAP NetWeaver PI 7.1

provides enhancedprocess automation

capabilities and first BAM

infrastructure

Further adoption of

Business TaskManagement (UWL)

Continuous support f or

Business Workflow andGuided Procedures

SAP NetWeaver CE

delivers BPM capabilities:

Composite Business

Processes Orchestrate Enterprise

Services & human activities

Full process lifecycle

support

Integrated composite

developer experience:

workflow, events, UI,services, connectivity

Exposes application

process flow m odels

for reference andextension

Human Interaction

Management Evolution of B usiness Task

Management (UWL)

Future releases

Common process layer Drive deep changes based on

SOA by design

Act ionable Process AnalysisProvides drill-down into

process inst ances andprocess design time

Enables Change Management

BAM with obs erved activities

BPM powered Situational

Composites

Process composition for

Business Analyst

Advanced process

collaboration

ProcessEfficiency

2008

Roadmap Highlights

The BPM roadmap will be brought to the market in a staged approach extending the functional capabilities as well asproviding additional value for our customers. Until 2010 we will provide BPM capabilities in three stages as outlined below:

Stage 1: Further SOA Delivery

– Enterprise Services Repository and Services Registry are integral part of PI 7.1 and CE 7.1. The ESR provides out-of the-box access tobusiness semantics (process components, enterprise service definitions)

– Enhanced Integration Processes (ccBPM with SAP NetWeaver PI 7.1): continuous performance improvements, modeling enhancementsand support for human interaction (generic user decisions)

– First Business Activity Monitoring (BAM) infrastructure including event provisioning and correlation mechanisms.

– Continuous support for SAP Business Workflow and Guided Procedures customers.– Continuous application adoption of the Universal Worklist (UWL)

Stage 2: Accelerating Composition

In stage 2, SAP will deliver new BPM capabilities with the SAP NetWeaver Composition Environment (CE).

– Composite Business Processes orchestrate Enterprise Services & human activities

– Support the full process lifecycle from model, dry-run, deploy, execute and monitor

– Provides an integrated composite developer experience including workflow, event, user interface, services, and connectivity

– Leverage application process flow models for reference and extensions

– Includes human interaction management (HIM) as an evolution of business task management and the Universal Worklist (UWL)



Copyright 2007 SAP AG. All Rights Reserved

No part of this publication may b e reproduced or transmitted in any form o r for any p urpose without the express permission of SAP AG. The information contained herein may be c hanged without prior notice.

Some software products marketed by SAP AG and its distributors co ntain proprietary software components of o ther software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint 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, System i, System i5, System p, System p5, System x, System z,System z9, z/OS, AFP, Intelligent Miner, W ebSphere, Netfinity, Tivo li, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or regist ered trademarks of IBM Corpo ration.

Ado be, the A dob e logo , Acro bat, Pos tScr ipt, an d Reader ar e either trade marks or r egis tered tradem arks o f Ado be Syst ems Inc orp orate d in t he United States an d/or o ther c oun tries .

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered t rademarks of th e Open Group.

Citrix, ICA, Program Neighborh ood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks o f Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered t rademarks 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.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AGin Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document servesinformational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP®product and is not intended to b e binding upon SAP to any particular course of business, product s trategy, and/or development. Please note that this document is subject to change and may bechanged by SAP at any time without notice.

SAP assumes no responsibility for errors o r omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within thismaterial. This document is prov ided 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 d amages o f any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation s hall notapply in cases of intent or gross negligence.

The statutory liability for person al injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links c ontained in these materials anddoes not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

globalizing local business events

Documents