SM300 Business Process and Interface Monitoring FS310 Inkasso/Exkasso
SM300
Business Process and Interface Monitoring
THE BEST-RUN BUSINESSES RUN SAP © SAP AG 2009
© SAP AG 2009
SAP Software Components: ST400 SP15, ST-SER700_2008_1, ST-A/PI01K
Version 62
Material number: 50092591
© SAP AG
SM300
Preface-1
© SAP AG
SM300
Preface-2
Copyright
Copyright 2009 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.
© SAP AG 2009
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.
… © SAP AG
SM300
Preface-3
…
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 AG
SM300
Preface-4
Course Prerequisites
Required Knowledge
SAPTEC Fundamentals of SAP NetWeaver Application Server
SM001 (e-Learning) Introduction to SAP Solution Manager
© SAP AG 2009
© SAP AG
SM300
Preface-5
Training Curriculum – SAP Solution Manager
© SAP AG 2009
© SAP AG
SM300
Preface-6
Training Curriculum – End-to-End (E2E) Solution Operations
© SAP AG 2009
© SAP AG
SM300
Preface-7
Course Overview
Course Overview Unit 1 Introduction to Business Process Monitoring Unit 2 Procedure Unit 3 Monitoring Configuration Unit 4 Using Business Process Monitoring
Unit 8
Data Consistency Monitoring
Unit 5 Cross-Application Monitoring
Unit 9
Reporting
Unit 6 Application Monitoring Unit 7 Interface Monitoring
Unit 10 Handover to Production Unit 11 Managing Jobs in SAP Solution Manager
© SAP AG 2008
© SAP AG
SM300
Preface-8
Target Audience
This course is intended for the following audiences:
Project Leaders
Project Members
Technical Consultants
Duration: 3 days
© SAP AG 2009
User notes y These training materials are not a teach-yourself program. They complement the explanations provided by your course instructor. Space is provided on each page for you to note down additional information. y There may not be sufficient time during the course to complete all the exercises. The exercises provide additional examples that are covered during the course. You can also work through these examples in your own time to increase your understanding of the topics.
© SAP AG
SM300
Preface-9
Course Goals
This course will prepare you to:
Understand and create a Business Process Management concept in order to help you to successfully operate your core business processes
Involve the SAP Solution Manager in your BPM strategy
Set up Business Process Monitoring in SAP Solution Manager
© SAP AG 2009
© SAP AG
SM300
Preface-10
Course Objectives After completing this training you will be able to:
© SAP AG 2009
© SAP AG
create a Business Process & Interface Monitoring concept for your core business processes
prepare SAP Solution Manager for Business Process Monitoring
configure Business Process & Interface Monitoring in SAP Solution Manager
have an understanding of the Business Process Monitoring functionalities currently available in SAP Solution Manager
configure Data Consistency Monitoring in SAP Solution Manager
check if the prerequisites for BI reporting in SAP Solution Manager have been fulfilled
use long term trend analysis in SAP Solution Manager
use Service Level Reporting in SAP Solution Manager
use the Job Management functionalities in SAP Solution Manager
transfer your monitoring customizing into your productive system landscape
SM300
Preface-11
What will not be Covered in this Training
During this training we will not cover:
how to install SAP Solution Manager
how to configure the Service Desk in SAP Solution Manager
details for every single business process and interface monitoring functionality available in SAP Solution Manager
details for the User Exit in the application monitoring infrastructure
© SAP AG 2009
There are now so many monitoring functionalities available in BPMon in SAP Solution Manager that it is not possible to go through each functionality in detail. Since the general procedure of how to configure the monitoring functionality is usually independent of the actual functionality itself we will go through the general procedure of how to configure these monitoring functionalities and how will use some examples to illustrate the general procedures.
The user exit in the application monitoring infrastructure requires the writing of ABAP coding to create your own data collectors for monitoring. Again we will go through the general procedure and the general structure of the coding, but we will not go into the details of how to write different coding to realize different functionalities.
© SAP AG
SM300
Preface-12
Initial Situation at Company IDES
Company IDES is currently upgrading their SAP R/3 System to SAP ERP 2005. Within the upgrade the business processes become more complex, distributed over several systems. CRM - CDP
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Run MRP
Procurement Process
Manufacturing Process
Create Outbound Delivery
Create Billing Document
Post Goods Issue
Warehouse - TT5
Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
© SAP AG 2009
We will follow the example of company IDES throughout this training. We will see how IDES creates a monitoring concept in the implementation project phase, how they implement SAP Solution Manager as their central tool for Business Process Monitoring and how the handover to productive operation then takes place.
In addition, we will see how IDES uses SAP Solution Manager to realize related areas of Business Process Operations, namely how they use SAP Solution Manager for their job request process and their background job documentation, and how they monitor data inconsistencies via SAP Solution Manager.
© SAP AG
SM300
Preface-13
© SAP AG
SM300
Preface-14
Introduction to Business Process Monitoring
Course Overview Unit 1 Introduction to Business Process Monitoring Unit 2 Procedure Unit 3 Monitoring Configuration Unit 4 Using Business Process Monitoring
Unit 8
Data Consistency Monitoring
Unit 5 Cross-Application Monitoring
Unit 9
Reporting
Unit 6 Application Monitoring Unit 7 Interface Monitoring
Unit 10 Handover to Production Unit 11 Managing Jobs in SAP Solution Manager
© SAP AG 2008
© SAP AG
SM300
1-1
Business Process Monitoring: Unit Objectives
After completing this unit, you will:
understand the basics of Business Process Monitoring
be able to create Solutions in SAP Solution Manager
be able to create Logical Components in System Landscape of SAP Solution Manager
© SAP AG 2009
© SAP AG
SM300
1-2
Lesson 1: Introduction to E2E Solution Support
1. 2. 3. 4.
Introduction to E2E Solution Support Introduction to Business Process Monitoring Initial Customer Situation for Training Initial Situation in SAP Solution Manager Appendix: Create Products, Servers, and Systems
© SAP AG 2009
© SAP AG
SM300
1-3
Motivation for E2E Solution Support User
RFID
Java World
Portal
Devices
SAP Portal
External Applications
Office
Duet
Analytics
.net World
Office Integration and Self-Services
Web Services and xApps
APO BW SRM SEM
Rendering
R/3
ERP
APO ESOA SEM SRM
SAP Solution Manager © SAP AG 2009
To be able to support today SAP solutions, y different client side technologies such as mobile devices, portal, Adobe forms, MS office and Internet browser y different server side applications such CRM, SRM, SCM and BW on multiple platforms (ABAP, Java, .net, C++)
need to be supported
SAP Solution Manager provides key capabilities to support distributed environments across different technology stacks.
SAP Solution Manager provides open hubs to plug in external applications.
© SAP AG
SM300
1-4
Content of E2E Solution Support END-TO-END SOLUTION SUPPORT MEANS:
End-to-end Root Cause Analysis (Mission Critical Support)
End-to-end Change Control Management (TCO Reduction + Mission Critical Support)
End-to-end Business Process Integration and Automation Management (ROI Improvement + TCO Reduction + Mission Critical Support)
End-to-end Technical Upgrade Management
© SAP AG 2009
The various aspects of End-to-End Solution Support are structured into 4 areas of support.
© SAP AG
SM300
1-5
SAP Offerings regarding E2E Solution Support
SAP Standards for E2E Support Operations
Guidelines how to operate an SAP solution
available in http://service.sap.com/supportstandards
RunSAP as implementation methodology for E2E Support Operations
Guidelines how to implement the SAP Standards for E2E Support Operations
roadmap available within SAP Solution Manager
SAP Solution Manager as central tool for E2E Support Operations
Central tool for all E2E Support Operations
© SAP AG 2009
SAP Standards for Solution Operations:
y Define mission-critical operations processes y Provide Best Practices and Implementation Roadmaps y Based on a general organizational model y Trainings/Certifications are available y Available for download at http://service.sap.com/supportstandards
RunSAP:
SAP provides two major and aligned methodologies along the solution lifecycle.
Run SAP is SAP’s methodology to optimize the implementation and ongoing management of Endto-End Solution Operations. It focuses on establishing efficient support and operations of solutions.
In contradiction to that, the ASAP methodology focuses on efficient and streamlined implementation and upgrade projects.
© SAP AG
SM300
1-6
Roles in E2E Solutions Support
Customer’s Business Unit Global Business Process Champion Regional Business Process Champion
End User Incident and problem management
PMO (Program Management Office) Requests for change
Customer’s IT Organization Application Management Upgrade & life cycle management, application diagnostics
Custom Development
Business Process Operations Integration & automation
SAP NetWeaver Team System diagnostics/administration
IT Infrastructure
SAP Standards available Defined SAP interfaces
© SAP AG 2009
© SAP AG
SM300
1-7
Operations Phase Relevant Content of BPIAM Business Process Performance Optimization Data Volume Management
Optimize business process flow and throughput
Job Scheduling Management Archiving
MRP Run 1000
Backup
MRP Run 2000
Transports
Keep data growth & size under control
Business Process Operations
Billing Run Reorganization
MRP Run 3000
Automate business process while considering time and HW restrictions
Proactively ensure reliable business process flow and throughput
Proactively avoid or detect harmful data inconsistencies
Business Process & Interface Monitoring
Data Consistency Management
© SAP AG 2009
End-to-End Business Process Integration and Automation Management y contains all business process related E2E support procedures, in particular - Integration Management - Performance Management - Automation Management - Data Volume Management - Business Process and Interface Monitoring
All support areas that are part of Integration and Automation are linked with each other. If a job runs too long it has to be considered that this could be because of large data volumes on the data base. An alert in business process monitoring might be caused by a data inconsistency. The report to check the data inconsistency has to be scheduled as part of the Job Scheduling Management etc.
So none of these support areas can be considered on their own but should always be considered in relative to each other.
© SAP AG
SM300
1-8
Purpose of Business Process Integration & Automation Management Business Process
Business Departments
Functional View
Functional process description Functional process operation and control
Business Process Operations Business Process Functional & Technical View
Operations concept for Integration & Automation, including Monitoring objects (alert types, threshold values) Error handling procedures Escalation paths
IT Infrastructure & Technical Operations
Technical View (Process-independent)
Systems OS admin and monitoring DB administration DB backup und recovery Network monitoring Front-end management
Basis/mySAP Technology System log monitoring ABAP dump analysis Performance monitoring Workload monitoring
© SAP AG 2009
Combine functional and technical view for all activities so that the relevance for the core business processes is immediately clear for everything going on in the solution landscape.
© SAP AG
SM300
1-9
BPIAM Related Sample Error Situations
CRM - CDP
CIC employees experience bad response times
Create Sales Order
MRP run takes longer than given time window
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order Failed interface communication
Check Availability
Inconsistencies between material stock in ERP and material stock in Warehouse
Run MRP
Procurement Process
Manufacturing Process
Create Outbound Delivery
No archiving of object SD_VBRK lead to runtimes exceeding given KPIs
Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
Goods Issue posting fails again and again
© SAP AG 2009
These are error sample situations. The are all related to the business activities carried out on the systems, so their management falls into the area of BPIAM.
© SAP AG
SM300
1-10
SAP Standards for BPIAM
SAP Standards for E2E Solution Operations
The following standards fall into the area of Business Process Integration and Automation Management
Business Process & Interface Monitoring and Exception Handling
Job Scheduling Management Data Volume Management
Data Integrity and Transaction Consistency
SAP Standards for E2E Solution Support are available at
http://service.sap.com/supportstandards
© SAP AG 2009
© SAP AG
SM300
1-11
SAP Solution Manager as Central Tool for Integration and Automation SAP Solution Manager as support platform provides Best Practices / Concepts, Tools and Services for Integration & Automation Management Business Integration and Automation Management
SAP Certified Extensions = Integration Packages Performance
Powered by SAP Solution Manager
Wily, Mercury, Microsoft Non-SAP Diagnostics
Management Performance Analysis & Tuning for Business Processes, Support Volume Tests
Business Process & Interface Monitoring Operations Concepts for Business process & Interface alert monitoring
Data Volume Management Control and Avoid Data Growth, Data Archiving
Interface / Adapter
Integration Management
Integrate 3rd party tools to extend functions of SAP Solution Manager
Data Consistency Checks/ Procedures, Concepts for Master Data Distribution & Initial Data Load
Automation Management Concepts for process automation, Job scheduling concepts
IDS Scheer, HP,BMC Monitoring Tools for Non-SAP components
Redwood Job scheduling for SAP / Non-SAP components
© SAP AG 2008
To provide E2E functionality, SAP Solution Manager itself contains or in the future will contain functionality for non-SAP components. Or it will achieve E2E functionality for non-SAP systems by providing defined interfaces to other support tools.
© SAP AG
SM300
1-12
Lesson 2: Introduction to Business Process Monitoring
1. 2. 3. 4.
Introduction to E2E Solution Support Introduction to Business Process Monitoring Initial Customer Situation for Training Initial Situation in SAP Solution Manager Appendix: Create Products, Servers, and Systems
© SAP AG 2009
© SAP AG
SM300
1-13
Why Focus on Business Process Monitoring?
Can you answer the following questions for your Order to Cash process?
How many Sales Orders are open (not or only partially delivered)?
How many Sales Orders cannot be processed any further, because they are incomplete, have a delivery, billing or credit block?
How many outbound deliveries are open (goods receipt posting not complete)?
How many picking transfer orders are open (not confirmed) in your warehouse management system?
How many outbound deliveries have GI posted but no invoice was created?
How many invoices have been created but were not printed?
How many sales invoices were not posted to FI?
If yes, how long does it take to retrieve this information per sales organization, plant or warehouse?
© SAP AG 2009
© SAP AG
SM300
1-14
Why Focus on Business Process Monitoring? Two customer examples: Get Sales Order related data automatically
One person spends daily ~4hours collecting information about Sales Orders manually which have a delivery or billing block or which are open or incomplete SAP Solution Manager provides this data
Automatically & triggers auto-reaction methods if necessary
In a business process context
Ready for BI trend analysis
Identify problem situations that stay unnoticed otherwise
SAP Solution Manager identified
Planned Orders that should have been already converted into Process Orders several days ago
Confirmation errors caused by failed goods movements (COGI) for Process Orders that were several weeks old
© SAP AG 2009
© SAP AG
SM300
1-15
Purpose of Business Process & Interface Monitoring
Customer CRM
SAP R/3 BW Headquarter
Problem occurs in the system landscape Production SCM/APO
Supplier SRM/EBP
Distributor Legacy System • Who reacts? • How? • When is 2nd level informed? • Who is the escalation contact?
What part of the core business process is affected? Warehouse WMS
Subcontractor Legacy System CRM - C00
SAP ENTERPRISE PORTAL - EPP
SAP ECC - TT5
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Run MRP Procurement Process
Manufacturing Process
Create Outbound Delivery Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
© SAP AG 2009
© SAP AG
SM300
1-16
Definition Definition of Business Process Monitoring
Business Process Monitoring is the proactive and process-oriented monitoring of a company’s core business processes
It includes the observation of all technical and application-related functions that are required for a smooth and reliable flow of the core business processes
Goals of Business Process Monitoring
To detect problem situations as early as possible in order to solve them as fast as possible - before they become critical for the business
By introducing SAP Solution Manager:
To provide a central monitoring platform for the entire solution Automated, out of the box, monitoring and reporting functionalities
defined monitoring procedures To enable the customer’s Solution Support Organization to respond to and to solve problems more proactively
© SAP AG 2009
Detect possibly critical situations as early as possible Æ more time to react before the business is impacted
Judge relevance of problems by their impact on core business processes
Make sure that all problems that have an impact on the core business processes are recognized
Recognize dependencies of problems so you can quicker get to the root cause of the problem
© SAP AG
SM300
1-17
Overview – Business Process Monitoring in SAP Solution Manager People
SMS Service Desk Message
Email
Solution Manager Service Level Reporting
BI (ad-hoc) Reporting
Continuous Online
Solution Landscape
ERP
Alert Monitoring
SCM
BI
CRM
© SAP AG 2009
© SAP AG
SM300
1-18
Cross-Application Monitoring Functionalities Cross-Application Monitoring Objects
Background Jobs Dialog Performance (per transaction & function code, per user pattern)
General Application Log (SLG1) Update Errors (Transaction- / Program-specific)
Document Volumes (based on SAP table statistics)
Interface Monitoring Objects
qRFC Alert Monitoring
BDoc Alert Monitoring (CRM)* ALE/IDoc Alert Monitoring per IDoc Type
XI/PI Alert Monitoring Batch Input Monitoring
File Monitoring
tRFC Alert Monitoring*
Workflow Monitoring*
Customer Specific Monitoring Objects
Customer Exit in Application Monitoring Infrastructure All Alert Information available via CCMS Monitoring Infrastructure *functionality with next ST-A/PI 01L © SAP AG 2009
© SAP AG
SM300
1-19
Application-Specific Monitoring Functionalities Application-Specific Monitoring Objects
Enterprise Resource Planning Logistics Sales & Services
Warehouse Management Inventory Management
Enterprise Resource Planning Financials
Customer Relationship Management Sales
Logistics Execution Procurement
Services Customer Interaction Center
Manufacturing Plant Maintenance
Advanced Planner & Optimizer Demand Planning
Quality Management* IS – Utilities
Supply Network Planning
Production Planning /Detailed Scheduling
IS – Banking
Deposits Management (FS-AM) Bank Analyzer
global ATP Extended Warehouse Management
Banking Services IS – Insurance
Strategic Enterprise Management – BCS
IS – Telecommunications *functionality with next ST-A/PI 01L
© SAP AG 2009
© SAP AG
SM300
1-20
Data Consistency Monitoring Functionalities Data Consistency Monitoring Objects
Enterprise Resource Planning Logistics Sales & Services
Warehouse Management Inventory Management
Customer Relationship Management CRM – ECC
Enterprise Resource Planning Financials
CRM – CDB Trade Promotion Management
Leasing
Extended Warehouse Management Supply Chain Management
liveCache - Database CIF-Interface
Generic Intra-system Check
Intersystem Check Custom Developed Consistency Reports
*functionality with next ST-A/PI 01L © SAP AG 2009
© SAP AG
SM300
1-21
Example: Sales Order Management DMS Send Urgent Order
• No. of open Sales Orders • No. of incomplete Sales Orders Perform Order Create Sales Rescheduling Order (V_V2)
• No. of SOs with delivery block • No. of SOs with billing block • No. of SOs with credit block • No. of outbound deliveries created • No. of open outbound deliveries
Job runtime Create Outbound Delivery (VL10A)
• No. of overdue shipments Create Shipment (VT01N)
Create Picking Transfer Order (TO)
• No. of Open Picking TOs
Confirm Picking TO (LT11)
• No. of deliveries with GI posted but no invoice
Post Goods Issue
• No. of invoices not transferred to FI • No. of invoices not printed
ERP Job runtime
Dialog Response Time
Confirm Picking TO with difference
Dialog Response Time
Job runtime
Perform Billing (VF04)
In case of Discrepancies block Discrepancies on Bin in Storage Type 999 • Stock Level in difference storage type • Unblocked stock in difference storage type
© SAP AG 2008
© SAP AG
SM300
1-22
Example: Business Process Monitoring Graphic
© SAP AG 2008
© SAP AG
SM300
1-23
Example: Business Process Details
© SAP AG 2008
© SAP AG
SM300
1-24
Example: Alert Details
© SAP AG 2008
© SAP AG
SM300
1-25
Alert History and Alert Analysis
List of 373 open Transfer Orders on satellite system
© SAP AG 2009
© SAP AG
SM300
1-26
BI Standalone Reporting (Dashboard) Graphical Graphical Analysis Analysis
Open Transfer Orders MUC
Open Transfer Orders FRA
Transfer Orders Munich / Outbound TO items (open) Transfer Orders Frankfurt / Outbound TO items (open)
© SAP AG 2009
© SAP AG
SM300
1-27
BI Standalone Reporting (Dashboard) Tabular Tabular Analysis Analysis
Open TOs MUC Open TOs FRA
© SAP AG 2009
© SAP AG
SM300
1-28
Solution Management Optimization Service for Business Process Management The Solution Management Optimization (SMO) Service for Business Process Management comprises:
The creation of a Business Process Management and Monitoring Concept including the definition of
Monitoring objects
Error handling procedures Escalation paths
Configuration of Business Process Monitoring in the SAP Solution Manager
Wrap up presentation and summarizing service report
The service covers the analysis of 1 or 2 core business processes (depending on their complexity), and its delivery is planned for 2 consultants for 3 to 5 days on-site/remote. This service is exclusively available within an SAP Support Engagement (i.e. SAP MaxAttention and SAP Safeguarding). © SAP AG 2009
© SAP AG
SM300
1-29
Further Information about Business Process Monitoring Further Documentation in Media Library of Quick Link BPM on SAP Service Marketplace service.sap.com/bpm White Paper on standard process „Exception Handling and Business Process & Interface Monitoring“ under service.sap.com/supportstandards
Available class room trainings:
SM300 – Business Process and Interface Monitoring (3 days)
E2E300 – E2E Business Process Integration and Automation Management (5 days including certification)
Check SAP Service Marketplace service.sap.com/education
© SAP AG 2009
© SAP AG
SM300
1-30
Lesson 3: Initial Customer Situation for Training
1. 2. 3. 4.
Introduction to E2E Solution Support Introduction to Business Process Monitoring Initial Customer Situation for Training Initial Situation in SAP Solution Manager Appendix: Create Products, Servers, and Systems
© SAP AG 2009
© SAP AG
SM300
1-31
Company IDES Initial Situation
During the upgrade project company IDES is planning to implement business process „Order to Cash“. Company IDES uses SAP Solution Manager as Project Management tool and is currently in Integration Testing Phase. Based on the business requirements, the experience gathered during the integration testing and similar business processes that are already live they have determined that they need to monitor their business processes in addition to their regular system monitoring activities, to have a truly comprehensive solution monitoring concept.
© SAP AG 2009
© SAP AG
SM300
1-32
Support Organization at IDES
Business Department Production
Business Department Sales Business Process Champion
Business Process Champion
IT Department
Business Process Operations Team
© SAP AG 2009
© SAP AG
SM300
1-33
How IDES is Currently Using SAP Solution Manager
CRM - C00
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Operations Part
Service Desk
System Monitoring
Early Watch Alerts
Run MRP
Procurement Process
Manufacturing Process
Create Outbound Delivery
Implementation Part
Business Blueprint
Project Management
Roadmap
Test Management
Create Billing Document
Post Goods Issue
Warehouse - TT5
Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
© SAP AG 2009
Implementation Part
Project Management: accessible through transaction DSWP > Solution Landscape > Project Scoping
Business Blueprint (Transaction SOLAR01): Business Process Documentation within the Implementation Part of SAP Solution Manager (part of Project Management), similar to Solution Directory of Operations Part
Roadmap: Part of Project Management to document all necessary milestones and steps within a projects
Test Management: Part of Project Management to organize testing for projects
© SAP AG
SM300
1-34
Lesson 4: Initial Situation in SAP Solution Manager
1. 2. 3. 4.
Introduction to E2E Solution Support Introduction to Business Process Monitoring Initial Customer Situation for Training Initial Situation in SAP Solution Manager Appendix: Create Products, Servers, and Systems
© SAP AG 2009
© SAP AG
SM300
1-35
Introduction SAP Solution Manager SAP Solution Manager ...
Takes a consistent businessprocess and phase-oriented approach
End-to-end functionality for application management and continuous improvement
Knowledge Management
Project Management
Test Management
IMPLEMENT OPERATE
Solution Monitoring
Business Process
Provides full life-cycle support and collaboration with SAP
Knowledge Transfer
Contains best practices for implementation, operation and optimization of SAP solutions
Service Desk
OPTIMIZE
Change Management
Service Delivery
Is delivered as part of your annual maintenance fee
Æ Simply everything you need to manage your SAP solution !!! © SAP AG 2009
SAP Solution Manager is an application which provides various functionalities to manage the different stages of your business process life cycle.
Solution Monitoring is one part of the SAP Solution Manager functionalities, intended to help you manage the productive operation of your business processes.
© SAP AG
SM300
1-36
SAP Solution Manager as Central Support Platform
FVS
PLM CUS
CUS SCM
4.6C
Application Support
System Administrator
SAP Solution Manager
SAP Active Global Support
SAP Service Marketplace © SAP AG 2008
SAP Solution Manager can serve as a central access point for your solution support organization. So, instead of having several support tools in use you have one central tool which can be used of all parts of your solution support organization. The system administrator can access information about the status of the systems and associated administrative tasks, while the application support can find information about the status of the business processes running on these systems.
The functionality of the central support platform includes the access to and from SAP. The Solution Manager can be used as a tool to access the SAP Service Marketplace and to create and access your R/3 frontend-messages.
© SAP AG
SM300
1-37
Solution Monitoring in the SAP Solution Manager Early Watch Alert and Service Level Reporting
Weekly evaluation of system status and performance Weekly or monthly reporting on SLAs for the involved systems and business processes
System Monitoring and Administration
Technical real-time monitoring of system components based on the CCMS infrastructure System-related tasks with integrated and automated log
Business Process and Interface Monitoring
Real-time monitoring of business processes and interfaces Covers all technical and business applicationspecific functions required for a smooth and reliable flow of business processes © SAP AG 2008
Solution Monitoring in SAP Solution Manager covers different functionalities y Early Watch Alerts provide you with a weekly evaluation of the status and performance of the systems in your solution landscape. Service Level Reports are weekly or monthly reports on Service Level Agreements within the whole solution landscape (systems and business processes). y System Monitoring covers the technical monitoring of the systems (software components, hardware components). This includes monitoring of for instance CPU utilization, paging, buffer fill status, database performance, general dialog performance etc. System Administration helps you keep track of the manual tasks that have to be carried out on the systems, like checking the system log files or checking for ABAP dumps. y Business Process Monitoring means the technical monitoring of the business process activities being carried out on the system, like monitoring the behavior of background jobs belonging to the business process, monitoring for error entries in application related logs or monitoring of involved interfaces (e.g. error status for specific IDOC types). It includes the definition of monitoring responsibilities, error handling procedures and escalation paths.
© SAP AG
SM300
1-38
Software Components of SAP Solution Manager
SAP Solution Manager System
Relevant for Business Process Monitoring are the following software components on SAP Solution Manager: ST:
SAP Solution Manager Tool (General SAP Solution Manager Infrastructure)
ST-SER:
SAP Solution Manager Service Tools (Service sessions, including BPMon Setup session)
ST-A/PI:
Application Service Tools (Application Monitoring Infrastructure for Business Process Monitoring)
ST-PI:
SAP Solution Tools Plug-In (Integration Job Documentation and BPMon)
BI_CONT:
Business Intelligence Content (BI content for Reporting based on BPMon)
ST ST-SER
ST-A/PI ST-PI
BI_CONT
© SAP AG 2008
Basis of a SAP Solution Manager 7.0 is a CRM 5.0 system. Some parts of SAP Solution Manager, like the Service Desk, use CRM functionalities. The core functionality of Business Process Monitoring in the SAP Solution Manager, however, does not use CRM functionalities.
© SAP AG
SM300
1-39
System Landscape Containing SAP Solution Manager
SAP Solution Manager installed on a dedicated system
BW BW
SAP SAP R/3 R/3
Satellite systems connected to SAP Solution Manager via RFC
Satellite systems have to be defined in SAP Solution Manager to make functionality available for them
SAP SAP Solution Solution Manager Manager
CRM CRM
APO APO
IMS IMS
© SAP AG 2008
SAP Solution Manager is installed on a dedicated system. If SAP Solution Manager functionality should be used for a system in the system landscape it has to be connected to SAP Solution Manager via RFC destinations. These connected systems are called “satellite systems”.
© SAP AG
SM300
1-40
How to Tailor Solutions
When tailoring your solutions you have to consider the following
Authorizations Concept
Authorizations are based on solutions and functionality z
inside a solution you cannot restrict authorizations based on business processes, monitoring objects, systems or business process steps
Organizational Concept
One team should not have to handle too many solutions Solution structure should reflect the organizational structure
© SAP AG 2009
1. Business Process Documentation. y it has to be clear which solutions contain the current information for the business processes and which business process is contained within which solution. y one business process has to be entirely within one solution and cannot not spread across several solutions.
2. System Monitoring
System Monitoring can be done for all systems in a solution (also those NOT in the leading role of the solution) y Not more than 1000 alerts should be within one solution. If you cannot monitor all system within the solution, you restrict yourself to the systems in the leading role.
3. Business Process Monitoring
Can be done only for the systems in the leading role of the solution. So you cannot monitor on the development system and the productive system within one solution. y If the monitoring is supposed to be used during testing on QAS or DEV, a solution can be created for that purpose and deleted after the testing has finished.
4. Service Level Reporting
System have to be in one solution to create one SLR for them
© SAP AG
SM300
1-41
How to call SAP Solution Manager
The Operations part of SAP Solution Manager is called via transaction /nDSWP. There are several other transactions to call different functional areas of SAP Solution Manager.
© SAP AG 2009
When calling the transaction you always get to the screen in the Operations part of SAP Solution Manager that you last were in.
There are several other transactions to call the Operations part of SAP Solution Manager, namely /nsolution_manager and /ndsmop.
© SAP AG
SM300
1-42
Entering SAP Solution Manager for the First Time
When you enter the Operations part of SAP Solution for the very first time you are brought to the Solution Overview Screen.
Solution Overview Screen
When you enter the Operations part of SAP Solution Manager afterwards, you are always brought to the last screen you were in.
Main Screen
© SAP AG 2009
If you don’t see the navigation panel in the Main Screen, look for the small arrow to open the panel.
Via “Solution Overview” in the Main Screen of the Operations part you can switch to the solution overview screen or switch solutions (drop-down menu).
© SAP AG
SM300
1-43
Creating a Solution in SAP Solution Manager
In order to create a Solution choose Create in the Entrance Screen of the SAP Solution Manager and specify all the required information in the next screen.
© SAP AG 2009
You can delete solutions after they have been created. You can also split solutions. You can not merge solutions.
© SAP AG
SM300
1-44
Exercise
Exercise: Create Solution
© SAP AG 2009
© SAP AG
SM300
1-45
Maintaining System Landscape in SAP Solution Manager
Satellite Systems have to be defined in SAP Solution Manager
System Landscape is basis for many functionalities
Cross solution documentation
Entries can be maintained automatically or manually
Regular background jobs update system information (like installed software components)
BW BW
SAP SAP R/3 R/3 SAP SAP Solution Solution Manager Manager
CRM CRM
APO APO
IMS IMS
© SAP AG 2009
In order to use SAP Solution Manager as central support tool for your systems you have to define your system landscape.
The definition of the system landscape is basis for several functionalities. All solutions use the information available in the system landscape, thus changes to the system landscape can have an enormous impact and should be executed with careful prior deliberation.
You can automatically load the system landscape information from an SLD or your transport management system. You can also manually maintain entries in the system landscape.
© SAP AG
SM300
1-46
How to Identify a System in SAP Solution Manager
To identify satellite systems in SAP Solution Manager you have to provide the following information:
Product Information
SAP Products are available in the System Landscape Maintenance and do not have to be created again
non-SAP products have to be created in the System Landscape Maintenance so that non-SAP systems can be maintained in the system landscape
Server Information
is the basis for the creation of RFC destination from within the system landscape contains hardware information, like IP address, hardware provider etc.
System Information
linking the product information and the sever information to the system
for SAP systems: providing z
installation number
z
client SAP server names
z
© SAP AG 2009
You can also define databases in the System Landscape and link these to the relevant systems. For Business Process Monitoring, it is not required to maintain databases.
© SAP AG
SM300
1-47
Procedure for System Landscape Maintenance
System Landscape Maintenance Here you have to create, in this order: Products Servers Systems Logical Components
A detailed description on how to create Products, Servers, and Systems can be found in the appendix of this unit.
© SAP AG 2009
Products and Servers are unrelated information, so you can also create servers before you create products. However, both need to be available before you can create the system.
The creation Products, Servers, and Systems in the System Landscape Maintenance is not part of this training, but you can find a detailed description on how to create Products, Servers, and Systems within the appendix of this Unit.
© SAP AG
SM300
1-48
System Maintenance in the SAP Solution Manager
Choose Operations Setup Æ Solution Landscape Æ System Landscape Maintenance in the Main Screen of SAP Solution Manager
© SAP AG 2008
In the area Solution Landscape in the Operations Setup you can also maintain your solution landscape, your projects and your solution settings.
© SAP AG
SM300
1-49
Logical Components System in the system landscape can be logically grouped.
DEV ERP PRD Portal QAS ERP
QAS CRM PRD CRM DEV CRM
QAS Portal
DEV Portal
PRD ERP
The development ERP system logically forms a unit with the QAS ERP system and the productive ERP system. In SAP Solution Manager this unit is called Logical Component. All systems within a logical component must be of the same product. Different clients of an SAP system can belong to different logical components.
DEV ERP client 200
QAS ERP client 200
PRD ERP client 200
Logical Component Z_ERP
© SAP AG 2009
© SAP AG
SM300
1-50
Create Logical Component 1/2 1. Products 2. Servers 3. Systems 4. Logical Components
Specify information and confirm the pop-up..
© SAP AG 2009
The identifier of the logical component has to be in the customer name space.
The selection of the product and the main instance determines which systems you can assign to this logical component. This means that you cannot assign a CRM system and an SCM system to the same logical component. It also means that you cannot assign the BI system and the Enterprise Portal installed within an SAP NetWeaver to the same logical component.
© SAP AG
SM300
1-51
Create Logical Component 2/2 1. Products 2. Servers 3. Systems 4. Logical Components
Set the status of the logical component to “Active”. Assign the relevant systems by using the value help. SAP application servers have to be assigned with SID and client. © SAP AG 2009
Save.
A logical component represents a transport path. It could for instance consist of development system Æ quality assurance system Æ production system. You can assign the various systems to the logical component separately. Most SAP systems usually are assigned with the relevant client.
© SAP AG
SM300
1-52
Exercise
Exercise: Create Logical Component
© SAP AG 2009
© SAP AG
SM300
1-53
Appendix
Appendix
© SAP AG 2009
© SAP AG
SM300
1-54
Appendix: Create Products, Servers, and Systems
1. 2. 3. 4.
Introduction to E2E Solution Support Introduction to Business Process Monitoring Initial Customer Situation for Training Initial Situation in SAP Solution Manager
© SAP AG 2009
© SAP AG
SM300
1-55
Procedure for System Landscape Maintenance
System Landscape Maintenance Here you have to create, in this order: 1. Products 2. Servers 3. Systems 4. Logical Components
A detailed description on how to create Products, Servers, and Systems can be found in the appendix of this unit. © SAP AG 2009
Products and Servers are unrelated information, so you can also create servers before you create products. However, both need to be available before you can create the system.
The creation Products, Servers, and Systems in the System Landscape Maintenance is not part of this training, but you can find a detailed description on how to create Products, Servers, and Systems within the appendix of this Unit.
© SAP AG
SM300
1-56
Create Products 1/2 1. Products
Products are created via button “Other Object” or Ctrl+ F5. Specify
Product Key (has to be in customer name space) Product Name
Description
© SAP AG 2009
The pop-up to create new product can also be reached by executing a right mouse click on any product and choosing §Create additional product”. The right mouse click to create a product can be executed either on the node “Products” or any available product.
SAP Products are provided with the installation of the SAP Solution Manager and do not have to be explicitly defined.
© SAP AG
SM300
1-57
Create Products 2/2 1. Products
The product has to be set to “Active”. In addition, you have the provide a product version.
© SAP AG 2009
© SAP AG
SM300
1-58
Create Servers 1/2 1. Products 2. Servers
Servers are created via button “Other Object” or Ctrl+ F5. Specify the server name and save.
© SAP AG 2009
© SAP AG
SM300
1-59
Create Servers 2/2 1. Products 2. Servers
In tab “Technical Data” specify information so that the server can be identified.
© SAP AG 2009
The server information is the basis when later creating the RFC destinations from within the System Landscape Maintenance. Identify IP address and router information so that the RFC destinations can be created.
© SAP AG
SM300
1-60
Create System 1/2 1. Products 2. Servers 3. Systems
Systems are created via button “Other Object” or Ctrl+ F5. Specify the System ID and the product/version. For SAP systems you also have t specify the installation number. Save. © SAP AG 2009
© SAP AG
SM300
1-61
Create System 2/2 1. Products 2. Servers 3. Systems
You have to select at least one relevant main instance. For each main instance a sub-node is created in the navigation tree.
© SAP AG 2009
In order to use Business Process Monitoring on a system, it must not be set to “Planned” in tab “Header Data” in node .
For SAP system, you have to provide the following information in tab “Header Data” in node : y Message Server (via value help) y System Number.
In tab “Client” specify the client that is supposed to be monitored.
© SAP AG
SM300
1-62
Relevant Main Instance of System
One system can have several components installed that logically are different components. Select the components that have been installed on the satellite system. For Business Process Monitoring, normally the SAP Application Server has to be selected.
© SAP AG 2009
Example: An ERP system can have several components installed: y SAP ECC Server y BI in the NetWeaver stack y SAP Enterprise Portal in the NetWeaver stack
In this case you have to select 3 main instances for the ERP system.
© SAP AG
SM300
1-63
© SAP AG
SM300
1-64
Exercises Unit:
Introduction to Business Process & Interface Monitoring
Lesson:
Initial Situation in SAP Solution Manager
Exercise 1: Create a Solution At the conclusion of this exercise, you will be able to: • Create a solution landscape in SAP Solution Manager • Navigate in SAP Solution Manager TT4 is the SAP Solution Manager system for the company IDES. There they eventually want to configure monitoring for their business process “Order-to-Cash”.
1-1
Create a Solution Landscape 1-1-1
Name two transactions to call the operations part of SAP Solution Manager: Answer: ______________________________________________
1-1-2
Create a Solution Landscape in the operations part of your SAP Solution Manager with the following data: • Solution Name “SM300-## Landscape” (## = your group number) • Original Language “EN”
1-1-3
Navigate to the Business Process Monitoring area in the Operations part of your solution. Note down what you can see: Answer:______________________________________________________
1-1-4
Navigate to the Business Process Monitoring area in the Operations part of solution “SM300 Master Solution”. Note down what you can see: Answer:______________________________________________________
1-1-5
Call transaction /nDSWP again. Which screen are you brought to? Answer:______________________________________________________
1-1-6
© SAP AG
Change back to your solution.
SM300
1-65
© SAP AG
SM300
1-66
Solutions Unit:
Introduction to Business Process & Interface Monitoring
Lesson:
Initial Situation in SAP Solution Manager
Exercise 1: Create a Solution
1-1
Solution to step “Create a Solution Landscape” 1-1-1
/nDSWP, /nSOLUTION_MANAGER, /nDSMOP
1-1-2
Call /nDSWP Æ Create. In the subsequent screen enter the field information.
1-1-3
Go to Operations Æ Solution Monitoring Æ Business Process Monitoring. There is no graphic yet, only the information: There are no production processes.
1-1-4
Go to Solution Overview and choose solution SM300 Master Solution. Choose Operations Æ Solution Monitoring Æ Business Process Monitoring. There you can see business process Order-to-Cash and the Data Consistency Cockpit.
1-1-5
You are brought back to screen Operations Æ Solution Monitoring Æ Business Process Monitoring of solution SM300 Master Solution, the last screen you were in before calling the transaction again.
1-1-6
Go to Solution Overview and choose solution SM300-## Landscape (## = your group number).
© SAP AG
SM300
1-67
© SAP AG
SM300
1-68
Exercises Unit:
Introduction to Business Process & Interface Monitoring
Lesson:
Initial Situation in SAP Solution Manager
Exercise 2: Create a Logical Component At the conclusion of this exercise, you will be able to: • Create Logical Components in SAP Solution Manager
Basis for the monitoring with SAP Solution Manager is that the systems in the system landscape have been grouped into logical components.
2-1
Logically, the systems in the landscape of IDES are used as follows:
Portal
SAP ECC systems
non SAP CRM systems
TP5
TD5
TQ5
TT5
ERP : client 800
ERP : client 800
ERP : client 800
Warehouse : client 600
Warehouse : client 600
Warehouse : client 600
CDE
CDQ
CDP
Development systems
2-1-1
Quality assurance systems
Production systems
Question: How many logical components are required as basis for business process “Order to Cash”? Answer: _____________________________________________________________
2-1-2 © SAP AG
Check which matching logical components already exist in the system landscape? SM300
1-69
System
Client
Logical Component
2-1-3
Maintain missing logical components in the system landscape in TT4. Choose meaningful names for the logical components (name should contain the associated product and your group number ##). Make a note which system belongs to which logical component in the table above.
2-1-4
Can system CQA and system TT5 belong to the same logical component? Answer:______________________________________________________
2-1-5
Can system TT5 client 800 and system TT5 client 600 belong to the same logical component? Answer:______________________________________________________
© SAP AG
SM300
1-70
Solutions Unit:
Introduction to Business Process & Interface Monitoring
Lesson:
Initial Situation in SAP Solution Manager
Exercise 2: Create a Logical Component
2-1
Solution to System Landscape Maintenance 2-1-1
2-1-2
Answer: You need 4 logical components for business process “Order to Cash”: •
one component for the Portal
•
one component for client 800 on TT5, TQ5 and TD5 (ERP system)
•
one component for client 600 on TT5, TQ5 and TD5 (Warehouse system)
•
one component for the non-CRM system, containing CDE, CQA and CDP
The following logical components already exist:
System
Client
Logical Component
2
TP5 1
TT5 TQ5
5
TD5 C h TT5 o o TQ5 s e
TD5
Z_EP Z_ECC
800 800 800
Z_WAREHOUSE
600 600 600
S CDE y s CQAt
no logical component yet exists that contains all three of these systems, create component Z_CRM-##
CDP
© SAP AG
SM300
1-71
2-1-3
Choose Landscape Components Æ Other Object (Shift F5), mark Logical Component and choose the blank page to create a new logical component. Alternatively, you can execute a right mouse click on System Groups and Logical Components Æ Logical Components in the tree. Create one new logical component this way: One logical component Z_CRM-## (## = group number) for product nonSAP CRM. In node Z_CRM-## assign the systems in tab Current System Assignments.
2-1-4
Answer: Systems within one logical component must have the same product. Therefore systems of different product cannot belong to the same logical component, hence CQA and TT5 cannot be in one logical component.
2-1-5
Answer: Technically system TT5:800 and TT5:600 can belong to the same logical component. Logically this would be wrong. Both client 600 and 800 are used as productive clients. A logical component can only have one system/client in the production role, so TT5:600 and TT5:800 should belong to different logical components.
© SAP AG
SM300
1-72
Procedure
Course Overview Unit 1 Introduction to Business Process Monitoring Unit 2 Procedure Unit 3 Monitoring Configuration Unit 4 Using Business Process Monitoring
Unit 8
Data Consistency Monitoring
Unit 5 Cross-Application Monitoring
Unit 9
Reporting
Unit 6 Application Monitoring Unit 7 Interface Monitoring
Unit 10 Handover to Production Unit 11 Managing Jobs in SAP Solution Manager
© SAP AG 2008
© SAP AG
SM300
2-1
Business Process Monitoring: Unit Objectives
After completing this unit, you will:
know how to define and create a monitoring concept
be able to create a business process in SAP Solution Manager
know the necessary steps to set a monitoring project productive
© SAP AG 2009
© SAP AG
SM300
2-2
Overview of Procedure
1. 2. 3. 4. 5. 6.
Overview of Procedure Business Process Analysis Definition of Monitoring Activities Integration into Support Organization Definition of Reporting Activities GoLive with Monitoring
© SAP AG 2009
© SAP AG
SM300
2-3
Initial Situation
Company IDES wants to create a concept for monitoring business process “Order-to-cash”
CRM - CDP
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Run MRP
Procurement Process
Manufacturing Process
Create Outbound Delivery Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
© SAP AG 2009
The project team wants to ensure that the business process “Order to cash” is monitored properly with the GoLive. Therefore, the concept of what should be monitored how and with which tools is developed by the project team.
© SAP AG
SM300
2-4
Starting Point for Business Process and Interface
Strategic Strategic Framework Framework
Technical Technical Technical Technical and and and Operations and Integration Integration Operations Design Implementation Design Implementation
Define Define and and Create Create aa Monitoring Monitoring Concept Concept
Implement Implement the the Monitoring Monitoring Concept Concept
Cutover Cutover and and Start Start of of Production Production
Start Start Monitoring Monitoring
Operations and Continuous Improvement
Continuous Continuous Improvement Improvement
Ideal Starting Point:
Creation of Monitoring concept started during the “Technical and Integration Design” phase of implementation project
Later Starting Points:
Establishing a Business Process and Interface Monitoring concept can be started during a later phase of at any time during the productive operation of the business processes.
© SAP AG 2009
A Business Process Monitoring concept is part of the operations concept for the entire solution. It should ideally be established during the implementation phase of a project and be handed over to productive operations with the GoLive of the business processes. This way, the monitoring can be already used during the user acceptance text and the GoLive support, and this way the business processes are already properly monitored after they have gone live.
© SAP AG
SM300
2-5
Implementation Methodology for Business Process and Interface Monitoring Define Define and and Create Create aa Monitoring Monitoring Concept Concept
Step Step 11 Identify Identify core core business business processes processes
Implement Implement the the Monitoring Monitoring Concept Concept
Step Step Step 22 Step 33 Identify Identify Identify Identify process business process steps steps business and requirements and interfaces interfaces requirements regarding regarding process process execution execution
Step Step Step 77 Step 66 Define Assign Assign Define communication monitoring monitoring communication and activities activities to to and escalation escalation procedures responsibles responsibles procedures
Start Start Monitoring Monitoring
Continuous Continuous Improvement Improvement
Step Step Step 44 Step 55 Define Define Define Define monitoring monitoring monitoring monitoring objects, activities objects, alerts alerts activities and and thresholds thresholds
Step Step 88 Define Define Reporting Reporting Objects Objects and and Reporting Reporting Activities Activities
Step Step Step 99 Step 10 10 Define Assign Define Assign communication reporting communication reporting and activities and escalation escalation activities to to procedures responsibles procedures responsibles
© SAP AG 2009
Creating a Business Process Monitoring concept consists of several steps. Before you can actually set up any monitoring you have to identify the critical business processes, process steps and interfaces. According to the business requirements regarding availability, performance and throughput you can determine monitoring requirements and based on those monitoring requirements define monitoring objects (exactly which transaction, job etc. has to be monitored for which alerts with which thresholds), error handling and escalation procedures (what has to be done in case of problems) and finally monitoring activities (who has to carry out the actual monitoring task, how often, using which tools).
Steps 1-7 cover the setup of an alerting concept , whilst steps 8-10 cover the setup of a reporting concept.
The details for the steps within the roadmap are explained in the following slides.
© SAP AG
SM300
2-6
Business Process Analysis
1. 2. 3. 4. 5. 6.
Overview of Procedure Business Process Analysis Definition of Monitoring Activities Integration into Support Organization Definition of Reporting Activities GoLive with Monitoring
© SAP AG 2009
© SAP AG
SM300
2-7
Relevant Steps in Implementation Methodology Define Define and and Create Create aa Monitoring Monitoring Concept Concept
Step Step 11 Identify Identify core core business business processes processes
Implement Implement the the Monitoring Monitoring Concept Concept
Step Step Step 22 Step 33 Identify Identify Identify Identify process business process steps steps business and requirements and interfaces interfaces requirements regarding regarding process process execution execution
Step 6 Step 7 Define Assign communication monitoring and escalation activities to procedures responsibles
Start Start Monitoring Monitoring
Step 4 Define monitoring objects, alerts and thresholds
Step Step 88 Define Define Reporting Reporting Objects Objects and and Reporting Reporting Activities Activities
Continuous Continuous Improvement Improvement
Step 5 Define monitoring activities
Step 9 Step 10 Define Assign communication reporting and escalation activities to procedures responsibles
© SAP AG 2008
Identify core business processes by estimating the financial impact of business process standstill.
© SAP AG
SM300
2-8
Goal of Business Process Analysis
Identify business processes that are crucial for the success of the company (core business processes)
Provide Business Process Information and Requirements relevant for support operations, including
Business process flow Technical details for business process steps and interfaces Volume Information and Time restrictions
Goal is to provide documentation to assist with the support of the business process as opposed to end user documentation
© SAP AG 2009
© SAP AG
SM300
2-9
Identify Core Business Processes
Step 1 Identify core business processes
Step 2 Step 3 Step 4 Step 5 Identify Identify business Define Define process requirements monitoring monitoring activities steps and regarding process objects, alerts interfaces execution and thresholds
Step 6 Define communication and escalation procedures
Step 7 Assign monitoring activities to responsibles
Responsible:
Business Department
Core Business Process:
Business process critical for the success of the company Generates the bulk of the income
Example: Company IDES:
produces and sells pumps, motorcycles, PC’s and light bulbs
“Order to Cash” is a core business process If process “Order to Cash” is down IDES company cannot sell any goods and therefore does not generate any income from sales © SAP AG 2009
Determine for each business process: y Business process owner y Dependencies on other business processes y Process availability y Process time constraints y Document volume to be processed y Process restart ability.
© SAP AG
SM300
2-10
Identify Process Steps and Interfaces
Step 1 Identify core business processes
Step 2 Step 3 Step 4 Step 5 Identify Identify business Define Define process requirements monitoring monitoring activities steps and regarding process objects, alerts interfaces execution and thresholds
Step 6 Define communication and escalation procedures
Step 7 Assign monitoring activities to responsibles
Responsible:
Business Department, in collaboration with 2nd level Application Support
Business Process Steps and Interfaces:
Graphical representation of business process flow
Details for business processes and interfaces, including Execution mode (dialog transaction, program or report etc.) Corresponding software component Dependencies on other process steps Interface techniques
© SAP AG 2009
© SAP AG
SM300
2-11
Example: Identify Process Steps and Interfaces
CRM - CDP
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Run MRP
Procurement Process
Manufacturing Process
Create Outbound Delivery Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
© SAP AG 2008
Document the process flow, including the business process steps and interfaces.
Document technical details.
© SAP AG
SM300
2-12
Identify Business Requirements Regarding Process Execution
Step 1 Identify core business processes
Step 2 Step 3 Step 4 Step 5 Identify Identify business Define Define process requirements monitoring monitoring activities steps and regarding process objects, alerts interfaces execution and thresholds
Step 6 Define communication and escalation procedures
Step 7 Assign monitoring activities to responsibles
Responsible:
Business Department, in collaboration with 2nd level Application Support
Business Requirements:
For entire business process and for parts of the business process
Time restrictions on execution of single steps or sequence of steps within business process
Availability requirements for business process or steps/interfaces within business process
Throughput requirements Performance requirements
© SAP AG 2009
© SAP AG
SM300
2-13
Example: Identify Business Requirements CRM - CDP
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Run MRP
Procurement Process
Manufacturing Process
Create Outbound Delivery Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
Relative Object
Details
Business Requirement
Business Process
“Order to Cash”
Business process has to run without interruption Process flow shout be finished least 6000 times per day
Business Process Step
“Create Outbound Delivery” on ECC
Document volume (6000 deliveries with an avg. of 15 line items per document) Performance of transaction acceptable
© SAP AG 2008
© SAP AG
SM300
2-14
Business Process Documentation in SAP Solution Manager Business Process Documentation can be either maintained via Business Blueprint or in the Implementations part in the Solution Directory of the Operations part
Graphical Documentation of Business Process
Integration to Process description from Implementation project (Copying, but no direct linkage and no synchronization)
Documentation of: Technical details for business
process steps and interfaces (reports, transactions) Fallback Scenario Business Process Champion Business Requirements
Interface to ARIS Toolset
© SAP AG 2009
© SAP AG
SM300
2-15
Business Process Documentation in Operations Part of SAP Solution Manager Business Process in the Operations part needs to be maintained in the Solution Directory. This Solution Directory is accessible via Solution Landscape Æ Solution Landscape Maintenance.
© SAP AG 2009
The Solution Directory is the central point for maintaining business processes in SAP Solution Manager. Here, you can assign logical components to your solution landscape, can create business processes and copy business processes from implementation projects or other sources. You can also maintain your solution settings (like name of the solution) here.
© SAP AG
SM300
2-16
Assign Logical Components to Solution Go to the parent node in the tree. There, access tab System Group and define the leading role of the solution. Then use the value help to assign the relevant logical components to the solution.
© SAP AG 2009
Business Processes are executed on logical components. Before you can maintain a business process you therefore have to assign the concerned logical components to the solution landscape.
The leading role of the solution determines which system of the logical components Business Process Monitoring will be executed on once its active.
Once logical components have been assigned to the solution, you can no longer change the leading role of the solution.
In node you can also change the solution settings (tab “Solution Settings”) like what day of the week the Early Watch Alert data is supposed to be processed and for what systems the EWA should be processed within this solution.
© SAP AG
SM300
2-17
Pop-Up for Logical Components Select the relevant Logical Components. Make sure that these have a system (and client) assigned in the leading role of the solution. Confirm.
© SAP AG 2008
For the logical components you want to assign, you need to have a system (and for SAP Application servers a client) assigned to the leading role of the solution. Otherwise you will not be able to set your business process to active.
© SAP AG
SM300
2-18
Logical Components Assigned to Solution Once the logical components are assigned to the solution you can see the systems in the leading role of the solution in tab System Group. Here you can also delete the assignment of the logical components to the solution should this be necessary.
© SAP AG 2009
In order to delete the assignment of a logical component to a solution, you have to ensure that no business process steps within the solution are executed on this logical component. Otherwise you’ll get an error message when trying to delete the assignment.
You can only delete the assignment here. The logical component itself can only be deleted in the System Landscape.
© SAP AG
SM300
2-19
Hierarchy Levels in Business Process Documentation Business Scenario Business Process Business Process Step Business Process Step ...
You have 3 hierarchy levels available for Business Process Documentation in SAP Solution Manager:
Business Scenario
Business Process
Business Process Step
Business Process Business Process Step Business Process Step ...
... © SAP AG 2009
Example for company IDES business process “Order to Cash”: y Business Scenario: Outbound Logistics y Business Process: Order to Cash y Business Process Steps: - Create Sales Order - Check Availability - Run MRP - ...
© SAP AG
SM300
2-20
Create a Business Scenario In the tree go to node Æ Business Scenarios. There, in tab “Structure” enter the name of the scenario and set the status to “Production”. Save.
© SAP AG 2009
You have to set the status to “Production” if you later on want to activate Business Process Monitoring for the business processes within this business scenario.
You can also copy entire business scenarios from different solutions, from the template library or from an implementation project.
© SAP AG
SM300
2-21
Copying Business Processes from Implementation Project Go to node Æ Business Scenarios Æ Æ Business Processes. There in tab “Structure” select source “Project”. Then use the value help for the process name to access the business blueprint information of projects available in SAP Solution Manager.
© SAP AG 2009
The copy-functionality is available on all 3 hierarchy levels within the business process documentation. The usage of the copying is always the same: y In the node for your hierarchy level go to tab “Structure” y Select your source. y Use the value help to copy the information via a pop-up.
As a source, you always have the following possibilities: y Project - uses business blueprint information defined within any project in the Implementations part of SAP Solution Manager y Solution - uses business process documentation in any solution in the Operations part of SAP Solution Manager y Business Process Repository - uses a template library of standard business scenarios and business processes delivered by SAP
© SAP AG
SM300
2-22
Popup in Value Help
;
Navigate to the business process you want to copy. By clicking on the process name you can display the process flow. Choose “Copy” to copy the flow into your solution. © SAP AG 2009
© SAP AG
SM300
2-23
Assigning Logical Components
If not enough logical components have been assigned to your solution to display the logical component, SAP Solution Manager automatically assigns missing logical components to the solution. Confirm the popup.
© SAP AG 2009
You cannot influence which logical components are copied to your solution.
© SAP AG
SM300
2-24
Set Status to “Production”
To use BPMon for the process you have to set the status to “Production”,
© SAP AG 2009
When you copy a business process, the status for the process is per default set to “Planned”. You have to set status “Production” manually.
You can only set the status for the process to “Production” if there are systems in the leading role for all involved logical components.
Your business scenario has to be in status “Production” to contain productive business processes. If the scenario is in status “Planned” and you change the process status to “Production” you will get a pop-up informing you that the status for the scenario will be changed with the status of the process.
© SAP AG
SM300
2-25
Adding Business Process Steps
Go to node Æ Business Scenarios Æ Æ Business Processes
Æ In tab “Structure” add business process steps or change assignment to logical components. Save.
© SAP AG 2009
If you change the assignment of the logical component, you might get a warning if the new logical component belongs to a different product. You can ignore this warning (close the popup).
© SAP AG
SM300
2-26
Changing Layout of Graphic
In the same node, go to tab “Graphic” to change the layout of the business process. Use drag-and-drop to change the size and layout of the boxes in the graphic.
© SAP AG 2008
You have to save changes you have applied to tab “Structure” so that you can access the graphic in change mode.
© SAP AG
SM300
2-27
Interface Maintenance in Graphic
Execute a right mouse click on the sending business process step. Choose “Create Line (synchronously)” or “Create Line (asynchronously)”. Then execute a right mouse click on the receiving step and choose “Create Line”.
© SAP AG 2009
Asynchronous lines enter and leave the boxes on the top and on the bottom, synchronous lines enter and leave boxes to the sides.
You cannot directly define the layout of the interface. The lines are drawn based on the interface type and the layout of the involved business process steps.
© SAP AG
SM300
2-28
Properties within the Business Process Graphic Via right mouse click on any box within the graphic you can access the properties for the box. In the properties you can maintain the size, style and alignment of the text and assign a color to the box. Right mouse click.
© SAP AG 2009
For business process steps the detailed properties are visible by choosing “Show Details” in the popup.
© SAP AG
SM300
2-29
Specify Processing Details In node in tab Transactions you can assign processing information for the respective business process step. This includes reports, transactions, URLs etc.
© SAP AG 2009
You can use the information you have entered here later on as basis for Business Process Monitoring or Service Level Reporting in SAP Solution Manager.
© SAP AG
SM300
2-30
Exercise: Create Business Process in SAP Solution Manager
Exercise: Create Business Process in SAP Solution Manager
© SAP AG 2009
© SAP AG
SM300
2-31
Definition of Monitoring Activities
1. 2. 3. 4. 5. 6.
Overview of Procedure Business Process Analysis Definition of Monitoring Activities Integration into Support Organization Definition of Reporting Activities GoLive with Monitoring
© SAP AG 2009
© SAP AG
SM300
2-32
Relevant Steps in Implementation Methodology Define Define and and Create Create aa Monitoring Monitoring Concept Concept
Step 1 Identify core business processes
Implement Implement the the Monitoring Monitoring Concept Concept
Step 2 Step 3 Identify Identify process steps business and interfaces requirements regarding process execution
Step 6 Step 7 Define Assign communication monitoring and escalation activities to procedures responsibles
Start Start Monitoring Monitoring
Continuous Continuous Improvement Improvement
Step Step Step 44 Step 55 Define Define Define Define monitoring monitoring monitoring monitoring objects, activities objects, alerts alerts activities and and thresholds thresholds
Step Step 88 Define Define Reporting Reporting Objects Objects and and Reporting Reporting Activities Activities
Step 9 Step 10 Define Assign communication reporting and escalation activities to procedures responsibles
© SAP AG 2008
© SAP AG
SM300
2-33
Define Monitoring Objects, Alerts and Thresholds
Step 1 Identify core business processes
Step 2 Step 3 Step 4 Step 5 Identify Identify business Define Define process requirements monitoring monitoring activities steps and regarding process objects, alerts interfaces execution and thresholds
Step 6 Define communication and escalation procedures
Step 7 Assign monitoring activities to responsibles
Responsible:
2nd level Application Support, in collaboration with Business Department
Monitoring Objects:
Translate Business Requirements for business process into monitoring requirements
Based on monitoring requirements, the monitoring object is defined (what is supposed to be monitored)
For the monitoring object alert is defined (what is the possibly critical situation I want to be informed about)
For the alert thresholds are defined (how critical is the observed situation)
© SAP AG 2009
© SAP AG
SM300
2-34
Monitoring Requirements
To find monitoring requirements go through the business process step by step and interface by interface and determine requirements for the following areas:
Errors
Performance
Throughput
Backlog
Example
Errors:
Update Errors Errors in Application Log Dumps Job doesn’t start Job cancels
Performance:
Throughput:
Outbound Deliveries Throughput
Outbound Deliveries Item Throughput
Backlog:
Dialog Performance VL10 Runtime Background Job
Old open Outbound Deliveries
© SAP AG 2009
© SAP AG
SM300
2-35
Example: Define Monitoring Objects, Alerts and Thresholds CRM - CDP
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Run MRP
Procurement Process
Manufacturing Process
Create Outbound Delivery Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
Monitoring Object
Alert
Thresholds
Outbound Delivery Creation
Number of open outbound deliveries for shipping point 1000 that are older than 5 days
>20 total is noteworthy
Runtime of delivery due list run
> 10 min is noteworthy
>50 total is critical
> 20 min is critical
© SAP AG 2008
Different thresholds for different severities
Business Requirements: Process should be able to process 6000 orders daily, processing of entire business process should not take more than 10 days
After talking to the business it was determined that once the material was available the material should be sent to the customer within 7 days. 99% of the materials are sent within 3 days. Therefore monitoring the number of outbound deliveries that have been open (not delivered) for more than 5 days was determined as monitoring object.
© SAP AG
SM300
2-36
Define Monitoring Activities
Step 1 Identify core business processes
Step 2 Step 3 Step 4 Step 5 Identify Identify business Define Define process requirements monitoring monitoring activities steps and regarding process objects, alerts interfaces execution and thresholds
Step 6 Define communication and escalation procedures
Step 7 Assign monitoring activities to responsibles
Responsible:
2nd level Application Support
Monitoring Activities:
Which tool is used for monitoring the object
With which frequency is the object monitored
What exactly has to be done to monitor the object
What is the business relevance of an alert situation
What can be done in alert situations (error handling procedures)
Where is all information regarding the monitoring activity accessible to the operator executing the activity (central access point for error handling procedures)
Which information should be logged where for further purpose
© SAP AG 2009
For the error handling procedures in some cases input from the business department may be required. It might be that some error handling procedures can only be carried out by the business department (like completing a customer address, creating order for different material etc).
© SAP AG
SM300
2-37
Example: Define Monitoring Activities CRM - CDP
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Run MRP Procurement Process
Manufacturing Process Create Outbound Delivery Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
Monitorin g Object
Alert
Business Relevance
Tool
Monitoring Procedure
Frequency
Error Handling
Log Book
Outbound Delivery Creation
Number of open outbound deliveries for shipping point 1000 that are older than 5 days
Materials in open deliveries have not been sent to customer
VL06G
Call transaction, select shipping point 1000, execute, sort by date, check number of entries
Daily between 16:00 and 17:00
Check status of materials in warehouse Solve error situation for transfer order Contact business to confirm transfer orders
Log number of open deliveries Report contact to business
© SAP AG 2008
Open deliveries in this example are those deliveries where goods issues has not been posted
Transfer Orders can only be confirmed by the warehouse operator since only he knows if the material has been taken from the shelf.
© SAP AG
SM300
2-38
Exercise: Identify Monitoring Objects
Exercise: Identify Monitoring Objects
© SAP AG 2009
© SAP AG
SM300
2-39
Integration into Support Organization
1. 2. 3. 4. 5. 6.
Overview of Procedure Business Process Analysis Definition of Monitoring Activities Integration into Support Organization Definition of Reporting Activities GoLive with Monitoring
© SAP AG 2009
© SAP AG
SM300
2-40
Define Communication and Escalation Procedures
Step 1 Identify core business processes
Step 4 Step 2 Step 3 Step 5 Define Identify Identify business Define monitoring process requirements monitoring objects, alerts activities steps and regarding process and thresholds interfaces execution
Step 6 Define communication and escalation procedures
Step 7 Assign monitoring activities to responsibles
Responsible:
2nd level Application Support, in collaboration with other parts of the support organization (owners of Incident/Problem Management Process and Change Management Process)
Communication and Escalation Procedures: Who is when to be contacted using which tool? What information has to be provided within the communication? Interfaces to Incident/Problem Management Process when is the Incident Management process supposed to be used to contact the next
support level Interface to Change Management Process changes to the solution landscape, e.g. different variant for report if job cancels
repeatedly changes to the monitoring concept itself, e.g. different thresholds
Are additional escalation procedures required? © SAP AG 2009
Incident/Problem Management and Change Management processes may have to be adjusted to suit the monitoring procedures (for instance new components, new responsibilities, adjusted templates for tickets...)
Collaboration of the owners of the respective IT Service Management processes is necessary.
© SAP AG
SM300
2-41
Example: Communication and Escalation Procedures CRM - CDP
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Run MRP Procurement Process
Manufacturing Process Create Outbound Delivery Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
Monitoring Object
Alert
Communication procedures
Incident Management Process
Change Management process
Escalation procedures
Outbound Delivery Creation
Number of open outbound deliveries for shipping point 1000 that are older than 5 days
Contact business process owner via email as part of error handling procedures
If error handling procedures do not apply open “high” ticket on component “SV-SMG-MONBPM”
For changes open Request for Change in ticketing tool on component “CHANGE-SM-MON” or “CHANGESALES”
Use escalation procedures defined within Incident Management process
© SAP AG 2008
© SAP AG
SM300
2-42
Assign Monitoring Activities to Responsibles Step 1 Identify core business processes
Step 4 Step 5 Step 2 Step 3 Define Define Identify Identify business monitoring monitoring process requirements activities objects, alerts steps and regarding process and thresholds interfaces execution
Step 6 Define communication and escalation procedures
Step 7 Assign monitoring activities to responsibles
Responsible:
Business Operations Team, in collaboration with 2nd level Application Support
Monitoring Responsible:
Carries out the monitoring activities
Part of Business Operations Team Monitoring Activity including • tools • monitoring procedures • error handling procedures
Communication and Escalation Procedures
Access to Business Process Description © SAP AG 2009
© SAP AG
SM300
2-43
Definition of Reporting Activities
1. 2. 3. 4. 5. 6.
Overview of Procedure Business Process Analysis Definition of Monitoring Activities Integration into Support Organization Definition of Reporting Activities GoLive with Monitoring
© SAP AG 2009
© SAP AG
SM300
2-44
Define Reporting Objects and Reporting Activities Step 8 Define Reporting Objects and Reporting Activities
Step 9 Define communication and escalation procedures
Step 10 Assign reporting activities to responsibles
Responsible:
2nd level Application Support, in collaboration with Business Department
Reporting Objects and Reporting Activities:
Which business process related Service Level Agreements between Business Department and Application support exist? Which monitoring objects are relevant for reporting?
Over which period should be reported how often using which tools?
Which thresholds are considered critical both for trend and total value? What is the strategy for root cause analysis of trends? Where is all information regarding the reporting activity accessible to the operator executing the activity (central access point for error handling procedures)? Which information should be logged where?
© SAP AG 2009
© SAP AG
SM300
2-45
Example: Reporting Objects and Reporting Activities CRM - CDP
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Run MRP Procurement Process
Manufacturing Process Create Outbound Delivery Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
Monitoring Object
Alert
Reporting relevant
Reporting Period and Frequency
Tool and Reporting Procedure
Strategy for root cause analysis
Log Information
Outbound Delivery Creation
Number of open outbound deliveries for shipping point 1000 that are older than 5 days
yes
Weekly reporting over last 30 days (daily numbers)
Check Log for last 30 days
1. Check which materials were involved 2. Check trend for number of open TOs 3. Check business problems with material availability
Critical Trends identified
© SAP AG 2008
Alert Thresholds for a reporting object can be:
Number of open deliveries: y Total on any day > 200 y Overall trend > 10 % growth (1st day compared to last day) y Growth > 5% if total > 100 for two successive days
© SAP AG
SM300
2-46
Define Communication and Escalation Procedures
Step 8 Define Reporting Objects and Reporting Activities
Step 9 Define communication and escalation procedures
Step 10 Assign reporting activities to responsibles
Responsible:
2nd level Application Support, in collaboration with other parts of the support organization
Communication and escalation procedures: Define Interfaces to Incident/Problem Management Process including who has to be contacted when using which tool including root cause analysis
Interface to Change Management Process Interface to Service Level Management, including what has to reported to whom (e.g. in Business Department) which business process related service levels have to be provided by the IT
organization
© SAP AG 2009
Incident/Problem Management, Change Management and Service Level Management processes may have to be adjusted to suit the reporting procedures (for instance new components, new responsibilities,...)
Collaboration of the owners of the respective IT Service Management processes is necessary
© SAP AG
SM300
2-47
Example: Communication and Escalation Procedures CRM - CDP
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Run MRP Procurement Process
Manufacturing Process Create Outbound Delivery Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
Reporting Object
Communication procedures
Incident Management Process
Change Management process
Service Level Management process
Escalation procedures
Open Outbound Deliveries for shipping point 1000 that are older than 5 days
Contact business process owner via email as part of root cause analysis
If root cause analysis do not solve the situation open “high” ticket on component “SVSMG-MON-BPM”
For changes open Request for Change in ticketing tool on component “CHANGE-SMMON” or “CHANGESALES”
Include in quarterly Service Level Report from IT to business
Use escalation procedures defined within Incident Management process
© SAP AG 2008
© SAP AG
SM300
2-48
Assign Reporting Activities to Responsibles Step 8 Define Reporting Objects and Reporting Activities
Step 9 Define communication and escalation procedures
Step 10 Assign reporting activities to responsibles
Responsible:
2nd level Application Support
Reporting Responsible:
Carries out the reporting activities
Part of 2nd level Application Support Reporting Activity including • tools • reporting procedures • root cause analysis procedures
Communication and Escalation Procedures
Access to Business Process Description © SAP AG 2009
© SAP AG
SM300
2-49
GoLive with Monitoring
1. 2. 3. 4. 5. 6.
Overview of Procedure Business Process Analysis Definition of Monitoring Activities Integration into Support Organization Definition of Reporting Activities GoLive with Monitoring
© SAP AG 2009
© SAP AG
SM300
2-50
Implementing the Monitoring Concept
Strategic Framework
Technical Technical Technical and and and Integration Operations Operations Design Implementation Implementation
Define and Create a Monitoring Concept
Implement Implement the the Monitoring Monitoring Concept Concept
Cutover and Start of Production
Start Monitoring
Operations and Continuous Improvement
Continuous Improvement
Test and implement all tools and procedures Train involved people in tools and procedures Test monitoring process Interaction between different teams Identify need for adjustments to IT Service Management processes
© SAP AG 2009
© SAP AG
SM300
2-51
Start Monitoring
Strategic Framework
Technical Technical and and Integration Operations Design Implementation
Define and Create a Monitoring Concept
Implement the Monitoring Concept
Cutover Cutover and and Start Start of of Production Production
Start Start Monitoring Monitoring
Operations and Continuous Improvement
Continuous Improvement
Start Monitoring after all tests have been completed successfully.
© SAP AG 2009
© SAP AG
SM300
2-52
SAP Standard for Business Process and Interface Monitoring IT Department
Business Department Key User
Business Process Operations
Business Process Champion
Application Management
Detect Alert Situation
Identify Application Problem
Execute Initial Analysis Create Service Desk message
Execute exception handling
Assign Service Desk message to issue RCA process Create action plan Change Request process
Sign-off alert resolution
Solve Service Desk message
© SAP AG 2008
The SAP Standard ‘Exception Handling and Business Process & Interface Monitoring’ has defined this architecture and process flow.
The standards for exception handling and for business process and interface monitoring for a company’s core business processes involve roles both from the business department and the IT department. Certain activities like the initial alerting and simple error handling procedures can be executed by the business process operations team within the IT organization, whilst the more detailed root cause analysis has to be carried out by the application management team.
The business department (both in the role of the key user or the business process champion) evaluates the business relevance of exceptions or alert situations and carries out business related error handling procedures.
Business process and interface monitoring should be executed using a central monitoring tool that provides access to all information relevant for executing the standard process. This includes information like the business process and interface documentation, error handling procedures, responsibilities etc. Since business process and interface monitoring can always result in the raising of incidents, the interface to the incident management processes should be well defined and supported by the monitoring tool. The interface to the change request management process should likewise be defined and supported by the monitoring tool.
More information you can find under https://service.sap.com alias ‘supportstandards’.
© SAP AG
SM300
2-53
Continuous Improvement
Strategic Framework
Technical Technical and and Integration Operations Design Implementation
Define and Create a Monitoring Concept
Implement the Monitoring Concept
Cutover and Start of Production
Start Monitoring
Operations Operations and and Continuous Continuous Improvement Improvement
Continuous Continuous Improvement Improvement
Business Process and Interface Monitoring:
Not a static concept
Integrated into Change Management process of a customer
Regular reviews to ensure that the monitoring concept still fits the business requirements
triggered regularly by owner of Business Process Monitoring concept
© SAP AG 2009
© SAP AG
SM300
2-54
Exercises Unit:
Procedure
Lesson:
Document Business Process in SAP Solution Manager
Exercise 3: Create Business Process At the conclusion of this exercise, you will be able to: • Maintain Business Processes in SAP Solution Manager.
Business Process “Order to Cash” is already partly documented in SAP Solution Manager in upgrade project “BPIAM - ERP2005 Upgrade Project for BPIAM”.
3-1
Document business process “Order to Cash” in your solution in SAP Solution Manager TT4 as pictured below. Execute the following parts of the exercise to achieve this. CRM – CDP C##
SAP ECC - TT5
Create Sales Order
Create Sales Create Sales Order Order
SAP ENTERPRISE PORTAL – TP5
Create Sales Order Order
Check Check Availability Availability
Run MRP Run MRP
Manufacturing Manufacturing Process Process
Procurement Procurement Process Process
Create Outbound Create Outbound Delivery Create CreateBilling Billing Document Document
Post Post Goods Goods Issue Issue
Warehouse - TT5
Create Outbound CreatDelivery e Outbound Delivery
Create Picking Create Picking Transfer Order Transfer Order
Post Goods Issue Post Goods Issue
ConfirmPicking Picking Confirm Transfer Transfer Order Order
3-1-1
Assign the required logical components to your solution.
3-1-2
Create business scenario “Outbound Logistics”. Set the status of business scenario “Outbound Logistics” to “Production”.
3-1-3
Copy business process “Order to Cash” from project “BPIAM”
© SAP AG
SM300
2-55
3-1-4
Access the graphic for business process “Order to Cash” in your solution. In which way does it differ from the business process pictured in this exercise Answer:______________________________________________________
3-1-5
© SAP AG
Create the missing business process steps and adjust the process flows and interfaces. Change the color for the ware house system to “Dark Blue”.
SM300
2-56
Solutions Unit:
Procedure
Lesson:
Document Business Process in SAP Solution Manager
Exercise 3: Create Business Process
3-1
Access system TT4, client 200. 3-1-1
Call transaction /nDSWP. Make sure you are in your solution. Navigate to the solution directory via Solution Landscape Æ Solution Landscape Maintenance. In the Solution Directory switch into Change Mode and then in node “SM300-## Landscape” make sure that the leading role of the solution is in “Production System”. Then, assign the following logical components in tab System Group via the value help in column Logical Component: •
SAP ECC Æ SAP ECC Server Æ Z_ECC
•
SAP ECC Æ SAP ECC Server Æ Z_WAREHOUSE
•
Portal Æ Portal 01 Æ Z_EP
•
Non-SAP CRM Æ Z_CRM-## (## = group number)
3-1-2
Open the tree (Solution Structure) to “SM300-## Landscape” Æ “Business Scenarios”. In node “Business Scenarios” go to tab “Structure”. Enter text “Outbound Logistics” to create a new business scenario and change status to “Production”. Save.
3-1-3
Open the solution structure to node SM300-## Landscape Æ Business Scenarios Æ Outbound Logistics Æ Business Processes. Go to tab “Structure”. Choose source “Project”. Then use value help for the process name. Then use value help for the scenario name. In the value help open the tree to “BPIAM Æ Business Scenarios Æ “Outbound Logistics” . Æ Business Processes Æ “Order to Cash”. Mark “Order to Cash” and confirm your selection. In tab “Structure” change status to “Production”. Save.
3-1-4
Open the solution structure to node SM300-## Landscape Æ Business Scenarios Æ Outbound Logistics Æ Business Processes Æ Order-to-Cash. Access tab “Graphic”. There you can see the business process “Order-toCash” as maintained in the project. Answer: The usage of a decentralized warehouse and the non-SAP CRM system are not described in the business process maintained in the project.
3-1-5 © SAP AG
Access tab “Structure”. Create the following additional entries: SM300
2-57
Step Name
Logical Component
Create Sales Order
Z_CRM-## (## = group number)
Create Sales Order
Z_EP
Create Outbound Delivery
Z_WAREHOUSE
Create Picking Transfer Order
Z_WAREHOUSE
Confirm Picking Transfer Order
Z_WAREHOUSE
Post Goods Issue
Z_WAREHOUSE
Save. Access tab “Graphic”. Via “Drag and Drop” change the layout of the warehouse system to the one displayed in the exercise. Delete the arrow between steps “Create Outbound Delivery” and “Post Goods Issue” on the SAP ECC system. To delete, execute a right-mouse click on the arrow and choose “Delete”. Create the missing arrows (see business process picture in exercise) via rightmouse clicks on the sending and the receiving business process steps. Choose synchronous lines for all horizontal arrows and asynchronous lines for all vertical arrows. Change the color of the warehouse system to dark blue. To do so execute a right-mouse click on the system box and choose “Properties”. Change the color and confirm.
© SAP AG
SM300
2-58
Exercises Unit:
Procedure
Lesson:
Definition of Monitoring Activities
Exercise 4: Identify Monitoring Objects At the conclusion of this exercise, you will be able to: • Identify Monitoring Objects for a Business Process.
Before monitoring can be configured in SAP Solution Manager, suitable monitoring objects for the business process have to be identified. For this exercise we focus on suitable monitoring objects for business process step “Create Sales Order” on the SAP ECC system. Sales Orders are either created online via transaction via VA01 or via background job ‘SD_CREATE_SALES_ORDERS_2H’.
4-1
Identify suitable monitoring objects for business process step “Create Sales Order” on the SAP ECC system TT5. 4-1-1
Name the 4 different monitoring areas Answer:______________________________________________________
4-1-2
Some possible situations in the system are listed in the table below. Decide whether the situation can be worth to be monitored, assign the correct monitoring area(s), decide as well if the error can be recognized by end users?
Situation
Relevant for monitoring? (Yes/No)
Monitoring Area(s)
Recognizable by end users? (Yes/No)
Short Dumps Update Errors Job Cancellations Error Messages in Job Log Error Messages in Application Log
© SAP AG
SM300
2-59
Situation
Relevant for monitoring?
Monitoring Area(s)
(Yes/No)
Recognizable by end users? (Yes/No)
Job not started on time Too many sales orders created Too few sales orders created Long dialog response time of transaction VA01 Background Job runs very long Many open Sales Orders (for delivery) Many incomplete Sales Orders Many Sales Orders with delivery block
4-1-3
Question: Why is it important if the end user can recognize the situation? Answer: _____________________________________________________________
© SAP AG
SM300
2-60
Solutions Unit:
Procedure
Lesson:
Definition of Monitoring Activities
Exercise 4: Identify Monitoring Objects
4-1
Identify suitable monitoring objects: 4-1-1
4-1-2
Answer: The four different monitoring areas are •
Error Monitoring
•
Performance Monitoring
•
Throughput Monitoring
•
Backlog Monitoring
Possible situations in the system:
Situation
Relevant Monitoring Area(s) for monitoring ?
Recognizable by end users ? (Yes/No)
(Yes/No) Short Dumps
Yes
Error monitoring
Yes
Update Errors
Yes
Error monitoring
Not always
Job Cancellations
Yes
Error monitoring
No
Error Messages in Job Log
Yes
Error monitoring
No
Error Messages in Application Log
Yes
Error monitoring
Normally not
Job not started on time
Yes
Error/Performance/Throughput No
Too many sales orders created
No *
Throughput monitoring
No
Too few sales orders created
Yes
Throughput monitoring
No
Long dialog response time of transaction VA01
Yes
Performance monitoring
Yes
Background Job runs very long
Yes
Performance monitoring
No
© SAP AG
SM300
2-61
Situation
Relevant Monitoring Area(s) for monitoring ?
Recognizable by end users ? (Yes/No)
(Yes/No) Many open Sales Orders (not yet delivered)
Yes
Backlog monitoring
No
Many incomplete Sales Orders
Yes
Backlog monitoring
No
Many Sales Orders with delivery block
Yes
Backlog monitoring
No
*Remark: From the system perspective it is only a problem if the throughput of the process is not enough. Too much throughput is usually not critical. From the business point of view it can be a problem and worth to be monitored, because the business will run into capacity problems due to too many Sales Orders. 4-1-3
Why is it important whether the end user can recognize the situation? Answer: If the end user can recognize the situation this influences how the object should be monitored. Example: If a short dump occurs in transaction VA01, the end user will see it immediately on the screen. So there is little proactive monitoring the support organization can do. Here the trend analysis would be of more importance.
© SAP AG
SM300
2-62
Monitoring Configuration
Course Overview Unit 1 Introduction to Business Process Monitoring Unit 2 Procedure Unit 3 Monitoring Configuration Unit 4 Using Business Process Monitoring
Unit 8
Data Consistency Monitoring
Unit 5 Cross-Application Monitoring
Unit 9
Reporting
Unit 6 Application Monitoring Unit 7 Interface Monitoring
Unit 10 Handover to Production Unit 11 Managing Jobs in SAP Solution Manager
© SAP AG 2008
© SAP AG
SM300
3-1
Business Process Monitoring: Unit Objectives
After completing this unit, you will be able to:
Check technical prerequisites for Business Process Monitoring
Set up Business Process Monitoring for background jobs
Generate and activate Business Process Monitoring for operational use
Use existing documentation to set up further monitoring functionalities in SAP Solution Manager
Learn the basics of the CCMS Monitoring Infrastructure
© SAP AG 2009
© SAP AG
SM300
3-2
Initial Situation Company IDES now configures monitoring for business Process “Order-to-Cash” in SAP Solution Manager according to the identified operations requirements. CRM - CDP
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Run MRP
Procurement Process
Manufacturing Process
Create Outbound Delivery Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
© SAP AG 2009
© SAP AG
SM300
3-3
Lesson 1: Technical Prerequisites
1. Technical Requisites 2. Setup Procedure Appendix: CCMS Monitoring Infrastructure
© SAP AG 2009
© SAP AG
SM300
3-4
Technical Infrastructure for Business Process Monitoring in SAP Solution Manager Satellite System
SAP Solution Manager System
ST-PI ST
RFC Destination for Data Collection
ST-A/PI
ST-SER ST-A/PI
RFC Destination for dialog logon to satellite system
ST-PI
Local RFC Destination
© SAP AG 2008
You can check the currently available version of add-ons ST, ST-SER and ST-A/PI in SAP Service Marketplace, quicklink SWDC (http://service.sap.com/swdc).
The different add-ons contain various parts of the functionalities for Business Process and Interface Monitoring:
ST y Solution Manager Release: This is the SAP Solution Manager Add-On itself.
ST-SER y Technical Release: SAP Solution Manager Service Tools (ST-SER) contains all service sessions that are available for service delivery
ST-A/PI y Add-On Release: Contains coding for data collectors of mostly application-specific monitoring functionality, especially the TBIs. More information can be found in SAP Note 69455.
ST-PI y Contains coding for data collectors of mostly cross-application monitoring functionality, e.g. job monitoring and interface monitoring. More information can be found in SAP Notes 539977, 560475 and 560630.
© SAP AG
SM300
3-5
Technical Prerequisites for Business Process Monitoring in SAP Solution Manager
The prerequisites for Business Process Monitoring in SAP Solution Manager are detailed in SAP Note 784752. They are: 1. Dialog users with correct authorizations available in SAP Solution Manager and Satellite system 2. Correct version of software components installed 3. System Landscape maintained in SAP Solution Manager 4. RFC Connections maintained 5. General Settings maintained 6. Optional settings maintained if needed 7. Solution created in SAP Solution Manager 8. Business Processes documented in SAP Solution Manager
© SAP AG 2009
© SAP AG
SM300
3-6
1. Dialog Users and Authorizations
SAP Solution Manager System
Satellite System
Dialog User with roles
Early Watch User optional with additional authorizations
SAP_SV_SOLUTION_MANAGER SAP_SOLMAN_DIRECTORY_ADMIN (optional)
SAP Note 834534 contains more information about authorizations © SAP AG 2009
The relevant users require the following authorizations in the systems: SAP Solution Manager y Role SAP_SOLMAN_DIRECTORY_ADMIN (optional, in case you need to correct entries in the system landscape maintenance (transaction SMSY)) y Role SAP_SV_SOLUTION_MANAGER y Required roles for Business Process & Interface Monitoring Work Center Usage: SAP_SMWORK_BASIC SAP_SMWORK_BPM y Required roles for Job Management Work Center Usage: SAP_SMWORK_BASIC SAP_SMWORK_JOB_MAN Satellite system y Early Watch users with the following additional authorizations: - Display authorization for the following transactions: SE16 SPRO (optional, in case you need to configure application monitoring - TBIs) - Change authorizations for the following transactions in the relevant development system: RZ20 RZ21 BDMO (optional, in case you need to configure interface monitoring) In this case, you have to create a Customizing request and a workbench request that have been assigned to the relevant
© SAP AG
SM300
3-7
2. Correct Version of Software Components Installed Software requirements for the SAP Solution Manager to make full usage of the latest Business Process Monitoring features (refer to SAP Note 521820; the latest Support Packages for ST and ST-SER have to be installed): Satellite System
SAP Solution Manager System
ST400 SP15
ST-SER 700_2008_1 SP4
ST-A/PI 01K_CRM500
ST-PI 2005_1_710 SP 6
ST-PI2005_1_###
for Releases lower than 4.6D import SP8
for Releases higher than 4.6C import SP6
ST-A/PI 01K_###
(### = depending on the basis release of the system)
© SAP AG 2009
To make full use of the monitoring functions in SAP Solution Manager 7.0, you should have installed the current versions of the these software components.
The most current versions are available on SAP Service Marketplace under the quick link /SWDC or under the quick link /SUPPORTTOOLS.
To check if all necessary plug-ins have been installed, choose System-> Status in the menu.
© SAP AG
SM300
3-8
3. System Landscape maintained in SAP Solution Manager
The following settings must have been maintained in the system landscape for all satellite systems relevant for Business Process Monitoring:
Server
Product
System Information, using product and server
For SAP systems providing additionally z z z
client information installation number relevant instance of the SAP installation (Application Server, Portal, BI etc.)
All relevant systems (and the correct client) have to be assigned to a logical component.
© SAP AG 2009
For details please refer to unit 01 Introduction in this training.
© SAP AG
SM300
3-9
4. RFC Connections Maintained SAP Solution Manager System
Satellite System READ RFC Destination
LOGIN RFC Destination
Local RFC Destination
There are 3 types of RFC destinations that are required for Business Process Monitoring
LOCAL RFC Destination on SAP Solution Manager
READ RFC Destination to connect SAP Solution Manager with the satellite system for data collection
LOGIN RFC Destination to connect SAP Solution Manager with the satellite system for dialog login
© SAP AG 2009
When creating RFC destinations, you also have to create and maintain users that utilized by the RFC destinations. The authorization to create and maintain these users is not included in the roles and authorizations mentioned on the previous slides.
It is highly advisable to create the RFC destinations to the satellite system from the System Landscape Maintenance of SAP Solution Manager (SMSY) so that the corresponding RFC user automatically has the correct authorizations assigned.
For details on how to create satellite systems and assign them to the solution see the introduction to the SAP Solution Manager on the first day of this training.
© SAP AG
SM300
3-10
4. RFC Connections Maintained – Local RFC Destination SAP Solution Manager System
BPM_LOCAL_200
BPMon Client 200 BPMon Engine
For infrastructure reasons an RFC destination pointing to the productive BPMon client on SAP Solution Manager is needed (in case of TT4 this client is 200). This RFC destination must be called “BPM_LOCAL_”. Create this RFC destination in transaction /nSM59 and assign communications user SM_BPMO with its password in the logon data of this RFC destination.
Client 000 CCMS
© SAP AG 2009
The local RFC destination points to the client of the SAP Solution Manager system in which the monitoring customizing will be set up. For this, a user (SM_BPMO) with authorization profile S_CSMREG and role SAP_SUPPDESK_CREATE has to be created in this client on the Solution Manager system. Make sure your using the newest version of the authorization profile and the role (role has to be generated and user comparison has to be executed). If there are several clients productive for BPMon, this local RFC destination has to be created several times on SAP Solution Manager, one for each productive client.
© SAP AG
SM300
3-11
4. RFC Connections Maintained – RFC Destinations to Satellite Systems
Switch to change mode.
RFC destination can be set up in the System Maintenance in area Operations Setup / Solution Landscape. Switch to change mode in the System Maintenance to be able to set up RFC destinations.
© SAP AG 2009
It is also possible to set up the RFC destinations in transaction SM59 and assign the destinations for monitoring in transaction RZ21. In case of problems with the monitoring it is always advisable to check the RFC settings in SM59 and RZ21.
© SAP AG
SM300
3-12
How to Set up RFC Destinations Choose Landscape Components / Systems / / / Server in the tree. In tab “Clients”, mark the line with the client that is supposed to be monitored. Choose “RFC” to create the RFC destinations. Choose to create RFC destinations.
© SAP AG 2008
The RFC destination for data collection is usually called the SM_CLNT_READ. The RFC destination for dialog login can be the SM_CLNT_LOGIN destination. If the trusted RFC destination has been set up correctly and the dialog user has the necessary authorization profile assigned, you can use the SM_CLNT_TRUSTED RFC destination for dialog login.
Both RFC destinations have to be assigned for system monitoring (RZ21). This can also be maintained from within the System Landscape Maintenance of SAP Solution Manager.
Details regarding the RFC destinations are available in the IMG of the SAP Solution Manager system. In the IMG the RFC destinations to the satellite system are covered in chapter SAP Solution Manager / Basic Settings. The local RFC destination is covered in chapter SAP Solution Manager / Scenario-Specific Settings / Operations / Business Process Monitoring.
© SAP AG
SM300
3-13
Popup to Create RFC Destinations Read RFC-Destination. You can automatically create a user on the satellite system along with the necessary authorizations or use an already existing user.
Login RFC-Destination. If a “Trusted” relationship between the satellite system and the SAP Solution Manager system has been set up it is also possible to use the “Trusted system RFC Destination”. Overview of the RFC destinations and users that will be created. It also shows if these RFC destinations already exist.
Flag to identify the RFC destinations as relevant for Business Process Monitoring. If destination have already been assigned in transaction RZ21 there are displayed here.
Choose to create RFC destinations. © SAP AG 2009
By setting the flag “Assign RFC Destinations for System Monitoring” you ensure that an entry for the satellite system is written into transaction RZ21. You can check the entry in RZ21 / Technical Infrastructure / Display Topology.
© SAP AG
SM300
3-14
Maintain SAP Instances For Business Process Monitoring the names of the SAP Instances have to be maintained here. This can be done manually or you choose “Read System Data Remote” after having created and assigned the RFC destinations.
Choose to read system data.
© SAP AG 2009
It is also possible to enter the instances manually. If you want to set up Monitoring for the Performance of dialog transactions it is mandatory that the instances are specified here.
When clicking on the button „Read System Data Remote“ additional information from the satellite system like additional clients and software components are also imported.
© SAP AG
SM300
3-15
5. General Settings Maintained
The following settings must also be maintained:
Time setting for the user in the LOCAL RFC Destination:
In the user master data (fixed values), the user in the LOCAL RFC Destination must be assigned the time zone of the system. (If the field is empty, the system uses the CET time zone).
© SAP AG 2009
Remote Availability of SAP Solution Manager Graphic y To maintain a business process in SAP Solution Manager using a remote connection, you must make sure that the HTTP Connect connection for Solution Manager is open (see Note 592085).
© SAP AG
SM300
3-16
6. Optional Settings Maintained if Needed
The following settings can be maintained optionally:
SAP Connect is configured
This setting is only required if you want to send e-mails for alerts. In addition, there exists a user that has been assigned an e-mail address in the user master data. This email address is within the name space of the used mail server. This user will be used as sender for all emails for alerts.
Service Desk in SAP Solution Manager is configured
This setting is only required if you want to service desk messages for alerts.
iBase components for the involved satellite systems have been defined. Business partners for message creators and message processors have been created.
See SAP note 1244982 for details.
© SAP AG 2009
SAP Connect y Up to ST-SER 700_2006_1: SAP Connect (transaction SCOT) has been configured correctly in client 000 of SAP Solution Managers (see SAP Note 455140). The user with the email address has to exist in client 000. y As of ST-SER 700_2006_2: SAP Connect (transaction SCOT) has been configured correctly in the productive client of Business Process Monitoring for SAP Solution Manager (see SAP Note 455140). The user with the email address has to exist in the productive client for BPMon.
Service Desk in SAP Solution Manager y iBase components for the systems to be monitored y Business partner for the creation of messages:
- In transaction BP, there must be a person in the "general business partner" role who has been assigned a user from the monitored client in the satellite system in the "Identification“ area. y Business partner for editing messages:
- In transaction BP, there must be a person in the "Employee" role who has been assigned a user from SAP Solution Manager in the "Identification“ area. - See SAP note 1244982 for details.
© SAP AG
SM300
3-17
7. Solution created in SAP Solution Manager Before setting up Business Process Monitoring in SAP Solution Manager a solution must have been created to have access to the various SAP Solution Manager functionalities.
© SAP AG 2009
© SAP AG
SM300
3-18
8. Business Processes documented in SAP Solution Manager The Business Process must have been maintained in SAP Solution Manager. This includes the definition of the business process steps and which logical component they are executed on.
© SAP AG 2009
The business process has to be in status “Production” in order to set up Business Process Monitoring.
© SAP AG
SM300
3-19
Exercise: Check Technical Prerequisites
Exercise: Check Technical Prerequisites
© SAP AG 2008
© SAP AG
SM300
3-20
Lesson 2: Setup Procedure
1. Technical Requisites 2. Setup Procedure Appendix: CCMS Monitoring Infrastructure
© SAP AG 2009
The setup procedure for Business Process Monitoring in SAP Solution Manager is mostly independent of the involved functionality. So before going into the details for the monitoring functionalities, the setup procedure is explained.
© SAP AG
SM300
3-21
Link between Setup Methodologies General BPMon Setup Methodology Step 1 Identify core business processes
Step 2 Step 3 Step 4 Step 5 Identify Identify business Define Define process requirements monitoring monitoring activities steps and regarding process objects, alerts interfaces execution and thresholds
SAP Solution Manager: • System Maintenance SAP Solution Manager: • Solution Directory
Step 7 Assign monitoring activities to responsibles
Details
Where SAP Solution Manager: • Entrance Screen
Step 6 Define communication and escalation procedures
Create Solution
• Create Solution
Create Logical Component
Create Business Process
• Create Product, Server, Database and System • Create RFC Destinations and Maintain SAP Server Names • Create Logical Component • • • • •
Assign Logical Components to Solution Create Contact Persons Choose Business Scenario Create Business Process and Business Process Steps Arrange Process Graphic and Create Process Flows
Corresponding Part of BPMon Setup Methodology in SAP Solution Manager © SAP AG 2008
The Step “Create Logical Component” can be executed by a member of System/Basis support or the administrator for SAP Solution Manager.
© SAP AG
SM300
3-22
Sample Situation for Example Business Process CRM - CDP
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Job Job SD_CREATE_SALES_ORDERS_2H SD_CREATE_SALES_ORDERS_15MIN cancels regularly not started or cancels Replication of the Outbound Delivery fails
Run MRP
Procurement Process
Manufacturing Process
Create Outbound Delivery Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
Goods issue not posted
Business Requirement:
Monitoring Requirement:
Orders for critical customers are created by job every 15 minutes
Start delay for job SD_CREATE_SALES_ORDERS_15min Cancellation of job SD_CREATE_SALES_ORDERS_15min
© SAP AG 2008
Critical customers: special agreements with these customers that materials are delivered within 1 day. For these, sales orders are replicated on ERP more frequently to allow for more time for the processing of the rest of the business process.
© SAP AG
SM300
3-23
Setup Procedure Business Process Monitoring in SAP Solution Manager Where
Details
SAP Solution Manager: • Entrance Screen
Create Solution
SAP Solution Manager: • System Maintenance
Create Logical Component
• Create Product, Server, Database and System • Create RFC Destinations and Maintain SAP Server Names • Create Logical Component
Create Business Process
• • • • •
SAP Solution Manager: • Solution Directory
SAP Solution Manager: • BPMon Setup Session
• Create Solution
Set up Monitoring Customizing in SAP Solution Manager
Assign Logical Components to Solution Create Contact Persons Choose Business Scenario Create Business Process and Business Process Steps Arrange Process Graphic and Create Process Flows
• Define Solution Support Organization • Choose Business Process and Process Steps to be monitored • Define Monitoring Objects per Step Per Monitoring Object: • Provide technical Details and Threshold Values for the Alerts. • Assign Monitoring & Analysis Tools and Set up Monitoring Tasks. • Set up Automatic Emails and Service Desk Messages
© SAP AG 2008
© SAP AG
SM300
3-24
Set up Monitoring Customizing in SAP Solution Manager Step in Roadmap
Details
Define Solution Support Organization
Define teams, assign team members (for documentation of monitoring responsibilities)
Choose Business Process and Business Process Steps to be monitored Define Monitoring Objects per Business Process Step
Choose which monitoring functionality should be used per business process step
Per Monitoring Object: Provide technical details and threshold values for the alerts Assign Monitoring & Analysis Tools Set up monitoring tasks
Configure automatic emails and Service Desk messages
E.g. which transaction should be monitored, when should an alert be raised Define direct links from SAP Solution Manager to monitored system or to additional material in Intranet What has to be done in case of an alert, who is responsible for monitoring, where can the problem be escalated (documentation) If an alert occurs who should be notified automatically per email or Service Desk message
© SAP AG 2009
© SAP AG
SM300
3-25
Link between Setup Methodologies General BPMon Setup Methodology Step Step Step 11 Step 22 Identify Identify Identify core core Identify business process business process processes steps processes steps and and interfaces interfaces
Step Step 33 Identify Identify business business requirements requirements regarding regarding process process execution execution
Step Step 44 Define Define monitoring monitoring objects, objects, alerts alerts and and thresholds thresholds
Step Step 55 Define Define monitoring monitoring activities activities
Step Step 66 Define Define communication communication and and escalation escalation procedures procedures
Define Solution Support Organization
Step Step 77 Assign Assign monitoring monitoring activities activities to to responsibles responsibles
x
Choose Business Process and Business Process Steps to be monitored
x
Define Monitoring Objects per Business Process Step
x
x
Per Monitoring Object: Provide technical details and threshold values for the alerts
x
Assign Monitoring & Analysis Tools
x x
Set up monitoring tasks
x
Configure automatic emails and Service Desk messages
x
x
x
Corresponding Part of BPMon Setup Methodology in SAP Solution Manager © SAP AG 2008
© SAP AG
SM300
3-26
Example Process: Monitoring Customizing CRM - CDP
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Job SD_CREATE_SALES_ORDERS_15MIN not started or cancels
Run MRP
Procurement Process
Manufacturing Process Create Outbound Delivery Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
Monitoring Requirement:
Technical Details:
Start delay for job SD_CREATE_SALES_ORDERS_15min
Job SD_CREATE_SALES_ORDERS_15MIN, scheduling information as maintained in SM37
Cancellation of job SD_CREATE_SALES_ORDERS_15min
Monitoring should be executed on every day sales orders are created (Mo-Fr)
© SAP AG 2008
Start Delay: y 10 min Æ yellow alert y 15 min Æ red alert
Error Handling: y Start job manually if job has not started on time
© SAP AG
SM300
3-27
Where to set up Monitoring Customizing
Setup Business Process Monitoring session
© SAP AG 2009
Each user has to register before entering the Setup Business Process Monitoring session for the first time. You will get a certification screen that requires you to enter your user credentials. This user registration is for documentation purposes only. No cross-checking takes place at this stage.
There is one Setup Business Process Monitoring session per solution. Monitoring customizing for all business processes is maintained in this one session. The Setup Business Process Monitoring session is available as soon as a logical component with a productive system has been assigned to the solution.
In the Setup Business Process Monitoring session you have a session tree on the left hand side. On the right hand side you have two areas: The node description area and the area for data entry. The node description area contains a lot of detailed information about what has to be maintained to what purpose in the area for data entry and should always be your first point for consultation in case of questions and problems.
© SAP AG
SM300
3-28
Define Solution Support Organization
Define Solution Support Organization Choose Business Process and Business Process Steps to be monitored
The Solution Support Organization is defined in node Solution Support Organization and the sub-nodes created for each monitoring team in the session tree.
Define Monitoring Objects per Business Process Step Per Monitoring Object: Provide technical details and threshold values for the alerts Assign monitoring & analysis tools Set up monitoring tasks Configure automatic emails and Service Desk messages
Specify the monitoring teams which take part in the Business Process Monitoring concept.
© SAP AG 2009
In order to later on assign persons to certain monitoring tasks you have to group these persons into teams first. You can create as many teams as you wish.
© SAP AG
SM300
3-29
Assign Members to Support Team Members for the teams and the monitoring roles for the teams are defined in node ‘Team ’. In tab ‘Team Members’ assign members to the monitoring team via the value help.
In tab ‘Monitoring Roles’ specify the roles of each monitoring team.
© SAP AG 2009
For the newly created teams you can assign team members.
Observe that team members can only be assigned via the value help.
© SAP AG
SM300
3-30
Define Contacts in Support Organization
Define Solution Support Organization
The Contacts for Solution Support Organization are defined in the Solution Directory (Solution Landscape Maintenance) by selecting on button Contacts:
Choose Business Process and Business Process Steps to be monitored Define Monitoring Objects per Business Process Step Per Monitoring Object: Provide technical details and threshold values for the alerts Assign monitoring & analysis tools Set up monitoring tasks Configure automatic emails and Service Desk messages
© SAP AG 2009
In order to create new members of the support organization you have to go to the Solution Landscape Maintenance in the Operations Setup area of the SAP Solution Manager. For each team you can assign monitoring roles. All of this is for documentation of monitoring responsibilities.
© SAP AG
SM300
3-31
Choose Business Process to be Monitored
Define Solution Support Organization
In node Business Processes within Business Process Monitoring Session choose which of the business processes documented for the solution should be monitored.
Choose Business Process and Business Process Steps to be monitored Define Monitoring Objects per Business Process Step Per Monitoring Object: Provide technical details and threshold values for the alerts Assign monitoring & analysis tools Set up monitoring tasks
Flag ‘Monitoring' for the business processes you want to monitor.
Configure automatic emails and Service Desk messages
© SAP AG 2009
The business scenario has to be in status Production before you can activate the monitoring for a process. If the flag Planned for the business process is set this means that you can set up the monitoring customizing but you will not be able to really activate the monitoring to get alerts. So if you see this flag, go back to the Solution Landscape Maintenance and change the settings for the business scenario.
For each of the business processes maintained in the solution landscape you now have to specify if they or parts of them should be monitored.
For the business process to be set to „Production“ the logical components assigned to the solution must contain systems in the leading role of the solution.
© SAP AG
SM300
3-32
Choose Business Process Steps to be Monitored For each business process you can now choose which business process steps are supposed to be monitored. Choose Business Processes / BPMon in the session tree and mark the steps in tab “Steps of Business Process”. Choose the business process steps to be monitored.
Client information
© SAP AG 2009
You can choose any number of business process steps to be monitored. When you save, sub-nodes for the selected business process steps as well as for the maintenance of interfaces are created within the session.
Node BPMon contains also a tab where you can document the restart procedure for the business process.
© SAP AG
SM300
3-33
Define Monitoring Objects per Business Process Step
Define Solution Support Organization
Choose for each business process step in node Business Processes / BPMon / Step which areas should be monitored to ensure the smooth running of the business process.
Choose Business Process and Business Process Steps to be monitored Define Monitoring Objects per Business Process Step Per Monitoring Object: Provide technical details and threshold values for the alerts Assign monitoring & analysis tools Set up monitoring tasks Configure automatic emails and Service Desk messages
Choose the monitoring types relevant for the business process step.
© SAP AG 2009
The monitoring type can contain more than one monitoring functionality.
When saving, the respective sub-nodes are created for the selected monitoring types.
© SAP AG
SM300
3-34
Per Monitoring Object: Provide Technical Details
Define Solution Support Organization
Provide technical details for each monitoring type in node Business Processes / BPMon / Step / in the session tree.
Choose Business Process and Business Process Steps to be monitored Define Monitoring Objects per Business Process Step Per Monitoring Object: Provide technical details and threshold values for the alerts Assign monitoring & analysis tools Set up monitoring tasks Configure automatic emails and Service Desk messages
Provide technical details.
© SAP AG 2009
Technical details include name and scheduling information of background jobs, name of transactions that should be monitored, object and sub-object of the application log to be monitored etc.
Purpose of the technical information is to identify exactly the technical object that should be monitored.
© SAP AG
SM300
3-35
Get Scheduling Information for Background Jobs Choose “Check Job Identification Check corresponding jobs in SM37 on satellite system
Double-click on job name to load scheduling information for job into SAP Solution Manager
© SAP AG 2009
You can maintain the job information manually in SAP Solution Manager.
You can upload the scheduling information as it is available in SM37 of the satellite system. In this case, adjust the settings so that all jobs that are supposed to be monitored are monitored (for instance if different variants are used).
Monitoring of background jobs evaluates the job information within table TBTCO on the satellite system.
Some external job schedulers delete the job information in table TBTCO after the job has finished. For these, the jobs cannot be monitored via SAP Solution Manager.
SAP will provide an integration between Redwood Cronacle and Business Process Monitoring in SAP Solution Manager.
© SAP AG
SM300
3-36
Define Monitoring Schedule
Node Monitoring Schedule Choose days relevant for executing the monitoring and specify job period
Check the loaded job scheduling information.
© SAP AG 2009
Period can also be uploaded from satellite system (see previous slide).
© SAP AG
SM300
3-37
Per Monitoring Object: Define Thresholds Define thresholds for the monitoring objects in the subnodes to node Business Processes / / / in the session tree. Define alert thresholds.
Define alert status
© SAP AG 2009
Depending on the monitoring type there are different nodes in the session tree where the alert thresholds can be defined.
During the monitoring, alerts can have the statuses green, yellow and red (pretty much like a traffic light).
Some alerts are status alerts (like job cancellation). These alerts are raised if a certain status is reached for a technical object (e.g. job cancels). For these, you don’t have to specify thresholds but instead define which alert should be raised if the status is reached.
© SAP AG
SM300
3-38
Per Monitoring Object: Assign Monitoring & Analysis Tools Define Solution Support Organization
In node Business Processes / / / Analysis & Monitoring Tools you can assign transactions to the monitoring type that should be used for the error handling procedures in case of an alert.
Choose Business Process and Business Process Steps to be monitored Define Monitoring Objects per Business Process Step Per Monitoring Object: Provide technical details and threshold values for the alerts Assign monitoring & analysis tools Set up monitoring tasks Configure automatic emails and Service Desk messages
Assign, delete or insert monitoring transactions. © SAP AG 2009
The monitoring transactions defined here will appear as direct links from the SAP Solution Manager to the satellite system during the handling of the monitoring, enabling you to jump directly from an alert in the Solution Manager into the transaction in the respective satellite system.
Monitoring transactions may include customer written transactions. In particular, there is no crosschecking if the entered transactions make sense for the respective monitoring type or if they exist at all.
Transactions can be called on the satellite system or directly on the SAP Solution Manager system.
© SAP AG
SM300
3-39
Per Monitoring Object: Assign Monitoring URLs In node Business Processes / / / Analysis & Monitoring Tools you can assign URLs that should be used for error handling in case of an alert.
Assign, delete or insert URLs for error handling.
© SAP AG 2009
The URLs defined here will appear as direct links from the SAP Solution Manager to the Internet during the handling of the monitoring, enabling you to jump directly from an alert in the Solution Manager into the respective web page where further information regarding the monitoring object could be provided, i.e. further paths to analyze the problem or a knowledge database in the intranet where you can check for repetitive problems.
As well as for the monitoring transactions, there is no cross-checking if the entered URLs make sense for the respective monitoring type or if they exist at all.
Enter full URL in the popup of field “URL” in the table.
© SAP AG
SM300
3-40
Per Monitoring Object: Set up Monitoring Tasks
Define Solution Support Organization Choose Business Process and Business Process Steps to be monitored
Node Business Processes / / / Monitoring Activities provides the possibility to define activities sorted by the monitoring objects that have to be carried out in the regular monitoring of the business processes.
Define Monitoring Objects per Business Process Step Per Monitoring Object: Provide technical details and threshold values for the alerts Assign monitoring transactions Set up monitoring tasks Configure automatic emails and Service Desk messages
© SAP AG 2009
With the persons you have assigned to monitoring teams during the definition of the solution support organization you now can define responsibles for the monitoring of the customized monitoring objects. You can specify what exactly each person has to do for monitoring and what has to be done with alerts. The monitoring activities you have defined here you can later on generate into a MSWord Report, detailing for each team which monitoring activities the respective team is responsible for.
© SAP AG
SM300
3-41
Set up Monitoring Activities
The following information can be maintained:
Who is supposed to monitor (team and person)
How often is supposed to be monitored starting when (frequency and start time)
What does a problem indicate (problem indicators)
What has to be done in case of a problem (error handling)
Who has to be contacted if the problem can’t be solved (escalation path).
© SAP AG 2009
In the table 'Monitoring Activities' it is possible to specify: y Monitoring Team: Use the value help. The teams provided there have to have been defined before in the check 'Solution Support Organization'. y Person Resp.: Use the value help. The members of the monitoring teams have to have been specified before. y Frequency: Use the value help to specify at what frequency the specific monitoring activity is required. y Start Time: Specify at what time the required monitoring activity should start. y Problem Indicator: Describe, in a few words, what indicates a problem or error. y Error Handling: Briefly describe the way how to react in case of problems or errors, i.e. how to solve the problem/correct the error y Escalation Path: Succinctly specify how to proceed, if the problem cannot be solved by the person responsible.
© SAP AG
SM300
3-42
Per Monitoring Object: Configure Automatic Emails and Service Desk Messages Define Solution Support Organization Choose Business Process and Business Process Steps to be monitored Define Monitoring Objects per Business Process Step Per Monitoring Object: Provide technical details and threshold values for the alerts Assign monitoring transactions Set up monitoring tasks
You can set up notifications (emails or Service Desk messages) to be sent in case of alerts in node Business Processes / / / Notifications of the session tree. Prerequisites for the notifications to work are: Automatic email:
Transaction SCOT has been set up in the BPMon setup client of the SAP Solution Manager system Existing user in the BPMon setup client of the SAP Solution Manager system that has a valid email address assigned
Automatic Service Desk message:
Configure automatic emails and Service Desk messages
Service Desk has been set up in the SAP Solution Manager Business Partners in role Person and Employee have to exist for the respective installed base on SAP Solution Manager.
These prerequisites were mentioned before as advanced prerequisites for Business Process Monitoring. © SAP AG 2009
You can also set up automatic notifications to be sent for the whole business process in node Business Processes / / Notifications. Notifications set up here in this node will be overwritten if you specify different notification settings on business process step level. If you leave the settings on step level empty, the settings for the whole business process will be taken into account.
The sending of notifications is triggered by the execution of certain coding which is executed periodically. Due to the period there can be a slight time difference between the occurrence of an alert and the notification being sent.
© SAP AG
SM300
3-43
Set up Automatic Notifications In tab Workflow Notifications you can set up automatic notifications to be sent via SAP Office. The recipient type can be chosen via the value help. Possible are:
Email address
Mobile telephone (SMS)
Local SAP Office mail
Remote SAP Office mail
Each alert for the monitoring type will trigger a notification to be sent. The sender is always a SAP user name of the BPMon client in SAP Solution Manager system.
Mark “Detailed” to include text details in email (solution, business process, business process step, etc.).
© SAP AG 2009
Email Address: y Specify sender (user from BPMon client with valid email address) y Specify valid email address as recipient address y Recipient type U
Mobile Number y Specify sender (user from BPMon client with valid email address) y Specify the mobile number as follows: SMS:0049111111111 y Recipient type K
Local SAP Office Mail y Specify sender (user from BPMon client) y Specify user name as recipient address y Recipient type B
Remote SAP Office Mail y Specify sender (user from BPMon client) y Specify user name as recipient address y Specify Target System ID and Target Client y Specify Recipient type R
© SAP AG
SM300
3-44
Set up Automatic Service Desk Messages In tab Service Desk Messages you can set up automatic messages to be sent to the Service Desk of the SAP Solution Manager. Specify the following
Priority of the message Queue to which the message is to be sent Reporter (who is reporting the message) Processor (who is to solve the message) Text Template for the problem
By marking “Automatic” the message will be sent automatically. In this case, you need to specify what number of yellow or red alerts should trigger the creation of a Service Desk message.
© SAP AG 2009
Only if you want the messages to be sent automatically you have to specify the reporter and the number of yellow and red alerts that should trigger the sending of the message.
The text template is disregarded for automatic messages. For manually created messages the text template helps you to provide the correct information to the service desk employee.
SAP Solution Manager provides a certified interface via which 3rd party Service Desk tools can connect to the Service Desk within SAP Solution Manager. This way, Service Desk messages created in SAP Solution Manager can be automatically forwarded to these 3rd party Service Desk tools.
© SAP AG
SM300
3-45
Exercise: Configure Monitoring Customizing
Exercise: Configure Monitoring Customizing
© SAP AG 2008
© SAP AG
SM300
3-46
Setup Procedure Business Process Monitoring in SAP Solution Manager Where
Details
SAP Solution Manager: • Entrance Screen
Create Solution
SAP Solution Manager: • System Maintenance
Create Logical Component
• Create Product, Server, Database and System • Create RFC Destinations and Maintain SAP Server Names • Create Logical Component
Create Business Process
• • • • •
SAP Solution Manager: • Solution Directory
• Create Solution
SAP Solution Manager: • BPMon Setup Session
Set up Monitoring Customizing in SAP Solution Manager
SAP Solution Manager: • BPMon Setup Session
Generate
Assign Logical Components to Solution Create Contact Persons Choose Business Scenario Create Business Process and Business Process Steps Arrange Process Graphic and Create Process Flows
• Define Solution Support Organization • Choose Business Process and Process Steps to be monitored • Define Monitoring Objects per Step Per Monitoring Object: • Provide technical Details and Threshold Values for the Alerts. • Assign Monitoring & Analysis Tools and Set up Monitoring Tasks. • Set up Automatic Emails and Service Desk Messages • Set Data Collector Frequencies • Generate Monitoring Customizing
© SAP AG 2008
© SAP AG
SM300
3-47
Generate Customizing
SAP Solution Manager
Satellite Systems
Setup Business Process Monitoring session
Generate Internal Tables
© SAP AG 2009
Monitoring Customizing is generated for each business process individually.
Monitoring Customizing is written into internal tables.
No information is transferred to CCMS at this point.
Customizing can only generated for business processes marked as productive.
When you enter the part “Operations” of your solution after generating monitoring customizing for the first time a Business Process Monitoring session is created for the respective business process.
© SAP AG
SM300
3-48
Data Collector Frequencies
The different monitoring types are monitored via different data collectors. You can specify different monitoring intervals for the different types.
Specify the monitoring intervals for the different monitoring types.
© SAP AG 2009
Job can be distinguished into critical jobs (critical in the sense of monitoring, meaning the information about the job should be collected more frequently) and non-critical jobs (monitoring information can be collected less frequently).
Data collection is normally triggered not more frequently than every 5 minutes (technical restriction). This means 5 minutes is the lowest possible data collection frequency that can be entered.
Data collection periods can be set differently for the different monitoring objects.
© SAP AG
SM300
3-49
RFC Server Groups
The definition of a server groups allows you to control the resources used by RFC calls from SAP Solution Manager to the satellite systems. Use transaction RZ12 to maintain RFC groups.
Specify the RFC Server group being used by Business Process Monitoring
© SAP AG 2009
© SAP AG
SM300
3-50
Generate Monitoring Customizing
Choose 'Generate Customizing'.
Generation information is displayed in this area. After the Business Process Monitoring has been set up the Customizing has to be generated in order to create the Business Process Monitoring Session in the SAP Solution Manager. The customizing is generated in node Business Processes / / Generate Monitoring Customizing © SAP AG 2009
This is the very last step before activating the monitoring. The Customizing must be generated individually for each business process that is to be monitored. Once you generated the Customizing for a particular business process, a so-called Business Process Monitoring Session will be created (i.e., you will get a single Business Process Monitoring Session per business process in the Operations section of the SAP Solution Manager). When Customizing is generated, generation information is displayed in table area of this check, including error messages (E) in case of a failed Customizing generation.
The generation of the customizing takes place on the SAP Solution Manager system. During the generation of the customizing the following takes place: y The customizing information is written into tables in the SAP Solution Manager. y The Business Process Monitoring Session is created.
No data is passed to the satellite systems at this stage.
Customizing can be generated only for business processes that have been set to 'productive'. Otherwise the generation of the Customizing is just simulated. You can set the business process productive in the Operations Setup section. Go to ‘Solution Landscape/ Solution Landscape Maintenance, navigate to the scenario level and there choose 'Set to productive' . The same should be done on business process level.
© SAP AG
SM300
3-51
List of Configured Monitoring Customizing
Select button “Word Document” to create the list of the generated monitoring configuration.
© SAP AG 2009
MS Word has to allow access to visual basis projects. Otherwise the creation of the report fails.
You can access older list via Goto Æ Document Attachment.
© SAP AG
SM300
3-52
Exercise: Generate Monitoring Customizing
Exercise: Generate Monitoring Customizing
© SAP AG 2008
© SAP AG
SM300
3-53
Setup Procedure Business Process Monitoring in SAP Solution Manager Where
Details
SAP Solution Manager: • Entrance Screen
Create Solution
SAP Solution Manager: • System Maintenance
Create Logical Component
• Create Product, Server, Database and System • Create RFC Destinations and Maintain SAP Server Names • Create Logical Component
Create Business Process
• • • • •
SAP Solution Manager: • Solution Directory
SAP Solution Manager: • BPMon Setup Session
SAP Solution Manager: • BPMon Setup Session SAP Solution Manager: • BPMon Session
• Create Solution
Set up Monitoring Customizing in SAP Solution Manager
Assign Logical Components to Solution Create Contact Persons Choose Business Scenario Create Business Process and Business Process Steps Arrange Process Graphic and Create Process Flows
• Define Solution Support Organization • Choose Business Process and Process Steps to be monitored • Define Monitoring Objects per Step Per Monitoring Object: • Provide technical Details and Threshold Values for the Alerts. • Assign Monitoring & Analysis Tools and Set up Monitoring Tasks. • Set up Automatic Emails and Service Desk Messages
Generate
• Set Data Collector Frequencies • Generate Monitoring Customizing
Activate
• Activate Monitoring
© SAP AG 2008
© SAP AG
SM300
3-54
Activate Monitoring
SAP Solution Manager
Satellite Systems
Business Process Monitoring session Activate CCMS
Internal Tables
CCMS
© SAP AG 2009
There is one Business Process Monitoring session per business process.
The most current generated customizing is considered for the activation.
MTEs are created in CCMS with the Activation.
© SAP AG
SM300
3-55
Business Process Monitoring Session
In area 'Operations' choose ‘Solution Monitoring / Business Process Monitoring' and click on the alert icon for the entire business process to navigate to the monitoring session.
© SAP AG 2009
The Business Process Monitoring is activated in the Business Process Monitoring Session. This session is available in the SAP Solution Manager only after the Customizing for the setup of the Business Process Monitoring has been generated.
While there is one Setup Business Process Monitoring Session that includes all business processes there are several Business Process Monitoring Sessions, one for each business process that is monitored.
© SAP AG
SM300
3-56
Business Process Monitoring Session
The session tree of the Business Process Monitoring Session contains just the node “Activation” when no monitoring is active. This node has several tables: Protocol Monitoring Data Retention Times Alert Msg. Language Time Frame Job Monitoring Report
© SAP AG 2009
You can activate the monitoring with the default values maintained in this node.
Alerts for monitoring types will be stored in the Business Process Monitoring Session once the monitoring is activated. In order to minimize the amount of data that has to be held there you have to specify the storage time for the data in the session. Reorganization takes place automatically every time you enter the Business Process Monitoring Session. Aggregated alerts are not deleted since they are used for Service Level Reporting.
© SAP AG
SM300
3-57
Activate Monitoring
Choose to activate Business Process Monitoring.
© SAP AG 2009
Before Business Process Monitoring can be performed it has to be activated in the SAP Solution Manager. Since separate Business Process Monitoring Sessions exist for the different business processes the monitoring can be activate/deactivated separately for each business process.
During the activation of the Business Process Monitoring the following takes place: y The customizing is transferred into the satellite systems. y Monitoring Tree Elements (MTE's) are created in the RZ20. y Data collectors are initialized and started. y If the Monitoring is activated for the first time, background job BPM_ALERT_REORG (report DSWP_BPM_REORGANISATION) is scheduled in SAP Solution Manager with frequency once a day. During the runtime, this report checks in each Solution using Monitoring if stored alerts meet the time window specified by the data retention time setting in the Business Process Monitoring Setup session, older alerts will be deleted.
© SAP AG
SM300
3-58
Activation Protocol and Deactivation
Sub nodes have been created in the session tree.
For business processes with activated monitoring you can deactivate the monitoring here.
Ideally the protocol contains just the information about who last activated when. © SAP AG 2009
In case of error messages in the protocols for Generation or Activation check SAP Note 705569 for further details and explanations.
© SAP AG
SM300
3-59
Exercise: Activate Monitoring Customizing
Exercise: Activate Monitoring Customizing
© SAP AG 2008
© SAP AG
SM300
3-60
Complete Setup Procedure Business Process Monitoring in SAP Solution Manager Details
Where SAP Solution Manager: • Entrance Screen SAP Solution Manager: • System Maintenance SAP Solution Manager: • Solution Directory
Create Solution
• Create Solution
Create Logical Component
• • • • •
Create Business Process
SAP Solution Manager: • BPMon Setup Session
Set up Monitoring Customizing in SAP Solution Manager
SAP Solution Manager: • BPMon Setup Session
Generate
SAP Solution Manager: • BPMon Session
Activate
SAP Solution Manager: • Monitoring Graphic • BPMon Session
Use the Monitoring
• Create Product, Server, Database and System • Create RFC Destinations and Maintain SAP Server Names • Create Logical Component Assign Logical Components to Solution Create Contact Persons Choose Business Scenario Create Business Process and Business Process Steps Arrange Process Graphic and Create Process Flows
• Define Solution Support Organization • Choose Business Process and Process Steps to be monitored • Define Monitoring Objects per Step Per Monitoring Object: • Provide technical Details and Threshold Values for the Alerts. • Assign Monitoring & Analysis Tools and Set up Monitoring Tasks. • Set up Automatic Emails and Service Desk Messages • Set Data Collector Frequencies • Generate Monitoring Customizing • Activate Monitoring • • • • • •
Observe Alerts Relative to the Business Process Check Detailed Alert Information and Check for Open Alerts Review Historic Alerts Analyze Problem in the Satellite System Create Service Desk Message Confirm Alerts for Solved Problems
© SAP AG 2009
The complete setup procedure of Business Process Monitoring in SAP Solution Manager can be foundin the Media Library of BPM on the SAP Service Marketplace:
http://service.sap.com/bpm
Æ Media Library ÆTechnical Information ÆBusiness Process Monitoring – Setup Roadmap
© SAP AG
SM300
3-61
Use Business Process Monitoring in SAP Solution Manager Graphical Display
Clicking on an alert icon brings you to a detailed overview of the alerts for the respective business process step.
Choose alert. Choose alert.
Business Process Monitoring Session
Choosing an alert brings you to the alert history in the Business Process Monitoring Session.
© SAP AG 2009
© SAP AG
SM300
3-62
Alert Hierarchy Monitoring in the SAP Solution Manager is realized via the display of alerts. The following alerts are possible:
Priority
high
low
Alert! Very critical situation!
Action required.
Status not defined Critical situation
Action required.
Warning Checking necessary
Analysis recommended.
Okay.
No action required.
Alerts are usually called by their color, i.e., green, yellow, gray, or red alert.
© SAP AG 2009
The alert definition inside the SAP Solution Manager is valid for all monitoring types. The rating enables focusing on critical systems, significant business processes, major process steps and interfaces.
The alerts in the table are sorted by descending priority, meaning that an area containing green and yellow alerts will display a yellow summarization alert. Observe that a grey alert has a higher priority than a yellow alert!
© SAP AG
SM300
3-63
More Details how to set up BPMon
More details for setting up BPMon can be found in the Media Library of BPM on the SAP Service Marketplace: http://service.sap.com/bpm Æ Media Library ÆTechnical Information
Business Process Monitoring – Setup Roadmap Setup Guide – Business Process Monitoring
© SAP AG 2009
Business Process Monitoring – Setup Roadmap: Powerpoint presentation with the description of the most important “milestone steps how to setup Business Process Monitoring “from scratch”, ie. starting from the creation of systems up to the activation of a BPMon solution.
Setup Guide – Business Process Monitoring: Adobe PDF file describing in detail how to setup Business Process Monitoring with a focus on different monitoring types.
© SAP AG
SM300
3-64
Appendix
Appendix
© SAP AG 2009
© SAP AG
SM300
3-65
Appendix: CCMS Monitoring Infrastructure
1. Technical Requisites 2. Setup Procedure Appendix: CCMS Monitoring Infrastructure
© SAP AG 2009
© SAP AG
SM300
3-66
Monitoring Infrastructure SAP Solution Manager
Satellite System
200
800 BPMon Graphic
BPMon Session
Data Collectors
Service Desk SCOT
BPMon Engine
User SM_BPMO
User SOLMANTT4200
000
Data Collectors
000 User Central CCMS SAPSYS
Local CCMS
© SAP AG 2008
For Business Process Monitoring in SAP Solution Manager several infrastructure components are used. The central infrastructure component is the BPMon Engine on SAP Solution Manager. The BPMon engine is client specific. It calls the data collectors on the satellite systems via the READ RFC destination and determines if an email or service desk message needs to be sent for the alerts. If a message needs to be sent it creates the messages and hands it over to the respective infrastructure component (SAPConnect or Service Desk). The BPMon engine stores the alerts for the business process (until they are reorganized according to the settings specified in the BPMon session) which are the source of the BPMon session.
The BPMon engine is triggered every 5 minutes by the Central CCMS on SAP Solution Manager. The central CCMS also stores the alerts for the business process and is the source for the BPMon graphic in SAP Solution Manager.
© SAP AG
SM300
3-67
Computing Center Management System (CCMS)
CCMS of SAP systems provides a monitoring infrastructure that is used by the SAP Solution Manager. CCMS is called via transaction RZ20. To get an overview of all available alerts choose SAP CCMS Technical Expert Monitors Æ System / All Monitoring Segments / All Monitoring Contexts. © SAP AG 2009
In RZ20 you see: y Measured values and alerts y Various monitors y Organized by topic y Tree structure y Highest alert of a sub-tree is reported upward.
© SAP AG
SM300
3-68
Monitoring Tree Element (MTE)
MTE
The monitoring objects available in the CCMS are structured as nodes in a hierarchy. A node is called Monitoring Tree Element (MTE). © SAP AG 2009
The Alert Monitor provides the following functions: y You can use the Alert Monitor to obtain complete and detailed monitoring of all SAP, the host systems, and the database. y All errors generate alerts, which are displayed in a tree structure. y The alerts contain a status indicator with a colour and a numerical value. Yellow represents a warning and red a problem, and the numerical value represents the severity of a possible error. In the tree structure, the most severe alerts are displayed upwards in the display hierarchy. If a tree node is not displaying an alert, there is no error in the whole branch below it. y You can assign analysis and auto reaction methods to the alerts. These assist you to process the error quickly. If you double click the alert, the monitoring architecture starts the assigned analysis method (for example, the job management transaction for a job that has terminated prematurely). An auto reaction method, on the other hand, starts automatically as soon as the alert occurs. Auto reaction methods include executing operating system commands, and sending an e-mail or SMS message to the system administrator. y The Alert Monitor contains various views in which either the current or the open (that is, those that have not yet been analysed) problem messages are displayed. Alerts are also archived. y Threshold values, methods and detailed help for a large number of monitoring attributes, and three extensive monitor sets with monitors for all aspects of system management are predefined in the monitoring architecture on the basis of best practices and are available for you to use in every SAP system. y You can individually adjust all settings and configure your own monitors.
© SAP AG
SM300
3-69
Properties of MTE
Choose to change properties.
Choose to display properties.
Each MTE has properties assigned that determine when and how which alert is to be reported. Mark the respective MTE and choose “Properties”. © SAP AG 2009
© SAP AG
SM300
3-70
Properties of MTE: Performance Attributes
Performance Attributes
MTE
In tab “Performance Attribute” you can define:
Comparative Value to be taken into consideration for alerts Threshold Values for alerts
Trend for comparative value in relation to threshold values
© SAP AG 2009
The trend determines whether an alert is to be raised if the comparative value falls below or exceeds a threshold value.
© SAP AG
SM300
3-71
Properties of MTE: General Settings
General Settings
MTE
In tab “General” you can define:
Warm up phase (no alerts triggered within the first seconds after the MTE becomes active) Sleep Modus (automatically deactivate in the absence of values) © SAP AG 2009
© SAP AG
SM300
3-72
Methods for MTEs
Methods
MTE
In tab “Methods” you can assign:
Frequency for the data collection method (how often is alert data to be collected) Data collection method (how is the alert data to be collected) Auto-reaction method (what should be done in case of alerts) Analysis method (what is executed with a double click on the alert).
© SAP AG 2009
An example for an auto-reaction method is the automatic sending of emails in case of an alert.
© SAP AG
SM300
3-73
Monitoring Tree Element
MTE
© SAP AG 2009
During the activation of Business Process Monitoring in the SAP Solution Manager MTEs will be created both on the SAP Solution manager system and on the satellite systems. The properties for these MTEs will be set automatically. Some of the properties will not be displayed in RZ20. However, if already existing MTEs are included in the Business Process Monitoring or when Interface Monitoring is set up, the thresholds changed during the set up will be updated in the RZ20 during the monitoring activation. Some other properties can only be changed in RZ20 directly and have to be taken into consideration when setting up the monitoring.
© SAP AG
SM300
3-74
MTEs Created with BPMon Activation
With the Activation of BPMon MTEs are created. Most MTEs are created in the CCMS of the SAP Solution Manager system.
© SAP AG 2009
© SAP AG
SM300
3-75
Monitoring Types in the Central and Local CCMS
SAP SAP Solution Solution Manager Manager
Central RZ20
Satellite Satellite System System
RFC
Application Monitor Background Job Due List Log Application Log Document Volume
Local RZ20 Dialog Performance Update Error Other CCMS Interface Monitor (CCMS)
© SAP AG 2009
MTEs for the respective monitoring objects will be created either in the local or central CCMS.
For the objects that are monitored via the central CCMS you will have to define monitoring frequencies later on, indicating how often the data collector is supposed to run. The frequency determines in the end how current the monitoring information in the SAP Solution Manager will be. If for instance a collector is supposed to run only once per day the monitoring information will be current only once per day. If , on the other hand, collectors run too frequently you might unnecessarily increase the workload on the monitored system. The reaction times of the support organization should determine how often monitoring data is supposed to be collected.
© SAP AG
SM300
3-76
Current Versus Open Alerts
In the past there have been picking errors for critical materials.
Currently no picking error exist for critical materials.
The current status of an alert shows the status determined during the last collector run.
The open status of an alert shows alerts that have occurred in the past and that have not yet been marked as solved.
© SAP AG 2009
To mark a alert as solved is called “confirming the alert”. By confirming an alert you take it off the list of open alerts.
Open alerts are displayed in the CCMS until the are confirmed or until they are reorganized.
© SAP AG
SM300
3-77
© SAP AG
SM300
3-78
Exercises Unit:
Monitoring Configuration
Lesson:
Technical Prerequisites
Exercise 5: Check Technical Prerequisites At the conclusion of this exercise, you will be able to: • Check if a SAP Solution Manager system is ready for Business Process Monitoring • Check if a satellite system is ready for Business Process Monitoring. IDES now wants to use SAP Solution Manager as tool for Business Process Monitoring. Before the actual setup of the monitoring can take place, you have to ensure that SAP Solution Manager TT4 is ready for Business Process Monitoring and that you access to all information relevant for Business Process Monitoring in SAP Solution Manager. 5-1 Prerequisites on SAP Solution Manager system 5-1-1
List the points you have to check on the SAP Solution Manager system in the table below.
5-1-2
Check the points in the SAP Solution Manager system and note down your findings.
Point
© SAP AG
Status
SM300
3-79
5-2
Prerequisites on Satellite system 5-2-1
List the points you have to check on the satellite system in the table below:
5-2-2
Check the points in the satellite system and note down your finding
Point
5-3
Status
Access SAP Service Marketplace 5-3-1
Access the quicklink /BPM in the SAP Service Marketplace. Access the Setup Roadmap. In the details, find the task “Create Contact Persons”. Where, according to this roadmap, are contact persons created? Answer:______________________________________________________
5-3-2
Access the Setup Guide for Business Process Monitoring. Find out which SAP Note contains the important messages in the activation and generation protocol. Answer:______________________________________________________
© SAP AG
SM300
3-80
Solutions Unit:
Monitoring Configuration
Lesson:
Technical Prerequisites
Exercise 5: Check Technical Prerequisites
5-1 Prerequisites on SAP Solution Manager system Point
Status
Dialog User with correct Authorization
Check in transaction /nSU01
Correct version of software components installed
Check via SAP Menu Æ System Æ Status Æ SAP System data Æ Component version Æ Magnifier glass
Sufficient Authorizations assigned
ST400 SP15 ST-SER 700_2008_1 SP4 ST-A/PI 01K BI_CONT 703 SP8 System Landscape maintained in SAP Solution Manager
executed in previous exercises
RFC Connections maintained
Check the existence of RFC destination BPM_LOCAL_200 in transaction /nSM59. Check the correct functioning by accessing the details for the RFC destination and choosing Utilities Æ Test Æ Authorization Test. Observe the user maintained in this RFC destination for the next point of the technical prerequisites. Check the assignment of RFC destinations in transaction /nRZ21 Æ Topology Æ System Overview Æ Display Overview. The following RFC destinations are assigned •
SM_TT5CLNT800_READ
•
SM_TT5CLNT800_TRUSTED
Check the correct functioning of the RFC destination in transaction /nSM59 as described above for the local RFC destination. Check the correct assignment of the RFC destinations in transaction /nSMSY. There go to ECC system TT5 via Landscape Components Æ Systems Æ SAP ECC Æ TT5 Æ SAP ECC Server. The assignment of the RFC destinations are visible in tab Client. The destination in column RFC for Solution Manager is the destination used for dialog © SAP AG
SM300
3-81
login to the satellite system. Remark that even though only the RFC destinations to client 800 are assigned in transaction /nRZ21, there still have to be RFC destinations to client 600 if that should be monitored as well. General Settings maintained Check time setting for the user in the BPM_LOCAL_200 RFC destination in transaction /nSU01, in tab Defaults. Solution created in SAP Solution Manager
executed in previous exercises
Business Processes documented in SAP Solution Manager
executed in previous exercises
5-2
Prerequisites on Satellite system 5-2-1
List the points you have to check on the satellite system in the table below:
5-2-2
Check the points in the satellite system and note down your finding
Point
Status
Dialog User with correct Authorization
Check in transaction /nSU01 Sufficient Authorizations assigned
Correct version of software components installed
Check via SAP Menu Æ System Æ Status Æ SAP System data Æ Component version Æ Magnifier glass ST-PI 700_2005_1 SP6 ST-A/PI 01K
© SAP AG
SM300
3-82
5-3
Access the SAP service Marketplace. 5-3-1
Access http://service.sap.com/bpm in the internet. The Business Process Monitoring Setup Roadmap can be found under Media Library -> Technical Information -> Business Process Monitoring - Setup Roadmap. Access the Setup Roadmap. Answer: In step “Create Business Process” the second task is “Create Contact Persons”. According to the Roadmap, this task is executed in the Solution Directory of SAP Solution Manager. If you choose Create Contact Persons you are brought to a slide which explains how contact persons are created in SAP Solution Manager 7.0.
5-3-2
Access the Setup Guide for Business Process Monitoring via Media Library -> Technical Information -> Setup Guide - Business Process Monitoring. Answer: The SAP Notes are detailed in the last chapter of the Setup Guide. SAP Note 705569 contains the important messages in the activation and generation protocol.
© SAP AG
SM300
3-83
© SAP AG
SM300
3-84
Exercises Unit:
Monitoring Configuration
Lesson:
Setup Procedure
Exercise 6: Configure Monitoring Customizing At the conclusion of this exercise, you will be able to: • Set up monitoring customizing for a sample background job for Business Process Monitoring within SAP Solution Manager Many aspects of the setup procedure are independent of the actual monitoring functionality that is configured. Therefore, company IDES wants to start by configuring monitoring for the background job for sales order creation in business process “Order to Cash”.
6-1
How is the setup methodology for Business Process Monitoring in SAP Solution Manager connected to the general implementation methodology for Business Process Monitoring? Answer:______________________________________________________
6-2
Set up Support Teams 6-2-1
Access the Setup Business Process Monitoring session of your solution
6-2-2
Create the following teams in node “Solution Support Organization”:
© SAP AG
•
BPMon Team
•
Job Scheduling Team
SM300
3-85
6-3-2
Assign the following members to the teams: Team Name Job John Smith Scheduling Team Belinda BPMon Hampert Team
Company SALES AG
Phone 01234-5678-1
BCD Systemhaus
01234-5678-3
Question: How do you get persons to show up in the value help for the support teams? Answer: _____________________________________________________________ Create the missing members of the support organization and assign them to your support organization. 6-2-4
6-3
Assign the following team responsibilities: •
BPMon Team (Business Process Monitoring)
•
Job Scheduling Team (Program Scheduling Management)
Set up Monitoring Customizing 6-3-1
Choose to monitor business process “Order to Cash” and business process step 3 “Create Sales Order” (on SAP ECC). What is the status of business process ‘Order to Cash’? Answer:______________________________________________________ Which system /client is this business process step executed on? Answer:______________________________________________________
6-3-2
Select monitoring type Background Job in node (3) Create Sales Order [TT5] in table Monitoring Types. Save and go into sub-node Background Job. In tab Job Monitoring Objects enter job name “SD_CREATE*”. Flag “Select” and then choose “Check Job Identification”. In the pop-up double click on one of jobs called SD_CREATE_SALES_ORDERS_15MIN to load the scheduling information from the satellite system. Afterwards, enter “Urgent Orders” in field Job Identifier. What is the start procedure for the background job? Answer:______________________________________________________ Set the flag for “Critical” for this background job and choose to monitor MoFr (Monitoring Schedule).
6-3-3
In sub-node Start Delay define thresholds for the job start (10 minutes delay for yellow, 15 minutes delay for red). In sub-node Job Cancellation select rating “R” for the background job.
© SAP AG
SM300
3-86
6-3-4
In node Analysis & Monitoring Tools set up a link to transaction SM37 on the satellite system for the analysis of the background job. What did you observe when setting up this functionality? Answer:______________________________________________________ In addition set up a link to the SAP help http://help.sap.com for the analysis of job cancellations in this business process step. Short text for this link should be “SAP Help”
6-3-5
For the monitoring of background jobs assign Belinda Hampert of the BPMon Team as responsible. She should check the occurrence of alerts twice per day, starting at 08:00 a.m. Provide the following additional information for Mrs. Hampert: Problem Indicator: “Sales Order not created” Error Handling: “Check Job Log for cancellation. Unlock user. Open ticket on component SV-SMG-MON-BPM.” Escalation: “Inform Business Process Champion Mr. Meyer”
6-3-6
Set up automatic emails to be sent to your own email address for job cancellation alerts. Sender of these emails should be SAP user SM300-00. Check which email address is maintained for user SM300-00: Answer:______________________________________________________
6-3-7
Set up a text template for service desk messages in component SV-SMGMON-BPM. The template should contain the following fields: Job Log Error message: Job steps successfully completed:
© SAP AG
SM300
3-87
© SAP AG
SM300
3-88
Solutions Unit:
Monitoring Configuration
Lesson:
Setup Procedure
Exercise 6: Configure Monitoring Customizing
6-1
Connection of the setup methodologies Answer: The general implementation methodology for Business Process Monitoring has always to be followed when implementing BPMon. Steps within these methodologies can be realized via one or more steps in the BPMon Setup Roadmap for SAP Solution Manager.
6-2
Set up Support Teams 6-2-1
Access the Setup Business Process Monitoring session via Operations Setup
Æ Solution Monitoring Æ Business Process Monitoring Æ Setup Business Process Monitoring.
6-2-2
Go to node Business Process Monitoring Setup Æ Solution Support Organization. In tab Solution Support Organization enter the teams.
6-2-3
Answer: The contact persons have to be defined in the contact definition of the solution directory. To create contacts, leave the Business Process Monitoring Setup session and choose Solution Landscape Æ Solution Landscape Maintenance. In the Solution Directory choose button “Contacts”. In the next screen, enter the contact information as given in the exercise in node “Contacts”, tab “Contacts”. Save. Afterwards go back to the Business Process Monitoring Setup session. There, go to node Business Process Monitoring Setup Æ Solution Support Organization Æ Team “BPMon Team”. In tab Team Members assign contact Belinda Hampert via value help in column Name. Go to sub-node Team “Job Scheduling Team”. In tab Team Members assign contact John Smith via value help in column Name.
6-2-4
Go to node Team “BPMon Team”. In tab Monitoring Roles assign role Business Process Monitoring in column ‘Assign?’. Go to node Team “Job Monitoring Team”. In tab Monitoring Roles assign role Program Scheduling Management in column ‘Assign?’.
© SAP AG
SM300
3-89
6-3
Set up Monitoring Customizing 6-3-1
Go to node Business Process Monitoring Setup -> Business Processes. Answer: You can observe the status of the business process in tab “Business Processes”. Status for business process ‘Order to Cash’ should be ‘Production’. Check whether the flag for ‘Planned?’ is set for the business process. If the flag is set you have to return to the Solution Directory of your solution and set the status for the business process to ‘Production ’(to do so access node SM300-## Landscape -> Business Scenarios -> Outbound Logistics -> Business Processes in the Solution Directory. There in tab Structure set the status to “Production” and save. In addition to the business process the business scenario also has to be in status “Production”.) Afterwards, return to the BPMon Setup session. Go to node Business Process Monitoring Setup Æ Business Processes. In tab Business Processes select business process ‘Order to Cash’ and save. Sub-node Order to Cash (Prod.) has been created while saving. There, in tab Business Process Steps select step 3 Create Sales Order (TT5) and save. Answer: In tab Business Process Steps you can see that step 3 is executed on system TT5 in client 800.
6-3-2
When you select the monitoring type “Background Job”, observe some monitoring types are automatically reselected. These flags are set according to the processing information you provided for the step within the business process documentation. Answer: Start procedure for the background job is by time every 5 minutes. Set the flag “Critical” in node Background Job. Select the days relevant for monitoring in sub-node Monitoring Schedule.
6-3-3
In sub nodes Start Delay and Job Cancellation adjust the following Alert Configuration: Alerts
Threshold Yellow
Threshold Red
Start Delay
10 min.
20 min.
Job Cancellation
© SAP AG
R
SM300
3-90
6-3-4
In node Analysis & Monitoring Tools in table Transactions/Programs the following entries should be visible: Monitoring Type
Monitoring Object
Call
Type
Call Option
Background Job
Urgent Orders
SM37 Transaction
2
Answer: You did not have to maintain these settings. They were there per default. In table URLs you had to maintain the following entries: Monitoring Type
Monitoring Object
Short Text
URL
Background Job
Urgent Orders
SAP Help
http://help.sap.com (via popup)
6-3-5
In node Monitoring Activities in table Monitoring Activities you had to maintain the following entries:
Monito ring Type
Monito ring Object
Monitoring Team
Person Resp.
Frequency
Start Time
Problem Indicator
Error Handling
Escalation Path
Backgr ound Job
Urgent Orders
BPMon Team
Belinda Hampert
twice a day
08:00
Sales Order not created
Check Job Log for cancellation. Unlock user. Open ticket on component SV-SMGMON-BPM.
Inform Business Process Champion Mr. Meyer
6-3-6
In node Notifications you had to maintain the following entries in table Workflow Notifications:
Monitoring Type
Monitoring Object
Sender
Recipient Address
Reci. Type
Background Job
Urgent Orders
SM300-00
U
…
Details x
…
By leaving the number of yellow and red alerts blank each alert will trigger one email. User SM300-00 exists in client 200 of TT4 and has the email address of your trainer assigned.
© SAP AG
SM300
3-91
6-3-7
Monitoring Type
In node Notifications you had to maintain the following entries in table Service Desk Messages:
Monitoring Object
Background Urgent Orders Job
© SAP AG
…
Text Template
Automatic
Job Log Error message: Job steps successfully completed:
SM300
3-92
Exercises Unit:
Monitoring Configuration
Lesson:
Setup Procedure
Exercise 7: Generating Monitoring Customizing At the conclusion of this exercise, you will be able to: • Set up monitoring customizing for a sample background job for Business Process Monitoring within SAP Solution Manager Many aspects of the setup procedure are independent of the actual monitoring functionality that is configured. Therefore, company IDES wants to start by configuring monitoring for the background job for sales order creation in business process “Order to Cash”.
7-1
Generate the monitoring customizing 7-1-1
Go to the Operations part of SAP Solution Manager for your solution. Navigate to area Business Process Monitoring. What can you see? Answer:______________________________________________________
7-1-2
Go back to “Setup Business Process Monitoring”. Set the data collection period for critical background jobs on TT5 to 10 minutes.
7-1-3
Generate the monitoring customizing for the business process “Order to Cash”. What kind of information is written into the satellite system TT5 with the generation of the customizing? Answer:______________________________________________________
7-1-4
Check the Generation protocol for error messages. What kind of error messages can you see? Are there any warning messages? Answer:______________________________________________________
7-1-5
Go again to the Operations part of SAP Solution Manager for your solution. Navigate to area Business Process Monitoring. What has changed? Answer:______________________________________________________
© SAP AG
SM300
3-93
© SAP AG
SM300
3-94
Solutions Unit:
Monitoring Configuration
Lesson:
Setup Procedure
Exercise 7: Generating Monitoring Customizing
7-1
Generate the monitoring customizing. 7-1-1
Leave the Setup Business Process Monitoring session via back (F3). Go to the Operations part of SAP Solution Manager in the navigation panel on the left hand side. Choose Solution Monitoring Æ Business Process Monitoring. Answer: You can see the business processes “Order to Cash”.
7-1-2
Go to the Operations Setup part of SAP Solution Manager in the navigation panel on the left hand side. Choose Solution Monitoring Æ Business Process Monitoring Æ Setup Business process Monitoring. In the Setup Business Process Monitoring session go to node Business Process Monitoring Setup Æ Data Collection Frequencies. There in table ‘Frequency of Data Collection’ enter period 10 minutes for critical jobs on TT5 and save.
7-1-3
Go to node Business Process Monitoring Setup Æ Business Processes Æ Order-to-Cash (Prod.) Æ Generate Monitoring Customizing. Choose button Generate Customizing. Answer: No information is written into satellite system TT5 at this stage.
7-1-4
Answer: No error and no warning messages should occur in the generation protocol.
7-1-5
Answer: Business process “Order to Cash” now has a little “match” icon next to its name.
© SAP AG
SM300
3-95
© SAP AG
SM300
3-96
Exercises Unit:
Monitoring Configuration
Lesson:
Setup Procedure
Exercise 8: Activate Monitoring Customizing At the conclusion of this exercise, you will be able to: • Activate Business Process Monitoring
Now the monitoring configuration can be activated.
8-1
Activate Go to the Business Process Monitoring session for business process “Order to Cash”. 8-1-1
In node Activation set the monitoring data retention times to 5 days for unaggregated monitoring data, 1 day after which the aggregation of monitoring data starts and 20 days for the time the aggregated monitoring data should be kept.
8-1-2
Activate the monitoring. Check the activation protocol for errors. What kind of error messages did you observe? What has caused these error messages? (Please do NOT change the error situation so that other students can also observe the behavior!) Answers:_____________________________________________________ What kind of data is transferred to satellite system TT5 at this stage? Answer:______________________________________________________
8-1-3
Go to the monitoring graphic for business process “Order to Cash”. What has changed with the activation? Answer:______________________________________________________ Go back to the Setup Business Process Monitoring session. What has changed in node Generate Monitoring Customizing for business process “Order to Cash”? Answer:______________________________________________________
© SAP AG
SM300
3-97
© SAP AG
SM300
3-98
Solutions Unit:
Monitoring Configuration
Lesson:
Setup Procedure
Exercise 8: Activate Monitoring Customizing
8-1
Leave the Setup Business Process Monitoring session via back (F3). Go to the Operations part of SAP Solution Manager in the navigation panel on the left hand side. Choose Solution Monitoring Æ Business Process Monitoring. Choose “match” icon for business process “Order-to-Cash” to access the Business Process Monitoring session. 8-1-1
8-1-2
In node Activation maintain the following entries in table Monitoring Data Retention Times: No
Parameter
Num. of Days
1
Time, the unaggregated monitoring data is kept
5
2
Time, after which the aggregation of monitoring data starts
1
3
Time, the aggregated monitoring data is to be kept
20
In node Activation choose button Activate Monitoring. Check table Protocol for error messages. Answer: You can observe the error message “Local RFC connection BPM_LOCAL_200 does not work”. Wait until the trainer has solved the error situation and activate again. Answer: During the activation the customizing for monitoring objects collected via the CCMS of the satellite system are transferred to the satellite system.
8-1-3
Answer: With the activation the “match” icon for the business process has changed to a grey diamond monitoring icon. The highest alert available within the business process is now displayed in the graphic. If no alert is there yet this is a grey alert icon. Answer: In node Generate Monitoring Customizing in the Setup Business Process Monitoring session there is now a button Generate + Activate Monitoring. With this button you can activate changes to the monitoring customizing directly from within the Setup Business Process Monitoring session.
© SAP AG
SM300
3-99
© SAP AG
SM300
3-100
© SAP AG
SM300
3-101
Using Business Process Monitoring
Course Overview Unit 1 Introduction to Business Process Monitoring Unit 2 Procedure Unit 3 Monitoring Configuration Unit 4 Using Business Process Monitoring
Unit 8
Data Consistency Monitoring
Unit 5 Cross-Application Monitoring
Unit 9
Reporting
Unit 6 Application Monitoring Unit 7 Interface Monitoring
Unit 10 Handover to Production Unit 11 Managing Jobs in SAP Solution Manager
© SAP AG 2008
© SAP AG
SM300
4-1
Business Process Monitoring: Unit Objectives
After completing this unit, you will be able to:
Use SAP Solution Manager as a tool within a Business Process Monitoring concept
Understand the basics of the BPMon Infrastructure
© SAP AG 2009
© SAP AG
SM300
4-2
Lesson 1: Using Business Process Monitoring
1. Using Business Process Monitoring 2. BPMon Infrastructure
© SAP AG 2009
© SAP AG
SM300
4-3
Using Business Process Monitoring
IDES uses the monitoring during the User Acceptance Testing before the GoLive to test the corresponding support procedures.
© SAP AG 2008
© SAP AG
SM300
4-4
SAP Standard for Business Process and Interface Monitoring IT Department
Business Department Key User
Business Process Operations
Business Process Champion
Application Management
Detect Alert Situation
Identify Application Problem
Execute Initial Analysis Create Service Desk message
Execute exception handling
Assign Service Desk message to issue RCA process Create action plan Change Request process
Sign-off alert resolution
Solve Service Desk message
© SAP AG 2008
Boxes mark areas that can be realized with SAP Solution Manager.
© SAP AG
SM300
4-5
Execute Monitoring Activity and Detect Alert Situation Business Process Operations Detect Alert Situation
Execute Initial Analysis
Monitoring procedure is executed automatically by SAP Solution Manager Alert is detected automatically SAP SAP Solution Solution Manager Manager
Create Service Desk message
Message Message
Business Operations Team
Sign-off alert resolution
© SAP AG 2009
© SAP AG
SM300
4-6
Notification in Case of Alert
Automatic Email reporting an alert
Business Operations
Automatic Service Desk message reporting an alert
© SAP AG 2009
The support employee can be notified of automatically if an alert in the business process has occurred. Then, the support employee can check the alert in SAP Solution Manager.
© SAP AG
SM300
4-7
Determine Business Relevance of Alert Business Process Operations
The alerts for the business process can be accessed in the Operations area of the SAP Solution Manager.
Detect Alert Situation
Execute Initial Analysis Create Service Desk message
You Youcan canaccess accessthe thealerts alertsvia viathe the monitoring graphic in area when monitoring graphic in area whenyou you click clickon onthe theBusiness BusinessProcess Process Name. Name.
Sign-off alert resolution
Summarization Summarizationalert alertfor forthis this specific business process specific business process
© SAP AG 2009
To access the monitoring graphic choose “Solution Monitoring Æ Business Process Monitoring” in the Operations area.
You can see the aggregated alert for the business process in the monitoring graphic. If you click on the name of the business process you'll be brought to a more detailed graphic of the business process with the separate steps listed and the alerts aggregated for these steps. The graphical display screen has the advantage of also providing aggregated alerts for the hardware and the systems if system monitoring has been set up in SAP Solution Manager.
© SAP AG
SM300
4-8
Observe Alerts Relative to Business Process Steps
Summarization Summarization alerts alerts for for all all software software components, components, hardware hardware components components and and business business processes. processes. Aggregated Aggregated System System Monitoring Monitoring alert alert for for satellite satellite system. system. Aggregated Aggregated alert alert for for business business process process step. step.
© SAP AG 2009
If you click on the alert symbol for an specific step, you will navigate to a more detailed graphic containing all the alerts corresponding to that business process step.
© SAP AG
SM300
4-9
Check Detailed Alert Information The detailed alert information for a business process step is accessible via left mouse click on the aggregated alert for this step.
Detailed Detailed Alerts Alerts for for aa single single business business process process step. step.
© SAP AG 2008
By clicking on an specific alert, you navigate to the Business Process Monitoring session, where you can see detailed historical information about this specific alert.
© SAP AG
SM300
4-10
View Alert List The detailed information for the historic alerts is available in the Business Process Monitoring session.
© SAP AG 2009
How often has the alert occurred before?
Which error handling procedures helped in the past?
Are similar problems already being analyzed by 2nd level support?
© SAP AG
SM300
4-11
Accessing Historical Alert Information
Graphical Display
Clicking on an alert icon brings you to a detailed overview of the alerts for the respective business process step.
Choose alert.
Choose alert.
Business Process Monitoring Session
Choosing an alert brings you to this alert in the Business Process Monitoring Session. © SAP AG 2009
© SAP AG
SM300
4-12
Alert Information Table ‘Alert List'
Table 'Alert Configuration'
Only for Background Job Monitoring: Table ‘Bg. Job Details'
© SAP AG 2009
Table “Alert List” y Contains the list of alerts that have occurred in the past for this monitoring object y Provides details about when the alerts have occurred and how much the thresholds have been exceeded. y Shows which of those alerts have been confirmed and which alerts are still open y The rating of the respective node in the session tree is determined by the highest open alert available for this monitoring object. This means that the rating for the node can be different from the current rating for this alert in the monitoring graphic.
Table “Alert Configuration” y Shows the currently active customizing for this alert. This customizing can differ from the customizing visible in the Setup Business Process Monitoring session.
For background jobs only: “Table ‘Bg. Job Details” y Lists the setting for the background job that is monitored. These settings can differ from the settings visible in the Setup Business Process Monitoring session.
© SAP AG
SM300
4-13
Execute Initial Analysis
Business Process Operations Detect Alert Situation
Execute Initial Analysis
Error Handling Procedures accessible in Alert History (Business Process Monitoring session) Link to Tools in Satellite System Link to Operations Handbook in Intranet
Create Service Desk message
Sign-off alert resolution
© SAP AG 2009
© SAP AG
SM300
4-14
Access Error Handling Procedures and Escalation Paths Error Handling Procedures and Escalation Paths are available in node .
© SAP AG 2009
© SAP AG
SM300
4-15
Access Operations Handbook on Intranet
Link to URL.
With the URL you can provide more detailed error handling procedures (for instance in solution database or operations handbook on Intranet).
© SAP AG 2009
Any URL can be configured.
© SAP AG
SM300
4-16
Link to Analysis Tools in Satellite System
Link to monitoring transactions in the satellite systems.
© SAP AG 2008
Use the error handling procedures available in SAP Solution Manager.
© SAP AG
SM300
4-17
Analyze Problem in the Satellite System
According to the error handling procedures determine the cause and effect of the problem and decide on how to solve the problem.
© SAP AG 2009
Error handling procedures can involve contacting the business department. Some activities may have to be carried out by the Business Department (for instance create new sales order)
If error handling procedures have been exhausted forward the problem to next support level.
© SAP AG
SM300
4-18
Create Service Desk Message Business Process Operations
2. 2. Choose Chooseto tocreate create Service Desk Service Deskmessage. message.
Detect Alert Situation
Execute Initial Analysis Create Service Desk message
Sign-off alert resolution
1. 1. Mark Markalerts alertsrelevant relevantfor forthe the Service Desk message. Service Desk message.
© SAP AG 2009
© SAP AG
SM300
4-19
Service Desk Message The number of the Service Desk message as well as its status are displayed in the Business Process Monitoring session. By double-clicking on the message number you get directly to this message in the Service Desk of SAP Solution Manager.
Double click.
© SAP AG 2009
© SAP AG
SM300
4-20
Confirm Alerts for Solved Problems
Business Process Operations
Detect Alert Situation
Choose Chooseto toconfirm confirm the alerts. the alerts.
Execute Initial Analysis Create Service Desk message
Sign-off alert resolution
© SAP AG 2009
You can confirm alerts individually by marking the alerts and choosing “Confirm selected”. It is also possible to mass confirm alerts (all yellow or all red) for a particular monitoring object.
© SAP AG
SM300
4-21
User Stamp and Comments for Confirmed Alerts
Business Process Operations
By confirming all red alerts the status of the node has changed to yellow.
Detect Alert Situation
Execute Initial Analysis
You can provide comments for the confirmed alerts.
Create Service Desk message
Sign-off alert resolution
The information which user The information which user has confirmed the alerts has confirmed the alerts when is displayed. when is displayed.
© SAP AG 2009
The column “Comment” can also be used when no alerts have been confirmed. Here, you can for instance specify hints like “waiting for feedback from development” to tell other persons who also use the monitoring that the problem is already being taken care of.
© SAP AG
SM300
4-22
Open Alerts vs. Current Alerts
Mark alerts that should be confirmed and choose “Confirm”.
In addition to the Business Process Monitoring session alerts can be confirmed in the Detailed Alert View of the Monitoring Graphic. The information about the confirmed alerts is replicated into the Business Process Monitoring session.
© SAP AG 2009
Current alerts display what status has been determined during the last data collector run. The status of current alerts cannot be changed by users. Only the next data collector run can change the status of the current alerts.
Open alerts indicate alert situations that have not been solved. When an alert situation has been solved, the open alert is confirmed by the monitoring responsible. With this, the open alert is deleted.
Due to technical restrictions in RZ20 the replication of the confirmed alerts only works if the actual alerts have been confirmed, not if just the parent MTE for the alerts has been confirmed. In the example of the above screenshot this means that if only the upper line y “VA01 (tt5tdc00_TT5_50)\DBRequestTime (1) [More]” is confirmed in the graphic, no data will be replicated into the Business Process Monitoring session. To replicate, the line y “1.538 msec > 1.200 msec Transact-spec. dialog resp. time exceeds threshold...” has to be confirmed as well.
© SAP AG
SM300
4-23
Adjust Rating Hierarchy
Per solution, you can define to change your Rating Hierarchy via Settings Æ Solution Monitoring Æ Rating Hierarchy
© SAP AG 2009
Changing the rating hierarchy means you can decide where the “grey” alert should appear in the rating hierarchy.
In order to use this functionality, the service sap/bc/webdynpro/sap/dswp_rating_4_monitoring needs to be activated in /nSICF.
© SAP AG
SM300
4-24
Work Center for Business Process and Interface Monitoring /nsolman_workcenter
Role-based user interface
URL can be linked from Company’s intranet
The Business Process and Interface Monitoring work center allows central access to all BPMon functionalities in SAP Solution Manager.
© SAP AG 2009
Required roles for Business Process & Interface Monitoring Work Center Usage: y SAP_SMWORK_BASIC y SAP_SMWORK_BPM
© SAP AG
SM300
4-25
Exercise: Use Active Business Process Monitoring
Exercise: Use active Business Process Monitoring
© SAP AG 2008
© SAP AG
SM300
4-26
Lesson 2: BPMon Infrastructure
1. Using Business Process Monitoring 2. BPMon Infrastructure
© SAP AG 2009
© SAP AG
SM300
4-27
Monitoring Infrastructure SAP Solution Manager
Satellite System
200
800 BPMon Graphic
BPMon Session
Data Collectors
Service Desk SCOT
BPMon Engine
User SM_BPMO
User SOLMANTT4200
000
Data Collectors
000 User Central CCMS SAPSYS
Local CCMS
© SAP AG 2008
For Business Process Monitoring in SAP Solution Manager several infrastructure components are used. The central infrastructure component is the BPMon Engine on SAP Solution Manager. The BPMon engine is client specific. It calls the data collectors on the satellite systems via the READ RFC destination and determines if an email or service desk message needs to be sent for the alerts. If a message needs to be sent it creates the messages and hands it over to the respective infrastructure component (SAPConnect or Service Desk). The BPMon engine stores the alerts for the business process (until they are reorganized according to the settings specified in the BPMon session) which are the source of the BPMon session.
The BPMon engine is triggered every 5 minutes by the Central CCMS on SAP Solution Manager via the local RFC destination. The central CCMS also stores the alerts for the business process and is the source for the BPMon graphic in SAP Solution Manager.
© SAP AG
SM300
4-28
Different Monitoring Types in Central and Local CCMS
SAP SAP Solution Solution Manager Manager
Central RZ20
Satellite Satellite System System
RFC
Application Monitor Background Job Due List Log Application Log Document Volume
Local RZ20 Dialog Performance Update Error Other CCMS
© SAP AG 2009
MTEs for the respective monitoring objects will be created either in the local or central CCMS.
For the objects that are monitored via the central CCMS you will have to define monitoring frequencies later on, indicating how often the data collector is supposed to run. The frequency determines in the end how current the monitoring information in the SAP Solution Manager will be. If for instance a collector is supposed to run only once per day the monitoring information will be current only once per day. If , on the other hand, collectors run too frequently you might unnecessarily increase the workload on the monitored system. The reaction times of the support organization should determine how often monitoring data is supposed to be collected.
© SAP AG
SM300
4-29
Computing Center Management System (CCMS)
CCMS of SAP systems provides a monitoring infrastructure that is used by the SAP Solution Manager. CCMS is called via transaction RZ20. To get an overview of all available alerts choose SAP CCMS Technical Expert Monitors -> System / All Monitoring Segments / All Monitoring Contexts. © SAP AG 2009
In RZ20 you see: y Measured values and alerts y Various monitors y Organized by topic y Tree structure y Highest alert of a sub-tree is reported upward.
© SAP AG
SM300
4-30
MTEs Created with BPMon Activation
With the Activation of BPMon MTEs are created. Most MTEs are created in the CCMS of the SAP Solution Manager system.
© SAP AG 2009
© SAP AG
SM300
4-31
More Details about BPMon Infrastructure
A more detailled description of infrastructure in BPMon including
different types of Monitoring Functionalities
the entire process of data collection: starting with triggering the data collection up to the alert post processing and how the BPMon infrastructure affects the end user perspective.
can be found in the Media Library of BPM on the SAP Service Marketplace: http://service.sap.com/bpm Æ Media Library ÆTechnical Information Æ BPMon Infrastructure
© SAP AG 2009
You will also find an overview of all Monitoring Objects for Application Monitors in the unit’s appendix.
© SAP AG
SM300
4-32
Exercises Unit:
Use Business Process Monitoring
Lesson:
Using Business Process Monitoring
Exercise 9: Use Active Business Process Monitoring At the conclusion of this exercise, you will be able to: • Use Business Process Monitoring in SAP Solution Manager
Now that you’ve configured BPMon you can use the monitoring to handle the alerts that have occurred.
9-1
In the previous exercises you have set up and activated the Business Process Monitoring in SAP Solution Manager. Now, you can interpret the alerts you see in your solution. 9-1-1
Go to the Business Process Monitoring graphic for your solution. What is the total alert status of your solution? Area
Status
Software Hardware Business Processes 9-1-2
How many business processes are active for monitoring in your solution? What is their respective status in Business Process Monitoring? Process
© SAP AG
Status
SM300
4-33
9-1-3
Go to the detailed view for business process “Order to Cash”. Note down which business process steps are monitored and what their current status is: Process Step
9-1-4
Status
Which alerts are available for business process step 3 “Create Sales Orders” on the ECC system? Monitoring Object
9-1-5
Status
Check if there are open alert for business process step 3 “Create Sales Orders”: Monitoring Object
9-1-6
Open Alerts
Check the alert history for the cancellation of the background job for Urgent Orders. What behavior can you see? Answer: ____________________________________________________
9-1-7
Check the alert customizing for cancellation for this background job. Which alerts are customized with which thresholds? How often are alerts determined for this background job (data collection period)? Answer: ____________________________________________________
9-1-8
Check on TT5 if the technical behavior is the same for all these background jobs of the last 5 days. Answer: ____________________________________________________
9-1-9
Check the error handling procedures for the background job. Who is responsible for monitoring this job? Answer: _____________________________________________________
© SAP AG
SM300
4-34
9-1-10 Create a Service Desk Message for the cancellation alerts for this background job (one message for all alerts). What changes with the creation of the message? Answer: _____________________________________________________ 9-1-11 Confirm all cancellation alerts for the background job. What changes in the Business Process Monitoring session? 9-1-12 Change the rating hierarchy so that grey alerts are the lowest level of the hierarchy.
© SAP AG
SM300
4-35
© SAP AG
SM300
4-36
Solutions Unit:
Using Business Process Monitoring
Lesson:
Using Business Process Monitoring
Exercise 9: Use Active Business Process Monitoring
9-1
Interpret the alerts. 9-1-1
9-1-2
9-1-3
9-1-4
9-1-5
© SAP AG
Choose Operations Æ Solution Monitoring Æ Business Process Monitoring to access the graphic. The total status of your solution can be seen in the bar above the monitoring graphic. You should see the following statuses: Area
Status
Software
None
Hardware
None
Business Processes
Red
Just one business process is active for monitoring: Process
Status
Order to Cash
Red
Click on the name “Order to Cash” in the graphic to access the detailed view for the business process. The following business process steps are monitored Process Step
Status
3 Create Sales Order
Red
Which alerts are available for business process step 3 “Create Sales Orders”? Monitoring Object
Status
Urgent Orders Cancellation
Red
Urgent Orders Start Delay
Green
Choose button Open Alerts to see the open alerts: Monitoring Object
Open Alerts
Urgent Orders Cancellation
Red
Urgent Orders Start Delay
Green
SM300
4-37
9-1-6
Click the on alert name to access the alert history. Answer: The job has always been canceled.
9-1-7
The alert customizing for cancellation for the background job can be found in tab “Alert Configuration”. The tab contains the following entries: Alert if Job is cancelled Red The other alerts customized that can be found in tab “Alert Configuration” in the nodes under “Urgent Orders” are: Alerts
Threshold Yellow
Threshold Red
Start delay
10 min.
15 min.
The data collection period can be checked in the Setup session; as the job is marked as “non-critical”, the data for the alert determination are collected every 60 minutes. 9-1-8
Choose button SM37 (TT5). Change the date to the last 5 days. Execute. Answer: Not all jobs during the last days have cancelled.
9-1-9
In Solution Manager go to node Urgent Orders (parent node). In tab Monitoring Activities you find the information Answer: The job is supposed to be restarted manually. Belinda Hampert is responsible for monitoring.
9-1-10 Go back to node Urgent Orders Æ Job Cancellation. In tab Open and confirmed Alerts select all yellow alerts and choose Create Notifications. In the message popup enter the following information: Priority
High
IBase
TT5 0120003411 800
Component
SV-SMG-MON-BPM
Answer: The message number and status are written into the session for all yellow alerts. 9-1-11 Choose Confirm all Red Answer: The alert in front of node Job Cancellation changes. 9-1-12 Go back to the monitoring graphic. In the SAP menu choose “Settings” Æ”Solution Monitoring” Æ “Rating Hierarchy”. In the next screen, switch to rating hierarchy “grey Æ green Æ yellow Æ red”. Save.
© SAP AG
SM300
4-38
Cross Application Monitoring
Course Overview Unit 1 Introduction to Business Process Monitoring Unit 2 Procedure Unit 3 Monitoring Configuration Unit 4 Using Business Process Monitoring
Unit 8
Data Consistency Monitoring
Unit 5 Cross-Application Monitoring
Unit 9
Reporting
Unit 6 Application Monitoring Unit 7 Interface Monitoring
Unit 10 Handover to Production Unit 11 Managing Jobs in SAP Solution Manager
© SAP AG 2008
After completing this unit the participant will be able to: y to use Background Job Monitoring y to use Dialog Performance Monitoring y to use Application Log Monitoring y to use Other CCMS Monitoring
in SAP Solution Manager
© SAP AG
SM300
5-1
Business Process Monitoring: Unit Objectives
After completing this unit, you will be able to:
set up Background Job Monitoring
set up Dialog Performance Monitoring
set up Application Log Monitoring
set up Other CCMS Monitoring
in SAP Solution Manager
© SAP AG 2009
© SAP AG
SM300
5-2
Initial Situation
Company IDES now configures cross-application monitoring for business process “Order-to-Cash” in SAP Solution Manager according to the identified operations requirements. CRM - CDP
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Run MRP
Procurement Process
Manufacturing Process
Create Outbound Delivery Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
© SAP AG 2009
© SAP AG
SM300
5-3
Cross-Application Monitoring Functionalities in SAP Solution Manager
Monitoring functionalities that are relevant for business processes from all application areas
Background Job Monitoring
Dialog Performance Monitoring
Application Log Monitoring
Monitoring of CCMS Alerts
© SAP AG 2009
© SAP AG
SM300
5-4
Monitoring Types in the Central and Local CCMS
SAP SAP Solution Solution Manager Manager
Central RZ20
Satellite Satellite System System
RFC
Application Monitor Background Job Due List Log Application Log Document Volume
Local RZ20 Dialog Performance (CCMS)* Update Error Other CCMS Interface Monitoring (CCMS)*
* = newer functionality exists within the application monitor © SAP AG 2009
MTEs for the respective monitoring objects will be created either in the local or central CCMS.
For the objects that are monitored via the central CCMS you will have to define monitoring frequencies later on, indicating how often the data collector is supposed to run. The frequency determines in the end how current the monitoring information in the SAP Solution Manager will be. If for instance a collector is supposed to run only once per day the monitoring information will be current only once per day. If , on the other hand, collectors run too frequently you might unnecessarily increase the workload on the monitored system. The reaction times of the support organization should determine how often monitoring data is supposed to be collected.
© SAP AG
SM300
5-5
Lesson 1: Background Job Monitoring
1. 2. 3. 4.
Background Job Monitoring Dialog Performance Monitoring Application Log Monitoring Other CCMS Monitoring Appendix: I. Update Error Monitoring II. Document Volume Monitoring
© SAP AG 2009
© SAP AG
SM300
5-6
Monitoring Type – Background Job Background Job Monitoring means the monitoring of the behavior of background jobs on SAP systems.
© SAP AG 2009
The planned behavior of the background job (e.g. start time, end time) has to be explicitly specified in the SAP Solution Manager.
© SAP AG
SM300
5-7
Identify Background Job
Which job is supposed to be monitored
job name (also possible to use rules for job names)
report / variant executed in a particular step
external program
How is this job scheduled
by time
by event
by preceding job
manually or via external scheduler
periodicity
© SAP AG 2009
Identification by job name: y Refers to name of the background job as it is shown in transaction SM37 y Use wild card '*' in the job name (not for the whole name) to identify set of jobs. y It’s possible to specify the job name and the ABAP program or external program.
Identification by ABAP program: y ABAP program that is executed during a step of the job. Specify the correct job step number in which the program is executed. (wrong number means jobs cannot be identified). In addition to a program name a program variant can be specified. y In the ABAP program name the use of a wildcard '*'is not allowed. However, you can use '*' in the variant. y ABAP programs have to be assigned via value help. If it does not contain any values you can add ABAP programs in tab “Add/Remove ABAP Program”
Identification by external program: y To be set up in the same way as described for ABAP programs. It is important to specify the correct job step number. Additionally, parameters can be specified. y External programs and parameters must not include wildcards.
© SAP AG
SM300
5-8
Load Job Information from Satellite System 1/2
Enter the job name or the ABAP report. Choose “Select”. Then choose “Check Job Identification”.
© SAP AG 2009
© SAP AG
SM300
5-9
Load Job Information from Satellite System 2/2
Double click on the job name. The job information is loaded into the Setup BPMon session. Verify the information and adjust it if needed.
© SAP AG 2009
© SAP AG
SM300
5-10
Job Scheduling Information Weekly Schedule:
Starting procedure “by time”
job starts on a certain date at a certain time
ob can be repeated periodically (for instance every 2 hours)
Starting procedure “by event”
job starts when a certain event is raised with a specific parameter
non-periodic
Starting procedure “by preceding job”
job starts when a specific other job ends
non-periodic
Starting procedure “use job start condition”
job starts irregularly at uncertain times, so the job start condition as available in table TBTCO is considered as relevant
for instance for job scheduled by external scheduler
Monthly Schedule:
job starts according to date, time and period defined respective to a specific factory calendar
© SAP AG 2009
Periodic jobs in the monitoring sense are jobs that are running several times per day.
A background job running once per day is not considered as periodic in the monitoring sense.
“Use job start condition” can be used for periodic jobs that are scheduled by event or scheduled by preceding job. It can also be used for manually scheduled jobs (start condition immediately in SM36)
“Use job start condition” will identify every job of the specified job identification as relevant (e.g. every job of a certain name will be monitored, no matter when the job was executed or how often the job was executed).
Job with a weekly schedule run at least once per week.
Jobs with a monthly schedule run less than once per week. With this, you can identify jobs that run once per month or once per quarter.
For start procedures “by preceding job”, “by event” and “use job start condition” the start time will be ignored if specified.
For start procedure “use job start condition” you have to specify a start time if you want to be informed later on if the job has not run at all during the day.
For jobs started by time the specified start time represents the earliest possible start time. This means if you specify 8:00 as start time and the job actually starts at 7:50 the job will not be identified.
© SAP AG
SM300
5-11
Data Collection for Background Job Monitoring
Background Jobs are divided into critical and non-critical for monitoring.
Critical Jobs:
Data Collection more frequent, per default every 5 minutes You are informed about problems for the job sooner after the problem occurred
Non-Critical Jobs
Data Collection less frequent, per default every 60 minutes
© SAP AG 2009
© SAP AG
SM300
5-12
Monitoring Schedule Information
Periodicity Information is loaded from the satellite system. Decide on which days you want monitor the background job.
© SAP AG 2009
© SAP AG
SM300
5-13
Functional Scope of Background Job Monitoring Start Delay
Start Delay
Job
Planned Start Time
Actual Start Time
Alert
Not Started on Time
Planned Start Times
Job
Actual Start Time
Defined Comparison Time
End Delay
End Delay
Job
Actual End Time
Planned End Time
Duration
Maximum Duration
Job
Actual Start Time
Actual End Time
Cancellation
Cancellation
Job
Actual Start Time Job
Parallel Processing
2 min
Job
Planned Start Time
Out of Time Window
Out of Time Window
Job
Actual Start Time
Begin of Time Window
End of Time Window
Job Log Messages
Job Log Messages Job Log:
Job Log Content
Number of parallel jobs
Job
34 Orders created 12 Orders created 46 Orders created
Content of Job Log Messages
© SAP AG 2009
The availability of the alerts depends on the start procedure defined for the job . y Start Delay: You can monitor if the start of a job has been delayed. This alert is always available. For jobs that are started by event, by preceding job or by job start condition this alerts means the technical start delay. The technical start delay is the delay as visible in transaction SM37. For jobs started by time the start delay is considered relative to the specified start time. y Not started on time: You can monitor if no job has started until a defined time of the day. y End Delay: You can monitor if job has not finished by a certain time. This alert is available for non-periodic jobs. y Maximum Duration: You can monitor if the job has exceeded a certain run time. This alert is always available. y Cancellation: You can raise a yellow or red alert if the job has cancelled. This alert is always available. y Parallel Processing: You can monitor if a specified number of identical jobs are running in parallel (started within 2 minutes of each other). This alert is available if in the scheduling information the job has been specified as processed in parallel. y Out of Time Window: You can monitor if a job has run outside a certain time window (started too early or finished too late). This alert is available for non-periodic jobs. y Job Log Messages: You can monitor if certain messages appear in the job log. This alert is always available. y Job Log Content: You can add values in the job log messages and monitor the total sum of these values
© SAP AG
SM300
5-14
Available Alerts for Background Job Monitoring
Weekly schedule nonperiodic
Weekly Schedule periodic
Weekly Schedule
Monthly Schedule
Job configured as started by time started by event
Start Delay End Delay Not started Max. on time Duration
Cancellation
Yes
Yes
Yes
Yes
Out of Time Window Yes
Yes
Yes Yes (technical start delay started by Yes Yes preceding (technical job start delay Started by Yes No time
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes Yes (makes sense mostly for nonperiodic) Yes Yes
Yes
No
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes Yes (makes sense only for nonperiodic) Yes Yes
Yes
Yes
started by Yes job start (technical condition start delay) + next day alert started by Yes factory calendar
Yes (makes sense only for nonperiodic) Yes Yes
Parallel Job Log Job Log Processing Messages Content Yes
Yes
Yes
© SAP AG 2009
All alerts are available only if a comparative value has been defined. This means that for a start delay alert a start time always has to be provided, for a time window alert an alert time window has to be defined etc.
© SAP AG
SM300
5-15
Define Alert Status or Alert Thresholds
Define threshold values or alert statuses for each alert you want to use.
© SAP AG 2009
For job log messages, it is also possible to define for what kind of messages you want to monitor the job log (message type, message ID and number) and what quantity of those messages should raise what kind of alert. It is possible to use wildcards in the specification of the messages.
© SAP AG
SM300
5-16
Exercise: Configure Background Job Monitoring
Exercise: Configure Background Job Monitoring
© SAP AG 2008
© SAP AG
SM300
5-17
Lesson 2: Dialog Performance Monitoring
1. 2. 3. 4.
Background Job Monitoring Dialog Performance Monitoring Application Log Monitoring Other CCMS Monitoring Appendix: I. Update Error Monitoring II. Document Volume Monitoring
© SAP AG 2009
© SAP AG
SM300
5-18
Dialog Performance Monitoring
Monitoring of dialog steps for a dialog transaction Based on statistical records available in transaction /nSTAD There are 2 ways to monitor dialog performance in BPMon
Dialog Performance Monitor (CCMS)
Dialog Performance Monitor (Application Monitor)
© SAP AG 2009
In transaction /nSTAD, statistical data records can be regarded which were recently collected on the system. Statistical records include performance data such as Response Time, Wait Time, CPU Time, DB Request Time etc., broke down to single transactions and programs which were executed on the system within the specified time frame.
© SAP AG
SM300
5-19
Dialog Performance (CCMS)
Select monitoring type “Dialog Performance” for the business process step. To use this functionality you need to have SAP instance names documented for the system in the System Landscape in SAP Solution Manager. This functionality uses the standard CCMS monitoring functionality for dialog transaction performance.
© SAP AG 2009
© SAP AG
SM300
5-20
Dialog Transaction Details
1. 1. Add Addtransactions transactions to tothe the business businessprocess processstep. step. Save. Save. 3. 3. Choose ChooseSAP SAPInstance Instance on which on whichthe thetransaction transaction should shouldbe bemonitored. monitored.
2. 2. Choose Choosetransactions transactions to be monitored. to be monitored. 4. 4. Select Select alert alert types. types.
© SAP AG 2009
© SAP AG
SM300
5-21
Alert Thresholds for Performance Monitoring For Performance Monitoring the CCMS infrastructure of the satellite system is used.
You Youcan canreload reloadthe theexisting existingthreshold thresholdvalues values from from the thesatellite satellitesystem. system.Choose Choose“Copy “Copyall” all”ifif you want to use the existing threshold values you want to use the existing threshold values for for your yourmonitoring. monitoring.
© SAP AG 2009
You have to specify four thresholds: y alert changes from green to yellow (A) y alert changes from yellow to red (B) y alert changes from red to yellow (C) y alert changes from yellow to green. (D)
The relation between the thresholds should be as follows: D≤ A≤ C≤ B
This ensures that an alert is lowered only if a real performance improvement has occurred.
© SAP AG
SM300
5-22
Properties for Performance Monitoring Alerts
Choose Choose“Change”. “Change”.
Choose Choose“Properties”. “Properties”.
You can change the thresholds for Performance MTEs directly in RZ20 of the satellite system. How the comparative value (in this case the statistical performance data) is determined can be changed only directly in CCMS. © SAP AG 2009
Per default the performance data is smoothed according to a mathematical procedure over the last 15 minutes.
Alerts are only raised, if a status change takes place according to the thresholds set.
© SAP AG
SM300
5-23
Dialog Performance (Application Monitor)
Select monitoring type “Application Monitor” for the business process step. This functionality uses the application monitoring infrastructure. In addition to providing monitoring for all steps of a transaction this functionality also allows you to monitor just specific steps of a transaction (like saving of order).
© SAP AG 2009
© SAP AG
SM300
5-24
Select Monitoring Object Choose to load the available application monitoring functionality from the satellite system. Then use the value help to assign the dialog monitoring object to the business process step.
In pop-up double click on Dialog Performance Monitor. Save.
© SAP AG 2009
© SAP AG
SM300
5-25
Give Monitoring Object Name
Give a name to the monitoring object. Then choose “Select” and save.
© SAP AG 2009
© SAP AG
SM300
5-26
Select Key Figures
In the next node select the key figures (alert types) you want to use in tab “Key Figures”.
© SAP AG 2008
If you do not suspect performance problems in a particular part of the transaction processing, you should start with configuring monitoring of the total response time. Often it is also helpful to monitor the data base response time.
The list of key figures depends on the version of ST-A/PI installed on the satellite system. The volume dependant monitoring of the total response time is available as of ST-A/PI01K.
© SAP AG
SM300
5-27
Key Figures available for Dialog Performance Monitoring DB response time GUI response time Roll wait time CPU time Total response time Number of dialog steps Total number of dialog steps DB proc. call time (APO) Total response time (data vol.-depend.)
© SAP AG 2009
© SAP AG
SM300
5-28
Monitoring Schedule
In the same node, choose the period for the monitoring data collection in tab “Monitoring Schedule”. Select the days the data collection is supposed to be executed and the period that should be used.
© SAP AG 2009
The details for the monitoring schedule in the application monitoring infrastructure are explained in unit “Application Monitoring”.
The statistical records in a system are reorganized after some time (usually hours). Therefore you should select a regular execution of the data collection (every hour or less) to ensure that all statistical records for the time frame that should be evaluated are still available in the system.
© SAP AG
SM300
5-29
Define Selection Criteria for Alert In node “” in tab “” double-click on a field in column “Counter. This opens a pop-up where you can enter the selection criteria.
© SAP AG 2009
The availability of selection criteria depends on the ST-A/PI version installed on the satellite system.
Selection Criteria: y Value 1: - Transaction code as visible in STAD y Value 2: - Function code as visible in STAD (“*” = all function codes, “ “ = all empty function codes) - In the screenshot, the value „SICH“ describes the OK-Code meaning „SAVE“ in transaction VA01 y Call Type: - Dialog Transaction, RFC Call, or HTTP Request y User Patter: - String in User Name (can be left blank) y Instances: - SAP Instance (can be left blank) y Processing Intervals - for performance of data collection
© SAP AG
SM300
5-30
Specify Alert Thresholds
The selection criteria are identified via the Counter. Since the counter ID is a technical name, specify a description for the ID and specify the thresholds. Save.
© SAP AG 2009
© SAP AG
SM300
5-31
Exercise: Configure Dialog Performance Monitoring
Exercise: Configure Dialog Performance Monitoring
© SAP AG 2008
© SAP AG
SM300
5-32
Lesson 3: Application Log Monitoring
1. 2. 3. 4.
Background Job Monitoring Dialog Performance Monitoring Application Log Monitoring Other CCMS Monitoring Appendix: I. Update Error Monitoring II. Document Volume Monitoring
© SAP AG 2009
© SAP AG
SM300
5-33
Monitoring Type – Application Log Application Log Monitoring means the monitoring of messages written into the general application log (transaction SLG1). The messages contain information about application events.
© SAP AG 2009
The application log is a central repository for logs, which are output during various system activities (transaction SLG1). There is no general rule as to what is written into the application log. You have to check for each business process step separately what entries are written into the application log.
An application log is not written consecutively but at one point in time. Thus, an application that writes into application logs at several points creates a new log each time.
© SAP AG
SM300
5-34
Setup Application Log Monitoring
Application Logs are identified by their object. This object has to be explicitly specified (no wildcards). Sub object and user may contain wildcards. Technical names of Object and Sub-object can be determined by table BALHDR. You have to decide how application logs are to be evaluated – each log separately, all logs of this object per clock hour or all logs of this object per calendar day. Specify Specifyat atleast least object and object and aggregation aggregationlevel. level.
© SAP AG 2009
In the BPMon Setup session you need to enter the technical name of Object and Sub-Object, but in the result list of transaction SLG1 you only find the text of object and sub-object.
The easiest way to find out the technical names for specific log files is to take the log number (the very right column which is displayed on last slide) and look in table BALHDR for the technical names of the Object and Sub-object.
Aggregation per log, per hour and per day:
Per log: y Each log for this Object written will be evaluated separately. If many logs were written since the last run of the data collector you will get many alerts (one for each log) during the next collector run.
Per hour: y The logs will be summarized by full clock hours. If the data collector runs at 11:30 and than again at 12:30 there are two time intervals evaluated – the one from 11:00 – 12:00 and the one from 12:00 – 12:30. So two alerts are generated per object at most. If the collector run at 11:30 already results in a yellow or red alert for the time interval 11:00 – 11:30 because the threshold values were exceeded and the collector run at 12:30 does not lead to a different alert for the interval 11:00 – 12:00 no new alert will be reported.
Per day: y The logs will be summarized by full calendar days. Each time the data collector runs the whole of the day as it has happened so far is evaluated. If the alert status doesn’t change compared to the last collector run no new alert will be reported into the session.
© SAP AG
SM300
5-35
Threshold Values for Application Log Monitoring
Specify Specifythe thethreshold thresholdvalues. values.
© SAP AG 2009
© SAP AG
SM300
5-36
Exercise: Configure Application Log Monitoring
Exercise: Configure Application Log Monitoring
© SAP AG 2008
© SAP AG
SM300
5-37
Lesson 4: Other CCMS Monitoring
1. 2. 3. 4.
Background Job Monitoring Dialog Performance Monitoring Application Log Monitoring Other CCMS Monitoring Appendix: I. Update Error Monitoring II. Document Volume Monitoring
© SAP AG 2009
© SAP AG
SM300
5-38
Computing Center Management System (CCMS)
CCMS of SAP systems provides a monitoring infrastructure that is used by the SAP Solution Manager. CCMS is called via transaction RZ20. To get an overview of all available alerts choose SAP CCMS Technical Expert Monitors Æ System / All Monitoring Segments / All Monitoring Contexts. © SAP AG 2009
In RZ20 you see: y Measured values and alerts y Various monitors y Organized by topic y Tree structure y Highest alert of a sub-tree is reported upward.
© SAP AG
SM300
5-39
Monitoring Type – Other CCMS Monitor Other CCMS Monitoring means including already existing monitoring objects into the Business Process Monitoring in the SAP Solution Manager.
© SAP AG 2009
It means (as basically all other monitoring objects do as well) linking a technical problem on the system to a particular business process step.
© SAP AG
SM300
5-40
MTE Name In order to include the MTE in Business Process Monitoring in the SAP Solution Manager copy the name of the MTE from the satellite system into the Setup Business Process Monitoring session on the SAP Solution Manager.
Copy CopyMTE MTEname nametotoclipboard. clipboard. Position cursor the MTE and choose F1. © SAP AG 2009
© SAP AG
SM300
5-41
Setting up Other CCMS Monitoring Copy the name of the MTE from CCMS into the Setup Business Process Monitoring session. It is not required to specify threshold values for the alert. Provide Provide meaningful meaningful name name for for alert. alert.
Paste Paste MTE MTE name name from from RZ20. RZ20.
Optional: Optional: Choose Choose to to reload reload threshold threshold values from the satellite values from the satellite system. system.
© SAP AG 2009
Since MTE names are not fully displayed in the F1-Help it is important that you use copy/paste to enter the MTE name and do not attempt to enter the name manually as displayed in the F1-Help. You can chose any alert name, though it makes sense to use some kind of 'speaking' name.
If the MTE uses this rating strategy can enter thresholds for the alert to change from green to yellow, yellow to red, red to yellow and yellow to green. Keep in mind that not all combinations of values make sense. You can also load the current values from the satellite system, by choosing ‘Load thresholds from Sat. Sys.’.
© SAP AG
SM300
5-42
Exercise: Configure Other CCMS Monitoring
Exercise: Configure Other CCMS Monitoring
© SAP AG 2008
© SAP AG
SM300
5-43
Appendix
Appendix
© SAP AG 2009
© SAP AG
SM300
5-44
Appendix: Update Error Monitoring
© SAP AG 2009
© SAP AG
SM300
5-45
Motivation for Update Error Monitoring
During the execution of dialog transactions, the data is usually written to the DB at the end of the transaction, using an update work process instead of a dialog work process. If the update work process fails, the data is not written to the database. © SAP AG 2009
© SAP AG
SM300
5-46
Configure Update Error Monitoring
Select the object type (transaction or report). Define the user and specify the threshold values. Save. You can also specify thresholds for red alerts. Hard-coded, 1 update error for the selection criteria raises a yellow alert.
© SAP AG 2009
Update errors in an SAP system are documented with reference to the report or the transaction causing the error, not the background job. Therefore you cannot specify the background job here.
© SAP AG
SM300
5-47
Exercise: Configure Update Error Monitoring
Exercise (optional): Configure Update Error Monitoring
© SAP AG 2008
© SAP AG
SM300
5-48
Appendix: Document Volume Monitoring
© SAP AG 2009
© SAP AG
SM300
5-49
Monitoring Type – Document Volume Document Volume Monitoring means the monitoring of the number of updates, inserts and deletes of any table. This monitoring is based on the table call statistics visible in transaction ST10.
© SAP AG 2009
Since the document volume monitoring is based on the table call statistics only the total number of updates, inserts and deletes can be monitored. There is no monitoring if a certain field in a table has been changed.
The document volume monitor is the only out-of-the-box functionality available to monitor Customer tables. If more extensive monitoring functionality is required for Customer tables, you can implement your own monitoring functionalities in the user exit in the application monitoring infrastructure.
© SAP AG
SM300
5-50
Setting up Document Volume Monitoring
The details and alert thresholds for document volume monitoring are all customized in the same node of the session tree.
Specify Specifydetails detailsfor forthe the monitoring object monitoring objectand andthe the alert alertthreshold thresholdvalues. values.
© SAP AG 2009
Document Volume is monitored per full calendar day.
This monitoring type allows the monitoring of document volumes in terms of update, insertion, and/or deletion operations on single tables. There are two types of alert available.
MaxRecordsAffected y An alert will be triggered if the number of table operations exceeds the threshold
MinRecordsAffected y An alert will be triggered if the number of table operations has not reached the threshold. For this alert the threshold for “red” has to be smaller than the one for “yellow”.
Specify the following information y Name of the table that stores the documents you are interested in y Operation (Delete, Insert, Update) y Threshold values for the number of records affected, resulting in alert messages for changes from GREEN to YELLOW (and back) and from YELLOW to RED (and back) y Clock hour at which the alert should be determined y Weekdays relevant for monitoring.
© SAP AG
SM300
5-51
Exercise: Configure Document Volume Monitoring
Exercise (optional): Configure Document Volume Monitoring
© SAP AG 2008
© SAP AG
SM300
5-52
Exercises Unit:
Cross Application Monitoring
Lesson:
Background Job Monitoring
Exercise 10: Configure Background Job Monitoring At the conclusion of this exercise, you will be able to: • Set up configuration for background job monitoring
The creation of sales orders on the ECC system TT5 is realized via background jobs. These background jobs are crucial for the successful execution of the business process ‘Order to Cash’ and should therefore be monitored.
10-1 In step 3 ‘Create Sales Order’ the sales orders for non-critical customers are created via background job ‘SD_CREATE_SALES_ORDERS_2H’. This job is scheduled to start at 08:00 and runs periodically every 2 hours on Mo-Su. The job can be executed with different users. 10-1-1 In node (3) Create Sales Order [TT5] choose monitoring type “Background Job” if not already selected and save. 10-1-2 In node Background Job customize the job identification. Enter the job name ‘SD_CREATE_SALES_ORDERS_2H’ in tab Job Monitoring Objects. Specify the Job Schedule, the start procedure and mark this job as critical. Use “SO Creation” as Job Identifier. What entry do you have to maintain in column “Job Schedule”? Job Schedule:______________________________________________ 10-1-3 In the sub-node Monitoring Schedule specify that you want to monitor the job Mo-Fr and enter the period.
© SAP AG
SM300
5-53
10-1-4 Configure alerts for Start Delay, Maximum Duration, Cancellation and Error Messages in the job log.
© SAP AG
•
Start Delay: If the background job has not been started 15minutes after the scheduled start time, a yellow alert should be raised. 30 minutes after the scheduled start time a red alert should be raised.
•
Maximum Duration: Normally the jobs runs for about 15 minutes. If the jobs runs longer than 30 minutes a yellow alert should be raised, if it runs longer than 60 minutes a red alert should be raised.
•
Cancellation: If a background job cancels a yellow alert should be raised.
•
Job Log Message: Every error message should trigger a red alert.
SM300
5-54
Solutions Unit:
Cross Application Monitoring
Lesson:
Background Job Monitoring
Exercise 10: Configure Background Job Monitoring
10-1 You access the Setup Business Process Monitoring session of your solution. You go to node Business Process Monitoring Setup Æ Business Processes Æ ‘Order to Cash’ (Prod.) Æ (3) Create Sales Order [TT5]. If this node is not visible you have not executed the previous exercise correctly. All further entries during this exercise have to be maintained in the node (2) Create Sales Order [TT5] and its sub nodes. 10-1-1 In node (3) Create Sales Order [TT5] fill in the following entries in table Monitoring Types and save: Monitoring Type
Relevant?
Application Monitor Background Job
(D)
Dialog Performance Update Error Due List Log Application Log Document Volume Other CCMS Monitor
(D) means that this flag was set during a previous exercise. 10-1-2 In sub node Background Job select button ‘Append Row’ to create a new line and fill in the following entries in table Job Monitoring Objects and save: Job Identifier: SO Creation Job Name: SD_CREATE_SALES_ORDERS_2H Job Schedule: W Critical: D
© SAP AG
SM300
5-55
Start Procedure: 1 Planned Start: 08:00:00 Answer: Since the job runs at least once per week the Job Schedule has to be ‘weekly’. 10-1-3 In the sub-node Monitoring Schedule fill in the following information: Mo
Tu
We
Th
Fr
D
D
D
D
D
Sa
Su
Period 120
10-1-4 In the other sub-nodes maintain the following entries: Node Start Delay Start Delay for YELLOW
Start Delay for RED
15
30
Node Maximum Duration Duration for YELLOW
Duration for RED
30
60
Node Job Cancellation Alert If Job Cancelled Yellow Node Job Log Messages
© SAP AG
Msg Type
Msg Msg Lower Lower Upper Class No Threshold Threshold Threshold for for RED for YELLOW YELLOW
Upper Threshold for RED
E
*
1
*
1
SM300
5-56
Exercises Unit:
Cross-Application Monitoring
Lesson:
Dialog Performance Monitoring
Exercise 11: Configure Dialog Performance Monitoring At the conclusion of this exercise, you will be able to: • Set up monitoring customizing for dialog performance monitoring.
Sales orders can also be created directly on system TT5 (as opposed to coming from the CRM system or the SAP Enterprise Portal). In these cases the performance of the dialog transaction VA01is of high importance and should be monitored.
11-1 In step 3 “Create Sales Order” set up monitoring for the dialog performance of VA01. Question: So far, IDES has not experienced problem with the dialog performance of VA01. In this case, which alerts should be configured? Answer: ____________________________________________________________________ Question: You will have to configure your individual thresholds for the monitoring. Which functionality for dialog performance monitoring do you have to use? Answer: □ Application Monitor □ CCMS Monitor 11-1-1 Configure Dialog Performance Monitoring for the response time of the entire transaction with the following thresholds within the monitoring type you have identified above: (##00) ms for yellow, (2*##00)ms for red (## = your group number) Data Collection should run every 60 minutes every day of the week. Question: Would it make sense to set the data collection period to 1440 minutes (24h)? Answer: _____________________________________________________________
© SAP AG
SM300
5-57
Question: Does it make sense to restrict the monitoring to a certain SAP instance of SAP system TT5? Answer: _____________________________________________________________ 11-2 In the same business process step set up monitoring for the total response time of the saving with VA01. 11-2-1 Question: How can you find out what the function code for the saving of a sales order with VA01 is? Answer: _____________________________________________________________ 11-2-2 Create a sales order with the following data to find the function code: Sales organization: 1000 Distribution channel: 10 Division: 00 Sold to party / ship to party: 1000 Material: P-101 Quantity: 1 11-2-3 Configure monitoring of the response time of the saving with the following thresholds: 2000 ms for yellow, 3000 ms for red Data collection every 60 minutes.
© SAP AG
SM300
5-58
Solutions Unit:
Cross-Application Monitoring
Lesson:
Dialog Performance Monitoring
Exercise 11: Configure Dialog Performance Monitoring
11-1 In the Setup Business Process Monitoring session of your solution all further entries during this exercise have to be maintained in the node (3) Create Sales Order [TT5] and its sub nodes. Answer: If you don’t have any clear indicators what could be performance critical, you should always start with the monitoring of the total response time. Sometimes it can also make sense to set up monitoring of the database response time. Answer: If you want to use your individual thresholds you have to use the application monitor in the application monitor. 11-1-1 In node (3) Create Sales Order [TT5] fill in the following entries in table Monitoring Types and save: Monitoring Type
Relevant?
Application Monitor
D
Background Job
(D)
Dialog Performance Update Error Due List Log Application Log Document Volume Other CCMS Monitor
(D) means that this flag was set during a previous exercise. In node Application Monitor, choose button “Load App. Monitors TT5”. Afterwards, in tab “Application Monitoring Objects”, use the value help for column Application Monitor and select ”Dialog Performance Monitor”. In column “Monitoring Object Name” give the name “VA01 Performance“. Flag “Select” and save. In sub-node “VA01 Performance” select to monitor total response time in tab “Key Figures”. In tab “Monitoring Schedule” select all days and specify the period as 60 minutes. Save.
© SAP AG
SM300
5-59
In sub-node “Total Response Time” go to tab “Total Response Time” and double click on a field in column “Counter”. This opens the pop-up to enter the selection criteria. Enter: •
Value 1: VA01
•
Value 2: * (do not leave the flied empty)
•
Call Type: D
Hit the clock button in the pop-up. This will close the pop-up. Enter “Entire VA01” in column “Short Text” and enter the thresholds as given in the exercise. Save. Afterwards generate and activate your configuration. Answer: The data collection period should not be too large, because the statistical records are normally kept in the satellite system only for some hours. So setting it to 24h might mean that the data collectors only have records of the last 6 hours to evaluate. Answer: TT5 only has one instance (transaction /nSM51), so it does not make sense to restrict the monitoring to one instance. 11-2 Configure Function Code monitoring. 11-2-1 Answer: You can see the function code in the statistical records for transaction VA01. The easiest way is to create a sales order yourself and then identifying the respective dialog step with transaction STAD. 11-2-2 The function code for saving the sales order is SICH. 11-2-3 In node Application Monitor Æ VA01 Performance Æ Total response time that was use above add a second line to the table in tab “Total Response Time. Double click on the new field in column “Counter”. This opens the pop-up to enter the selection criteria. Enter: •
Value 1: VA01
•
Value 2: SICH
•
Call Type: D
Hit the clock button in the pop-up. This will close the pop-up. Enter “Saving VA01” in column “Short Text” and enter the thresholds as given in the exercise. Save. Afterwards generate and activate your configuration. Remark: Since both monitors use the same data collection frequency, you can configure both alerts in the same monitoring objects.
© SAP AG
SM300
5-60
Exercises Unit:
Cross-Application Monitoring
Lesson:
Application Log Monitoring
Exercise 12: Configuring Application Log Monitoring At the conclusion of this exercise, you will be able to: • Set up monitoring customizing for application log.
During the creation of the sales orders messages are written into the application log. At least the error messages amongst these messages should be monitored.
12-1 Set up monitoring customizing for application log monitoring for business process step 3 “Create Sales Order”. 12-1-1 Find out which application log objects are used to document messages that occurred during transaction VA01. Question: Which transaction do you use to find out this information? Answer: _____________________________________________________________ List your object and sub-object below: Object: Subobject:
© SAP AG
SM300
5-61
12-1-2 Configure monitoring for error messages in this object/subobject. Question: Why is the value help for object/sub-object during the configuration of the monitoring empty? Answer: _____________________________________________________________ Question: IDES has not yet any experience with the error messages in this log. How should you configure the monitoring for the error messages in this case (aggregation and thresholds)? Answer: _____________________________________________________________ Configure monitoring for all error messages in the application log for the identified object/sub-object. Configure the monitoring so that 1 error message creates a yellow alert and no red alerts are raised for error messages. 12-2 Question: Which application log monitoring object and sub-object are available in the value help for application log monitoring in business process step “Post Goods Issue”? Where do these entries come from? Answer: ____________________________________________________________________
© SAP AG
SM300
5-62
Solutions Unit:
Cross-Application Monitoring
Lesson:
Application Log Monitoring
Exercise 12: Configuring Application Log Monitoring
12-1 In the Setup Business Process Monitoring session of your solution all further entries during this exercise have to be maintained in the node (3) Create Delivery [TT5] and its sub nodes. 12-1-1 Answer: Use transaction /nSLG1 to check the available application log entries for transaction VA01. There are application log entries for transaction VA01 for object Z_SALES and sub-object Z_ORDERS. 12-1-2 In node (3) Create Sales Order [TT5] fill in the following entries in table Monitoring Types and save: Monitoring Type
Relevant?
Application Monitor
(D)
Background Job
(D)
Dialog Performance Update Error Due List Log Application Log
D
Document Volume Other CCMS Monitor
(D) means that this flag was set during a previous exercise. In node Application Log maintain the following entries in table Total N° of Messages: Object
Sub-object
User
Transaction
Z_SALES
Z_ORDERS
*
VA01
Program
Aggregation
N° Msgs for YELLOW
N° Msgs for RED
L
In sub-node “Critical Appl. Log Messages” enter Object
Sub-object
Msg Typer
Msg Class
Msg Number
N° Crit Msgs for YELLOW
Z_SALES
Z_ORDERS
E
*
*
1
N° Crit Msgs for RED
When you save, the threshold for red is set to 1999999999 for technical reasons. © SAP AG
SM300
5-63
Answer: The value help is empty because there is no transaction assigned to this business process step. For some (though not all) transactions a value help with typical application log objects is available. This is because not all transactions write into the application log. Answer: In order to be informed about every application log error message all 3 aggregation types can be used. When unsure which aggregation to use, start by using the aggregation per log. If every error message is of interest, configure thresholds so that every error message creates a red alert. Later on you can adjust your configuration if necessary. 12-2 In the Setup Business Process Monitoring session go to node Business Process Monitoring Setup Æ Business Processes Æ Order to Cash. In tab Business Process Steps flag business process step “Post Goods Issue” for monitoring and save. Choose monitoring type “Application Log” for this business process step and save. Go to node “Application Log”. In tab “Total N° of Messages” use the value help (F4) in column “Object”. Answers: In the value help you can see object WHS and sub-object WHS_GLVKOW. Transaction MIGO writes into the application log with this object and sub-object. Because transaction MIGO was assigned to this business process step in the business blueprint and from there copied into your solution, the application log information is now available in the value help.
© SAP AG
SM300
5-64
Exercises Unit:
Cross-Application Monitoring
Lesson:
Other CCMS Monitoring
Exercise 13: Configuring Other CCMS Monitoring At the conclusion of this exercise, you will be able to: • Set up monitoring customizing for Other CCMS.
Errors for the creation of critical sales orders are monitored via a customer developed MTE in the CCMS of system TT5. The monitoring of these errors should now be included in the monitoring via AP Solution Manager.
13-1 Include the CCMS monitoring in the monitoring for business process step 3 “Create Sales Orders”. 13-1-1 Errors for critical sales orders are reported in the CCMS of TT5 under “Order to Cash” Æ “Critical Sales Orders” Æ “Critical Sales Orders in Error”. Include this monitoring in your BPMon concept in SAP Solution Manager. Specify the alert name as “Sales Order Errors”. 13-1-2 Find out what thresholds are currently used for this monitoring object. Answer: _____________________________________________________________ Question: What happens, if you change the thresholds for this monitoring object? Answer: _____________________________________________________________
© SAP AG
SM300
5-65
© SAP AG
SM300
5-66
Solutions Unit:
Cross-Application Monitoring
Lesson:
Other CCMS Monitoring
Exercise 13: Configuring Other CCMS Monitoring
13-1 In the Setup Business Process Monitoring session of your solution all further entries during this exercise have to be maintained in the node (3) Create Sales Order [TT5] and its sub nodes 13-1-1 In node (3) Create Sales Order [TT5] fill in the following entries in table Monitoring Types and save: Monitoring Type
Relevant?
Application Monitor
(D)
Background Job
(D)
Dialog Performance Update Error Due List Log Application Log
(D)
Document Volume Other CCMS Monitor
D
On TT5 get the technical information for the MTE via F1 after having placed your cursor on the node “Critical Sales Orders in Error”. The technical name is “TT5\Order to Cash\...\Critical Sales Orders\Critical Sales Orders in Error”. Important: You have to copy/paste the MTE name. Typing the MTE name into SAP Solution Manager will not work. On TT4 maintain the following entries in SAP Solution Manager in the Setup Business Process Monitoring session in node Business Process Monitoring Setup Æ Business Processes Æ Order to Cash (Prod.) Æ (3) Create Sales Order [TT5] Æ Other CCMS Monitor in tab Other CCMS Monitors: Alert Name
MTE(Monitoring Tree Element)
…
Sales Order Errors
TT5\Order to Cash\...\Critical Sales Orders\Critical Sales Orders in Error
…
© SAP AG
SM300
5-67
13-1-2 Choose button “Reload CCMS: Thresholds” in node Other CCMS Monitor. Answer: The following thresholds are customized in TT5: …
GREEN to YELLOW
YELLOW to RED
RED to YELLOW
YELLOW to GREEN
Unit
…
1
10
10
10
Pcs
Answer: When changing the thresholds for this monitoring object and generating and activating again the new values will be written into the CCMS.
© SAP AG
SM300
5-68
Exercises Unit:
Cross-Application Monitoring
Lesson:
Update Error Monitoring (optional)
Exercise 14: Configuring Update Error Monitoring At the conclusion of this exercise, you will be able to: • Set up customizing for update error monitoring.
When sales orders are created in dialog, the update work process can fail, which means that the sales order was not create on the database. Therefore the update errors for transaction VA01 have to be monitored.
14-1 Set up update error monitoring for business process step 3 “Create Sales Order”: 14-1-1 Find out how many update errors of transaction VA01 are currently on the system. Question: Which transaction do you have to you the list the update errors? Answer: 14-1-2 Customize the alerts for transaction VA01 with the following thresholds: •
V1 Update errors: 2 update error should raise a red alert
•
V2 Update errors: 4 update errors should raise a red alert
14-1-3 Question: Why is it not possible to customize thresholds for yellow alerts for update errors? Answer: _____________________________________________________________ 14-1-4 Question: How do you have to customize the alert threshold to raise a red alert if 1 update error has occurred? Answer: _____________________________________________________________
© SAP AG
SM300
5-69
© SAP AG
SM300
5-70
Solutions Unit:
Cross-Application Monitoring
Lesson:
Update Error Monitoring (optional)
Exercise 14: Configuring Update Error Monitoring
14-1 In the Setup Business Process Monitoring session of your solution all further entries during this exercise have to be maintained in the node (3) Create Sales Order [TT5] and its sub nodes 14-1-1 Answer: You can find update errors with transaction SM13. Currently there are no update errors for VA01 available in TT5. 14-1-2 In node (3) Create Sales Order [TT5] fill in the following entries in table Monitoring Types and save: Monitoring Type
Relevant?
Application Monitor
(D)
Background Job
(D)
Dialog Performance Update Error
D
Due List Log Application Log
(D)
Document Volume Other CCMS Monitor
(D)
(D) means that this flag was set during a previous exercise. In sub node Update Error maintain the following entries in table Monitoring Update1Errors / Update2Errors: Object type
Object name
User
No. of Errs for RED (Upd1)
No. of Errs for RED (Upd2)
T
VA01
*
2
4
Generate and activate to complete your configuration.
© SAP AG
SM300
5-71
14-1-3 Answer: The threshold for yellow is set in the coding since update errors are always critical errors. Therefore, 1 update error always results in a yellow alert. 14-1-4 Answer: To get a red alert for the occurrence of an update error you have to set the threshold for No. of Errs for RED to 1.
© SAP AG
SM300
5-72
Exercises Unit:
Cross-Application Monitoring
Lesson:
Document Volume Monitoring (optional)
Exercise 15: Configuring Document Volume Monitoring At the conclusion of this exercise, you will be able to: • Set up monitoring customizing for document volume.
During Business Process Step 3 “Create Sales Order” sales orders to critical customers are replicated to table ZVBAKCRIT (one entry per sales order). By monitoring the inserts to this table you should monitor the number of such sales orders that were created on each day.
15-1 Set up monitoring customizing for document volume monitoring for business process step 3 “Create Sales Order”. 15-1-1 Set up monitoring so that if less than 10 critical sales orders are created per day (before 8pm) a red alert is raised, less than 50 critical sales orders for a yellow alert. Question: Which tab do you have to use to maintain the customizing? Answer: MaxRecordsAffected MinRecordsAffected
□ □
© SAP AG
SM300
5-73
© SAP AG
SM300
5-74
Solutions Unit:
Cross-Application Monitoring
Lesson:
Document Volume Monitoring (optional)
Exercise 15: Configuring Document Volume Monitoring
15-1 In the Setup Business Process Monitoring session of your solution all further entries during this exercise have to be maintained in the node (3) Create Sales Order [TT5] and its sub nodes 15-1-1 In node (3) Create Delivery [TT5] fill in the following entries in table Monitoring Types and save: Monitoring Type
Relevant?
Application Monitor
(D)
Background Job
(D)
Dialog Performance Update Error
(D)
Due List Log Application Log
(D)
Document Volume
D
Other CCMS Monitor
(D)
(D) means that this flag was set during a previous exercise. Answer: You have to maintain tab MinRecordsAffected. In sub-node Document Volume maintain the following entries in table MinRecordsAffected: Table Name
Operation
ZVBA Insert KCRIT
© SAP AG
No. of Recs for YELLOW
No. of Recs for RED
Time
Mo
We
Th
Fr
Sa
Su
10
50
20:00
D D D
D
D D
D
SM300
Tu
5-75
© SAP AG
SM300
5-76
Application Monitoring
Course Overview Unit 1 Introduction to Business Process Monitoring Unit 2 Procedure Unit 3 Monitoring Configuration Unit 4 Using Business Process Monitoring
Unit 8
Data Consistency Monitoring
Unit 5 Cross-Application Monitoring
Unit 9
Reporting
Unit 6 Application Monitoring Unit 7 Interface Monitoring
Unit 10 Handover to Production Unit 11 Managing Jobs in SAP Solution Manager
© SAP AG 2008
© SAP AG
SM300
6-1
Business Process Monitoring: Unit Objectives
After completing this unit, you will be able to:
Set up basic, application-related monitoring in SAP Solution Manager
Understand how customer-specific monitoring objects can be implemented in Business Process Monitoring using the User Exit in the Application Monitoring Infrastructure
© SAP AG 2009
© SAP AG
SM300
6-2
Initial Situation
Company IDES now configures application specific monitoring for business process “Order-to-Cash” in SAP Solution Manager according to the identified operations requirements. CRM - CDP
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Run MRP
Procurement Process
Manufacturing Process
Create Outbound Delivery Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
© SAP AG 2009
© SAP AG
SM300
6-3
Lesson 1: Setup Application Monitoring
1. Setup Application Monitoring 2. Monitoring for Sample Business Process 3. User Exit Appendix: Example for User Exit
© SAP AG 2009
© SAP AG
SM300
6-4
Application Monitor The application monitoring infrastructure contains a large number of monitoring functionalities, depending on the version of ST-A/PI installed on the satellite system and the type of satellite system. The general procedure of how to configure the application monitoring functionalities is independent of the actual functionality.
© SAP AG 2009
© SAP AG
SM300
6-5
Monitoring Types in the Central and Local CCMS
SAP SAP Solution Solution Manager Manager
Central RZ20
Satellite Satellite System System
RFC
Application Monitor Background Job Due List Log Application Log Document Volume
Local RZ20 Dialog Performance Update Error Other CCMS
© SAP AG 2009
MTEs for the application monitoring functionalities are always created in the central CCMS.
© SAP AG
SM300
6-6
Application Monitoring Infrastructure
SAP SAP Solution Solution Manager Manager
ST-SER
Satellite Satellite System System
RFC
Nodes in Session Tree Tables in session nodes
ST-A/PI Data Collectors, depending on version of ST-A/PI and application type of satellite system
ST-A/PI Infrastructure for calling application monitor data collectors and receiving results
© SAP AG 2009
If you want to use application monitoring functionalities, ST-A/PI needs to be installed both on the satellite system and the SAP Solution Manager system.
© SAP AG
SM300
6-7
Steps how to set up Application Monitors
Define Solution Support Organization
Choose monitoring type “Application Monitor”
Choose Business Process and Business Process Steps to be monitored
Reload application monitoring objects from satellite system
Define Monitoring Objects per Business Process Step
Choose monitoring object
Per Monitoring Object:
Choose key figures (alert types)
Provide technical details and threshold values for the alerts
Set data collector frequencies
Assign monitoring transactions Customize value combinations
Set up monitoring tasks Configure automatic emails and Service Desk messages
Provide thresholds or status for alerts
© SAP AG 2009
© SAP AG
SM300
6-8
Choose Monitoring Type “Application Monitor”
Choose monitoring type “Application Monitor”
For the business process step or interface choose Monitoring Type “Application Monitor” and save. With this, a sub-node “Application Monitor” in the session tree is created.
Reload application monitoring objects from satellite system Choose monitoring object
Choose key figures (alert types) Set data collector frequencies Customize value combinations Provide thresholds or status for alerts
© SAP AG 2009
Application Monitors are available for business process steps and interfaces.
© SAP AG
SM300
6-9
Load available Application Monitoring Objects
Choose monitoring type “Application Monitor” Reload application monitoring objects from satellite system Choose monitoring object
Application Monitoring objects are contained in add-on STA/PI installed on the satellite system. This means that with the implementation of a new ST-A/PI on the satellite system new monitoring objects may be available. Therefore, you should reload the application monitoring objects before setting up the customizing so that you have access to the newest functionalities available. Load Application Monitoring Objects
Choose key figures (alert types) Set data collector frequencies Customize value combinations Provide thresholds or status for alerts
© SAP AG 2009
© SAP AG
SM300
6-10
Choose Monitoring Object
Choose monitoring type “Application Monitor”
Assign the monitoring object via the value help. With the saving of this node the sub node for the monitoring object will be created in session tree.
Reload application monitoring objects from satellite system Choose monitoring object
Choose key figures (alert types)
2. Double-click on line
Set data collector frequencies Customize value combinations Provide thresholds or status for alerts 1. Use value help © SAP AG 2009
© SAP AG
SM300
6-11
Available Monitoring Objects
Available Monitoring Objects depend on:
version of ST-A/PI installed on satellite system
product of satellite system
whether being assigned to a business process step or interface
© SAP AG 2008
CRM Monitoring functionalities are only available on a CRM satellite system. In the above example, the satellite is an ERP system, so the available monitoring functionalities are cross-application monitoring functionalities and ERP monitoring functionalities.
You can assign interface monitoring functionalities of the application monitor to business process steps as well. However, for interfaces, only certain application monitors are available (depends on choice of developer if functionality is relevant for interface or not).
© SAP AG
SM300
6-12
Name Monitoring Object
Give a name for the monitoring object. Flag “Select”. Save.
© SAP AG 2009
It is advisable to assign different monitoring objects for throughput monitoring and backlog monitoring. In this case, you assign the monitoring object “Sales Documents” twice to the business process step. y In the first case you name the monitoring object “Sales Orders Throughput”. In this monitoring object you configure only the throughput alerts (number of orders and items created). y In the second case you name the monitoring object “Sales Orders Backlog”. In this monitoring object you configure only the backlog alerts (number of blocked and open sales orders).
© SAP AG
SM300
6-13
Choose Key Figures per Monitoring Object
Choose monitoring type “Application Monitor”
Choose which of the key figures available for the monitoring object should be used for monitoring.
Reload application monitoring objects from satellite system Choose monitoring object
Choose key figures (alert types) Set data collector frequencies Customize value combinations Provide thresholds or status for alerts Select key figure(s). © SAP AG 2009
© SAP AG
SM300
6-14
Set Data Collector Frequencies
Choose monitoring type “Application Monitor” Reload application monitoring objects from satellite system
For application monitors you define the data collection frequencies individually for each monitoring object in tab ‘Monitoring Schedule’.
Choose monitoring object
Choose key figures (alert types) Set data collector frequencies Customize value combinations Provide thresholds or status for alerts
© SAP AG 2009
© SAP AG
SM300
6-15
Scheduling of Application Monitor Functionalities Monitoring can be executed either on a weekly basis or on a monthly basis.
…
…
For performance reasons it is sometimes necessary to flag field ‚Data Collection in Background‘
© SAP AG 2009
Monitoring can be executed periodically on a weekly basis every x minutes within a certain time window (like Mo-Fr every 5 minutes) or at a specific time during the day (like every day at 6pm). On a monthly basis, monitoring can also be based on a factory calendar which has to be deposited either on the Solution Manager system or on the connected satellite system. You then can specify on which day of the month the data collection should be performed. For a monthly schedule, enter a factory calendar ID. Use the "Use Fac. Cal. remote" indicator to specify whether the factory calendar ID is located in the SAP Solution Manager system or the remote system. If a factory calendar ID is not specified, each day of the month is regarded as a working day. In the "Working Days" and "Relative to Month's..." columns, specify the working day on which data evaluation is to take place (in terms of the number of days relative to the start or end of the month). Unless otherwise specified, the day is calculated relative to the start of the month. If a number is not specified, data evaluation takes place on each working day in the factory calendar. If you specify "All working days" in the "Working Days" column, the "Relative to Month's..." field and the fields for the first month and the period do not have to be maintained, whereas the factory calendar ID field is mandatory. In the "1st Month" column, specify the first month to be taken into account when calculating the monitoring schedule. The initial value is the current month. In the "Period [# Months]" column, specify the time period (in months) required for calculating the monitoring schedule. If not explicitly specified, a period of one month is used. The jobs for executing data collection via background job are scheduled on the satellite system with the activation of the monitoring. Up to 2 jobs are scheduled: BPM_DATA_COLLECTION_1 and BPM_DATA_COLLECTION_2 (both using report /SSA/EXS)
© SAP AG
SM300
6-16
Performance of Data Collection
Possible Problems:
Performance Impact on Satellite System if expensive data collectors run too often
Timeout of data collectors if they are executed in dialog work process (via RFC)
Solution:
Evaluate how often data collection should run based on your monitoring requirements
If possible, test the duration of the data collection in the satellite system in transaction ST13 before configuring the monitoring
Data Collection that could run into a timeout should be executed via background job instead of RFC
© SAP AG 2009
Performance of data collection for Throughput and Backlog Indicators (TBIs): y depends on the customized selection criteria for monitoring objects y based on the selection criteria large numbers of records can be read with each run of the data collector y based on the customizing indexes on database tables can be ignored
Both the customizing of the selection criteria (performance of a single data collection run) as well as the data collector frequency defined for each monitoring object (total load of data collection on system) should be checked for their impact on the performance of the system..
In general, the data collectors for TBIs should run only once or twice per day. SAP Best Practice is “once per day”.
For other monitoring functionalities contained within the Application Monitor, the recommendations regarding the data collection frequency and the method of execution can differ.
© SAP AG
SM300
6-17
Tool “TBI_Reports” in Transaction ST13 on Satellite System To test the performance of the data collection call transaction /nST13 on the satellite system.
Choose tool “TBI_REPORTS” and execute.
Select your relevant TBI functionality.
© SAP AG 2009
Note: Not all monitoring functionality available in the application monitor can be tested this way. As a general rule, only the throughput and backlog indicators can be tested via ST13.
© SAP AG
SM300
6-18
Check Result and Performance of Data Collection
Use the F4 help in the second part of field MONID to choose one or all available key figures. Enter further selection criteria and execute.
Check the duration of the data collection (within seconds or minutes?) and check the results to verify the correctness of the selection criteria.
© SAP AG 2009
© SAP AG
SM300
6-19
Data Collection via Background Job SAP Solution Manager
Satellite System
200
800 BPMon Graphic
BPMon Session
Data Collector Coding executed by background job
Service Desk
Result Table
SCOT
BPMon Engine
000
User SM_BPMO
User SOLMANTT4200
000
User SAPSYS Central CCMS
Local CCMS
© SAP AG 2009
If the actual data collection is executed by a background job (flag “DC in background”), the RFC call from the BPMon engine does not execute the data collection. Instead, the RFC call simply accesses the result table in the satellite system to pick up the result of the last background job run. The access to the result table is not performance critical.
© SAP AG
SM300
6-20
Customize Value Combinations
Choose monitoring type “Application Monitor” Reload application monitoring objects from satellite system
In the sub-node for the alert, double-click on the field in column “Counter” in table . This opens a pop-up where you can enter your selection criteria. Use the value help for the selection fields. It will show you the possible values on the satellite system.
Choose monitoring object
Choose key figures (alert types) Set data collector frequencies Customize value combinations Provide thresholds or status for alerts
© SAP AG 2009
Depending on the monitoring functionality, selection criteria may have to be defined both on monitoring object level and key figure level.
The value helps in the pop-up are the actual value helps available on the satellite system.
For some selection fields, no value help will be available.
© SAP AG
SM300
6-21
Provide Thresholds or Status for Alerts
Choose monitoring type “Application Monitor” Reload application monitoring objects from satellite system Choose monitoring object
Once you have defined the selection criteria, specify the thresholds against which you want to monitor. In addition, give a short description what is monitored for the selection criteria behind your counter ID. Save your settings.
Choose key figures (alert types) Set data collector frequencies Customize value combinations Provide thresholds or status for alerts
© SAP AG 2009
For throughput alerts you can usually configure 2 sets of alerts: if there was too much throughput or if there was too little throughput.
For backlog alerts you can only configure 1 set of thresholds, since a small backlog is not a problem, only a large backlog.
© SAP AG
SM300
6-22
Exercise: Configure Application Monitoring
Exercise: Configure Application Monitoring
© SAP AG 2008
© SAP AG
SM300
6-23
Lesson 2: Monitoring for Sample Business Processes
1. Setup Application Monitoring 2. Monitoring for Sample Business Process 3. User Exit Appendix: Example for User Exit
© SAP AG 2009
© SAP AG
SM300
6-24
Application Monitoring Objects for Sample Business Process Sales Order Backlog No. of open Sales Orders No. of incomplete Sales Orders No. of SOs with delivery block No. of SOs with billing block No. of SOs with credit block
Sales Orders Throughout No. of Sales Orders created No. of Sales Order items created
non SAP CRM - CDP
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Run MRP
Procurement Process No. of outbound deliveries created No. of open outbound deliveries
Manufacturing Process
Create Outbound Delivery Create Billing Document
No. of invoices not transferred to FI No. of invoices not printed No. of open/overdue customer items FI-AR
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
No. of deliveries with GI
posted but no invoice created
No. of Open Picking TOs
© SAP AG 2009
See the unit’s appendix for further sample business processes.
© SAP AG
SM300
6-25
Available Application Monitoring Functionalities
Available Monitoring Objects for
ERP Logistics
ERP Financials
SAP CRM
SAP APO
Extended Warehouse Management
Mass Activity Monitoring
SEM-BCS
All currently available Monitoring Objects can be found in the Media Library of BPM on the SAP Service Marketplace: http://service.sap.com/bpm Æ Media Library Æ Customer Information Æ Business Process & Interface Monitoring - Part 2 © SAP AG 2009
You will also find an overview of all Monitoring Objects for Application Monitors in the unit’s appendix.
© SAP AG
SM300
6-26
Example: Monitoring Objects/Alert Types for Procurement 1/2) Alert Type
Selection Options
MRP Run Key Figures Statistics
Plant
Runtime Canceled Dumps
Key Figures MRP List
Plant, MRP controller, Exception Group
# of exceptions in MRP List No MRP List created
Planned Orders Opening Order Date = Today (external procurement) Opening Order Date < Today (external procurement)
Plant, Order Type, MRP Controller, Offset Period
Opening Order Date in Offset Period (external procurement)* Purchase Requisition # of Requisition Items created
Purchasing organization, Plant, Creation indicator, Item category, Account Assignment Category, Document type, Created by, Older than x days, Outline agreement, Agreement item, Data from previous day
# of open Requisition Items # of overdue Requisition Items
© SAP AG 2008
© SAP AG
SM300
6-27
Example: Monitoring Objects/Alert Types for Procurement (2/2) Alert Type
Selection Options
Purchase Orders # of Purchase Orders created* # of Purchase Order Items created
Purchasing organization, Plant, Document category, Item category, Account assignment Category, Document type, Created by, Outline agreement, Agreement item, Data from previous day, Older than x days
# of open Purchase Order Items # of overdue Purchase Order Items # of Purchase Orders not yet completed* MM Invoices (AP) # of blocked invoices for payment # of blocked invoices for payment (cash discount endangered)
Company code, Fiscal year, Older than x days, due within x days
* As of next ST-A/PI 01L
© SAP AG 2008
© SAP AG
SM300
6-28
Sample Procurement Process ERP (PRD)
Run MRP
Job Runtime
MRP Log
No. of Purch. Req. created No. of Purch. Req. open No. of Purch. Req. overdue
No. of Purch. Orders created No. of Purch. Orders open No. of Purch. Orders overdue
Create Purchase Requisitions by MRP
Convert Purchase Req. to Purchase Order
Create Purchase Requisitions Manually
Job Runtime
Sent/Print Purchase Order
No. of Purch. Req. created No. of Purch. Req. open No. of Purch. Req. overdue
Job Runtime
No. of open Transfer
Requirements Create Binning Transfer Order
No. of consumption postings No. of Inbound Deliveries
created
Receive Inbound Delivery
No. of Transfer Orders created No. of open Transfer Orders
Confirm Binning Transfer Order
No. of Goods Receipts created
Post Goods Receipt Stock Level of critical
stock in GR area
Dialog Response Time
Perform Invoice Verification
Dialog Response Time Job Runtime
© SAP AG 2009
© SAP AG
SM300
6-29
Lesson 3: User Exit
1. Setup Application Monitoring 2. Monitoring for Sample Business Process 3. User Exit Appendix: Example for User Exit
© SAP AG 2009
© SAP AG
SM300
6-30
Features
Within the Business Process Monitoring User Exit, customer can implement their own Application Monitors as an enhancement (no change in SAP Standard) which make use of the same underlying infrastructure for Alerting
Scheduling mechanism
Definition of keyfigures, counters and thresholds
Autoreaction Methods
for Reporting
BI based Reporting
Service Level Reporting
Prerequisites: Newest ST A/PI must be installed on satellite system where the customer application monitors should be implemented A detailed Setup-Guide for User Exit in Business Process Monitoring is available at SAP Service Marketplace at http://service.sap.com/bpm © SAP AG 2009
© SAP AG
SM300
6-31
Setup Strategy
Create Entry Areas for BPMon Setup session (Activity on the Satellite System)
Define Monitoring Object Define Parameters for Monitoring Object (to refine exactly which job, log etc. should be monitored), possibly along with value help Define Alerts/Key Figures and define what kind of alert this should be – status, key figure, list Define Parameters for alerts (e.g. job start time) with possible value help
Create Report Z_BPM_ECU_COLLECTOR
Create Data Collectors (Activity on the Satellite System)
Copy coding for monitoring objects and key figures. Change Coding for Form DC_CUCUST## Change Coding for Form DC_CUCUST##_**
© SAP AG 2009
There are two activities that have to be carried out in order to create an application monitor. The creation of the entry areas is achieved by filling fields in screens. No coding has to be written for this activity.
© SAP AG
SM300
6-32
Appendix
Appendix
© SAP AG 2009
© SAP AG
SM300
6-33
Appendix: Example for User Exit
© SAP AG 2009
© SAP AG
SM300
6-34
Example for User Exit
Our Example: We want to monitor if table ZVBAKCRIT contains entries that are older than 5 days.
© SAP AG 2008
Table ZVBAKCRIT contains open sales orders for critical customers.
You should know exactly what you want to monitor and how the setup should look like so that you know which entries have to be maintained in which fields.
Although the basic structure is the same in the different ST-A/PI releases you should install the latest ST-A/PI to have access to all new functionalities and features (the length of text fields for instance has been increased with newer ST-A/PIs). The minimum is version 01G (before this the user exit was not available).
© SAP AG
SM300
6-35
Design the Areas for Entering the Monitoring Configuration Before creating the monitoring object and key figures decide how the monitoring setup should look like in the Setup Business Process Monitoring session. Monitoring Object: Open Critical Sales Orders Number of Days
In the following steps you can create these tables by executing these steps: Define Monitoring Object Define Parameters for Monitoring Object (to refine exactly which job, log etc. should be monitored) Define Alerts/Key Figures and define what kind of alert this should be – status, key figure, list Define Parameters for alerts (e.g. job start time) with possible value help © SAP AG 2009
© SAP AG
SM300
6-36
Create Areas for Data Entry
Call transaction SE38. Via this transaction execute report /ssa/exm. In the following screen, execute with
project ID ECU
change mode CHANGE.
© SAP AG 2009
© SAP AG
SM300
6-37
Define Monitoring Object
Enter a description for a monitoring object. Save.
© SAP AG 2009
Delete all lines without a description before saving.
The customizing ID is the technical name for the monitoring object.
© SAP AG
SM300
6-38
Specify General Data Define general settings by choosing “Customize Parameters”. In the next screen, define possible assignment and data collection settings. Save. Go back to previous screen.
© SAP AG 2009
© SAP AG
SM300
6-39
Define Key Figure (Alert)
Select “Define Key Figures”.
In the next screen, provide a name for the key figure and define the key figure type.
© SAP AG 2009
Key figure types are y KZ (Kennzahl), allows thresholds y ST (Status), similar to job cancellation y LI Key Figure (list) y LS Status (list)
© SAP AG
SM300
6-40
Customize Parameters for Key Figure
Select “Customize Parameter” for the key figure. Define the ID and the name of the parameter for the key figure. In addition, define which thresholds you want to use.
© SAP AG 2009
© SAP AG
SM300
6-41
Create Data Collectors
Create data collector in report Z_BPM_ECU_COLLECT OR. You can get templates for the coding per monitoring object and key figure by choosing button “Report template (Crtl + F6)” in during the definition of the monitoring object and key figure.
© SAP AG 2009
Activate the coding after it is completed.
© SAP AG
SM300
6-42
Configuration in BPMon Setup Session
Reload application monitoring objects to have your monitoring object available in the value help.
© SAP AG 2009
© SAP AG
SM300
6-43
Complete Monitoring Configuration
Give a name for the monitoring object and flag “Select”. Save. In the sub-node, select the key figure and define the monitoring schedule. Save. In the sub-node, give a name for the alert and provide selection criteria and threhsolds.
© SAP AG 2009
The full monitoring schedule functionality of the application monitoring infrastructure is available for your monitoring object.
Generate and Activate after you have completed your setup.
© SAP AG
SM300
6-44
Exercises Unit:
Application Monitoring
Lesson:
Application Monitoring Infrastructure
Exercise 16: Configure Application Monitoring
At the conclusion of this exercise, you will be able to: • Set up monitoring customizing for the Application Monitor
In order to monitor the creation of the sales orders, the throughput and the backlog of sales orders should be monitored
16-1 Set up monitoring customizing for the throughput of sales orders. 16-1-1 Create a monitoring object for sales order throughput for business process step “Create Sales Order”. Name this monitoring object “SO Throughput”. Select the throughput key figures for the monitoring object. 16-1-2 For business process “Order to Cash” sales orders that satisfy the following selection criteria are relevant: •
Document Category: Order
•
Document Type: OR
•
Sales Organization: 1000
•
Distribution Channel: 10
•
Division: 00
Check the performance of the data collection on the satellite system using transaction ST13. Question: Should the data collection be executed in dialog or in background? Answer: _____________________________________________________________ 16-1-3 Configure data collection to run every night at 00:30.
© SAP AG
SM300
6-45
16-1-4 Configure the selection criteria for the throughput key figures as given above. Monitor if the throughput was not large enough by using the following thresholds •
Order Throughput: 100 for Red, 500 for Yellow
•
Item Throughout: 1000 for Red, 2000 for Yellow
16-2 Set up monitoring customizing for the backlog of sales orders. 16-2-1 Create a monitoring object for sales order backlog for business process step “Create Sales Order”. Name this monitoring object “SO Backlog”. Select the backlog key figures (total values) for the monitoring object. 16-2-2 For business process “Order to Cash” sales orders that satisfy the following selection criteria are relevant: •
Document Category: Order
•
Document Type: TA
•
Sales Organization: 1000
•
Distribution Channel: 10
•
Division: 00
Normally, the processing of the business process takes 5 days or less. Therefore, backlog of sales orders older than 5 days is relevant for monitoring. Question: Do you have to check the performance of the data collection again? Answer: _____________________________________________________________ Question: Does the monitoring of client 800 in TT5 also report on sales orders that were created in client 600? Answer: _____________________________________________________________ 16-2-3 Configure data collection to run every night at 01:00. 16-2-4 Configure the selection criteria for the backlog key figures as given above. Monitor if the backlog is too large by using the following thresholds: •
© SAP AG
1 for Yellow, 1000 for Red
SM300
6-46
Solutions Unit:
Application Monitoring
Lesson:
Application Monitoring Infrastructure
Exercise 16: Configure Application Monitoring
16-1 Set up monitoring customizing for the throughput of sales orders. 16-1-1 In the Setup BPMon session go to node “Business Process Monitoring Setup” Æ “Business Processes” Æ “Order to Cash (Prod.)” Æ “(3) Create Sales Orders [TT5]” Æ “Application Monitor”. In tab “Application Monitoring Objects” create an additional line and use the value help in column Application Monitor to assign monitoring object “Sales Documents”. In column “Monitoring Object Name” enter “SO Throughput”. Flag “Select” and save. In sub node “SO Throughput” select key figures “Sales Documents (created)” and “Sales Document Items (created)”. 16-1-2 Call transaction /nST13 on TT5. Execute tool “TBI_REPORTS”. Select “Sales and Services”. In tab “Sales Documents”, select the key figure “Sales Documents (created)” from the second part of field “MONID” using the F4 help. Enter the further selection criteria given in the exercise (Document Category, Document Type, Sales Organization, Distribution Channel, Division). In addition, flag “Data from prev. day”. Execute by hitting the clock-button. Repeat the last steps for key figure “Sales Document Items (created)”. Answer: The selection screen returns within seconds, so the data collection can run in dialog mode. 16-1-3 Return to TT4 to the node you were in before. Go to tab “Monitoring Schedule”. Select “Schedule Type” W. Flag every day of the week for data collection. Configure data collection to start at 00:30. Delete all entries in columns “End Time” and “Period”. Make sure that field “DC in background” is unflagged. Save. 16-1-4 In both sub-nodes for the key figures go to tab “”. Double click on a field in column “Counter”. In the pop-up, enter the selection criteria given in the exercise. In addition, flag “Data from prev. day”. Provide a short text “Sales Org. 1000/10/00”. Enter the thresholds as given in the exercise. Save.
© SAP AG
SM300
6-47
16-2 Set up monitoring customizing for the backlog of sales orders. 16-2-1 In the Setup BPMon session go back to node “Business Process Monitoring Setup” Æ “Business Processes” Æ “Order to Cash (Prod.)” Æ (3) Create Sales Orders [TT5]” Æ “Application Monitor”. In tab “Application Monitoring Objects” create an additional line and use the value help in column Application Monitor to assign monitoring object “Sales Documents”. In column “Monitoring Object Name” enter “SO Backlog”. Flag “Select” and save. In sub node “SO Backlog” select key figures “Open orders”, “Incomplete sales documents”, “Orders with delivery block”, “Orders with billing block”, “Orders with credit block”, “Orders (GI date in past but not delivered)”. For the configuration, restrict yourself to the highlighted key figures. 16-2-2 Answer: You do not have test the data collection again, since the selection criteria is more distinctive than for the throughput monitoring. Answer: Only the sales orders in the client in which you execute the tool TBI_REPORTS are considered. 16-2-3 Return to TT4 to the node you were in before. Go to tab “Monitoring Schedule”. Select “Schedule Type” W. Flag every day of the week for data collection. Configure data collection to start at 01:00. Delete all entries in columns “End Time” and “Period”. Make sure that field “DC in background” is unflagged. Save. 16-2-4 In all sub-nodes for the key figures go to tab “”. Double click on a field in column “Counter”. In the pop-up, enter the selection criteria given in the exercise. Fill also field “Older than x days” where available. Provide a meaningful short text. Enter the thresholds as given in the exercise. Save. Complete your configuration by generating and activating your monitoring customizing.
© SAP AG
SM300
6-48
Interface Monitoring
Course Overview Unit 1 Introduction to Business Process Monitoring Unit 2 Procedure Unit 3 Monitoring Configuration Unit 4 Using Business Process Monitoring
Unit 8
Data Consistency Monitoring
Unit 5 Cross-Application Monitoring
Unit 9
Reporting
Unit 6 Application Monitoring Unit 7 Interface Monitoring
Unit 10 Handover to Production Unit 11 Managing Jobs in SAP Solution Manager
© SAP AG 2008
© SAP AG
SM300
7-1
Business Process Monitoring: Unit Objectives
After completing this unit, you will be able to: Set up a basic Interface Monitoring concept Set up basic monitoring of IDoc and qRFC interfaces with SAP Solution Manager Use existing documentation to set up further monitoring functionalities in SAP Solution Manager
© SAP AG 2009
© SAP AG
SM300
7-2
Lesson 1: Configuring Interface Monitoring
1. 2. 3. 4. 5.
Configuring Interface Monitoring IDoc Monitoring qRFC Monitoring SAP XI/PI Monitoring via SAP Solution Manager File Monitoring Appendix: I. qRFC Monitoring II. SAP XI/PI Monitoring via SAP Solution Manager III. SAP Batch Input Monitoring
© SAP AG 2009
© SAP AG
SM300
7-3
Data Distribution between Systems SAP system
SAP system ALE/IDoc
BD87, WE02, WE05
tRFC/qRFC
SM58, SMQS, SMQ1
SMQR, SMQ2
File
BD87, WE02, WE05
IDoc
SAP XI
BD87, WE02, WE05
IDoc
EDI subsystem
non-SAP system XML
EDI document (EDIFACT)
© SAP AG 2009
From technical viewpoints, you may use different interface techniques for data transfer between systems. The monitoring activities that have to be carried out depend on the used interface technique, therefore the first thing to determine is the interface technique.
© SAP AG
SM300
7-4
Initial Situation In addition to monitoring the application and cross-application specific aspects of business process “Order to Cash”, company IDES now also wants to configure interface monitoring for their business process. CRM - CDP
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Run MRP
Procurement Process
Manufacturing Process
Create Outbound Delivery
Create Billing Document
Post Goods Issue
Warehouse - TT5
Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
© SAP AG 2009
© SAP AG
SM300
7-5
Select Interface for Monitoring
In the Business Process Monitoring Setup session, go to node “Interface Monitoring”. In tab “Interfaces in Business Process” select which interface you want to monitor. Save.
© SAP AG 2009
The interfaces are listed here only if they have been created in the solution directory. If no interfaces exist, the node “Interface Monitoring” is not displayed.
© SAP AG
SM300
7-6
Select Monitoring Type
Select the monitoring type you want to use. Save. Most interface monitoring functionalities are available in the application monitoring infrastructure.
© SAP AG 2009
Most of the interface monitoring functionalities can not only be attached to an interface in the business process, but also to a business process step. You only need to specify an Application Monitor object in the business process step. Then you can select the interface monitoring object from the F4 help. All alerts belonging to this object can then be found in the operations part of the session when navigating to the corresponding business process step.
© SAP AG
SM300
7-7
Load Monitoring Objects
Load the monitoring objects from the satellite system. Since two satellite systems are involved in the interface, you can load monitoring objects from both the sending and the receiving system of the interface.
© SAP AG 2009
Interface Monitoring Objects always have to be created for the sending system and the receiving system. That’s why there are two buttons to load the application monitors into the BPMon setup session: one button for the sending system and one button for the receiving system. ST-A/PI01K needs to be installed on both systems so that the interface can be fully monitored using the Application Monitoring functionality. Only interface relevant application monitoring functionalities can be assigned to an interface.
© SAP AG
SM300
7-8
General Remarks about Interface Monitoring Configured in Setup Business Process Monitoring session Can be assigned to Interfaces Prerequisite: interfaces are created in the business process graphic Business Process steps
Performance issues might appear
© SAP AG 2009
Interface Monitoring is configured in Setup Business Process Monitoring session. Consider possible Performance problems: Data Collection for Interface Monitoring accesses tables that can be very large in productive systems. Depending on the selection criteria, data collection via background job may be advisable. For some monitoring functionalities the flag to collect in background is set automatically and can not be changed.
© SAP AG
SM300
7-9
Monitoring Graphic after Activation (including XI and Legacy System) qRFC Monitoring Outbound qRFC Monitoring Inbound
File Monitoring + Batch Input Monitoring
DESADV IDocs - Inbound
XI Processing
DESADV IDocs Outbound
MATFET IDocs
MATMAS IDocs © SAP AG 2009
© SAP AG
SM300
7-10
Lesson 2: IDoc Monitoring
1. 2. 3. 4. 5.
Configuring Interface Monitoring IDoc Monitoring qRFC Monitoring SAP XI/PI Monitoring via SAP Solution Manager File Monitoring Appendix: I. qRFC Monitoring II. SAP XI/PI Monitoring via SAP Solution Manager III. SAP Batch Input Monitoring
© SAP AG 2009
© SAP AG
SM300
7-11
Initial Situation: Monitoring of Interface for Replication of Outbound Delivery
CRM - CDP
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Replication the Replication ofofthe Outbound Deliveryfails fails Outbound Delivery
Run MRP
Procurement Process
Manufacturing Process
Create Outbound Delivery Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
The outbound delivery between the ERP system and the warehouse system is replicated via ALE. If the outbound delivery is not replicated to the warehouse system, the business process execution stops.
© SAP AG 2009
Monitoring of the interface between ERP and the warehouse system for the replication of the outbound delivery.
© SAP AG
SM300
7-12
What Is an IDoc?
System 1
System 2 tRFC, File
Application
IDoc
IDoc
Application R/3, non-SAP
R/3
IDoc = Intermediate Document Object related by message types IDoc as data container Asynchronous communication Release independent Extensive Exception Handling © SAP AG 2008
An Intermediate document (IDoc) is a container for exchanging data between R/3, R/2 and non-SAP systems.
© SAP AG
SM300
7-13
IDoc Record Types
Control record
IDoc ID Partner IDoc type and message type External structure
Data records Control part
Status records
Application data
IDoc ID Status information
© SAP AG 2008
Each IDoc in the SAP database consists of Exactly one control record A number of data records, which span a tree of segments A set of status records increasing in number over time A single transmission of data between two systems via the IDoc interface can carry one of the following kinds of information: IDocs (consisting only of one control record and multiple data records) Status information (consisting only of status records) IDoc types are special data structures for special applications or messages. Filling such a structure with application data means creating an IDoc (as an instance of the IDoc type). Normally, each business process (for example, a purchase order) corresponds to a certain IDoc type, which can include the relevant data. The segment hierarchy can be represented in tree form as parent and child segments. This representation allows the application data to be structured.
© SAP AG
SM300
7-14
Where Are IDocs Used? – Application Link Enabling (ALE)
SAP 4.x
IDoc
NonSAP System
IDoc
IDoc
SAP 4.x
IDoc
EDI Converter
EDI
Business Partner
Controlled exchange of Intermediate Documents (IDocs) between application systems Separation and integration of operational units Master and transactional data Exchange with Business Partners via EDI © SAP AG 2009
Application Link Enabling (ALE) is a means of creating and operating distributed applications. This involves business-controlled message exchange using consistent data across loosely linked SAP and non-SAP applications. ALE integrates applications using synchronous and asynchronous communication. It does not require a central database. EDI = Electronic Data Interchange Exchange of business documents between business partners by means of electronic messages
- Example: exchange of purchase or sales orders and invoices between customers and vendors An EDI subsystem/converter maps IDocs to international standard formats Most common between R/3 system and EDI subsystem is the flat file interface (standard EDI scenario). ALE = Application Link Enabling Integrated business processes across distributed systems within one company
- Example: replication of master data between several R/3 Systems Distribution of master data, transactional data, and control data Most common between R/3 systems is the (asynchronous) transactional RFC interface (standard ALE scenario)
© SAP AG
SM300
7-15
Example: ALE Scenario
Customizing data Financials
Sales, shipping and
Central controlling Central SOP
Master data
Information Systems:
Inventory Purchasing Sales Central purchasing Reference system for master data and control data
billing Purchasing of
trading goods Inventory
Application data
management Local controlling
LS SALES
© SAP AG 2008
Logical system (LS): System in which applications run that share a common data basis. In SAP terms, a logical system is a client in a database. Messages are exchanged between logical systems. Customizing data synchronization: This includes, for example, organizational units (company code, division, plant), units of measurement, and many other parameters that must be set in the system. Before data can be exchanged between two systems, the Customizing in certain areas must be the same in both systems. Master data distribution: Cross-system master data can be maintained centrally and then distributed. The final values are assigned locally. Alternatively, a view of the master data is maintained locally. In this case there is always one maintenance system for each view. The master data is transferred to a central R/3 System and distributed from there. The shared master data (SMD) tool supports this. Application data distribution: Application data is distributed between the distributed systems as specified by the business processes defined in the distribution model.
© SAP AG
SM300
7-16
How are IDocs Processed?
Create IDoc
Application
Outbound Processing
ALE
Sending IDoc
Communication
Inbound Processing
ALE
Post IDoc
Application
Sender
Receiver
Application creates IDoc and passes it to the ALE layer Outbound processing in the ALE layer IDoc sent to the receiving system in the communication layer Inbound processing in the ALE layer IDoc passed to the Application
© SAP AG 2009
The process of exchanging data via ALE takes place in the following layers: Application Layer (application data in sending and receiving system) Distribution Layer (processing in ALE layer both in the sending and receiving system) Communication Layer (data transfer through tRFC or file) The sender generates status records until the IDoc has left the system. The receiver generates status records from the moment the IDoc has arrived. Unless the ALE audit is explicitly activated there is no exchange of status information between the two systems (sender does not know about IDocs status on receiver and vice versa) IDocs can be distributed as flat files or via tRFC.
© SAP AG
SM300
7-17
ALE – IDoc Flow and IDoc Status 54
Sender System (Outbound)
Receiver System (Inbound)
52 51
Application
53
Application MC Record 62
Message Control
Work Item
66 01
ALE layer + IDoc Basis
25
64
26
60
ALE layer + IDoc Basis
61
30
50
02 39
03 12
41
File
tRFC
© SAP AG 2008
IDoc Status: All the IDoc statuses are maintained with transaction WE47. Here you can see ‘key’ statuses during IDoc processing. tRFC communication: When the receiver system is an SAP system, an IDoc is sent via tRFC which can be monitored with transaction SM58. Otherwise, a file is generated to transfer via EDI. Message control parameters are used to control the circumstances under which a document is sent. It considers the following factors: The document to be sent The type of document When the document must be dispatched The output to be used
© SAP AG
SM300
7-18
Important Monitoring Transactions: WE05 WE05: Display the records of selected IDocs and the content of the records in the satellite system Doubleclick to enter detailed information
© SAP AG 2009
Transaction WE05 provides the following information: Complete IDoc traffic on the satellite system for a specific time window, sorted by Message Type The actual status of the IDoc Partner information (Partner Number, Partner Type, Port). This information can be used for customizing the data collector in SAP Solution Manager All statuses the IDoc has passed during the processing on the system in chronological order (to be found in the Status records) The payload of the message in the Data records
© SAP AG
SM300
7-19
Important Monitoring Transactions: BD87 BD87: Search for IDocs in error status on the satellite system
© SAP AG 2009
Transaction BD87 provides the following information: An overview of the current status of all IDocs on the satellite system (in a certain time frame). Hence error statuses can be identified immediately. Information about erroneous tRFC entries referring to IDoc processing. It is possible to navigate into single IDocs to get more detailed information.
© SAP AG
SM300
7-20
Setup of IDoc Monitoring in SAP Solution Manager
Assign Application Monitor “IDoc Monitoring” to the interface for both the sending and the receiving system. Reason: both the outbound and the inbound processing could fail and hence should be monitored.
There are 2 key figures available: Delta Number Monitor: evaluates the IDocs since the last data collector run Total Number Monitor: evaluates all IDocs on the system
© SAP AG 2009
Delta number monitor: Data collector evaluates number of suitable IDocs since the last collector run (IDocs that newly turned into the monitored status(es) / IDocs whose status has changed since the last data collector run). Total number monitor: Data collector evaluates number of suitable IDocs for the last x days ( parameter ‘IDoc Age’ on object level).
© SAP AG
SM300
7-21
Define Selection Criteria per Monitoring Object In the same node, switch to tab “Detail Information”. Double click on the field in column “Counter”. This opens a pop-up where you can enter your selection criteria. Use value help for selection fields. This value help will show you possible values on the satellite system.
© SAP AG 2009
Direction (Inbound or Outbound): Direction of the message flow from the perspective of the monitored system. If the direction is INBOUND fill in sender information for the parameters below. If the direction is OUTBOUND fill in receiver parameters below! Partner port (RCVPOR or SNDPOR): For example, FILEPORT Partner number (RCVPRN or SNDPRN): For example, SIDCLNT110 Partner type (RCVPRT or SNDPRT): For example, LS Partner function (RCVPFC or SNDPFC): For example, payer in SD Message type (MESTYP): For example, ORDERS Basic type (IDOCTP): For example, ORDERS05 Message code (MESCOD): Further separator besides MESTYP Message function: Further separator besides MESTYP IDoc age (in hours): Ignore IDocs which are older than x hours. Caution: The collector will ignore values higher than 2 weeks = 336 hours!
© SAP AG
SM300
7-22
Define Monitoring Schedule and Execution
In the same node, switch to tab “Monitoring Schedule”. Here you define how often the data collection for this monitoring object should run.
Due to the size of the IDoc tables in most customer systems the IDoc monitoring is performance critical. Hard coded, data collection cannot run more frequently than every 15 minutes. IDoc data collection is always executed via background job. © SAP AG 2009
Data Collection can be executed periodically within certain time windows (like Mo-Fr every 15 minutes) or at specific times during the day (like every day at 6pm). By using a monthly monitoring schedule instead of a weekly schedule it is also possible to have the data collection run only at specific days of the year (like every 1st working day of the month). Basis for that monthly schedule are factory calendars. You can select to consider either a factory calendar on SAP Solution Manager or on the involved satellite system. Monthly data collection only makes sense if the critical IDocs are created only on single days during the month. Normally for IDoc monitoring you should select a weekly monitoring schedule. The data collection for IDoc Monitoring is hard coded to 15 minutes. The column 'Period [min]' determines the frequency how often the measured value is evaluated and should be set higher than or equal to 15minutes.
© SAP AG
SM300
7-23
Define Selection Criteria per Alert
In the sub-node for the alert, double click on the field in column “Counter” in table . This opens a pop-up where you can enter your selection criteria. Use value help for selection fields. This value help will show you possible values on the satellite system. © SAP AG 2009
Possible Selection Criteria: Status Number(s): e.g. 51 for IDoc in error Status Message Qualifier: The field identifies the origin of the messages which are transmitted in the status. E.g. SAP messages are identified with 'SAP'. Status Message ID: e.g. E0 Status Message Number: e.g. 099 Status Age (in min): Minimum Status Age (Sometimes the status should be at least x minutes old before taking this IDoc into account). Default is 0 minutes. The status information of an IDoc can be found in the status records of the IDoc (use transaction WE05). It is possible to define several counters for the same alert. For example, several statuses for the same selection criteria (same IDoc type and same receiver information) should be monitored independently from each other: Status Number 30 (‘IDoc ready for dispatch’) with Status Age 10 min (IDoc backlog monitoring) Status Number 02 (‘Error passing data to port’) with Status Age 0 min (IDoc error monitoring)
© SAP AG
SM300
7-24
Specify Threshold Values
Once you have defined the selection criteria, specify the thresholds against which you want to monitor. Save your settings.
© SAP AG 2009
For throughput alerts you can always monitor if the throughput was exceeded or fell short of. That means you can define 2 sets of threshold values. For backlog alerts you can only define one set of threshold values: if the backlog was exceeded. Note: Be aware that the threshold values work as more/less than. E.g. a value of 10 for the threshold ‘Red, if less than’ results in a red alert if the threshold value is 9 or smaller.
© SAP AG
SM300
7-25
Exercise: Configure IDoc Monitoring
Exercise: Configure IDoc Monitoring
© SAP AG 2008
© SAP AG
SM300
7-26
Available Key Figures
Alert Type
Select Options
IDoc Monitoring
On object level:
‘Delta’ monitor: number of suitable IDocs since the last data collection ‘Total number’ monitor: number of suitable IDocs for the last x days
Direction, Port, Partner Number, Partner Type, Partner Function, Message Type, Basic Type, Message Code, Message Function, IDoc Age (in hours)
On key figure level: Status Number(s), Status Message Qualifier, Status Message ID, Status Message Number, Status Age (in min)
Depending on your monitoring concept it could make sense to use only one key figure or both key figures in parallel.
© SAP AG 2008
Delta number monitor: Data collector evaluates number of suitable IDocs since the last collector run (IDocs that newly turned into the monitored status(es) / IDocs whose status has changed since the last data collector run). Total number monitor: Data collector evaluates number of suitable IDocs for the last x days ( parameter ‘IDoc Age’ on object level). Parameters on monitoring object level: Partner port (RCVPOR or SNDPOR): For example, FILEPORT Partner number (RCVPRN or SNDPRN): For example, SIDCLNT110 Partner type (RCVPRT or SNDPRT): For example, LS Partner function (RCVPFC or SNDPFC): For example, payer in SD Message type (MESTYP): For example, ORDERS Basic type (IDOCTP): For example, ORDERS05 Message code (MESCOD): Further separator besides MESTYP Message function: Further separator besides MESTYP IDoc age (in hours): Ignore IDocs which are older than x hours. Caution: The collector will ignore values higher than 2 weeks = 336 hours! In contrast to the other Application Monitor functionalities, the IDoc data collector provides selection criteria not only on monitoring object level, but also on the (subsequent) key figure level. Here, the statuses to be monitored have to be deposited. It is also possible to specify selection criteria concerning the Status Message which can be found in the Status records. The Status Message can be used to distinguish between IDocs with the same technical information (sender and receiver information), but different application background.
© SAP AG
SM300
7-27
Possible Use-cases for IDoc Monitoring Monitoring aspect
Error monitoring
Error monitoring
Backlog Monitoring
Volume statistics
Monitoring Object
IDocs type MATMAS Partner xy1
IDocs type MATMAS Partner xy2
IDocs type ORDERS Partner xy3
IDocs type ORDERS Partner xy4
IDocs in status 51
IDocs in status 65
IDocs in status 03
IDocs in statuses 50-99
IDocs in status 65
IDocs in status 65
IDocs in status 30
Every 30 min more than (>)
Every 30 min more than (>)
Every 60 min more than (>)
Key Figure(s)
DC frequency & monitoring direction
Once per day less than ( SP08 7.00 => SP06 6.40 => SP08 7.10 => SP04
Recommended mode for the IFMon collector Required customizing for parameter „Command string“
Alternative scenarios
ST-A/PI release 01K or later in satellite system?
no
Basis release of satellite system is 6.20 or later?
no
ST-PI 2005_1 with sufficient SP level available? º
no
Solution Manager Diagnostics connected?
no
Basis release of satellite system is 4.6C, 4.6D or 6.10?
Large qRFC tables or many monitoring objects expected?
no
no
SMD‘s qRFC collectors are started as per Wily Host Agent configuration
Schedule the SMD‘s qRFC collectors manually per program /SSA/EIM
Use „direct selection“ mode (own qRFC raw data selection for each monitoring object)
Use old qRFC monitoring based on CCMS infrastructure
Customize command strings as per setting in SMD‘s WilyHostAgent Template.xml
Customize command strings as per used variant of scheduled program /SSA/EIM
Customize command strings with the dummy entry ‚DIRECTSELECT‘
New IFMon collector for qRFC (based on application monitoring) not usable in this case!
© SAP AG 2009
Technical prerequisites: You need an ABAP-based SAP system of Basis release 4.6C or later as the satellite system to be monitored. You need the add-on ST-A/PI (minimum release 01K) for the IFMon data collector. For the recommended SMD integration you need the add-on ST-PI 2005_1. The minimum ST-PI target release that supports the qRFC collectors is Basis 6.20. Furthermore the ST-PI 2005_1 needs a certain minimum support package level for the storage of the qRFC metrics into the ST-A/PI cluster table:
Basis release 6.20 => SP08 (SAPKITLQG8) Basis release 6.40 => SP08 (SAPKITLQH8) Basis release 7.00 => SP06 (SAPKITLQI6) Basis release 7.10 => SP04 (SAPKITLQJ4) The monitored satellite system must be connected to a SMD (Solution Manager Diagnostics) system, which triggers the SMD data collectors. Without SMD, you can still use the SMD data collectors (delivered within ST-PI), but they must be scheduled manually. For older Basis releases (4.6C and 6.10), you can only use the “direct select” option of the IFMon data collector.
© SAP AG
SM300
7-94
Available Key Figures for qRFC Monitoring
Alert Type
Select Options
Status (error) monitoring
Customizing options:
Number of entries with critical status in group
qRFC direction
Age of oldest critical status in group
RFC destination
Combination of "Entries" and "Age" in critical state
Queue group
Number of entries with interim status in group
Command string of SMD qRFC backlog coll.
Age of oldest interim status in group Combination of "Entries" and "Age" in interim state
Command string of SMD qRFC status coll.
Backlog monitoring Considered statuses:
Number of individual queues in group Total number of entries in all queues of group Average number of entries per queue in group Maximum number of entries per queue in group Age of oldest entry in group Combination of "Total entries" and "Oldest age"
Inbound: ANORETRY, SYSFAIL, ARETRY, CPICERR, MODIFY, NOEXEC, RETRY, RUNNING, STOP, WAITING, WAITSTOP Outbound: ANORETRY, SYSFAIL, VBERROR, ARTRY, CPICERR, EXECUTED, MODIFY, NOSENDS, RETRY, RUNNING, STOP, SYSLOAD, WAITING, WAITSTOP, WAITUPDA
© SAP AG 2008
Usually it is not necessary to include all the above mentioned key figures. Choose those that bring the most meaningful information to monitor your business process and are most adequate for defining thresholds.
© SAP AG
SM300
7-95
Explanation of Status Key Figures Key Figure
Explanation
Number of entries with critical state in group
Number of entries in a queue group which are in a critical state.
Age of oldest critical state entry in group
Age of the oldest entry in a queue group which is in a critical state.
Combination of Entries and Age in critical state
A combination of the key figures ‘Number of entries with critical state in group’ and ‘Age of oldest critical state entry in group’.
Number of entries with interim state in group
Number of entries in a queue group which are in an interim state.
Age of oldest interim state entry in group
Age of the oldest entry in a queue group, which is in an interim state.
Combination of Entries and Age in interim state
A combination of the key figures ‘Number of entries with interim state in group’ and ‘Age of oldest interim state entry in group’. Use this key figure if you are not interested in just the number or age of interim queue states, but the combination of those attributes.
Inbound queues: states ANORETRY and SYSFAIL Outbound queues: states ANORETRY, SYSFAIL, and VBERROR.
Inbound queues: states ANORETRY and SYSFAIL Outbound queues: states ANORETRY, SYSFAIL, and VBERROR.
Use this key figure if you are not interested in just the number or age of critical queue states, but the combination of those attributes. Inbound queues: states ARETRY, CPICERR, MODIFY, NOEXEC, RETRY, RUNNING, STOP, WAITING, WAITSTOP, Outbound queues: ARTRY, CPICERR, EXECUTED, MODIFY, NOSENDS, RETRY, RUNNING, STOP, SYSLOAD, WAITING, WAITSTOP and WAITUPDA.) Inbound queues: states ARETRY, CPICERR, MODIFY, NOEXEC, RETRY, RUNNING, STOP, WAITING, WAITSTOP Outbound queues: states ARTRY, CPICERR, EXECUTED, MODIFY, NOSENDS, RETRY, RUNNING, STOP, SYSLOAD, WAITING, WAITSTOP and WAITUPDA.
© SAP AG 2008
© SAP AG
SM300
7-96
Explanation of Backlog and Age Key Figures Key Figure
Explanation
Number of individual queues in group
Number of individual queue names that are in the same monitored queue group (having the same prefix).
Total number of entries in all queues of group
Total number of all entries in all queues that belong to the monitored queue group.
Average number of entries per queue in group
Average number of entries in all queues that belong to the monitored queue group. Calculated as ‘Total number of entries in all queues of group’ divided by ‘Number of individual queues in group’.
Maximum number of entries per queue in group
The number of entries in the largest queue of the monitored queue group.
Age of oldest entry in group
The age of the oldest queue entry within the monitored queue group.
Combination of Total entries and Oldest age
A combination of the key figures ‘Total number of entries in all queues of group’ and ‘Age of oldest entry in group’. Use this key figure if you are not interested in just large or old queues, but the combination of those attributes. There are two pairs of thresholds for yellow and red alert level. Define suitable thresholds for the queue entries and the oldest age individually. Both values are rated, and the lower rating is the basis for alerting. In other words, only if the thresholds of both attributes are reached (for example both have yellow rating), the overall rating will be yellow.
Age of qRFC data collection
The age of the last execution of the data collectors. This can be used for monitoring the periodic executions.
© SAP AG 2008
© SAP AG
SM300
7-97
Appendix: SAP XI/PI Monitoring via SAP Solution Manager
Appendix: I. qRFC Monitoring II. SAP XI/PI Monitoring via SAP Solution Manager III. SAP Batch Input Monitoring
© SAP AG 2009
© SAP AG
SM300
7-98
Setup of Message-based Alerting – Create Alert Category in the ALM Navigate to the Alert Framework ALM (transaction ALRTCATDEF) on the SAP XI system to create an alert category. Enable the alert reception in the ALM alert inbox by either: • Deposit fixed recipients by pressing the button ‘Fixed Recipients’. • Defining recipients via user roles. • Defining a subscription authorization.
© SAP AG 2009
Find more information concerning the creation of Alert Categories on SAP Service Marketplace: http://www.service.sap.com/bpm Management Framework)
© SAP AG
Media Library
SM300
Technical Information
ALM (Alert
7-99
Setup of Message-based Alerting – Specify Alert Category Specify the newly created alert category In the lower part of the ALM. Note that attributes like ‘Escalation Recipient’ are relevant for the ALM functionality only. If the alert handling of the SAP Solution Manager should be used only the category description needs to be maintained.
Specify as well text information that will be added to the alerts within the ALM on tab ‘Long and Short Text’. This information is not available for the alert text within CCMS and SAP Solution Manager but is useful when confirming the alerts in ALM. © SAP AG 2009
The following attributes are available: An error occured during the file processing: - Message: &SXMS_MSG_GUID& - Error: &SXMS_TO_ADAPTER_ERRTXT& - Error Category: &SXMS_ERROR_CAT& - Error Code: &SXMS_ERROR_CODE& The following Interface is affected: - Sender Service: &SXMS_FROM_SERVICE& - Sender Party: &SXMS_FROM_PARTY& - Sender Namesp: &SXMS_FROM_NAMESPACE& - Sender Interface: &SXMS_FROM_INTERFACE& - Receiver Service: &SXMS_TO_SERVICE& - Receiver Party: &SXMS_TO_PARTY& - Receiver Namesp: &SXMS_TO_NAMESPACE& - Receiver Interface: &SXMS_TO_INTERFACE& Infos for errors on Adapter Engine: - Adapter Type: &SXMS_TO_ADAPTER_TYPE& - Error Text: &SXMS_TO_ADAPTER_ERRTXT&
© SAP AG
SM300
7-100
Setup of Message-based Alerting – Create an Alert Rule in the RWB Navigate to transaction SXMB_IFR of the SAP XI system to enter the Runtime Workbench (RWB). Click on ‘Alert Configuration’ and give the rule a name (in field ‘Description’). Set the flag ‘Rule Active’. De-select ‘Suppress Multiple Alerts of This Rule’. This way, alerts are not just updated but new alerts are generated whenever this rule is met.
Specify filter criteria for the rule (see next slide).
© SAP AG 2009
© SAP AG
SM300
7-101
Setup of Message-based Alerting – Examples for Alert Rules Filter Criteria Customizing for sender and receiver
Customizing for sender without receiver (for errors that happen before the receiver determination)
© SAP AG 2009
Specify the filter criteria in the section ‘Alert Rule Definition’ as follows: Set the field ‘Connected to Message’ to ‘Not Relevant’. If your rule results in alerts that are not assigned to a message, that is, they are caused by errors that occurred before the message was sent, select the option ‘No’ for the ‘Connected to Message’ condition. In this case you cannot enter any further details about the sender or receiver. Depending on the needed granularity the message-based alerting allows to restrict the single rules to single error codes, if needed. For simplification reasons the flag for ‘No Restriction’ should be set which includes all errors for the sender and receiver combination. But still at least two rules need to be defined as errors can occur before the receiver determination. One with the fully specified sender information and wildcards (*) for the receiver information. Another with fully specified sender information and fully specified receiver information.
© SAP AG
SM300
7-102
Setup of Message-based Alerting – Link Alert Rule to Alert Category In section ‘Select Alert Category’ select the alert category that you want to use. To add the new rule to the list of alert rules, choose ‘Add Rule’.
© SAP AG 2009
© SAP AG
SM300
7-103
Setup of Message-based Alerting – Prepare CCMS In transaction RZ20 select the level ‘CCMS monitor sets’ and switch to change mode by selecting Extras Activate Maintenance function. 1) Name the Monitor Set. Afterwards select the new monitor set and press the button ‘New’.
2) Select the ‘>’ entry and create a ’Rule Node’ by specifying the rule ‘CCMS_GET_MTE_BY_CLASS’.
3) Enter the central monitoring system under ‘R3System’ and use the MTE class ‘SXI_RWBAlerts’. Set the ‘Display following parts of MTE name:’ and the ‘Context’ flag. © SAP AG 2009
© SAP AG
SM300
7-104
Setup of Message-based Alerting – Schedule Background Jobs (on XI) Check if a background job is already scheduled for the below listed ABAP programs. If not, use transaction SM36 to schedule a background job with two steps every 2-5 minutes, each for one of the programs: SXMSALERT_PROCESS_DATA_GET SXMSALERT_ACTIVE_ALERTS
© SAP AG 2009
© SAP AG
SM300
7-105
Appendix: SAP Batch Input Monitoring
Appendix: I. qRFC Monitoring II. SAP XI/PI Monitoring via SAP Solution Manager III. SAP Batch Input Monitoring
© SAP AG 2009
© SAP AG
SM300
7-106
SAP Batch Input – Overview
Sequential File Master data
Batch Input Program
Queue Dataset
Function Batch Input
Data Collector (as of ST-A/PI 01K)
Database Master data
© SAP AG 2008
Batch input is used primarily for bulk data transfers, for example, the one-time import of data from a legacy system into a newly installed SAP system. Another typical use is for periodic (hourly, daily...) transfers of data from external systems or legacy systems that are still in use into the SAP system, where all enterprise data is consolidated.
© SAP AG
SM300
7-107
SAP Batch Input – Available Key Figures
Alert Type
Select Options
SAP Batch Input Monitoring
On object level:
Number of sessions in specified status(es)
Session name
Number of errors per session
Creating program
Number of transactions in specified status(es)
Created by
Number of transactions processed per session
Max. Session Age in Days
Batch Input session – background job cancellation
On key-figure level: Status(es) Threshold values
© SAP AG 2008
Explanation of Key Figures: Number of sessions in specified status: Can be used to check if special sessions are “hanging” in a defined status Other possible use-cases: - Trigger an alert if there is at least one session in status not processed (E). - The data collector runs on an hourly basis. At least 10 sessions should be processed successfully (status F=Processed and R=in Process) each hour. - At least 90% of the sessions found should be in status 'processed'. Number of Errors per Session Measures the number of errors per sessions which typically indicate transactions that cannot be finished when processing. Number of transactions in specified status Used to monitor whether the number of processed transactions falls below or exceeds a defined threshold value. Possible use-case: e.g. each batch input session have to contain at least 2 but maximum 10 transactions.
…
© SAP AG
SM300
7-108
… Number of transactions processed per session Sometimes it is necessary to know the throughput of one session. Therefore this KPI was designed to measure the number of transactions in the defined status(es). Possible use-cases: - The data collector runs on an hourly basis. Each hour at least 100 transactions should be successfully processed (status F=finished). - At least 90% of the transactions found should be in status 'finished'. - Per hour maximum 10% of the transactions are allowed to be in status D=deleted. Batch Input Session – Background Job Cancellation When a session is processed in background a corresponding batch job is created. If this job fails the running session cannot be processed and its status is sometimes not updated.
© SAP AG
SM300
7-109
Batch Input Monitoring
Select the application monitor “BatchInput Monitoring”. Save. In the sub node, select the key figures.
© SAP AG 2009
© SAP AG
SM300
7-110
Specify Details for Key Figure
In tab ‘Detail information’ enter at least the name of the Batch Input session to be monitored and its maximum age in days. Optional fields are ‘Creating Program’ and ‘Created by’ which can be filled with the wildcard character as well. In tab ‘Monitoring Schedule’ specify the time and frequency of the data collection.
© SAP AG 2009
© SAP AG
SM300
7-111
Defining Selection Criteria for Alert
In the subsequent nodes, the key figures have to be specified further. Double-click on a field on column “Counter” to maintain ‘Status’, ‘Collector mode’ and ‘Unit’ for the Batch Input sessions that are supposed to be monitored. Afterwards, define the thresholds for the alert.
© SAP AG 2009
Note: Not all key figures provide an selection screen when double-clicking on the counter.
© SAP AG
SM300
7-112
Parameters Status(es): Status of the transaction that can be found in SM35 Select session Analysis. It is possible to define a more complex selection list. Collector mode: ALL: An alert is triggered at every collector run DELTA: A history is build up during the collector run. If an alert has been already triggered for a specific session there will be no new alert for the same session again.
Unit: Number: The number of sessions matching the selection criteria is taken into account for rating the alert. Percentage: The percentage in comparison to all transactions of the found sessions is taken into account.
© SAP AG 2009
© SAP AG
SM300
7-113
© SAP AG
SM300
7-114
Exercises Unit:
Interface Monitoring
Lesson:
IDoc Monitoring
Exercise 17: Configure IDoc Monitoring
At the conclusion of this exercise, you will be able to: • Set up IDoc monitoring in the application monitor
Deliveries between the ERP system and the Warehouse are replicated via IDocs of type DESADV. Monitoring of these IDocs should be included in the BPMon concept.
17-1 Set up monitoring of IDocs of type DESADV. 17-1-1 Choose the interface which is going from TT5 Client 800 to TT5 Client 600. Name it “ECC->WHS (Deliveries)” and select it for monitoring. 17-1-2 Configure monitoring of the IDocs of type DESADV going from TT5:800 to TT5:600. Question: What additional information do you need to monitor the interface properly? Answer: ____________________________________________________________ Configure delta monitoring of the outbound IDocs going to logical system R3_00_600: Error Monitoring: •
IDocs in status 02 and 26: 1 for yellow, 50 for red
Throughput Monitoring: •
IDocs in status 12: 100 for yellow, 10 for red, monitoring if the throughput was too little
Backlog Monitoring: •
© SAP AG
IDocs in status 01, 25 and 30: 1 for yellow, 50 for red
SM300
7-115
© SAP AG
SM300
7-116
Solutions Unit:
Interface Monitoring
Lesson:
IDoc Monitoring
Solution 17: Configure IDoc Monitoring
17-1 Set up monitoring of IDocs of type DESADV. 17-1-1 Go to node Business Process Monitoring Setup Business Processes Order to Cash (Prod.) Interface Monitoring. Name the interface going from TT5 Client 800 to TT5 Client 600 “ECC->WHS (Deliveries)” and select it for monitoring. Save. 17-1-2 Go to sub-node “ECC->WHS (Deliveries)”. In tab “Monitoring Type” select “Application Monitor” and save. Go to sub-node “Application Monitor”. In tab “Application Monitoring Object” use the value help in column “Application Monitor” to assign the monitoring functionality “IDoc Monitoring”. Give the Monitoring Object Name “Deliveries to WHS”. Flag the object for monitoring. Save. Go to sub-node “Deliveries to WHS”. In tab “Key Figures” select key figure “Delta Number Monitor”. Go to tab “Detail Information”. There, double click on the field in column “Counter”. This opens a pop-up to define selection criteria. Answer: You need information about the logical system names of the involved systems, possibly also about the IDoc Basic Type, and Partner Port. Configure monitoring for the logical system given in the exercise. Direction
O
Partner Port Partner Number
R3_00_600
Partner Type
LS
Partner Function Message Type
DESADV
Basic Type Message Code Message Function IDoc age (in hours)
672
In tab “Monitoring Schedule” enter the data collection to run every 15 minutes in background Mo-Su. Save.
© SAP AG
SM300
7-117
In sub-node “Delta Number Monitor” append a new line in tab “Delta Number Monitor”. Double click on the field in column “Counter”. This opens a pop-up to define selection criteria. Call one alert Error Monitoring and enter for Counter 001: Status Number(s)
02, 26
Status Msg. Qualifie Status Msg. ID Status Msg. Number Status Age (in min)
Remark: Use the Multiple Selection functionality to enter several Status Numbers by clicking the yellow arrow button at the right side of field Status Numbers. In the pop-up, use tab Select Single Values to enter the different Status Numbers (one number per row). Counter
Short text
Yellow if more
Red if more
001
Error Monitoring
1
50
Red if less
Yellow if less
Call one alert Throughput Monitoring and enter for Counter 002: Status Number(s)
12
Status Msg. Qualifie Status Msg. ID Status Msg. Number Status Age (in min)
Counter
Short text
002
Throughput Monitoring
Yellow if more
Red if more
Red if less
Yellow if less
10
100
Call one alert Backlog Monitoring and enter for Counter 003: Status Number(s)
01, 25, 30
Status Msg. Qualifie Status Msg. ID Status Msg. Number Status Age (in min)
10
Counter
Short text
Yellow if more
Red if more
003
Backlog Monitoring
1
50
© SAP AG
SM300
Red if less
Yellow if less
7-118
Exercises Unit:
Interface Monitoring
Lesson:
qRFC Monitoring
Exercise 18: Configure qRFC Monitoring
At the conclusion of this exercise, you will be able to: • Configure monitoring of qRFC interfaces
Sales orders are replicated from the CRM system to the SAP ECC systems via qRFC in inbound queues R3AU*. Therefore, these queues should be monitored as part of the BPMon concept.
18-1 Set up monitoring of RFC queues R3AU*. 18-1-1 Name the interface “CRM->ECC (Orders)” and select it for monitoring. 18-1-2 Configure monitoring for the inbound processing of RFC queues in the SAP ECC system via the application monitor. Monitor both for error situations and for backlog. Use the following information for configuring the monitoring: Backlog Monitoring: •
Age of oldest entry: 180 minutes for yellow, 300 minutes for red
Error Monitoring: •
Entries with critical status: 1 for yellow, 100 for red
Question: Since the SMD is not correctly configured for qRFC Monitoring, which coding for data collection has to be used? Answer: _____________________________________________________________
© SAP AG
SM300
7-119
© SAP AG
SM300
7-120
Solutions Unit:
Interface Monitoring
Lesson:
qRFC Monitoring
Solution 18: Configure qRFC Monitoring
18-1 Set up monitoring of RFC queues R3AU*. 18-1-1 Go into the Setup BPMon session. There, go to node Business Process Monitoring Setup Business Processes Order to Cash (Prod.) Interface Monitoring. Name the interface from CDP to TT5 “CRM->ECC (Orders)” and select it for monitoring. Save. 18-1-2 Go to sub-node “CRM->ECC (Orders)”. In tab “Monitoring Type” select “Application Monitor” and save. Go to sub-node “Application Monitor”. In tab “Application Monitoring Object” use the value help in column “Application Monitor” to assign the monitoring functionality “qRFC Monitoring”. Be careful to choose the right system, as there might be “qRFC Monitoring” entries for both the CDP and the TT5 system. Choose the one belonging to TT5, as you want to monitor the inbound processing of the queues in the SAP ECC system. Provide the Monitoring Object Name “Sales Queues Inbound”. Flag the object for monitoring. Save. Go to sub-node “Sales Queues Inbound”. In tab “Key Figures” select key figures “BL: Age of oldest entry” and “ST: Number entries with critical state”. Go to tab “Detail Information”. There, enter the following information (you can use the F4 help to find the right values): qRFC Direction
RFC Destination
Queue Group
Command String… backlog coll.
Command String… status coll.
I
*
R3AU*
DIRECT-SELECT
DIRECT-SELECT
In tab “Monitoring Schedule” enter the data collection to run every 15 minutes in dialog Mo-Su. Save. Backlog Monitoring: In sub-node “BL: Age of oldest entry” enter:
© SAP AG
Counter
Short text
Yellow
Red
001
Backlog Monitoring
180
300
SM300
7-121
Error Monitoring: In sub-node “ST: Number entries with critical state” enter: Counter
Short text
Yellow
Red
001
Error Monitoring
1
100
Generate and Activate. Answer: DIRECT-SELECT means you use the coding in ST-A/PI.
© SAP AG
SM300
7-122
Data Consistency Monitoring
Course Overview Unit 1 Introduction to Business Process Monitoring Unit 2 Procedure Unit 3 Monitoring Configuration Unit 4 Using Business Process Monitoring
Unit 8
Data Consistency Monitoring
Unit 5 Cross-Application Monitoring
Unit 9
Reporting
Unit 6 Application Monitoring Unit 7 Interface Monitoring
Unit 10 Handover to Production Unit 11 Managing Jobs in SAP Solution Manager
© SAP AG 2008
© SAP AG
SM300
8-1
Business Process Monitoring: Unit Objectives
After completing this unit, you will be able to:
Understand the general concept of data consistency in the system landscape
Set up basic monitoring of data consistency monitoring objects in SAP Solution Manager
© SAP AG 2009
© SAP AG
SM300
8-2
Lesson 1: Motivation for Data Consistency Monitoring
1. Motivation for Data Consistency Monitoring 2. Configuration of Data Consistency Monitoring
© SAP AG 2009
© SAP AG
SM300
8-3
Initial Situation: Data Consistency Monitoring
During the monitoring, IDES identifies problems with data inconsistencies between the ECC and the warehouse system. Therefore they set up data consistency monitoring in SAP Solution Manager.
© SAP AG 2009
© SAP AG
SM300
8-4
Example for Data Inconsistencies
CRM - CDP
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Incorrect stock information
Goods issue posted using an old transaction without data transfer
Run MRP
Incorrect stock information Procurement Process
Manufacturing Process
Create Outbound Delivery Post Goods Issue
Create Billing Document
Business Process brought to standstill by data inconsistencies
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
Goods issue missing Æ billing not possible
© SAP AG 2008
A warehouse employee is using a wrong transaction to post the goods issue in the warehouse. This transaction does not transfer the data to the ERP system.
As a consequence the goods issue is missing in the ERP system. This leads to an incorrect stock information which for other sales orders causes wrong results of the availability check and the MRP run.
© SAP AG
SM300
8-5
Where Data Inconsistencies can Occur (1/3)
CRM System
SAP ERP System
Configure Product
Create Sales Order
Create Sales Order
…
Real World Situation
≠
Post Goods Issue
System Situation
© SAP AG 2009
Examples:
• System - Real world situation: goods issue not posted in the system although the material has left the warehouse • Within one software component: update work process fails. • Between two software components: RFC destinations wrongly maintained or target system not available
© SAP AG
SM300
8-6
Where Data Inconsistencies can Occur (2/3)
CRM System
SAP ERP System
Configure Product
Create Sales Order
Create Sales Order
…
Inconsistencies within one software component
Post Goods Issue
© SAP AG 2009
Examples:
• System - Real world situation: goods issue not posted in the system although the material has left the warehouse • Within one software component: update work process fails. • Between two software components: RFC destinations wrongly maintained or target system not available
© SAP AG
SM300
8-7
Where Data Inconsistencies can Occur (3/3)
CRM System
SAP ERP System
Configure Product
Create Sales Order
Create Sales Order
…
Inconsistencies between two or more software components
Post Goods Issue
© SAP AG 2009
Examples:
• System - Real world situation: goods issue not posted in the system although the material has left the warehouse • Within one software component: update work process fails. • Between two software components: RFC destinations wrongly maintained or target system not available
© SAP AG
SM300
8-8
Examples for Real Inconsistencies
ECC System
CRM System
Case A
Case B
Customer Smith Address: New York City
Customer Smith Address: New York City
Customer Smith Address: New York City
Customer Smith Address: Berlin
Case C Customer Smith Address: New York City
© SAP AG 2008
An inconsistency is present if two instances representing the same data show different values, or data is missing completely in one of both systems. It is not possible without the context which of these cases of inconsistencies are more severe. While a data set missing completely seems to be very serious at first glance it is usually easy to detect and easy to correct, while inconsistent content may be unobserved for a long time leading to a lot of follow up errors like incorrect dependent data.
© SAP AG
SM300
8-9
Differences: Temporary Inconsistencies
ECC System
CRM System
Time t1
Time t2
Time t3
Customer Smith Address: New York City
Customer Smith Address: Berlin
Customer Smith Address: Berlin
Customer Smith Address: New York City
Customer Smith Address: New York City
Customer Smith Address: Berlin
© SAP AG 2008
Differences are temporary inconsistencies. They will always occur between running, connected systems.
The Root Cause Analysis of inconsistencies and the estimation of severity may lead to incorrect results if temporary inconsistencies are present.
Example. Customer master data for customer Smith is changed on the CRM system. It takes some time for the change to be replicated to the ECC system. During this time the data for customer Smith between the two system is inconsistent. But this only a temporary inconsistency, as it will be resolved once the IDoc with the new customer data is processed on the ECC system.
© SAP AG
SM300
8-10
Reasons for Data Inconsistencies: Why can they Occur User Level Data inconsistencies due to Real world operation ≠ system transaction Wrong Usage of transaction
Application Level Data inconsistencies within one system or between two systems due to Logical inconsistencies in application integration Errors in application programs Absence of error handling
Technology Level Data inconsistencies due to Absence of transactional correctness Data Loss
© SAP AG 2008
© SAP AG
SM300
8-11
Period End Closing
In co r in rec on t S e ale Ta s bl O e rg Cr ea te Sa les Or de rs
Domino Effect
© SAP AG 2008
Small inconsistencies may have a serious overall impact. For example a typing error while maintaining some assignment between a company code and a sales organization affects at first only a small customizing table, this incorrect information is handed down to thousands of sales orders and billing documents including dependent data like controlling and financing affecting the complete period end closing in the end.
Thus it is very important to consider potential side effects depending on the business processes using the corrupted data when assessing the severity of the issue.
© SAP AG
SM300
8-12
Lesson 2: Configuration of Data Consistency Monitoring
1. Motivation for Data Consistency Monitoring 2. Configuration of Data Consistency Monitoring
© SAP AG 2009
© SAP AG
SM300
8-13
Available Monitoring Objects for Data Consistency Monitoring SAP provides data consistency checks in the Business Process Monitoring Session for the following application areas: ERP Sales & Services
ERP Financials
SAP CRM
SAP APO
(Extended) Warehouse Management
All currently available Monitoring Objects can be found in the Media Library of BPM on the SAP Service Marketplace: http://service.sap.com/bpm Æ Media Library ÆCustomer Information Æ Business Process & Interface Monitoring – Part 2
© SAP AG 2008
© SAP AG
SM300
8-14
Data Consistency Cockpit Assign all Data Consistency Monitoring objects to a separate business process called “Data Consistency Cockpit”. The Data Monitoring Cockpit allows displaying the data consistency status within the entire solution landscape. Instead of accessing many different systems to check for data consistency the status of the entire solution is visible in one screen.
© SAP AG 2009
Monitoring data consistency for a certain data type usually is not just relevant for one business process, but for several business processes. Therefore the recommendation is: instead of assigning the data consistency monitoring objects to a business process, create a business process called “Data Consistency Cockpit” in SAP Solution Manager and assign the data consistency monitoring objects to that business process. This way all data inconsistencies can be centrally monitored.
© SAP AG
SM300
8-15
Example: Stock Comparison between IM and WM
CRM - CDP
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Run MRP
Procurement Process
Manufacturing Process
Create Outbound Delivery Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
Compare Stock Level between IM and WM
© SAP AG 2008
In case of a decentralized warehouse management system it is necessary to compare the stock of the warehouse management system with the stock of the ERP system.
© SAP AG
SM300
8-16
Initial Situation
Example: Stock Comparison IM – WM
Initial Situation
Monitoring relevant background information
Monitoring Requirements
Set up Data Consistency Run in Satellite Systems
Set up Monitoring Customizing in SAP Solution Manager
Definition of Error Handling Procedures CRM - CDP Create Sales Order
SAP ENTERPRISE PORTAL - EPP Create Sales Order
SAP ECC - TT5 Create Sales Order Check Availability
Compare Stock Level between IM and WM
Run MRP Procurement Process
Manufacturing Process
Create Outbound Delivery Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
© SAP AG 2009
© SAP AG
SM300
8-17
Initial Situation
CRM - CDP
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
3. Incorrect stock information
4. Incorrect stock information
Check Availability
1. Goods issue posted using an old transaction without data transfer
Run MRP
Procurement Process
Manufacturing Process
Create Outbound Delivery
2. Goods issue missing Æ billing not possible
Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
Goods Issue on the Warehouse system is posted using an old transaction. Because of that the goods issue is not replicated in the ERP system. Therefore Availability Check and MRP Run use the wrong stock information. 3
© SAP AG 2009
In this example process, the MRP run only considers the stock of material A in the ERP system. So if in the warehouse system there are 0 pieces of material A, but the ERP system shows 100 pieces of material A, the procurement process and the manufacturing process will not be triggered by the MRP run. Instead, the MRP will simply create an outbound delivery, which cannot be delivered, because in the warehouse system (and on the shelf in the warehouse) there is no material A.
© SAP AG
SM300
8-18
Monitoring Relevant Background Information
Example: Stock Comparison IM – WM
Initial Situation
Monitoring relevant background information
Monitoring Requirements
Set up Data Consistency Run in Satellite Systems
Set up Monitoring Customizing in SAP Solution Manager
Definition of Error Handling Procedures CRM - CDP Create Sales Order
SAP ENTERPRISE PORTAL - EPP Create Sales Order
SAP ECC - TT5 Create Sales Order Check Availability
Compare Stock Level between IM and WM
Run MRP Procurement Process
Manufacturing Process
Create Outbound Delivery Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
© SAP AG 2009
© SAP AG
SM300
8-19
Background Information
Warehouses to be considered for stock level comparison:
For the stock comparison between IM and WM it is important to know which plant/warehouse or which plant/storage location should be checked.
Within the business process “Order to Cash”, all materials are stored in warehouse 001 in plant 1000 (storage location 0088). So for the Order-toCash-process inconsistencies for all other warehouses are irrelevant.
Possible reasons for inconsistencies:
Temporary Inconsistencies
Example: Goods Issue has been posted on the warehouse system, but the corresponding IDoc has not yet been processed in the ERP system.
Real Inconsistencies
Example: Wrong transaction used to post Goods Issue on the warehouse system, thus the GI is not replicated to the ERP system
© SAP AG 2009
The combination plant/warehouse in WM identifies the plant/storage locations in IM.
Since one warehouse can include storage locations of more than one plant, it usually makes sense to specify the plant in addition to the warehouse.
© SAP AG
SM300
8-20
Monitoring Requirements
Example: Stock Comparison IM – WM
Initial Situation
Monitoring relevant background information
Monitoring Requirements
Set up Data Consistency Run in Satellite Systems
Set up Monitoring Customizing in SAP Solution Manager
Definition of Error Handling Procedures CRM - CDP Create Sales Order
SAP ENTERPRISE PORTAL - EPP Create Sales Order
SAP ECC - TT5 Create Sales Order Check Availability
Compare Stock Level between IM and WM
Run MRP Procurement Process
Manufacturing Process
Create Outbound Delivery Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
© SAP AG 2009
© SAP AG
SM300
8-21
Monitoring Requirements
In order not to be alerted for temporary inconsistencies a stock difference between the warehouse and the ERP system is only supposed to be considered as critical when this difference is more than 10% of the total stock of a material in the warehouse.
© SAP AG 2009
© SAP AG
SM300
8-22
Set up Data Consistency Run in Satellite Systems
Example: Stock Comparison IM – WM
Initial Situation
Monitoring relevant background information
Monitoring Requirements
Set up Data Consistency Run in Satellite Systems
Set up Monitoring Customizing in SAP Solution Manager
Definition of Error Handling Procedures CRM - CDP Create Sales Order
SAP ENTERPRISE PORTAL - EPP Create Sales Order
SAP ECC - TT5 Create Sales Order Check Availability
Compare Stock Level between IM and WM
Run MRP Procurement Process
Manufacturing Process
Create Outbound Delivery Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
© SAP AG 2009
© SAP AG
SM300
8-23
Data Consistency Check LX23 SAP provides transaction LX23 (report RLABGL00) as a tool to check the stock differences between Inventory Management and Warehouse Management More information about this tool is provided in Note 535043.
© SAP AG 2009
A stock comparison using Transaction LX23 displays stock differences between Inventory Management and Warehouse Management. This involves actual differences between the two inventory management levels which can be compared via an automatic physical inventory.
LX23 offers a detection mode as well as a correction mode (Checkbox 'Clear differences')
For stock differences that are recognized with Transaction LX23, the system always assumes that the WM stock leads (meaning the system assumes that the WM stock is the correct one). Correspondingly, if the tool is run in correction mode, the IM stock is adjusted to the WM stock.
The stock comparison report first reads all IM stocks and all special stocks. In the second step the WM stocks are read and summed up. If a difference then results when a comparison is carried out between the two internal tables, the individual stocks are listed and the difference is calculated.
© SAP AG
SM300
8-24
Set up Monitoring Customizing in SAP Solution Manager
Example: Stock Comparison IM – WM
Initial Situation
Monitoring relevant background information
Monitoring Requirements
Set up Data Consistency Run in Satellite Systems
Set up Monitoring Customizing in SAP Solution Manager
Definition of Error Handling Procedures CRM - CDP Create Sales Order
SAP ENTERPRISE PORTAL - EPP Create Sales Order
SAP ECC - TT5 Create Sales Order Check Availability
Compare Stock Level between IM and WM
Run MRP Procurement Process
Manufacturing Process
Create Outbound Delivery Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
© SAP AG 2009
© SAP AG
SM300
8-25
Select Business Process “Data Consistency Cockpit” as Relevant for Monitoring Access the Business Process Monitoring Setup session. Select the Business Process “Data Consistency Cockpit” for monitoring.
© SAP AG 2009
© SAP AG
SM300
8-26
Select Interface or Business Process Step as Relevant for Monitoring Some data consistency monitoring objects can be assigned to interfaces, others can only be assigned to business process steps. The context of the consistency check determines if the monitoring object is available just for business process steps or for interfaces as well. Select the interface you want to assign the LX23 check to. You don’t have to specify an interface technique. © SAP AG 2009
In our example LX23 checks consistency between and ERP system and a decentralized warehouse, so it makes most sense to assign the monitoring to the interface between the ERP system and the warehouse system.
© SAP AG
SM300
8-27
Select Monitoring Type
Select Monitoring Type “Application Monitor” for the interface and save.
© SAP AG 2009
Remember that for the application monitor the available monitoring functionalities is determined by the version of the ST-A/PI add-on installed on the satellite system.
© SAP AG
SM300
8-28
Assign Monitoring Object
In the sub-node, choose button “Load Application Monitors ”. After the reload use the value help to assign the Data Consistency Monitoring object.
© SAP AG 2009
Each monitoring functionality in the application monitor has an (unchangeable) internal flag that determines if the functionality can be assigned to an interface or not. Because of this internal flag the value help for the application monitor for an interface contains fewer entries than the value help for an application monitor assigned to a business process step.
© SAP AG
SM300
8-29
Provide Name for Monitoring Object
Provide a name for the monitoring object, flag “Select” and save.
© SAP AG 2009
© SAP AG
SM300
8-30
Select Alert Type (Key Figure)
In the sub-node for the monitoring object choose which key figures you want to use.
© SAP AG 2009
For data consistency checks you always have one alert that checks when the last data consistency check was run. In addition to that, you also have key figures evaluating the outcome of the data consistency check.
© SAP AG
SM300
8-31
Define Variant
To identify the correct IM-WM consistency check (the check for the relevant plant/warehouse) the correct variant used for report RLABGL00 has to be specified in table “Detail Information”.
© SAP AG 2009
© SAP AG
SM300
8-32
Define Monitoring Schedule and Execution
In the same node, switch to tab “Monitoring Schedule”. Here you define how often the data collection for this monitoring object should run. Save.
© SAP AG 2009
Since the actual “data collection” is executed by the data consistency check report in the satellite system, the transfer and the evaluation of the consistency check results can be executed directly (don’t flag “DC in Background”).
In our example the consistency check runs only once per week, so it makes sense to restrict the data collection for the transfer and evaluation of the results to a specific day per week.
© SAP AG
SM300
8-33
Define Alert Thresholds
Define the alert thresholds according to the monitoring requirements.
© SAP AG 2009
What is monitored in the Maximum Proportional Difference Quantity per Warehouse stock
Let’s assume LX23 shows the following results: Batch UM
IM Stock
WM Stock Difference quantity
A
PCE
6
2
4
B
PCE
7
2
5
C
PCE
-4
0
-4
The difference quantity for a material is divided by the WM quantity (LX23 always assumes that the WM quantity is the correct quantity). The absolute of this figure is the Proportional Difference Quantity per Warehouse stock. It tells us for this material what percentage of the stock in WM shows up as a difference. If the stock in WM for the material is 0, the percentage is set to 100%.
In the above example the proportions are Batch A: 200% Batch B: 250 % Batch C: 100%
The maximum of these proportions is measured in this alert.
© SAP AG
SM300
8-34
Set up Monitoring Customizing in SAP Solution Manager
Example: Stock Comparison IM – WM
Initial Situation
Monitoring relevant background information
Monitoring Requirements
Set up Data Consistency Run in Satellite Systems
Set up Monitoring Customizing in SAP Solution Manager
Definition of Error Handling Procedures CRM - CDP Create Sales Order
SAP ENTERPRISE PORTAL - EPP Create Sales Order
SAP ECC - TT5 Create Sales Order Check Availability
Compare Stock Level between IM and WM
Run MRP Procurement Process
Manufacturing Process
Create Outbound Delivery Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
© SAP AG 2009
© SAP AG
SM300
8-35
Error Handling Procedures
Run LX23 to detect inconsistencies
Filter temporary inconsistencies
Use LX23 to correct stock information
Correct dependent data like confirmations/rescheduling
© SAP AG 2009
For correcting stock inconsistencies between a decentralized warehouse management system and an SAP ERP system transaction LX23 can be used to detect inconsistencies.
Temporary inconsistencies should be excluded for example by making sure that all IDocs of message type SHP_OBDLV_CONFIRM_DECENTRAL, SHP_IBDLV_CONFIRM_DECENTRAL and MBGMCR are transferred from the decentralized warehouse management system to the central ERP system. On the central ERP system you must make sure that these IDocs are processed successfully before analyzing the stock differences.
When temporary inconsistencies have been filtered out you can use LX23 to correct the real stock inconsistencies. When doing this you should avoid stock changing postings in both systems.
As a last step dependent data should be corrected. If for example the MRP has created wrong results because of a wrong stock information in the ERP system you should run the MRP again to create the correct number of procurement elements.
© SAP AG
SM300
8-36
Exercise: Data Consistency Monitoring
Exercise: Data Consistency Monitoring
© SAP AG 2008
© SAP AG
SM300
8-37
Data Consistency Monitoring – Data Collector Architecture Monitored Satellite System
Solution Manager
Application
ST-SER: BPMon Setup Session
Schedule Consistency Report
Customize Collectors
Save Raw Data in Cluster Table/ Standard Tables
ST-SER: BPMon Monitoring Session
ST-A/PI: Data Collectors Evaluate Stored Data
Display Alerts / Pro-active Alerting
Trigger Alerts
Provide Further Information on Alerts
© SAP AG 2009
Data collection for data consistency objects is performed slightly different compared to other monitoring objects like Application Monitors:
Customizing is defined in Solution Manager in Business Process Monitoring Setup Session. However, the actual data collection is performed by the underlying consistency report itself. This means the BPMon only triggers the consistency report to run with the specified selection criteria at the times defined in the BPMon Monitoring Schedule.
The results of the run of the data consistency report are stored in cluster tables on the satellite system. The framework for BPMon data collectors (deposited in ST-A/PI) then evaluates this data, triggers the alerts and sends them back to Solution Manager, where alert handling is performed the same way as for other monitoring objects.
© SAP AG
SM300
8-38
Data Consistency: Handling Overview Process Design/Training Prevent
Reconciliation Strategy + BCC
Correct
Detect
End-to-End Monitoring
Analyze RCA + Business Continuity Concept © SAP AG 2009
Handling of inconsistencies can be divided into 4 phases:
•
1) Prevention of inconsistencies should be taken into account during the process design and training phase already. Transactional correctness needs to be ensured already during the program design phase. There should be sufficient end user training before Go-Live to enable your end-user to handle even unforeseen exceptions according to defined procedures. Preventing data inconsistencies should also be kept in mind in the business process design phase as well as during the design of customizing and system data change processes. Sufficient interface monitoring and corresponding error handling procedures are a prerequisite for data consistency.
•
2) By implementing and performing an inconsistency monitoring procedure inconsistencies can be detected at an early stage, so that further harm is prevented.
•
3+4) There should be a business continuity concept so that when an inconsistency is detected it can be decided quickly if and to what extent you can continue to work with the system during correction and investigation phase and how to revert back as fast as possible to a normal business operation.
Correcting data inconsistencies should include a root cause analysis, so that the root cause is eliminated whenever possible before the data inconsistency is corrected by an appropriate method, as well as defined correction procedures for each important, business critical object.
© SAP AG
SM300
8-39
© SAP AG
SM300
8-40
Exercises Unit:
Data Consistency Monitoring
Lesson:
Configuration of Data Consistency Monitoring
Exercise 19: Configure Data Consistency Monitoring
At the conclusion of this exercise, you will be able to: • Configure and Use Data Consistency Monitoring in SAP Solution Manager Stock inconsistencies between the ERP system in TT5, client 800 and the warehouse system in TT5, client 600 should monitored.
19-1 Configure the Stock Comparison Evaluation between the warehouse and the ERP system. 19-1-1 Access the Setup BPMon session of your solution. Select to monitor the interface for the Goods Issue replication in business process “Order to Cash”. Assign the WM-IM Stock comparison to the interface. Question: How does this contradict the Best Practice described in the training? Answer: _____________________________________________________________ Select to monitor the Max. Prop. Diff. Quantity / WM Stock and the age of the last LX23 run. Monitor the LX23 runs with variant SM300 and select to have the data collection to run every 5 minutes in dialog. Question: In real life 5 minutes is not a suitable data collection period for data consistency monitoring. Why? Answer: _____________________________________________________________ 19-1-2 Define thresholds for the alert: Max. Prop. Diff. Quantity / WM Stock: Age of last run:
10% for yellow, 20% for red 7 days for red
Generate and activate your monitoring.
© SAP AG
SM300
8-41
19-2 Use the active Data Consistency Monitoring. Identify alerts for data inconsistencies. 19-2-1 Question: What consistency alerts can you see? Answer: o Max. Prop. Diff. Quantity / WM Stock:________________________ o Age of last run:___________________________________________ 19-2-2 Access the SAP recommendations for stock inconsistencies. Question: What steps can you take to clear the observed inconsistencies? Answer: _____________________________________________________________
© SAP AG
SM300
8-42
Solutions Unit:
Data Consistency Management
Lesson:
Configuration of Data Consistency Monitoring
Exercise 19: Configure Data Consistency Monitoring
19-1 Configure the Stock Comparison Evaluation between the warehouse and the ERP system. 19-1-1 Access the Setup BPMon session of your solution. Open the tree to Business Processes Æ Order to Cash (Prod.) Æ Interface Monitoring. Select to monitor the interface for the Goods Issue replication (sending step “Post Goods Issue” and receiving step “Post Goods Issue”). Give the interface the name “WHS Æ ECC.” Save. In the sub-node WHS Æ ECC, select monitoring type “Application Monitor” and save. In sub-node Application Monitor choose button “Load App. Monitors TT5” to reload the application monitoring objects from TT5. Then use the value help in column Application Monitor. In the popup, select “WM-IM Stock comparison” and confirm the popup. Select your new entry as relevant for monitoring and save your entry. Answer: Normally the data consistency monitoring should be executed in a separate business process called “Data Consistency Cockpit”. In node WM-IM Stock comparison select to monitor the Max. Prop. Diff. Quantity / WM Stock and the Age of last X23 run by selecting these entries in tab “Key Figures”. Afterwards, go to tab “Detail Information”. Use the value help to select the used variant SM300. Now switch to tab “Monitoring Schedule”. Flag Mo, Tu, …, Su and enter a period of 5 minutes. Save your entries. Answer: During normal business process operation there are always short inconsistencies. Therefore, inconsistency checks should not run too often (more like once per week or once per month). If the inconsistency check runs only once per week, it does not make sense to have the data collection in SAP Solution Manager run every 5 minutes. 19-1-2 Go to the nodes for the alerts. For Max. Prop. Diff. Quantity/WM Stock. enter thresholds 10 for yellow and 20 for red. Save your entries. For Age of last X23 run enter 7 days as red threshold. Save your entries. Go to node “Generate Monitoring Customizing”. Select button “Generate + Activate”.
© SAP AG
SM300
8-43
19-2 Use the active Data Consistency Monitoring. Identify alerts for data inconsistencies. 19-2-1 Access the monitoring graphic in your solution via Operations Æ Solution Monitoring Æ Business Process Monitoring. In the monitoring graphic, select the process name. This opens the detailed process graphic. In the detailed process graphic, select the alert icon on the interface from the warehouse to the ECC system. This opens the detailed alert view. Observe the alerts as you can see them on your system. Answer: o Max. Prop. Diff. Quantity / WM Stock: No stored results of LX23 for variant SM300 have been found. o Age of last run: No stored results of LX23 for variant SM300 have been found. 19-2-2 Click on the alert for the Max. Prop. Diff. Quantity / WM Stock. This brings you to the correct node in the Business Process Monitoring session. There select button Recommendation at the very right above the Alert List. Answer: The recommendations refer you to SAP note 535043.
© SAP AG
SM300
8-44
Reporting
Course Overview Unit 1 Introduction to Business Process Monitoring Unit 2 Procedure Unit 3 Monitoring Configuration Unit 4 Using Business Process Monitoring
Unit 8
Data Consistency Monitoring
Unit 5 Cross-Application Monitoring
Unit 9
Reporting
Unit 6 Application Monitoring Unit 7 Interface Monitoring
Unit 10 Handover to Production Unit 11 Managing Jobs in SAP Solution Manager
© SAP AG 2008
© SAP AG
SM300
9-1
Business Process Monitoring: Unit Objectives
After completing this unit, you will be able to:
Set up and use BI Reporting
Set up and use Service Level Reporting
Understand Bi based Reporting infrastructure within SAP Solution Manager
© SAP AG 2009
© SAP AG
SM300
9-2
Initial Situation
To identify long term trends, IDES sets up reporting for the business processes they are currently monitoring. CRM - CDP
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
Check Availability
Run MRP
Procurement Process
Manufacturing Process
Create Outbound Delivery Create Billing Document
Post Goods Issue
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
© SAP AG 2009
© SAP AG
SM300
9-3
Lesson 1: BI Reporting
1. BI Reporting 2. Service Level Reporting
© SAP AG 2009
© SAP AG
SM300
9-4
Purpose of BI Reporting
Ad-hoc trend analysis for measured values of Business Process Monitoring objects
Graphical and tabular display
Flexibility to design own queries
Possibility to compare results
© SAP AG 2009
Possibility to compare results from different Monitoring Objects (e.g. such as: sales order backlog for plant 1000 compared to sales order backlog in plant 2000).
© SAP AG
SM300
9-5
Infrastructure for BI Reporting
SAP Solution Manager BPMon Engine
Alerts
BI
BI Interface
Job to load alerts for solution into transfer table
BI Content for BPMon BI Data Extraction
Transfer Table
BI Process Chain
BPMon Infocube
BI Reporting Ad-hoc Trend Analysis
© SAP AG 2008
Background jobs load the alert data from the BPMon Engine into the transfer table. For each solution a job has to be created, otherwise the alerts within the solution will be ignored for the transfer. The process chains of BI then load the data from the transfer table into the BI Info cube. There the alerts are the basis for the ad-hoc reporting in BI as well as for the Service Level Reporting in SAP Solution Manager,
SAP suggests to use the BI installed within the SAP NetWeaver underlying SAP Solution Manager. However, using external SAP BI systems is also possible.
© SAP AG
SM300
9-6
Procedure for Configuring BI Reporting
Ensure technical prerequisites
Activate BPMon objects from BI content
Configure alert data transfer for relevant solutions
A Setup-Guide for Trend Analysis Reporting in Business Process Monitoring will be available end of 2008 at http://service.sap.com/bpm
© SAP AG 2009
© SAP AG
SM300
9-7
Technical Prerequisites for BI based Reporting in SAP Solution Manager
Minimum Version of Installed Software Components ST
400 SP13
ST-SER
2007_1 SP6 BI CONT 703 SP6
BI client in SAP Solution Manager is set up so that BI processing can be used
© SAP AG 2009
Check if BI client in SAP Solution Manager is set up y Check if entry in table RSADMINA exists where field BWMANDT is filled y If an entry exists, BI components can already be (partly) installed, so it is very important to install BI in this client (MANDT), please do not change this, because inconsistencies can occur !! y If there is no entry for client, a BI client can be defined via report RS_MANDT_UNIQUE_SET
© SAP AG
SM300
9-8
BI Workbench: Transaction RSA1
Use transaction RSA1 (Data Warehousing Workbench) in the BI client to configure the BPMon relevant content of BI.
Define Source System
Activate Data Source Activate technical content
Activate BPMon Content Schedule Process Chain for data upload (e.g. 03:00 A.M. daily basis)
© SAP AG 2009
In order to work with BI, a Source System has to be defined in transaction RSA1 which is the assigned source for getting data into BI. In our case the Solution Manager (client) must be defined as source system, because in this system the BPMon alert data is stored.
The Data Source can be regarded as a connection link between BI and Source system (Solution Manager) for data transfer (e.g. picture of „plug in socket“), it describes which data is retrieved from which tables in the source system. The Data Source must be activated from status „D“ as delivered in BI content with BI content to status „A“ which means active.
The technical content is a collection of general BI related objects which are needed to work with BI, the technical content will be activated automatically when BI is used for first time, e.g. when transaction RSA1 is called for the first time.
All BPMon related BI objects are delivered with BI Content which can be regarded as a collection of ready-to-use objects delivered by SAP as a standard. So customer can decide, if he wants to use these objects and hence activate them from BI Content or if he wants to develop his own objects. All BPMon related BI objects must be activated so that they can be used.
The process chain is a chain of background jobs executed in a defined order. Each data load and processing task in BI is done by using background jobs. For the uploading of BPMon alert data the „BPM Data Delta“ chain which is delivered with BI content must be scheduled on a periodic basis in the administration part of transaction RSA1.
© SAP AG
SM300
9-9
Extraction Report in Solution Manager
In the client of SAP Solution Manager create and schedule on daily basis a variant of report “RDSWP_BI_BPM_EXT RACT” for each solution whose alerts should be available in BI Reporting.
The extraction report should run before the Process Chain.
© SAP AG 2009
Steps to do in Solution Manager client to add a solution for BI Reporting
A variant of report RDSWP_BI_BPM_EXTRACT for each solution whose alerts should be available in BI Reporting must be created.
Editing the parameters of transfer report “RDSWP_BI_BPM_EXTRACT” in the variant, use the value help to get the solution name and the data model key.
Select the Period for BI extraction and how the data in the Transfer Table should be handled (due to the planned scheduling time).
Afterwards, schedule a daily background job to run this report (variant) to transfer the BPMon alerts of the solution to BI (e.g. 02:30 A.M. on daily basis).
This job must run before the scheduled Process Chain BPM Data Delta to transfer the data at the same day.
© SAP AG
SM300
9-10
Access BI Trend Analysis via Work Center
Enter transaction /nSOLMAN_WORKCENTER. There, in tab ‘Business Process and Interface Monitoring’ select your solution. Afterwards, select area ‘Reports’ to display the selection screen for the dashboard.
© SAP AG 2009
© SAP AG
SM300
9-11
Access BI Trend Analysis via URL in Internet Browser Execute report ‘RS_TEMPLATE_MAINTAIN’ via transaction SE38, Enter web template 0SM_BPM_WT0001 and execute.
Select option ‘Preview in Browser’.
Your browser window is opened and after logging in to the BI client of your SAP Solution Manager system the URL for Trend Analysis dashboard is visible in Browser window. You can maintain the URL in Favorites folder of your Browser or within your user favorites in SAP Solution Manager.
© SAP AG 2009
The web template is a BI object which allows graphical display of your Trend Analysis.
General URL to call the web template of our Trend Analysis in BI:
http://:/SAP/BW/BEX?CMD=LDOC&TEMPLATE_ID=0SM_BPM_WT0001
The URL can also be added to your favorites in the SAP Easy Access Menu:
Go to the session manager (initial screen when you log on to TT4). There, include the URL in your favorites via Favorites Æ Add additional objects.
© SAP AG
SM300
9-12
Selection Screen of BI Trend Analysis
After accessing the BI Trend Analysis, the selection screen is coming up. Use selection criteria to filter for data to be displayed later in the dashboard. After execution of the selection, the BI Trend Analysis Board is displayed.
© SAP AG 2009
Selection criteria marked with “*” show mandatory entries.
© SAP AG
SM300
9-13
Dashboard in BI The dashboard provides you with a graphical display of the measured values as well as a tabular display of the measured values. Several key figures can be included in one graphic.
© SAP AG 2009
© SAP AG
SM300
9-14
Exercise: Reporting in BI
Exercise: Reporting in BI
© SAP AG 2008
© SAP AG
SM300
9-15
Lesson 2: Service Level Reporting
1. BI Reporting 2. Service Level Reporting
© SAP AG 2009
© SAP AG
SM300
9-16
Purpose of Service Level Reporting
Regular and automatic creation of trend analysis reports
Graphical and tabular display
Possibilities to send reports via email
© SAP AG 2009
© SAP AG
SM300
9-17
Functional Scope of Service Level Reporting
Service Level Reporting based on BI Reporting
Monthly or weekly automated reports in SLR
Reporting time ranges individually definable per monitoring object
Last Week
Last Month
Last 6 Months
Aggregation types of measured values
Maximum (MAX)
Sum (SUM)
Average (AVG)
Individual graphical and tabular display for reporting of each monitoring objects
© SAP AG 2009
Real trend analysis based on BPMon is based on BI functionality. Reporting functionalities are available in BI directly and in the Service Level Reporting part of SAP Solution Manager.
© SAP AG
SM300
9-18
Technical Infrastructure for Service Level Reporting
SAP Solution Manager BPMon Engine
BI
BI Interface Job to load alerts for solution into transfer table
Alerts
BI Content for BPMon BI Data Extraction BI Process Chain
Transfer Table
BPMon Infocube
Data Retrieval from BI
BI Reporting
SL Report Content
Ad-hoc Trend Analysis
SLR Framework Report Processing Service Level Report
Job for session processing
© SAP AG 2008
Service Level Reporting requires current Service Definitions in transaction SDCCN.
© SAP AG
SM300
9-19
Configuration of Service Level Reporting
Access your solution to set up Service Level Reporting. The corresponding session is accessible under Operations Setup Æ Solution Monitoring Æ Service Level Reporting Æ Setup Service Level Reporting
© SAP AG 2009
© SAP AG
SM300
9-20
Define Title for Service Level Report
Enter a name for the service level report. This uniquely identifies your report. You can access the settings of an existing report via the value help.
© SAP AG 2009
© SAP AG
SM300
9-21
General Settings for Service Level Report
Define when the Service Level Report is supposed to be processed. You can define weekly reports or monthly reports.
© SAP AG 2009
© SAP AG
SM300
9-22
SL Reporting Based on BPMonitoring
Choose the business process you want to include in the reporting and specify the RFC destination to the BI system that is used for ad-hoc reporting for the BPMon alerts.
© SAP AG 2009
SL Reporting based on BPMon does not require EWA data to be available in the solution, since it relies completely on alerts created within BPMon.
If the BI is installed on the SAP Solution Manager system, the RFC destination is NONE.
© SAP AG
SM300
9-23
Alert Statistics Service Level Reporting based on the alert statistics allows you to report how many alerts have occurred and how many alerts were solved. Choose which monitoring types you want to include in the Service Level Report and define the aggregation level for the reporting (number of alerts per day or per week).
;
© SAP AG 2009
The reporting over the alert statistics does not use the alert storage in BI. Therefore BI reporting does not have to be configured for the reporting over the alert statistics.
© SAP AG
SM300
9-24
Alert Statistics in Service Level Report
Provides Information about
how many alerts occurred per aggregation level (e.g. per day or per week) how many of those alerts were solved
© SAP AG 2009
© SAP AG
SM300
9-25
Configure BI based Service Level Reporting
For each alert choose the reporting time frame and the aggregation type.
© SAP AG 2009
Aggregation Types are: y Maximum y Sum y Average
You can choose to report over the last week, the last month or the last 6 months within the same report.
All alert types for all configured monitoring objects are displayed for selection here, even those that are not configured at the moment.
© SAP AG
SM300
9-26
Service Level Reporting Based on BI
Provides Information about:
Graphical display of trend for measured values per monitoring object Tabular display of trend for measured values per monitoring object
© SAP AG 2009
© SAP AG
SM300
9-27
Access the Service Level Report
Access the Service Level Report from within the Operations part of SAP Solution Manager.
© SAP AG 2009
The processing of the service level report takes place via background job “SM:EXEC SERVICES”. This job is scheduled to run once per day during the initial configuration of SAP Solution Manager.
You can trigger the immediate processing of a service level report if the hour-glass icon is displayed for the Service Level report. This will schedule a background job “SM:EXEC SERVICE ” to be executed immediately.
The successful execution of the background job requires current service definitions to be available in transaction SDCCN. If the execution of this background job fails, check SAP Notes 658764 “Dump in SM:EXEC SERVICES/Service definition refresh” and 727998 “Complete Replacement of Service Definitions for SDCC/SDCCN”.
© SAP AG
SM300
9-28
Send Service Level Reports via E-Mail
You can decide to automatically send the Service Level Report to the interested parties within your Customer Organization. Choose Edit Æ Automatic E-Mail Transmission. In the pop-up choose to create an E-Mail recipient. In the subsequent popup choose the report type and provide the address of the E-Mail recipient. © SAP AG 2009
For Service Level Reports you can assign E-Mail addresses to system IDs, in the maintenance view of the table DSWP_SYS_EMAIL. Service Level Reports are then only sent to the E-Mail addresses which are assigned to the systems.
In addition, SAP Solution Manager contains the inactive BAdI DSWP_EMAILFILTER to send reports automatically by e-mail in the Operations part of Solution Manager. Via this BAdI you can y Change the subject text of the e-mail y Filter for e-mail addresses by criteria.
See the SAP IMG for details (SAP Solution Manager Implementation Guide Æ SAP Solution Manager Æ Configuration Æ Scenario-Specific Settings Æ Solution Monitoring /Reporting Æ Sending Service Reports by Internet E-Mail -> E-Mail Filter (Maintenance).
© SAP AG
SM300
9-29
Exercise: Service Level Reporting
Exercise: Service Level Reporting
© SAP AG 2008
© SAP AG
SM300
9-30
Exercises Unit:
Reporting
Lesson:
BI Reporting
Exercise 20: Reporting in BI At the conclusion of this exercise, you will be able to: • Include your solution in the BI reporting based on BPMon alerts
For the throughput and backlog indicators in addition to the alerts IDES also wants to execute trend analysis for business process “Order to Cash”,
20-1 Check the prerequisites for BI reporting. 20-1-1 Include the URL for the BI in the favorites of your dialog user. Question: How do find out which URL can be used to access the BI Trend Analysis? At the logon popup, enter user “sapsupport” with passwort “support”. Why can’t you use your SM300-## user? Answer: _____________________________________________________________ 20-1-2 Make sure that BPMon alerts for your solution are reported into the BI. Question: What time should you use for the execution of the relevant background job? Answer: ____________________________________________________________
© SAP AG
SM300
9-31
20-2 Use BI Reporting 20-2-1 Execute a trend analysis for the alerts in your solution. Question: What can you see? Answer: _____________________________________________________________ 20-2-2 Execute a trend analysis for solution “SM300 Master Solution”. Compare the number of open sales orders to the number of open sales order items. Question: What can you see? Answer: _____________________________________________________________ 20-2-3 Execute a trend analysis for solution “SM300 Master Solution” from Solution Manager Workcenter. Question: How can you access the BI Trend Analysis via the Workcenter? Answer: _____________________________________________________________
© SAP AG
SM300
9-32
Solutions Unit:
Reporting
Lesson:
BI Reporting
Exercise 20: Reporting in BI
20-1 Check the prerequisites for BI reporting. 20-1-1 Answer: In Solution Manager system, please execute report “RS_TEMPLATE_MAINTAIN” in transaction SE38. Then enter “0SM_BPM_WT0001” as name for the webtemplate and execute it. Afterwards select button “Preview in Browser”. A window of your Browser is opening, showing the logon screen, please login with provide user. Now you can retrieve the URL from the browser window. The general form of the URL is http://:/SAP/BW/BEX?CMD=LDOC&TEMPLATE_ID=0S M_BPM_WT0001. The actual server and port can be taken out of the Browser window. Go to the session manager (initial screen when you log on to TT4). There, include the URL in your favorites via Favorites Æ Add additional objects. The BI dashboard is available only in the client in which the BI is configured. In this case, this is client 001. User sapsupport is a user in client 001, whilst SM300-## is a user in client 200. 20-1-2 Call transaction /nSE38. Enter report name RDSWP_BI_BPM_EXTRACT. Flag “Variant” and choose “Display”. In the next screen, create a new variant by entering your solution and the data model key via the value help. Name the variant SM300-## and save. Answer: Call transaction SM37. Check when the job for the transfer of the SM300 Master Solution is currently scheduled (using report RDSWP_BI_BPM_EXTRACT). Schedule your report/variant to run 5 minutes before this job. For this, call transaction /nSM36. There, schedule a background job called “BI_BPMon_Data_Transfer_daily_##” with report RDSWP_BI_BPM_EXTRACT and variant SM300-## at the identified time.
© SAP AG
SM300
9-33
20-2 Use BI Reporting 20-2-1 In the dashboard open the value help for solution name. Answer: Your solution is not yet available in the value help. The transfer job and the process chain have to run at least once before your solution will become available in BI. 20-2-2 In the dashboard open the value help for solution name. Select “SM300 Master Solution”. For the calendar weeks, select all available weeks. Choose “Execute”. In the selection criteria select business process “Order to Cash” and Monitoring Object “Sales Order Backlog”. Answer: You can compare the trend for both alerts within one graphic. 20-2-3 The BI Trend Analysis can be directly via Solution Manager Workcenter. Answer: Please enter transaction SOLMAN_WORKCENTER. Then choose tab “Business Process and Interface Monitoring” and select solution “SM300 Master Solution” in the window. Finally, press button “Reports”.
© SAP AG
SM300
9-34
Exercises Unit:
Reporting
Lesson:
Service Level Reporting
Exercise 21: Service Level Reporting At the conclusion of this exercise, you will be able to: • Set up Service Level Reporting
To report to business, IDES want to set up a weekly Service Level Report based on the BPMon data.
21-1 Set up Service Level Reporting for Business Process “Order to Cash” in your solution. 21-1-1 Access the Setup SLR session. 21-1-2 Configure Service Level Reporting to be executed every Tuesday for the Total Response Time of Transaction VA01 in business process “Order to Cash”, business process step “Create Sales Order (TT5)”. 21-2 Use Service Level Reporting for Business Process “Order to Cash”. 21-2-1 Access the Service Level Report in solution “SM300 Master Solution”. Question: Why does it not make sense to access the Service Level Report in your solution? Answer: _____________________________________________________________ 21-2-2 Compare the number of open sales orders to the number of open sales order items. Question: What can you see? Answer: _____________________________________________________________
© SAP AG
SM300
9-35
© SAP AG
SM300
9-36
Solutions Unit:
Reporting
Lesson:
Service Level Reporting
Exercise 21: Service Level Reporting
21-1 Set up Service Level Reporting for Business Process “Order to Cash”. 21-1-1 Access the Setup SLR session via Operations Setup Æ Solution Monitoring Æ Service Level Reporting Æ Setup Service Level Reporting. 21-1-2 Go to node “Specify SL Report”. There, in tab “SLReport” enter the report name “BPMon based Reporting” (do NOT use the value help, type in the report name directly) and save. Go to sub-node “General Settings for SL Report TBI Reporting”. There, go to tab “Scheduling of SL Report”. Enter period type “Weekly”, Week Day “Tuesday” and Period “1”. Save. Go to node “SL Reporting based on BPMonitoring”. In tab “Productive Business Processes”, select business process “Order to Cash”. In tab “BI RFC Destination” choose destination “NONE”. Save. Go to sub-node “Order to Cash” Æ “Trend Analysis”. In tab “Monitoring Objects per Business Process” select the Total response time alerts to be included in the reporting with Aggregation “AVG”. Save. 21-2 Use Service Level Reporting for Business Process “Order to Cash”. 21-2-1 Access the Service Level Report in solution “SM300 Master Solution”. For this, switch to SM300 Master Solution, and there choose Operations Æ Solution Monitoring Æ Service Level Reporting Æ Service Level Report – BPMon Based Reporting. Answer: The Service Level Report always uses the alerts of the last calendar week. Since your solution did not yet exist in the last calendar week, there are no alerts there from last week and your Service Level Report would be empty. You would have to wait until next week to see real values in your Service Level Report. 21-2-2 Scroll down to the graphic for the open sales orders and the open sales order items. Answer: You cannot compare the two alerts in one graphic. Each alert has its own graphic.
© SAP AG
SM300
9-37
© SAP AG
SM300
9-38
Handover to Production
Course Overview Unit 1 Introduction to Business Process Monitoring Unit 2 Procedure Unit 3 Monitoring Configuration Unit 4 Using Business Process Monitoring
Unit 8
Data Consistency Monitoring
Unit 5 Cross-Application Monitoring
Unit 9
Reporting
Unit 6 Application Monitoring Unit 7 Interface Monitoring
Unit 10 Handover to Production Unit 11 Managing Jobs in SAP Solution Manager
© SAP AG 2008
© SAP AG
SM300
10-1
Business Process Monitoring: Unit Objectives
After completing this unit, you will know:
how a Solution Manager test landscape should look like
how to switch a test Solution Manager landscape into a productive Landscape, with and without switching the SAP Solution Manager system
what to do and to consider when implementing new Support Package into your SAP Solution Manager landscape.
© SAP AG 2009
© SAP AG
SM300
10-2
Initial Situation IDES wants to set up a test landscape for BPMon so that monitoring relevant changes to the landscape can be tested before the are implemented into production. When the Process “Order to cash” goes live, IDES has to switch the monitoring configuration to the PRD SAP Solution Manager and the PRD satellite systems. IDES QAS SAP Solution Manager System
IDES PRD SAP Solution Manager System
Satellite A
Satellite A
Satellite B
Satellite C
Satellite D
Satellite E
© SAP AG 2009
© SAP AG
SM300
10-3
Lesson 1: Test Landscape for Business Process Monitoring
1. Test Landscape for Business Process Monitoring 2. Switching SAP Solution Manager Systems 3. Switching Satellite Systems without Switching SAP Solution Manager Systems 4. Support Package Implementation
© SAP AG 2009
© SAP AG
SM300
10-4
Test Landscape for BPMon
QAS SAP Solution Manager System
PRD SAP Solution Manager System
DEV Satellite
QAS Satellite
Test Landscape that contains sample configurations of all important used monitoring objects.
PRD Satellite
Productive Monitoring Landscape
Monitoring not active, only activated on demand
© SAP AG 2009
Initial Situation: Company IDES now wants to set up a test landscape for their Business Process Monitoring configuration in SAP Solution Manager.
Solution: Install one QAS SAP Solution Manager and connect at least 1 satellite system to it. For initial testing purposes this could be only a sandbox systems, but before going productive it is highly recommended to assign a QAS system or any other system with a quite recent copy of productive data in order to also detect issues with long runtimes of performance-critical data collectors, such as
Backlog and throughput monitors for applications (e.g. Sales documents)
Dialog Performance Monitor (based on Application Monitor framework)
Interface Monitors (mainly the IDoc Monitor and qRFC monitor, both based on Application Monitor framework)
Monitoring in this SAP Solution Manager does not always have to be active.
© SAP AG
SM300
10-5
Required Monitoring Configuration for the Test Landscape
Business process defined
satellite system exists in system landscape
logical component exists with satellite system assigned
BPMon test solution created
logical components assigned to solution
business scenario, business process and process steps created
Monitoring configuration for the most important monitoring functionalities you are using
© SAP AG 2009
© SAP AG
SM300
10-6
Lesson 2: Switching SAP Solution Manager Systems
1. Test Landscape for Business Process Monitoring 2. Switching SAP Solution Manager Systems 3. Switching Satellite Systems without Switching SAP Solution Manager Systems 4. Support Package Implementation
© SAP AG 2009
© SAP AG
SM300
10-7
Initial Situation: Switching SAP Solution Manager Systems QAS SAP Solution Manager System
PRD SAP Solution Manager System
DEV Satellite
QAS Satellite
PRD Satellite
When configuring a prototype for Business Process Monitoring, this mostly happens in the QAS SAP Solution Manager System. So after the prototype for monitoring has successfully been tested, the monitoring configuration now has to be transferred to the productive SAP Solution Manager system. © SAP AG 2009
Switching SAP Solution Manager systems usually also means partly switching satellite system, as usually the system landscape in the QAS SAP Solution Manager system differs from that in the PRD system.
© SAP AG
SM300
10-8
Transaction /nSOLUTION_TRANSFER QAS SAP Solution Manager System
upload solution.zip
download solution.zip
PRD SAP Solution Manager System
Source
Target
For transferring solutions between SAP Solution Manager you have to
Download the solution from the source SAP Solution Manager system onto your PC using transaction /nsolution_transfer Create a target solution on your target SAP Solution Manager system
Upload the solution to your target SAP Solution Manager system from your PC using transaction /nsolution_transfer Ensure technical prerequisites for target systems.
Adjust monitoring configuration and generate and active monitoring. Adjust reporting configuration. © SAP AG 2009
You can transfer solutions between SAP Solution Manager systems with transaction /nsolution_transfer. This transaction works as follows:
You log onto your source SAP Solution Manager system and call transaction /nsolution_transfer there. You download the solution in a zip-file onto your local hard drive. You then log on to your target SAP Solution Manager system and call transaction /nsolution_transfer. Now you upload the zip-file containing your solution to your target SAP Solution Manager system.
When using the transaction, you can transfer your entire solution from one system to the other system. There is no way to transfer only parts of the solution (like only certain business processes). There is also no way to synchronize solutions on two different SAP Solution Manager systems. You can only copy the information from one system to the other.
When transferring the solution, you can decide to use different logical components (thus different satellite systems) on the target SAP Solution Manager system than on the source system, so you can switch satellite systems at the same time.
You cannot change the leading role of the solution during the transfer with /nsolution_transfer.
© SAP AG
SM300
10-9
Transaction /nSOLUTION_TRANSFER
The export and import areas of transaction SOLUTION_TRANSFER are available in separate tabs. You use these tabs from top-to-bottom.
© SAP AG 2009
The transaction uses a web dynpro. The respective service has to be activated in transaction /nSICF before this transaction can be used. The respective service can be found under the path: y sap/bc/webdynpro/sap/dswp_su_solution_transfer_app
Since the transaction has to be used on both the source and the target SAP Solution Manager system for the complete transfer, this service has to be activated on both the source and the target SAP Solution Manager system.
© SAP AG
SM300
10-10
Solution Data that is Transferred
Solution Software Components
Systems
With transaction /nsolution_transfer all data that is stored in the data model is transferred. This includes
Solution specific Master Data
Master Data
Transactional Data
Systems Software Business Processes Configuration
Projects Issues Alerts Services Messages
Business Processes, including flow and technical details Support Contacts Business Process Monitoring Configuration
Scenarios
© SAP AG 2008
System Monitoring alerts are not stored in the data model and are therefore not transferred.
© SAP AG
SM300
10-11
Downloading the Solution QAS SAP Solution Manager System
download solution.zip
Source
Procedure:
Go the Export-tab of transaction SOLUTION_TRANSFER. Select source solution via value help. The system landscape of the solution is filled automatically
Choose whether to transfer
Documents
Issues, Top Issues and Expertise on Demand Requests
Service Plans
Choose “Export”. Save file “solution.zip” to your hard drive.
© SAP AG 2009
© SAP AG
SM300
10-12
Export Tab
© SAP AG 2009
Procedure: y Go the Export-tab of transaction SOLUTION_TRANSFER. y Select source solution via value help. The system landscape of the solution is filled automatically y Choose whether to transfer - Documents - Issues, Top Issues and Expertise on Demand Requests - Service Plans y Choose “Export”. y Save file “solution.zip” to your hard drive.
© SAP AG
SM300
10-13
Content of File SOLUTION.ZIP
File SOLUTION.ZIP contains 3 XML files:
ATTRIBUTE_*.XML
SOLUTION_*.XML
containing the actual data from the data model z
business process definition
z
monitoring configuration
STEERING_*.XML
logical components with systems z
product information
© SAP AG 2009
© SAP AG
SM300
10-14
Create Target Solution
© SAP AG 2009
© SAP AG
SM300
10-15
Uploading the Solution
upload solution.zip
PRD SAP Solution Manager System
Target
Procedure:
Go to the Import-Tab of transaction SOLUTION_TRANSFER
Use the “Browse” button to define the path to access the source solution on your hard drive. Afterwards choose “Upload”
Use the value help to define the target solution. This has to be a solution that already exists in your target SAP Solution Manager system.
Assign the correct logical components.
Decide how to transfer the solution to SAP. Define if Issues, Top Issues and Expertise on Demand Requests and Service Plans should be uploaded as well
Choose “Import”
© SAP AG 2009
© SAP AG
SM300
10-16
Import Tab
© SAP AG 2009
Procedure: y Go to the Import-Tab of transaction SOLUTION_TRANSFER y Use the “Browse” button to define the path to access the source solution on your hard drive. Afterwards choose “Upload” y Use the value help to define the target solution. This has to be a solution that already exists in your target SAP Solution Manager system. y Assign the correct logical components. y Decide how to transfer the solution to SAP. Choose ‘Copy’ not ‘Replace’ (see detailed explanation in paragraph ‘Import Options’ below) y Define if Issues, Top Issues and Expertise on Demand Requests and Service Plans should be uploaded as well y Choose “Import”
Import Options
This option is relevant for solutions with data (Top Issues) which you have already sent to SAP.
Replace: The target solution replaces the source solution. This option can only be selected once per source. The Replace option ensures that SAP, recognizes the replacement after resending the solution and its data (Top Issues). After importing and testing your solution data in the target system, you should no longer use the solution in the source system.
CopyThe source solution with data is the template for the target solution. If you send the target solution with your contents to SAP again, it is handled as a new solution Check whether it is advisable to put the data in Scope (Top Issues, Issues, Expertise on Demand Requests and Service Plans) in your new target solution.
© SAP AG
SM300
10-17
Manual Steps after Uploading Solution
QAS SAP Solution Manager System
PRD SAP Solution Manager System
DEV Satellite
QAS Satellite
PRD Satellite
What can have changed on the Productive SAP Solution Manager System
Technical Settings on PRD SAP Solution Manager system BPMon relevant configuration containing system information from SAP Solution Manager
Technical settings on new satellite systems BPMon relevant configuration containing system information from old satellite system Adjust settings for trend analysis © SAP AG 2009
© SAP AG
SM300
10-18
Ensure Technical Prerequisites for Target Systems
Target SAP Solution Manager System
Target Satellite Systems
Installed Software Components
Installed Software Components
RFC destinations to satellite system (READ and LOGIN) and are assign in RZ21 Local RFC destination exist
Service Desk and SAP Connect configured BI reporting configured
© SAP AG 2008
© SAP AG
SM300
10-19
Adjust Monitoring Configuration
In Solution Directory set the status of business scenarios and business processes to ‘Production’. In the BPMon Setup session, adjust the monitoring configuration of the following monitoring types:
Dialog Performance Monitoring (CCMS)
Dialog Performance Monitoring (Application Monitor)
Other CCMS
IDoc Monitoring
qRFC Monitoring
© SAP AG 2009
All monitoring types that contain system information of the satellite system have to be adjusted.
This can be y server information (dialog performance monitoring) y other information (like SID in the MTE name for Other CCMS) y communication parties in IDoc monitoring y RFC destination and Queue Group in qRFC monitoring
For monitoring objects that are monitored via the CCMS of the satellite system, you have to ensure that these monitoring objects are available in the CCMS of the satellite system. This might mean that you have to reconfigure the monitoring on the satellite system or that you have to transport the monitoring object from one satellite system to another.
© SAP AG
SM300
10-20
Generate and Activate
Generate the new monitoring customizing
Activate monitoring customizing
© SAP AG 2009
© SAP AG
SM300
10-21
Adjust Reporting Configuration
Define variant for ABAP report RDSWP_BI_BPM_EXTRACT for the target solution
Schedule daily background job to execute this report and variant
© SAP AG 2009
© SAP AG
SM300
10-22
Lesson 3: Switching Satellite Systems without Switching SAP Solution Manager Systems
1. Test Landscape for Business Process Monitoring 2. Switching SAP Solution Manager Systems 3. Switching Satellite Systems without Switching SAP Solution Manager Systems 4. Support Package Implementation
© SAP AG 2009
© SAP AG
SM300
10-23
Initial Situation
PRD SAP Solution Manager System
QAS Satellite
Company IDES now wants to switch the monitoring from one satellite system to another without changing the SAP Solution Manager system.
PRD Satellite
© SAP AG 2009
© SAP AG
SM300
10-24
Leading Role of a Solution BPMon is executed on the systems in the leading role of the solution.
PRD SAP Solution Manager System
You cannot change the leading role of a solution after any kind of customizing activity in Solution Directory !
PRD Portal
PRD CRM
PRD ERP
QAS Portal
QAS CRM
QAS ERP
If you want to switch satellite systems for BPMon you have to determine if this involves a change in the system role as well.
Leading role of solution DEV Portal
DEV CRM
DEV ERP
Logical Component Z_PORTAL
Logical Component Z_CRM
Logical Component Z_ERP
© SAP AG 2009
This also means that you cannot execute BPMon on a QAS system and a PRD system within the same solution. You need separate solutions to monitor your QAS systems and your PRD systems via BPMon.
Note: System monitoring is also possible for systems that are not in the leading role of the solution.
© SAP AG
SM300
10-25
Procedure for switching Satellite Systems
Procedure
Create target solution
Define leading role for target solution (only if system role change is required)
Create business scenario
Copy business process from source solution
Replace Logical Components (if required)
Ensure the Correct System Assignment for the Business Process Steps
Ensure technical prerequisites
Adjust monitoring configuration
Generate and Activate
© SAP AG 2009
Note: Changing the leading role for the target solution cannot be done after any other customizing activity for this solution in Solution Directory.
© SAP AG
SM300
10-26
Create Target Solution
© SAP AG 2009
If there is no switch in the system role involved, you do not have to create a new solution.
© SAP AG
SM300
10-27
Define Leading Role for Target Solution
© SAP AG 2009
While no logical components are assigned to the solution, you can change the leading role of the solution. Changes there have to be saved immediately.
Note: Changing the leading role for the target solution cannot be done after any other customizing activity for this solution in Solution Directory.
© SAP AG
SM300
10-28
Create Business Scenario
Create a business scenario and save.
Then go to node “Business Processes”, access tab “Structure” and change the source to “Solution”. Now use the value help to copy the business process from the source solution. Set the status of business scenario to ‘Production’.
© SAP AG 2009
You can also use the value help on business scenario level if you want to copy not just one business process but several. In that case, you have to change the source to “Solution” in node “Business Scenarios” and use the value help there.
Set the status of business scenario to ‘Production’.
© SAP AG
SM300
10-29
Copy Business Process from Source Solution In the popup navigate to the business process you want to copy and choose “Copy”. If you have not assigned all necessary logical components to your target solution, SAP Solution Manager assigns the missing logical components with the copying of the business process.
© SAP AG 2009
By clicking on the business process name in the pop-up you can view the graphic for the process you are about to copy.
© SAP AG
SM300
10-30
Replace Logical Component 1) Mark a Logical Component 2) Select button ‚Logical Components‘
The changed Logical Component will be copied automatically to the related Business Process Steps.
3) Select the new Logical Component.
4) Confirm. © SAP AG 2009
© SAP AG
SM300
10-31
Ensure the Correct System Assignment for the Business Process Steps After copying the business process, go into tab “Structure” for node “”. If necessary, assign the business process steps to the correct logical components. If necessary, go back to node “” and delete the unnecessary logical components from the solution. Set the status of business process to ‘Production’.
© SAP AG 2008
When the business process is copied, the initial status is “Planned”. You have to set this status to “Production” so that you can activate BPMon for the business process. You can do so in node “Business Processes” in tab “Structure”.
© SAP AG
SM300
10-32
Ensure Technical Prerequisites
SAP Solution Manager System
Target Satellite Systems Installed Software Components
RFC destinations to new satellite system (READ and LOGIN) and assignment in RZ21
© SAP AG 2008
© SAP AG
SM300
10-33
Adjust Monitoring Configuration
In Solution Directory set the status of business scenarios and business processes to ‘Production’. In the BPMon Setup session, adjust the monitoring configuration of the following monitoring types:
Dialog Performance Monitoring (CCMS)
Dialog Performance Monitoring (Application Monitor)
Other CCMS
IDoc Monitoring
qRFC Monitoring
© SAP AG 2009
All monitoring types that contain system information of the satellite system have to be adjusted.
This can be y server information (dialog performance monitoring) y other information (like SID in the MTE name for Other CCMS) y communication parties in IDoc monitoring y RFC destination and Queue Group in qRFC monitoring
For monitoring objects that are monitored via the CCMS of the satellite system, you have to ensure that these monitoring objects are available in the CCMS of the satellite system. This might mean that you have to reconfigure the monitoring on the satellite system or that you have to transport the monitoring object from one satellite system to another.
© SAP AG
SM300
10-34
Generate and Activate
Generate the new monitoring customizing
Activate monitoring customizing
© SAP AG 2009
© SAP AG
SM300
10-35
Adjust Reporting Configuration
Define variant for ABAP report RDSWP_BI_BPM_EXTRACT for the target solution
Schedule daily background job to execute this report and variant
© SAP AG 2009
© SAP AG
SM300
10-36
Lesson 4: Support Package Implementation
1. Test Landscape for Business Process Monitoring 2. Switching SAP Solution Manager Systems 3. Switching Satellite Systems without Switching SAP Solution Manager Systems 4. Support Package Implementation
© SAP AG 2009
© SAP AG
SM300
10-37
Procedures to go through for Support Package Implementation
Deactivate Monitoring in Test landscape
Implement support package in Test Landscape
Generate and Activate Monitoring in Test Landscape
Test for functional correctness
Implement support package in productive landscape
© SAP AG 2009
© SAP AG
SM300
10-38
Considerations for Release Management There are infrastructure dependencies between SAP Solution Manager and satellite systems SAP Solution Manager
Satellite
ST ST-PI
ST-SER
ST-A/PI
ST-A/PI
Newest functionalities contained in the add-ons in the satellite system, so regular update for these add-ons should be included in release management concept. Release of add-ons on satellite system and of add-ons on SAP Solution Manager system have to be able to work together. © SAP AG 2009
ST-A/PI on satellite system: y Until release 01I: - ST-SER on SAP Solution Manager has to be 2006_2 or lower. - ST-A/PI on SAP Solution Manager has to be 01I or lower. y As of release 01J: - ST-SER on SAP Solution Manager has to be 2007_1 or higher. - ST-A/PI on SAP Solution Manager has to be 01J or higher. y Release 01K: - ST-SER on SAP Solution Manager has to be 2008_1. - ST-A/PI on SAP Solution Manager has to be 01K. y As of release 01L: - ST-SER on SAP Solution Manager has to be 2008_2 or higher. - ST-A/PI on SAP Solution Manager has to be 01L or higher.
© SAP AG
SM300
10-39
© SAP AG
SM300
10-40
Managing Jobs in SAP Solution Manager
Course Overview Unit 1 Introduction to Business Process Monitoring Unit 2 Procedure Unit 3 Monitoring Configuration Unit 4 Using Business Process Monitoring
Unit 8
Data Consistency Monitoring
Unit 5 Cross-Application Monitoring
Unit 9
Reporting
Unit 6 Application Monitoring Unit 7 Interface Monitoring
Unit 10 Handover to Production Unit 11 Managing Jobs in SAP Solution Manager
© SAP AG 2008
© SAP AG
SM300
11-1
Business Process Monitoring: Unit Objectives
After completing this unit, you will be able to:
Understand the Job Request and Job Documentation Process in SAP Solution Manager
Explain the integration of Job Documentation in BPMon
See integration of external Job Scheduling with SAP CPS in BPMon
© SAP AG 2009
© SAP AG
SM300
11-2
Lesson 1: Job Management Process in SAP Solution Manager
1. 2. 3. 4. 5.
Job Management Process in SAP Solution Manager Job Request in SAP Solution Manager Job Documentation in SAP Solution Manager Integration of Job Documentation into Business Process Monitoring Integration of Job Documentation and BPMon with SAP CPS
© SAP AG 2009
© SAP AG
SM300
11-3
Initial Situation: Managing Jobs in SAP Solution Manager
Company IDES at the same time plans to start using the job request process and the job documentation in SAP Solution Manager for their jobs. These jobs are also monitored as part of BPMon.
© SAP AG 2009
© SAP AG
SM300
11-4
Business Process ”Order to Cash” – Job Scheduling Management CRM - CDP
SAP ECC - TT5
SAP ENTERPRISE PORTAL - EPP
Create Sales Order
Create Sales Order
Create Sales Order
New job S_TT5800_DE_PP_MRP_0001_D should run daily at 05:30 a.m.
Check Availability
Run MRP
Procurement Process
Manufacturing Process
Create Outbound Delivery Post Goods Issue
Create Billing Document
Business Process Champion
We would like to schedule an MRP run once per day for our new German plant 0001
Warehouse - TT5 Create Outbound Delivery
Create Picking Transfer Order
Post Goods Issue
Confirm Picking Transfer Order
© SAP AG 2009
© SAP AG
SM300
11-5
Why Focus on Job Scheduling Management?
Gain visibility over background jobs via comprehensive job documentation
Discontinue unnecessary background jobs
Speed up support processes by Using meaningful job naming conventions Documenting business requirements & responsibles Documenting error-handling procedures & escalation paths
Improve workload balancing & improve throughput
Using a central scheduling tool allows Control over background jobs scheduled by end-users Better workload distribution considering CPU & memory consumption Higher throughput, more efficient HW utilization & process automation
Improve Service Levels & Business Impact Analysis
Using Business Process Monitoring brings important background jobs into Business Process context & allows automated monitoring by exception
© SAP AG 2009
© SAP AG
SM300
11-6
SAP Standard for Job Scheduling Management Business Department Create Job Request
Receive Confirmation
Plan job request
Approve job request
End/Key User
Document job Test job Schedule job Run job Monitor job
Error SAP Technology Operation Team
Business Process Operations Team
Perform Root Cause Analysis Application Management Team
IT Support Organization © SAP AG 2009
© SAP AG
SM300
11-7
Process Flow in SAP Solution Manager SAP Solution Manager Service Desk
Job Documentation Automatically populated with respective job request data
Business Process Monitoring
End/Key user request – SD message creation in background
Manual Transfer of job documentation (copy & paste)
Pull Monitoring information from Back-end
Enterprise Portal/ Intranet
Web Form
External Job Scheduler
SAP System
© SAP AG 2008
If SAP Central Process Scheduling is used as external scheduling tool, the integration also allows automatic transfer of the job documentation.
© SAP AG
SM300
11-8
Work Center for Job Management The Job Management work center allows central access to all job management functionalities in SAP Solution Manager. It is accessible via transaction /nsolman_workcenter.
© SAP AG 2009
Required roles for Job Management Work Center Usage: y SAP_SMWORK_BASIC y SAP_SMWORK_JOB_MAN
© SAP AG
SM300
11-9
Lesson 2: Job Request in SAP Solution Manager
1. 2. 3. 4. 5.
Job Management Process in SAP Solution Manager Job Request in SAP Solution Manager Job Documentation in SAP Solution Manager Integration of Job Documentation into Business Process Monitoring Integration of Job Documentation and BPMon with SAP CPS
© SAP AG 2009
© SAP AG
SM300
11-10
Accessing Job Requests from Work Center
Request Job Approve Job Request Document Job
Schedule Job
Monitor Job
All existing Job Requests are listed in the Job Management Work Center and can be accessed from there.
© SAP AG 2009
© SAP AG
SM300
11-11
Use Job Request Form in SAP Solution Manager to Request New Job Request Job Approve Job Request Document Job
Schedule Job
Monitor Job
The Job Request form is accessible with the corresponding action in the Job Management Work Center. It can also be made available for end users directly via URL in the companies intranet. © SAP AG 2009
In the Job Request Form, you need to provide the following information:
y
Job Name
y
Information about the system the job should run on
y
Scheduling information - Repeat - Frequency - Start Date
y
Business Requirements: Short description of the purpose of the new job in the context of the existing business process (why is the job needed?)
y
Information to be filled into the Service Desk Message - Message Priority - Component - Short text - Long text - Reporter
© SAP AG
SM300
11-12
Service Desk Message created with Job Request
Request Job Approve Job Request Document Job
Schedule Job
Monitor Job
The content of the Job Request is attached to a corresponding Service Desk Message. Use ‘Transaction Monitor’ in the Service Desk of SAP Solution Manager or transaction /ncrm_dno_monitor to access the service desk message created for the job request.
© SAP AG 2009
© SAP AG
SM300
11-13
Entering Service Desk Message
Request Job Approve Job Request Document Job
Schedule Job
Monitor Job
Access the service desk message from the Service Desk or directly using transaction /ncrm_dno_monitor. © SAP AG 2009
© SAP AG
SM300
11-14
Planning – Check if New Job Request Fits into Existing Schedule
Request Job Approve Job Request Document Job
Schedule Job
Monitor Job
Before approving the job request you should use tool BACKGROUND_JOB_ANALYSIS in transaction ST13 to check the job distribution on the involved system. HW & time restrictions Æ scheduling at 5:30 might be a problem Æ other less important jobs might need a rescheduling. © SAP AG 2009
© SAP AG
SM300
11-15
Creating Job Documentation from Service Desk Message Request Job Approve Job Request Document Job
Schedule Job
Monitor Job
Switch to change mode. Then access the job request or create the job documentation by selecting the respective action and save. © SAP AG 2009
If you cannot see the action to access the job request or to create the job documentation, there is CRM customizing missing in your SAP Solution Manager system. So, configure the Service Desk integration by means of SAP notes 1111310 “Job Scheduling Management: Extended Configuration” and 1165629 “How to copy action from an action profile to another profile”.
© SAP AG
SM300
11-16
Lesson 3: Job Documentation in SAP Solution Manager
1. 2. 3. 4. 5.
Job Request Process in SAP Solution Manager Job Request in SAP Solution Manager Job Documentation in SAP Solution Manager Integration of Job Documentation into Business Process Monitoring Integration of Job Documentation and BPMon with SAP CPS
© SAP AG 2009
© SAP AG
SM300
11-17
Job Documentations in the Work Center
Request Job Approve Job Request Document Job
Schedule Job
Monitor Job
Once the job request has been approved it can be transferred to the central Job Documentation in SAP Solution Manager. You will find all existing Job Documentations in the Job Management Work Center. From there, you can also start a new Job Documentation. © SAP AG 2009
SAP Role SAP_SM_SCHEDULER_ADMIN is required to allow full access to the job documentation functionality in SAP Solution Manager.
Background Jobs available in table TBTCO in the satellite system can be loaded into the job documentation in SAP Solution Manager. In this case, the scheduling information as available in TBTCO is pre-filled for the background jobs.
Please note: Job documentations can be also created without Job Requests and corresponding Service Desk Message.
© SAP AG
SM300
11-18
Create Job Documentation
Request Job Approve Job Request Document Job
Schedule Job
Monitor Job
Enter the background job name and all job information directly in the job documentation. © SAP AG 2009
Use the Job Import functionality to document a job which already exists on the satellite system. Then the name of the job and its steps are filled in automatically into the Job Documentation.
© SAP AG
SM300
11-19
Specify Background Job Details
Request Job Approve Job Request Document Job
Schedule Job
Monitor Job
In tab ‘General’, you also have to define if the job documentation should integrate with SAP CPS or directly with the satellite system via the XBP interface. You can also create new or edit existing job steps. © SAP AG 2009
Integration via XBP means the direct integration with SM36 on the satellite system.
For the integration with SAP CPS, additional technical prerequisites are required. The adapter to integrate the job documentation with SAP CPS requires a license key.
For already existing jobs, the single jobs steps will be filled in automatically and can then be edited.
© SAP AG
SM300
11-20
Job Documentation – Scheduling Maintenance 1/2
Request Job Approve Job Request
1
Document Job
2
Schedule Job
Monitor Job
4 3
Configure corresponding Job Scheduling from within job documentation. In tab “System Landscape” either assign job to logical component or to business process step. Then choose button “Schedule” to define the scheduling information. © SAP AG 2009
© SAP AG
SM300
11-21
Job Documentation – Scheduling Maintenance 2/2
Request Job Approve Job Request Document Job
Schedule Job
Monitor Job
Specify all information marked with “*”. If you want to transfer the job scheduling information to the satellite system, choose the RFC destination you want to use for the transfer. Choose button “Create” to transfer the data to the satellite system. © SAP AG 2009
You can transfer the job documentation to table TBTCO in the satellite system, thus scheduling the job on the satellite system.
© SAP AG
SM300
11-22
Exercise: Create a Job Documentation
Exercise: Create a Job Documentation
© SAP AG 2008
© SAP AG
SM300
11-23
Job Import – System Selection
You can also load existing background jobs from the satellite system into SAP Solution Manager Work Center in order to create a job documentation for it. In a first step, you need to provide information about the satellite system. © SAP AG 2009
The Job Import Web Dynpro application uses service sap/bc/webdynpro/sap/wd_ags_ejr_job_import.
You need to specify at least the Logical System the job should be imported from.
© SAP AG
SM300
11-24
Job Import – Scheduler & Job Selection
In the next steps, choose the scheduler to be used and load the job from the satellite system.
© SAP AG 2009
You need to provide at least a part of the job name to load it from the satellite system. After entering your selection criteria, you can search for all jobs matching these criteria. An output list will be provided from where you can choose the job to be imported.
© SAP AG
SM300
11-25
Job Import – Accessing Job Documentation Directly
After importing the job you can directly jump into the corresponding Job Documentation.
© SAP AG 2009
In the Job Documentation the name of the job and its steps are filled in automatically.
© SAP AG
SM300
11-26
Lesson 4: Integration of Job Documentation into BPMon
1. 2. 3. 4.
Job Request Process in SAP Solution Manager Job Request in SAP Solution Manager Job Documentation in SAP Solution Manager Integration of Job Documentation into Business Process Monitoring 5. Integration of Job Documentation and BPMon with SAP CPS
© SAP AG 2009
© SAP AG
SM300
11-27
Prerequisites for the Integration into Business Process Monitoring Before you can configure background job monitoring so that the alerts show up in the Business Process Monitoring screen of SAP Solution Manager, you have to ensure the following:
Technical prerequisites for Business Process Monitoring are ensured.
You have created a solution with a productive business process. Field “Consider Job Definition” is flagged for the corresponding Business Process in the Business Process Monitoring Setup Session.
Business Process Monitoring is generated and activated for the business process.
© SAP AG 2009
© SAP AG
SM300
11-28
Job Documentation – Monitoring Maintenance 1/2
Request Job Approve Job Request
1
Document Job 2 Schedule Job
Monitor Job
4 3
Configure corresponding Business Process Monitoring alerts from within the job documentation. In tab “System Landscape”, you can define monitoring configuration via button “Monitoring”. © SAP AG 2008
© SAP AG
SM300
11-29
Job Documentation – Monitoring Maintenance 2/2
Request Job Approve Job Request Document Job
Schedule Job
Monitor Job
Enter the monitoring configuration in tabs “Data Collection” and “Alert Configuration”. Save. Then choose button “Activate Monitoring”. © SAP AG 2008
© SAP AG
SM300
11-30
Job Monitoring Alerts in the Work Center for Job Management
You can access the job monitoring alerts originated in Business Process Monitoring via the Work Center for Job Management. The alerts are also visible in the operative part of Business Process Monitoring Session. © SAP AG 2009
© SAP AG
SM300
11-31
Exercise: Configure Job Monitoring
Exercise: Configure Job Monitoring
© SAP AG 2008
© SAP AG
SM300
11-32
Lesson 5: Integration of Job Documentation and BPMon with SAP CPS
1. 2. 3. 4. 5.
Job Request Process in SAP Solution Manager Job Request in SAP Solution Manager Job Documentation in SAP Solution Manager Integration of Job Documentation into Business Process Monitoring Integration of Job Documentation and BPMon with SAP CPS
© SAP AG 2009
© SAP AG
SM300
11-33
Accessing SAP CPS from within the Work Center for Job Management The Job Management Work Center also allows access to SAP Central Process Scheduling.
© SAP AG 2009
Required roles for calling SAP CPS: y SAP_SM_REDWOOD_COMMUNICATION
For more information on the SAP CPS integration refer to SAP note 1122497 “Process scheduling for SAP Solution Manager”
© SAP AG
SM300
11-34
Scheduling in SAP Central Process Scheduler (1/2) Use filter criteria to find job more easily.
Select job from list.
Background Job is submitted to system via SAP Central Process Scheduler.
Details of the selected job.
© SAP AG 2009
In case you transferred the job from the SAP Solution Manager with the flag “Schedule Stopped” the corresponding job in SAP CPS can be found in status “held”. Now within the scheduler the scheduling can be refined and the job has to be submitted explicitly.
At the end SAP CPS controls the job scheduling NOT the SAP Solution Manager.
© SAP AG
SM300
11-35
Scheduling in SAP Central Process Scheduler (2/2)
© SAP AG 2009
In case you transferred the job from the SAP Solution Manager with the flag “Schedule Stopped” the corresponding job in SAP CPS can be found in status “held”. Now within the scheduler the scheduling can be refined and the job has to be submitted explicitly.
At the end SAP CPS controls the job scheduling NOT the SAP Solution Manager.
© SAP AG
SM300
11-36
SAP Solution Manager Process Scheduling Adapter SAP Solution Manager Change Request Management
Service Desk
Enterprise Portal/ Intranet Web Form
End/Key user request – SD message creation in background
Operator request – manual creation of SD message
SAP Central Process Scheduling by Redwood
Job Documentation Automatically populated with respective CR data
Business Process Monitoring
Transfer job documentation (incl. basic scheduling)
Job Scheduling
API
API
SAP NW 7.0 Redwood Process Server
SAP System
Push Monitoring information = New ntegration
© SAP AG 2008
If SAP Central Process Scheduling is used as external scheduling tool, the integration also allows automatic transfer of the job documentation.
© SAP AG
SM300
11-37
Further Information – SAP Notes
1054005 - FAQ: Job Scheduling Management with SAP Solution Manager
Describes roles and SPRO activities in order to get started with Job Management in SAP Solution Manager
1117355 - Job Scheduling Management: Work Center
Describes steps in order to activate the Job Management Work Center
1111310 - Job Scheduling Management: Extended Configuration
Describes configuration steps for Service Desk so that Job Request and Job Documentation get linked
1122497 - Process scheduling for SAP Solution Manager
Information around the Process Scheduling Adapter for SAP Solution Manager
White Paper about Job Scheduling Management
Can be found at http://www.service.sap.com/supportstandards Æ Support Standards Æ Media Library Æ Job Scheduling Management
© SAP AG 2009
© SAP AG
SM300
11-38
Exercises Unit:
Managing Jobs in SAP Solution Manager
Lesson:
Job Documentation in SAP Solution Manager
Exercise 22: Create Job Documentation
At the conclusion of this exercise, you will be able to: • Document Background Jobs in SAP Solution Manager
Company IDES uses SAP Solution Manager for documenting background jobs.
22-1
Create a job documentation for a new background job. 22-1-1 Call transaction /nsolman_workcenter to access the Solution Manager Workcenter. Enter the Job Management area to create a new Job Documentation. Question: Which information is needed mandatorily to create a job documentation? Answer: _____________________________________________________________ 22-1-2 Create a job documentation for the new background job “SD_CREATE_CRITICAL_SALES_ORDERS_15MIN_##”. Use the XBP interface to connect the job documentation to the satellite system. Attach the job documentation to step “Create Sales Order” in the ECC system of your solution. Question: Where in the job documentation can you find the detailed scheduling information for the background job (start time, period etc)? Answer: _____________________________________________________________ 22-1-3 Schedule the job to run on a daily basis every 15 minutes. As the job is critical to your business process, choose the corresponding category. Save your settings. Question: Is it necessary that the RFC connection to ECC system TT5 is working properly? Answer: _____________________________________________________________
© SAP AG
SM300
11-39
© SAP AG
SM300
11-40
Solutions Unit:
Managing Jobs in SAP Solution Manager
Lesson:
Job Documentation in SAP Solution Manager
Exercise 22: Create Job Documentation
22-1-1 Call transaction /nsolman_workcenter in Solution Manager system TT4. Choose tab “Job Management” to enter the Job Management area. Click on “Create Job Documentation” in part Common Tasks in the menu at the left side of the screen to open the browser for the job documentation. Answer: You need information about the business process the job documentation should be attached to. 22-1-2 Create a job documentation for the new background job “SD_CREATE_CRITICAL_SALES_ORDERS_15MIN_##”. In tab “General”, enter the job name and choose BC-XBP as interface technique in field “Scheduler”. Attach the job documentation to step “Create Sales Order” in the ECC system of your solution. Go to tab “System Landscape” and press button “Solution” in table “Logical Components and Solutions”. In the pop-up screen, fill in all the required information from your solution except “Logical Component”: •
Solution: SM300-## Landscape
•
Scenario: Outbound Logistics
•
Process: Order-to-Cash
•
Step: Create Sales Order (on Logical Component Z_ECC)
Afterwards, press button “Copy” to take over your selection. Answer: The scheduling information can be found using button “Schedule” in table “Systems”. At the moment, no scheduling information is available as the job documentation is not created based on an existing job request.
© SAP AG
SM300
11-41
22-1-3 Schedule the job to run on a daily basis every 15 minutes. Mark the system TT5 (Production System) in table “Systems” and press button “Schedule”. In the pop-up screen, press button “Change” to enter the scheduling information. Choose “A – High Priority” as “Job Class”. The scheduling itself should be done as follows: •
Start Method: Date/Time
•
Start Time: Current date / time
•
No Start after: leave blank
•
Period Unit: Minutes
•
Period: 15
To save your settings, press button “Save”. Answer: As no scheduling information has to be read from the satellite system, a test of the RFC connection to system TT5 is not necessary.
© SAP AG
SM300
11-42
Exercises Unit:
Managing Jobs in SAP Solution Manager
Lesson:
Integration of Job Documentation into Business Process Monitoring
Exercise 23: Configure Job Monitoring from Job Documentation At the conclusion of this exercise, you will be able to: • Configure Job Monitoring from within the Job Documentation
For background jobs that are available within the job documentation the monitoring of these jobs should be configured directly from there.
23-1 Set up monitoring of the previously documented job “SD_CREATE_CRITICAL_SALES_ORDERS_15MIN_##” from within the job documentation. 23-1-1 Question: What are the prerequisites that have to be ensured before configuring job monitoring from within the job documentation? Answer: _____________________________________________________________ Ensure the prerequisites for your solution. 23-1-2 Configure and activate the monitoring of job cancellation and maximum duration (5 mins) for background job “SD_CREATE_CRITICAL_SALES_ORDERS_15MIN_##” from within the job documentation. Question: What is different for the job monitoring from within the job documentation compared to the normal job monitoring within BPMon? Answer: _____________________________________________________________
© SAP AG
SM300
11-43
© SAP AG
SM300
11-44
Solutions Unit:
Managing Jobs in SAP Solution Manager
Lesson:
Integration of Job Documentation into Business Process Monitoring
Exercise 23: Configure Job Monitoring from Job Documentation
23-1 Set up monitoring of the previously documented job “SD_CREATE_CRITICAL_SALES_ORDERS_15MIN_##” from within the job documentation. 23-1-1 Answer: There are two prerequisites for integrating job monitoring from a job documentation into Business Process Monitoring in SAP Solution Manager: •
In the setup part of your solution, the flag “Consider Job Def.” has to be set for Business Process “Order-to-Cash”.
•
The monitoring for this Business Process has to be active.
Ensure the prerequisites for your solution. 23-1-2 Configure and activate the monitoring of job cancellation and maximum duration (5 mins) for background job “SD_CREATE_CRITICAL_SALES_ORDERS_15MIN_##” from within the job documentation. Perform the following steps:
© SAP AG
•
In the job documentation of the background job “SD_CREATE_CRITICAL_SALES_ORDERS_15MIN_##”, mark the entry TT5 (Production System) in table “Systems” and press button “Monitoring”. (Note: If you already closed the window for the job documentation, you can access it again via the Solution Manager Workcenter, area Job Monitoring. Navigate to “Job Documentation” and choose the entry for your own Job Documentation.)
•
In the next screen, enter Change Mode with the respective button. In tab “Data Collection”, specify the criteria for data collection. Flag field “Critical Job” and use the Start Procedure “Date / Time” on a weekly basis. Choose the weekdays for monitoring and the period (e.g. 15mins).
•
In tab “Alert Configuration”, define thresholds and ratings for job cancellation and maximum duration. Set the rating for cancelled jobs to red, and specify thresholds for maximum runtime (e.g. 2 mins for yellow, 5 mins for red).
•
In the end, press button “Activate Monitoring”.
SM300
11-45
Answer: In opposite to job monitoring within BPMon, no customizing is visible in the Business Process Monitoring Setup for the job monitoring from within the job documentation. Only alerts are generated and can be checked in the operations part of the session.
© SAP AG
SM300
11-46
