business activity monitoring: globalizing local ... - sap q&a · the correct action in the...
TRANSCRIPT
SAP NetWeaver Process Integration 7.1 1
SAP NetWeaver Process Integration 7.1Business Activity Monitoring: Globalizing Local BusinessEvents–Event to Resolution
SAP NetWeaver Regional Implementation GroupSAP Netweaver Process IntegrationDecember 2007
SAP NetWeaver Process Integration 7.1 2
Benefits
This document shows you a development example for Business ActivityMonitoring
SAP NetWeaver Process Integration 7.1 3
1. Introduction2. System Overview3. Development Step by Step
Agenda
SAP NetWeaver Process Integration 7.1 4
1. Introduction2. System Overview3. Development Step by Step
Agenda
SAP NetWeaver Process Integration 7.1 5
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 wehave to deal with?
Events are not tangible for business users – What kinds of business events aremanaged in my landscape today?Where and how do I set up new scenarios?
Missing “chattiness” of today’s applications and systems – Events remain unnoticedor without sufficient context.
The unknown – Do event-driven architectures affect my service-oriented architecture(SOA) strategy? What kind of event management capabilities do I really need?
SAP NetWeaver Process Integration 7.1 6
Evolution of Business Process and EventManagement
19952002
2004
TODAY
SAP BusinessWorkflow/
Events
SAP PIUWL/ ccBPM
Business Process ManagementBusiness Task ManagementBusiness Activity Monitoring Infrastructure
…SAP Reference
Model
SAP NetWeaver
SAP NetWeaver Process Integration 7.1 7
Leveraging Enterprise Services and Business EventsBusiness Activity Monitoring (BAM)
Business ActivityMonitoringA framework (technical infrastructure)that enables users to
Act on significant events and takethe correct action in the right workcontextMonitor, measure, and improve theefficiency of business processes
mySAP Business Suite
Event InfrastructureEvent Infrastructure
Alert
Milestone Monitoring PI
Event Resolution Cockpit
Non-SAP
ProcessEfficiency
BI
Service Business Object Event
SAP NetWeaver Process Integration 7.1 8
1. Introduction2. System Overview3. Development Step by Step
Agenda
SAP NetWeaver Process Integration 7.1 9
StatusBusiness Activity Monitoring (BAM)
mySAP Non-SAP
(2) Milestone Monitoring (PI)
DeliverGoods
CreateOpportunity Place Order
CreateLead
Alert
EventManager
Event
Filter
EventHandler
(3) Process Efficiency (BI)
Process Data Marts*
Process-centric BICockpits*
(1) Event Resolution (GP)
Alerting & resolution context
Available as ofSAP_Basis 620
Available as ofPI 7.1 (PI 3.0)
Prototype
Process Analysisas Standard
Business ContentAvailable as of BI
7.0
BAM combines existing and new functionality into a consistent framework for SAP,ISV’s and customers
SAP NetWeaver Process Integration 7.1 10
Use Case Sales Order Monitoring
GoodsReceiptSales Order Purchase
Order
SAP NetWeaver
Instances of process milestones
Event Resolution Dashboard
Alert
SAP CRM SAP ERP SAP ERP
Alert:
Consistency Check: If the goods receipt quantity does not match to the orderedquantity then an alert should be raised to the Dashboard.
BI Process Efficiency Analysis
SAP NetWeaver Process Integration 7.1 11
System Component View
PI BI
Alert Server Visual Composer
UWL
Guided Procedures
SAP NetWeaver 7.0SAP NetWeaver Portal
ERPCRMIn this examplePI and alert serverare on the same box
SAP NetWeaver Process Integration 7.1 12
System Connectivity View
SAP NetWeaver Process Integration 7.1 13
Runtime – Event Resolution: UWL Entry Point
SAP NetWeaver Process Integration 7.1 14
Runtime – Event Resolution: Dashboard
SAP NetWeaver Process Integration 7.1 15
Runtime – Event Resolution: Problem Analysis& Resolution
SAP NetWeaver Process Integration 7.1 16
Runtime – Process Efficiency Dashboard
SAP NetWeaver Process Integration 7.1 17
1. Introduction2. System Overview3. Development Step by Step
1. Step 1: PI2. Step 2: CRM3. Step 3: ERP4. Step 4: Alert Server5. Step 5: Guided Procedures6. Step 6: BI7. Step 7: Visual Composer
Agenda
SAP NetWeaver Process Integration 7.1 18
1. Introduction2. System Overview3. Development Step by Step
1. Step 1: PI2. Step 2: CRM3. Step 3: ERP4. Step 4: Alert Server5. Step 5: Guided Procedures6. Step 6: BI7. Step 7: Visual Composer
Agenda
SAP NetWeaver Process Integration 7.1 19
STEP 1: PI Design & Configuration
Asynch. Abstract MICRM_Sales_Order_Event(MT: CRM_Sales_OrderDT: CRM_Sales_Order)
MI = Message InterfaceMT = Message TypeDT = Data Type
Asynch. Abstract MIERP_Purchase_Order_Event(MT:ERP_Purchase_OrderDT:ERP_Purchase_Order)
Synch. Abstract MIERP_Purchase_Order_Item_Event(MT:ERP_Purchase_OrderDT:ERP_Purchase_Order)
Asynch. Abstract MIERP_Goods_Receipt_Event(MT:ERP_Goods_RecieptDT:ERP_Goods_Receipt)
ConditionStep
TransformationStep (MessageMapping:AlertContext)
Asynch. Abstract MIBAM_Alert_Event(MT: BAM_AlertDT: BAM_Alert)
Start
End
Asynch. Outbound MICRM_Sales_Order_Message(MT: CRM_Sales_OrderDT: CRM_Sales_Order)
Asynch. Outbound MIERP_Purchase_Order_Message(MT:ERP_Purchase_OrderDT:ERP_Purchase_Order)
= Message and Interface Mapping
Synch. Inbound MIERP_Purchase_Order_Item_Message(MT:ERP_Purchase_OrderDT:ERP_Purchase_Order)
Asynch. Outbound MIERP_Goods_Receipt_Message(MT:ERP_Goods_RecieptDT:ERP_Goods_Receipt)
Asynch. Inbound MIBAM_Alert_Message(MT: BAM_AlertDT: BAM_Alert)
PI ProcessEngine
PI IntegrationEngine
Sales Order Outbound Proxy Purchase OrderOutbound Proxy
Purchase Order ItemInbound Proxy
Goods ReceiptOutbound Proxy
Alert Inbound Proxy
ERP AlertServer
CRM
Legend:= Message = Message / Process Flow
SAP NetWeaver Process Integration 7.1 20
STEP 1: PI Data Types
SAP NetWeaver Process Integration 7.1 21
STEP 1: PI Monitoring Process
SAP NetWeaver Process Integration 7.1 22
STEP 1: PI Configuration
SAP NetWeaver Process Integration 7.1 23
1. Introduction2. System Overview3. Development Step by Step
1. Step 1: PI2. Step 2: CRM3. Step 3: ERP4. Step 4: Alert Server5. Step 5: Guided Procedures6. Step 6: BI7. Step 7: Visual Composer
Agenda
SAP NetWeaver Process Integration 7.1 24
STEP 2: CRM Event Enabling
Transaction Code SWED
SAP NetWeaver Process Integration 7.1 25
STEP 2: CRM Event Linkage
Transaction Code SWF_BAM
SAP NetWeaver Process Integration 7.1 26
1. Introduction2. System Overview3. Development Step by Step
1. Step 1: PI2. Step 2: CRM3. Step 3: ERP4. Step 4: Alert Server5. Step 5: Guided Procedures6. Step 6: BI7. Step 7: Visual Composer
Agenda
SAP NetWeaver Process Integration 7.1 27
STEP 3: ERP PO Event Enabling I
Customizing - Transaction Code SPRO SAP Reference IMG Materials ManagementPurchasing Messages Output Control Messages Types Defines Messages Types
for Purchaser Order Maintain Message Types for PO
SAP NetWeaver Process Integration 7.1 28
STEP 3: ERP PO Event Enabling II
SAP NetWeaver Process Integration 7.1 29
STEP 3: ERP PO Event Enabling III
SAP NetWeaver Process Integration 7.1 30
STEP 3: ERP PO Event Enabling IV
Customizing - Transaction Code SPRO SAP Reference IMG Materials ManagementPurchasing Messages Output Control Messages Types Defines Messages Types forPurchaser Order Fine-Tuned Control: Purchase Order
SAP NetWeaver Process Integration 7.1 31
STEP 3: ERP PO Event Enabling V
Customizing - Transaction Code SPRO SAP Reference IMG Materials ManagementPurchasing Messages Output Control Messages Types Message Determination SchemasDefine Message Schema for Purchase Order Maintain Message Determination Schema: Purchase
Order
SAP NetWeaver Process Integration 7.1 32
STEP 3: ERP PO Event Enabling VI
Master Data - Transaction Code MN04
SAP NetWeaver Process Integration 7.1 33
STEP 3: ERP PO Business ObjectEnhancement I
Business Object Builder - Transaction Code SWO1New Object Type ZZBUS2012Enhancement of BUS2012 with attribute PurchaseOrderDetails.OurReference (field EKKO-UNSEZ)to get the correlation to the CRM Sales OrderSource of the attribute: virtualProgram of the attribute:GET_PROPERTY OURREFERENCE CHANGING CONTAINER.data l_unsez like ekko-unsez.select single unsez from ekko into l_unsez whereebeln = OBJECT-KEY-PURCHASEORDER.OBJECT-OURREFERENCE = l_unsez.SWC_SET_ELEMENT CONTAINER 'OurReference' OBJECT-OURREFERENCE.END_PROPERTY.
SAP NetWeaver Process Integration 7.1 34
STEP 3: ERP PO Business ObjectEnhancement II
Delegation - Transaction Code SWO6
SAP NetWeaver Process Integration 7.1 35
STEP 3: ERP PO Event Linkage
Transaction Code SWF_BAM
SAP NetWeaver Process Integration 7.1 36
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 NetWeaver Process Integration 7.1 37
STEP 3: ERP GR – Outbound Proxy
Transaction Code SPROXY
SAP NetWeaver Process Integration 7.1 38
STEP 3: ERP GR – EnhancementImplementation
Transaction CodeSE19
SAP NetWeaver Process Integration 7.1 39
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_asynchronousEXPORTING
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 NetWeaver Process Integration 7.1 40
1. Introduction2. System Overview3. Development Step by Step
1. Step 1: PI2. Step 2: CRM3. Step 3: ERP4. Step 4: Alert Server5. Step 5: Guided Procedures6. Step 6: BI7. Step 7: Visual Composer
Agenda
SAP NetWeaver Process Integration 7.1 41
STEP 4: Alert Server – Alert Category I
Transaction Code ALRTCATDEF
SAP NetWeaver Process Integration 7.1 42
STEP 4: Alert Server – Alert Category II
SAP NetWeaver Process Integration 7.1 43
STEP 4: Alert Server – Alert Category III
SAP NetWeaver Process Integration 7.1 44
STEP 4: Alert Server – Alert Proxy
SAP NetWeaver Process Integration 7.1 45
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_Id
tablesIT_RECIPIENTS =
EXCEPTIONSALERT_CATEGORY_UNKNOWN = 1ALERT_NO_RECIPIENTS = 2ALERT_ERROR_UNKNOWN = 3DESTINATION_UNDEFINED = 4COMMUNICATION_FAILURE = 5SYSTEM_FAILURE = 6.
SAP NetWeaver Process Integration 7.1 46
1. Introduction2. System Overview3. Development Step by Step
1. Step 1: PI2. Step 2: CRM3. Step 3: ERP4. Step 4: Alert Server5. Step 5: Guided Procedures6. Step 6: BI7. Step 7: Visual Composer
Agenda
SAP NetWeaver Process Integration 7.1 47
STEP 5: Guided Procedures – Event ResolutionDesign Time
SAP NetWeaver Process Integration 7.1 48
1. Introduction2. System Overview3. Development Step by Step
1. Step 1: PI2. Step 2: CRM3. Step 3: ERP4. Step 4: Alert Server5. Step 5: Guided Procedures6. Step 6: BI7. Step 7: Visual Composer
Agenda
SAP NetWeaver Process Integration 7.1 49
STEP 6: BI – Process Data Extraction PI BI
SAP NetWeaver Process Integration 7.1 50
1. Introduction2. System Overview3. Development Step by Step
1. Step 1: PI2. Step 2: CRM3. Step 3: ERP4. Step 4: Alert Server5. Step 5: Guided Procedures6. Step 6: BI7. Step 7: Visual Composer
Agenda
SAP NetWeaver Process Integration 7.1 51
STEP 7: VC – Process Efficiency Dashboard
SAP NetWeaver Process Integration 7.1 52
BPM With SAP NetWeaver – RoadmapHighlights
2007
ProcessTransparency& Flexibility
2009/10Themes do not correspond to releases
End-to-endBusinessProcess
Further SOADelivery
Built-in ProcessFlexibility
CompositionAccelerator
Out-of-the box access tobusiness semantics viaEnterprise ServicesRepository (ESR)
Enterprise Modeling toplan standardization andupgrades
SAP NetWeaver PI 7.1provides enhancedprocess automationcapabilities and first BAMinfrastructure
Further adoption ofBusiness TaskManagement (UWL)
Continuous support forBusiness Workflow andGuided Procedures
SAP NetWeaver CEdelivers BPM capabilities:
Composite BusinessProcesses
Orchestrate EnterpriseServices & human activitiesFull process lifecyclesupport
Integrated compositedeveloper experience:
workflow, events, UI,services, connectivity
Exposes applicationprocess flow modelsfor reference andextension
Human InteractionManagement
Evolution of Business TaskManagement (UWL)
Future releases
Common process layerDrive deep changes based onSOA by design
Actionable ProcessAnalysis
Provides drill-down intoprocess instances andprocess design timeEnables Change ManagementBAM with observed activities
BPM powered SituationalComposites
Process composition forBusiness Analyst
Advanced processcollaboration
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 to
business 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)
SAP NetWeaver Process Integration 7.1 53
Copyright 2007 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 priornotice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other 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, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States 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, 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 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 ofSAP 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 ofthe 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 bechanged 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 thismaterial. 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 notapply 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 anddoes not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.