Run SAP like a Factory

Run SAP like a Factory Best Practice Process Document ALM Process: Business Process Operations Business Process Analytics

ALM Process Business Process Operations Business Process Analytics Problem Description: How to monitor critical Business Processes of the customer solution landscape? Monitoring business processes should be available for Business Process Steps as well as for Interfaces between process steps The Monitoring Capabilities have to cover application- and technical related monitoring objects, which are crucial for the smooth and reliable flow of the Business Process SAP Standards Exception Handling and Business Process & Interface Monitoring Best Practice Process Solution: Business Process Analytics Analyzing consistent Business Process Execution Operation centric Business Process Monitoring Define Solution based discrete Core Business Processes dedicated to Business Process Monitoring ( ->Manually integrated Solution Documentation ) Business Process Monitoring, Interface Monitoring, Data Volume/Consistency Management, Business Process Job Management, End-User Experience Monitoring as proactive Monitoring ( Service Level Reporting ) and re-active Monitoring ( Application Incident Management ) Lifecycle centric Process Management Business Process Management from Requirement to Design including Operational Process KPI s to Operation ( -> System integrated Solution Documentation ) Process Health Service Level Reporting Proactive Business Process Health Service Level Reporting allowing pro-active analysis of critical system health tendencies and potential technical SLA/KPI violations 2012 SAP AG. All rights reserved. 2

Best Practice Process - Detail Process Description Business Process Analytics is a SAP BW based analysis tool, which enables the customer to execute a quick, but detailed evaluation about his current situation in regards to Backlog Indicators. From a technical perspective, the data to be analyzed is transferred from the Managed System(s) to SAP BW. This is done via the SMD Extractor Framework. During the Application Lifecycle, the customer will go through the Business Process Improvement Phase, which deals with the clean up of old & open business data, the adjustment of customizing and the closing of business process design gaps. At the beginning of this phase, SAP highly recommends utilizing Business Process Analytics for the evaluation of Backlog Indicators as a starting point. The results from the Business Process Analysis Session as well as the customer experience provide valuable input in regards to the selection of Backlog Key Figures for deeper analysis. Business Process Analytics can be set up quickly and the selected Backlog Key Figures can be evaluated according to different dimensions: Drive a benchmarking for organizational units and /or document types Start an Age Analysis (per Year or for the last 12 Months), as well as Launch a Trend Analysis for specific Backlog Indicators Furthermore it is possible to drill down to the level of single documents in order to enable a detailed analysis by experts from the referring business departments. In order to identify the Root Cause(s) for current Backlogs, the involvement of the Business Departments is crucial. Based on the evaluations with Business Process Analytics, it might make a lot of sense to set up a tailored Business Process Monitoring Configuration as next step. SAP recommends to setup Business Process Monitoring with reference to the Backlog Key Figures, which have been evaluated in Business Process Analytics. The data, which is required for Business Process Monitoring, is then directly provided by SAP BW. As alternative you can make use of the Trend Analysis functionality in Business Process Analytics in order to evaluate the progress with the clean up of old & open business data. 2012 SAP AG. All rights reserved. 10

Best Practice Process Advantage / Integration Advantages Enables a quick and comprehensive evaluation about the current situation regarding Backlog Indicators Allows a benchmarking for organizational units and/or document types Allows an Age Analysis for Backlog Indicators The tool is easy to set up No expensive Select Statements on the respective database tables in the Managed System(s) required: As already mentioned, the SMD Extractor Framework is being used, in order to transfer the data from the Managed System(s) to SAP BW. All further evaluations are then based on the data, which is stored in the preconfigured SAP BW InfoCube for Business Process Analytics This is also true, if Business Process Monitoring is later set up with reference to the Backlog Key Figures, which have been evaluated in SAP BW Setting up Business Process Monitoring in this way, reveals another advantage: the number of documents, which is listed in the alert text, is always consistent to the number of documents, you get, when you drill down to the single document level Integrated with the Business Process Operations Process* Business Process & Interface Monitoring: Lifecycle centric Process Management Operation centric Business Process Monitoring * In the Business Process Repository, ALM processes are reflected in scenarios, Business Process Operations processes are reflected in processes 2012 SAP AG. All rights reserved. 11

2012 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iseries, pseries, xseries, zseries, eserver, z/vm, z/os, i5/os, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. 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 and Java are registered trademarks of Oracle and/or its affiliates. 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. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, 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 other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, ianywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company. 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. 2012 SAP AG. All rights reserved. 12