Business Activity

Monitoring: An Overview
Topics

Introduction

System Overview

Demo

Development Step by Step

Topics

Introduction

System Overview

Demo

Development Step by Step

 BAM according to Gartner Definition

Gartner introduced the term "business activity

monitoring" (BAM) in July 2001 and defined it as
"... the concept of providing realtime access to critical
business performance indicators to improve the speed
and effectiveness of business operations"

© SAP Know How Network Call

 Definition & Architecture
Business Activity Monitoring (BAM)
Business Activity Enterprise Portal Event Resolution Dashboard

Monitoring Process Efficiency Dashboard

A framework that enables

users to
„… act on significant
events/alerts and take the
correct action in the right
work context. XI BI Alert
Alert

„… monitor, measure and Milestone Monitoring Alert

improve the efficiency of Process

business processes Efficiency

Scenario Variants Extraction &

Non-SAP
„ Subscription of events and Transformation

milestone monitoring
„ Analytical alert publishing Event
Event Infrastructure
Infrastructure

„ Alert publishing mySAP Business Suite

Service Business Object Event

© SAP Know How Network Call

 Key Capabilities
Business Activity Monitoring (BAM)
What’s new?
Enterprise Portal Event Resolution Dashboard
Process Efficiency Dashboard
Event Resolution Dashboard
„ Central context storage
„ Event Resolution Templates to guide
users context-sensitively through
problem inspection and resolution

Process Milestone Monitoring

„ Event-based monitoring of key
process milestones XI BI Alert
Alert
„ Subscription and handling of Milestone Monitoring Alert
business process events
„ BPM modeling (BPEL) Process
Efficiency

Process Efficiency
„ Analysis of efficiency of processes
Extraction &
„ Based on milestone monitoring Non-SAP Transformation

Embedded Event Infrastructure

„ Infrastructure, embedded in mySAP
Event
Event Infrastructure
Business Suite applications Infrastructure

„ Enables collecting, pre-filtering and mySAP Business Suite

publication of events for inter-system
usage across SAP and Non-SAP Service Business Object Event

© SAP systems
Know How Network Call
 Monitoring Event Creation and Filtering
How it all comes together

BAM
listener

Sync and async

communication

Exposed
services
ECC CRM SRM …
Exposed
events
Purchase Sales Shopping
Business …
order order cart
objects

Local
events

Model
driven mySAP Business Suite
Event enabling
„ Propagate significant events beyond the application system boundaries (“chattiness”)

Scenario characteristics
„ BAM listener as passive component needs to be notified
„ Applications are communicative – raise events
© SAP Know How Network Call
 Monitoring Event Creation and Filtering
From Local Events to Global Events in Three Steps

(1) Define event signature in ESR (like for any other service)
(2) Generate outbound proxy for the defined event
(3) Cast local events to the outbound proxy call
(configuration, without Touching Core Business)

Message, Alert Global

events
Event Proxy

Event Manager Event Filter

Local
events
Change Status Alert
…
Documents Management Management

Enterprise
Enterprise
Service
Service Proxy
Repository
Repository Application
Generation

Application
Application System
System (Event
(Event Producer)
Producer) Release
Release 6.20-7.10
6.20-7.10

© SAP Know How Network Call

 Use Case Sales Order Monitoring

SAP NetWeaver

BI Process Efficiency Analysis Event Resolution Dashboard

Instances of process milestones

Alert
Purchase Goods
Sales Order
Order Receipt

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.

© SAP Know How Network Call

Topics

Introduction

System Overview

Demo

Development Step by Step

 System Component View

NetWeaver 2004s
EP Guided Procedures

UWL

Alert Server Visual Composer

XI BI

CRM ERP
in our example
XI and Alert
Servier is on
one box

© SAP Know How Network Call

 System Connectivity View

© SAP Know How Network Call

Topics

Introduction

System Overview

Demo

Development Step by Step

© SAP Know How Network Call
 Runtime – Event Resolution: UWL Entry Point

© SAP Know How Network Call

 Runtime – Event Resolution: Dashboard

© SAP Know How Network Call

 Runtime – Event Resolution: Problem Analysis & Resolution

© SAP Know How Network Call

 Runtime – Process Efficiency Dashboard

© SAP Know How Network Call

Topics

Introduction

System Overview

Demo

Development Step by Step

 Topics

Step 1 - XI
Step 2 - CRM
Step 3 - ERP
Step 4 - Alert Server
Step 5 - Guided Procedures
Step 6 - BI
Step 7 – Visual Composer
 STEP 1: XI Î Design & Configuration

Start

End
Asynch. Abstract MI Asynch. Abstract MI Synch. Abstract MI Asynch. Abstract MI Condition Transformation Asynch. Abstract MI
CRM_Sales_Order_Event ERP_Purchase_Order_ ERP_Purchase_Order_ ERP_Goods_Receipt_ Step Step (Message BAM_Alert_Event
(MT: CRM_Sales_Order Event Item_Event Event Mapping: (MT: BAM_Alert
DT: CRM_Sales_Order) (MT: (MT: (MT: AlertContext) DT: BAM_Alert)
ERP_Purchase_Order ERP_Purchase_Order ERP_Goods_Reciept
DT:
DT:
ERP_Purchase_Order) ERP_Purchase_Order)
DT: XI Process
ERP_Goods_Receipt)
Engine

Asynch. Outbound MI Asynch. Outbound MI Synch. Inbound MI Asynch. Outbound MI Asynch. Inbound MI
CRM_Sales_Order_Message ERP_Purchase_Order_ ERP_Purchase_Order_ ERP_Goods_Receipt_ BAM_Alert_Message
(MT: CRM_Sales_Order Message Item_Message Message (MT: BAM_Alert
DT: CRM_Sales_Order) (MT: (MT: (MT: DT: BAM_Alert)
ERP_Purchase_Order ERP_Purchase_Order ERP_Goods_Reciept XI Integration
DT: DT: DT:
ERP_Purchase_Order) ERP_Purchase_Order) ERP_Goods_Receipt) Engine

CRM ERP Alert

Server

Sales Order Outbound Proxy Purchase Order Purchase Order Item Goods Receipt Alert Inbound Proxy
Outbound Proxy Inbound Proxy Outbound Proxy

Legend:
MI = Message Interface = Message and Interface Mapping = Message = Message / Process Flow
MT = Message Type
DT = Data Type

© SAP Know How Network Call

 STEP 1: XI Î Data Types

© SAP Know How Network Call

 STEP 1: XI Î Monitoring Process

© SAP Know How Network Call

 STEP 1: XI Î Configuration

© SAP Know How Network Call

 Topics

Step 1 - XI
Step 2 - CRM
Step 3 - ERP
Step 4 - Alert Server
Step 5 - Guided Procedures
Step 6 - BI
Step 7 – Visual Composer
 STEP 2: CRM Î Event Enabling

Î Transaction Code SWED

© SAP Know How Network Call

 STEP 2: CRM Î Event Linkage

Î Transaction Code SWF_BAM

© SAP Know How Network Call

 Topics

Step 1 - XI
Step 2 - CRM
Step 3 - ERP
Step 4 - Alert Server
Step 5 - Guided Procedures
Step 6 - BI
Step 7 – Visual Composer
 STEP 3: ERP Î PO Event Enabling I
Î Customizing - Transaction Code SPRO Î SAP Reference IMG Î Materials Management
Î Purchasing Î Messages Î Output Control Î Messages Types Î Defines Messages Types
for Purchaser Order Î Maintain Message Types for PO

© SAP Know How Network Call

 STEP 3: ERP Î PO Event Enabling II

© SAP Know How Network Call

 STEP 3: ERP Î PO Event Enabling III

© SAP Know How Network Call

 STEP 3: ERP Î PO Event Enabling IV
Î Customizing - Transaction Code SPRO Î SAP Reference IMG Î Materials Management Î Purchasing Î
Messages Î Output Control Î Messages Types Î Defines Messages Types for Purchaser Order Î Fine-
Tuned Control: Purchase Order

© SAP Know How Network Call

 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 Order Î Maintain Message Determination Schema: Purchase Order

© SAP Know How Network Call

 STEP 3: ERP Î PO Event Enabling VI

Î Master Data - Transaction Code MN04

© SAP Know How Network Call

 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.
© SAP Know How Network Call
 STEP 3: ERP Î PO Business Object Enhancement II

Î Delegation - Transaction Code SWO6

© SAP Know How Network Call

 STEP 3: ERP Î PO Event Linkage

Î Transaction Code SWF_BAM

© SAP Know How Network Call

 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 ekpo into output-ERP_PURCHASE_ORDER-MATERIAL where EBELN = input-
ERP_PURCHASE_ORDER-ID and ebelp = '00010'.
select single menge from ekpo into 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.
© SAP Know How Network Call
 STEP 3: ERP Î GR – Outbound Proxy

Î Transaction Code SPROXY

© SAP Know How Network Call

 STEP 3: ERP Î GR – Enhancement Implementation

ÎTransaction Code
SE19

© SAP Know How Network Call

 STEP 3: ERP Î GR – BADI Implementation

method IF_EX_MB_DOCUMENT_BADI~MB_DOCUMENT_BEFORE_UPDATE.
data l_mseg type mseg.
data l_ZNW_ERP_GOODS_RECEIPT type ZNW_ERP_GOODS_RECEIPT1.
loop at xmseg into l_mseg.
if l_mseg-LIFNR eq '0000005587'.
l_ZNW_ERP_GOODS_RECEIPT-ERP_GOODS_RECEIPT-id = l_mseg-MBLNR.
l_ZNW_ERP_GOODS_RECEIPT-ERP_GOODS_RECEIPT-PURCHASE_ORDER_ID = l_mseg-EBELN.
l_ZNW_ERP_GOODS_RECEIPT-ERP_GOODS_RECEIPT-GRQUANT = l_mseg-MENGE.
l_ZNW_ERP_GOODS_RECEIPT-ERP_GOODS_RECEIPT-unit = l_mseg-meins.
l_ZNW_ERP_GOODS_RECEIPT-ERP_GOODS_RECEIPT-STORAGE_LOCATION = l_mseg-LGORT.
l_ZNW_ERP_GOODS_RECEIPT-ERP_GOODS_RECEIPT-GRDATE = SY-DATUM.
l_ZNW_ERP_GOODS_RECEIPT-ERP_GOODS_RECEIPT-GRTIME = SY-UZEIT.
DATA l_r_goods_receipt TYPE REF TO ZNW_CO_ERP_GOODS_RECEIPT_MESSA.
DATA l_n_async_messaging TYPE REF TO if_wsprotocol_async_messaging.
try.
CREATE OBJECT l_r_goods_receipt.
* exporting logical port name =
* exceptions CX_AI_SYSTEM_FAULT =
* get asynchronous messaging protocol
l_n_async_messaging ?= l_r_goods_receipt->get_protocol(
if_wsprotocol=>async_messaging ).
l_n_async_messaging->set_serialization_context('MY_QUEUE_ID').
CALL METHOD l_r_goods_receipt->execute_asynchronous
EXPORTING
output = l_ZNW_ERP_GOODS_RECEIPT.
CATCH cx_ai_system_fault.
CATCH cx_ai_application_fault.
endtry.
endif.
exit.
endloop.
endmethod.
method IF_EX_MB_DOCUMENT_BADI~MB_DOCUMENT_UPDATE.
endmethod.

© SAP Know How Network Call

 Topics

Step 1 - XI
Step 2 - CRM
Step 3 - ERP
Step 4 - Alert Server
Step 5 - Guided Procedures
Step 6 - BI
Step 7 – Visual Composer
 STEP 4: Alert Server – Alert Category I

ÎTransaction Code ALRTCATDEF

© SAP Know How Network Call

 STEP 4: Alert Server – Alert Category II

© SAP Know How Network Call

 STEP 4: Alert Server – Alert Category III

© SAP Know How Network Call

 STEP 4: Alert Server – Alert Proxy

© SAP Know How Network Call

 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
CALL FUNCTION 'SALRT_CREATE_API'
EXPORTING EXPORTING
name = 'so' ip_category =
'BAM_ALERT_GR'
value = input-bam_alert-sales_date-object_id. IP_WAIT_ON_COMMIT = ''
ii_container = l_r_cnt
…
* IMPORTING
* ep_alert_Id = l_Id
tables
IT_RECIPIENTS =
EXCEPTIONS
ALERT_CATEGORY_UNKNOWN = 1
ALERT_NO_RECIPIENTS = 2
ALERT_ERROR_UNKNOWN = 3
DESTINATION_UNDEFINED = 4
COMMUNICATION_FAILURE = 5
SYSTEM_FAILURE = 6.

© SAP Know How Network Call

 Topics

Step 1 - XI
Step 2 - CRM
Step 3 - ERP
Step 4 - Alert Server
Step 5 - Guided Procedures
Step 6 - BI
Step 7 – Visual Composer
 STEP 5: Guided Procedures – Event Resolution Design
Time

© SAP Know How Network Call

 Event Resolution Template – Attaching an alert

© SAP Know How Network Call

 Event Resolution Template: Inspection & Resolution

© SAP Know How Network Call

 Topics

Step 1 - XI
Step 2 - CRM
Step 3 - ERP
Step 4 - Alert Server
Step 5 - Guided Procedures
Step 6 - BI
Step 7 – Visual Composer
 STEP 6: BI – Process Data Extraction XI Î BI

© SAP Know How Network Call

 Topics

Step 1 - XI
Step 2 - CRM
Step 3 - ERP
Step 4 - Alert Server
Step 5 - Guided Procedures
Step 6 - BI
Step 7 – Visual Composer
 STEP 7: VC – Process Efficiency Dashboard

© SAP Know How Network Call

 Questions?

Q&A

© SAP Know How Network Call

 Copyright 2005 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, 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, z/OS, AFP,
Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation.
„ Oracle is a registered trademark of Oracle Corporation.
„ UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
„ Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
„ HTML, XML, XHTML and W3C 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.
„ 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 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. Data contained in this document serves informational 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 be binding upon SAP to any particular course of business, product
strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.
„ SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics,
links, or other 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 limitation shall 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 that you may access through the use of
hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web
pages.

© SAP Know How Network Call