Manage operations for service parts palnning with sap scm

4,374 views

Published on

2 Comments
1 Like
Statistics
Notes
No Downloads
Views
Total views
4,374
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
267
Comments
2
Likes
1
Embeds 0
No embeds

No notes for slide

Manage operations for service parts palnning with sap scm

  1. 1. Best Practice for Solution OperationsManage Operations for Service Parts Planning with SAP SCM Dietmar-Hopp-Allee 16 D-69190 Walldorf CS STATUS external final DATE VERSION August 5th, 2009 1.1 SOLUTION MANAGEMENT PHASE SAP SOLUTION Operations & Continuous Improvement Best Practices for Solution Operations TOPIC AREA SOLUTION MANAGER AREA Application & Integration Management Business Process Operation
  2. 2. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts PlanningTable of ContentsManagement Summary 5 1.1 Goal of Using this Best Practice 5 1.2 Alternative Practices 5 1.3 Staff and Skills Requirements 5 1.4 System Requirements 6 1.5 Duration and Timing 6 1.6 How to Use this Best Practice 6 1.7 Best Practice Procedure 6 1.7.1 Preliminary Tasks 6 1.7.2 Monitoring Concepts 6 1.7.3 Business Process Monitoring in SAP Solution Manager 7 1.7.4 Monitoring Types for Business Process Monitoring in SAP Solution Manager 8 1.7.4.1 Application Monitor 8 1.7.4.2 Background Job 9 1.7.4.3 ABAP Dump Collector 10 1.7.4.4 Dialog Performance 10 1.7.4.5 Update Errors 11 1.7.4.6 Due List Log 12 1.7.4.7 Application Log 13 1.7.4.8 Other CCMS Monitors 14 1.7.4.9 Analysis and Monitoring Tools 15 1.7.4.10 Monitoring Activities 17 1.7.4.11 Notifications 17 1.7.5 Business Process Monitoring Process 182 Business Process Monitoring for Service Parts Planning 20 2.1 Sample Scenario 20 2.2 Business Process Service Parts Planning 20 2.2.1 Business Process Step 1: Capture Demand History 21 2.2.1.1 Description 21 2.2.1.2 Monitoring Requirements: 22 2.2.1.3 Monitoring Objects in SAP Solution Manager 23 2.2.1.4 Monitoring without SAP Solution Manager 25 2.2.1.5 How to Find Meaningful Thresholds for Each Monitoring Object 25 2.2.2 Business Process Step 2: Stocking and De-stocking 25 2.2.2.1 Description 25 2.2.2.2 Monitoring Requirements: 26 2.2.2.3 Monitoring Objects in SAP Solution Manager 26 2.2.2.4 Further Monitoring Objects 26 2.2.2.5 Monitoring without SAP Solution Manager 27 2.2.2.6 How to Find Meaningful Thresholds for Each Monitoring Object 27 2.2.3 Business Process Step 3: Manage Demand History 27 2.2.3.1 Description 27 2.2.3.2 Monitoring Requirements: 28 2.2.3.3 Monitoring Objects in SAP Solution Manager 28 2.2.3.4 Further Monitoring Objects 29© 2010 SAP AG page 2/2
  3. 3. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts Planning 2.2.3.5 Monitoring without SAP Solution Manager 29 2.2.3.6 How to Find Meaningful Thresholds for Each Monitoring Object 29 2.2.4 Business Process Step 4: Forecasting 29 2.2.4.1 Description 29 2.2.4.2 Monitoring Requirements: 31 2.2.4.3 Monitoring Objects in SAP Solution Manager 31 2.2.4.4 Further Monitoring Objects 31 2.2.4.5 Monitoring without SAP Solution Manager 32 2.2.4.6 How to Find Meaningful Thresholds for Each Monitoring Object 32 2.2.5 Business Process Step 5: Economic Order Quantity & Safety Stock 32 2.2.5.1 Description 32 2.2.5.2 Monitoring Requirements: 33 2.2.5.3 Monitoring Objects in SAP Solution Manager 33 2.2.5.4 Further Monitoring Objects 33 2.2.5.5 Monitoring without SAP Solution Manager 34 2.2.5.6 How to Find Meaningful Thresholds for Each Monitoring Object 34 2.2.6 Business Process Step 6: Surplus & Obsolescence Planning 34 2.2.6.1 Description 34 2.2.6.2 Monitoring Requirements: 35 2.2.6.3 Monitoring Objects in SAP Solution Manager 35 2.2.6.4 Further Monitoring Objects 36 2.2.6.5 Monitoring without SAP Solution Manager 37 2.2.6.6 How to Find Meaningful Thresholds for Each Monitoring Object 37 2.2.7 Business Process Step 7: Distribution Requirements Planning (DRP) 37 2.2.7.1 Description 37 2.2.7.2 Monitoring Requirements: 38 2.2.7.3 Monitoring Objects in SAP Solution Manager 38 2.2.7.4 Further Monitoring Objects 39 2.2.7.5 Monitoring without SAP Solution Manager 39 2.2.7.6 How to Find Meaningful Thresholds for Each Monitoring Object 39 2.2.8 Business Process Step 8: Procurement Approval (DRP Approval) 40 2.2.8.1 Description 40 2.2.8.2 Monitoring Requirements: 41 2.2.8.3 Monitoring Objects in SAP Solution Manager 41 2.2.8.4 Further Monitoring Objects 43 2.2.8.5 Monitoring without SAP Solution Manager 43 2.2.8.6 How to Find Meaningful Thresholds for Each Monitoring Object 43 2.2.9 Business Process Step 9: Deployment 44 2.2.9.1 Description 44 2.2.9.2 Monitoring Requirements: 45 2.2.9.3 Monitoring Objects in SAP Solution Manager 45 2.2.9.4 Further Monitoring Objects 46 2.2.9.5 Monitoring without SAP Solution Manager 47 2.2.9.6 How to Find Meaningful Thresholds for Each Monitoring Object 47 2.2.10 Business Process Step 10: Inventory Balancing 47 2.2.10.1 Description 47© 2010 SAP AG page 3/3
  4. 4. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts Planning 2.2.10.2 Monitoring Requirements: 48 2.2.10.3 Monitoring Objects in SAP Solution Manager 48 2.2.10.4 Further Monitoring Objects 49 2.2.10.5 Monitoring without SAP Solution Manager 49 2.2.10.6 How to Find Meaningful Thresholds for Each Monitoring Object 503 Further Information 51 3.1 Troubleshooting 51 3.2 Related Best Practice Documents 51 3.3 Literature 51 3.4 Feedback and Questions 524 Appendix 53 4.1 Examples for recommended Monitoring Objects 53 4.1.1 Example Background Job Monitoring 53 4.1.2 Example Dialog Response Time Monitoring 54 4.1.3 Example Data Consistency 55 4.2 Available Monitoring Objects for scenario “Procure-to-stock” 57 4.2.1 Overview “Procure-to-Stock” 57 4.2.2 Monitoring Business Process “Procure-to-Stock” 58 4.2.3 Business Process Steps executed in SAP SCM APO – Service Parts Planning and Monitoring Objects 59 4.2.4 Business Process Steps executed in SNC and respective Monitoring Objects 59 4.2.5 Business Process Steps executed in ECC/ERP and Monitoring Objects 60 4.2.6 Business Process Steps executed in EWM and respective Monitoring Objects 61 4.2.7 Business Process Steps executed in the Supplier System and respective Monitoring Objects 63 4.3 Background Jobs 64© 2010 SAP AG page 4/4
  5. 5. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts Planning Management Summary1.1 Goal of Using this Best PracticeThis Best Practice will help you to set up a Business Process Monitoring concept for your SAP solution in theautomotive area. The concept aims to define procedures for business process oriented monitoring and errorhandling, and escalation procedures for Service Parts Planning with SAP SCM. These procedures areintended to ensure a smooth and reliable flow of this core business process so that your businessrequirements are met.This Best Practice offers guidance to define suitable application-oriented monitoring objects to detect anyirregularities or deviations from an ideal business process flow, or to detect error situations concerning a corebusiness process at an early stage.This Best Practice contains the recommended approach from SAP which uses the SAP Solution Manager forthe Monitoring functionalities whenever possible. However, even if you do not use the SAP Solution Managerwe recommend that you follow the procedures described in this document as much as possible in to ensure asmooth and reliable flow of your business processes as well as an appropriate response in case ofunforeseen errors.Additional information on how to monitor the end-to-end cross-system scenario “Procure-to-stock” can befound in the Appendix of this document.1.2 Alternative PracticesYou can have SAP experts deliver this Best Practice on-site by ordering an SAP Solution ManagementOptimization (SMO) service for SAP Business Process Management (BPM). This service is exclusivelyavailable within SAP’s support engagements SAP MaxAttention and SAP Safeguarding. If your companycurrently does not have any support engagement with SAP, it is also possible to get assistance by SAPexperts from SAP Consulting. If this case, please contact your local SAP Consulting representative.1.3 Staff and Skills RequirementsTo implement this Best Practice, you require the following teams:Application Management TeamThis team creates the ERP Business Process Monitoring concept and consists of experts from several areasof your company: Business department Solution support organization (for example the Basis Support or the Application Support) Implementation project teamBusiness Process Operations TeamThe Business Process Operations team will be responsible for applying the resulting procedures derived fromimplementing this best practice. They include the following groups: Persons designated to perform business process-oriented monitoring and to ensure that the process runs smoothly (for example, the Business Process Champion for each business process) All parties in your Solution Support Organization and IT department involved in monitoring focused on the application aspects (Application Support, Development Support, Job Scheduling Management)SAP Technology Operations Team All parties in your Solution Support Organization and IT department involved in monitoring focused on the system administration side (Program Scheduling Management, Software Monitoring Team, System Administration Team including the System Administrator)Business Process Champion The Business Process Champion is the person in the business department who is responsible for the successful execution of the business process. He/she coordinates all activities necessary for the business process. Therefore, he/she is usually responsible for the escalation paths in case of problems. Often, he/she is a second level in the escalation procedure, if the application monitoring team needs to escalate an issue.© 2010 SAP AG page 5/5
  6. 6. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts PlanningMore information about roles and responsibilities of these teams can be found in the super-ordinate BestPractice General Business Process Management, which you can obtain through SAP Solution Manager orthe SAP Service Marketplace, quicklink /BPM.Necessary or Useful Trainings SM300 Business Process Management and Monitoring E2E300 End-to-end Business Process Integration and Automation Management1.4 System RequirementsTo monitor business processes running in your SAP solution via SAP Solution Manager, the SAP BasisRelease of the systems to be monitored have to be at least 4.6C. To have all described monitoring objectsavailable in SAP Solution Manager, the add-on ST-A/PI01L has to be installed on the SAP ECC systems.1.5 Duration and TimingDurationCreating a Business Process Monitoring concept could take around one week per business process.Implementing the Business Process Monitoring concept might take approximately an additional week in total.TimingThe best time to apply this Best Practice is during the planning phase or during the implementation phase ofyour SAP solution.1.6 How to Use this Best PracticeHere you find a brief description of how you should proceed in using this document: Read through the General Business Process Management Best Practice, available on the SAP Service Marketplace. This document explains the procedures you should use to create a general Business Process Management concept. This includes the definition and documentation of the core business processes, definition of monitoring objects, definition of monitoring activities including error handling procedures, monitoring tools and monitoring frequencies, the definition of communication and escalation procedures and the assignment of responsibilities. At the beginning of section 2, you will find a typical flow chart of the core business process explained in this Best Practice. It is intended to be used as a guideline for writing down your company specific process documentation. In section 1.7.4, you find further information that is relevant for more than one scenario. If information from the generic part is relevant for a specific business process step in one of the scenarios, you will find a clear link to the corresponding chapter in the generic part.1.7 Best Practice Procedure1.7.1 Preliminary TasksBefore performing this Best Practice, ensure that you perform the following preliminary tasks or checks in thesystem: Complete all installation and post-installation actions and procedures including customizing Ensure that the initial data load has been successfully executed Apply all SAP recommendations from SAP Service Sessions and any SAP recommendations resulting from customer problem messages Implement all current SAP Support Packages upon availability1.7.2 Monitoring ConceptsThe monitoring procedures proposed for each business process step are the core of this Best Practice. Themonitoring procedures help you to ensure that the technical processes meet the requirements for stability,performance, and completeness. These procedures cover monitoring for the five areas: Error monitoring Performance monitoring© 2010 SAP AG page 6/6
  7. 7. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts Planning Throughput monitoring Backlog monitoring Data Consistency MonitoringFor each of the business process steps, you will find the following information: A detailed functional description of the process step Identified monitoring requirements for the process step Defined monitoring objects, alerts and selection criteria Description of error handling procedures and restartabilityGeneral monitoring activities that are valid for all or most scenarios are described in the generic part insection 1.7.4. Recommendations for performance monitoring can also be found in this chapter. Theperformance of the most important steps of your core business processes should be monitored on a regularbasis. The monitoring procedure for performance monitoring of all steps that are executed in an SAP solutionused for Spare Parts Management is generally the same. Therefore, you will only find specific performancemonitoring recommendations on selected business process steps.1.7.3 Business Process Monitoring in SAP Solution ManagerBusiness Process Monitoring (BPMon), as part of Solution Monitoring means the proactive and process-oriented monitoring of the most important or critical business processes including the observation of alltechnical and business application specific functions that are required for a steady and stable flow of thebusiness processes.The core business processes that are implemented in an SAP system or other software and operated by acompany are of particular importance. Business Process Monitoring is intended to ensure a smooth andreliable operation of the business processes and, thereby, that the core business processes meet acompany’s business requirements in terms of stability, performance, and completeness. SAP SolutionManager provides a graphical view to visualize a company’s (distributed) system and solution landscape andall related business processes. By using Business Process Monitoring, it is possible to define and customizealert situations from a basic set of configurable monitoring objects provided by the SAP Solution Manager.These resulting alerts are then visualized by green, yellow, and red alert icons for each individual businessprocess step in the graphical business process representation. The goal of Business Process Monitoring is todetect and respond to critical situations as early as possible so you can solve problems as quickly aspossible.In addition, SAP Solution Manager offers extended functionality for error handling and problem resolution. Bythe definition of contact persons and escalation paths, Business Process Monitoring can be integrated intothe company’s overall strategy for Business Process Management and Solution Management within theirSolution Support Organization.In general, Business Process Monitoring includes the solution-wide observation of: Business process performance (Key Performance Indicators) Background jobs (Job Scheduling Management tasks) Business application logs (such as any error log, general application log, due list logs, and so on) Data transfer via interfaces between software components Data consistency Technical infrastructure and components which are required to run the business processes Required periodic monitoring tasksFor further details on Business Process Monitoring please refer to http://service.sap.com/bpm.© 2010 SAP AG page 7/7
  8. 8. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts Planning1.7.4 Monitoring Types for Business Process Monitoring in SAP Solution ManagerMonitoring Types are part of the functional scope of Business Process Monitoring as it is available in the SAPSolution Manager. This chapter provides a short overview of available monitoring types for referencepurposes only. The available Monitoring Types are: Application Monitor (Throughput and Backlog Indicators, Data Consistency Checks, Mass Activity Monitors, Due List Log, MRP key figures, User Exit, Interface Monitoring) Background Jobs (Jobs running on SAP Systems with an SAP Basis) Dialog Performance (Dialog transaction performance) Update Errors (V1 and V2 update errors from SM13 for specific transactions and programs) Due List Log (messages for deliveries and billings) Application Log (messages from the Application Log SLG1) Document Volume (based on table call statistics in ST10) Other CCMS Monitor (all alerts that are configured in the CCMS Alert Monitor)Depending on what is executed during a specific business process step, the relevant Monitoring Types mustbe selected. To receive detailed information on how to set up the Monitoring Objects in SAP SolutionManager, please refer to the documentation that is available under http://service.sap.com/bpm.One prerequisite for setting up Business Process and Interface Monitoring in the SAP Solution Manager isthat all business processes and business process steps are maintained in the respective solution thatcontains all affected system components. If you want to learn more about how to set this up, see (URLhttp://help.sap.com) SAP Solution Manager Basic Settings.1.7.4.1 Application MonitorThe Application Monitor is just one of many different Monitoring Types within Business Process Monitoring.The latest monitoring objects are only provided if the latest ST-A/PI plug-in is installed on the satellite system.The Service Tool for ST-A/PI is available via the SAP Service Marketplace Quick Link /installations Entryby Application Group -> Plug-Ins SAP Solution Tools ST-A/PI. Ensure that the ST-A/PI is installed on the SAP Solution Manager system and on the respective satellite system. In case of problems, refer to SAP Note 915933. The Throughput and Backlog Indicator functionality available as of ST-A/PI 01J* is only working properly with ST-SER 700_2007_1. This is due to changes in the underlying architecture.More detailed information about the different Application Monitor functionalities and a detailed description onhow to define self-written monitoring collectors for the user exit are explained in the documents ‘Setup Guide– Application Monitoring ’ and ‘Setup Guide - User Exit’ respectively (URL http://www.service.sap.com/ AliasBPM Media Library).1.7.4.1.1 Throughput and Backlog Indicators (TBIs)As of ST-A/PI 01H, a completely new set of Application Monitors has been introduced. While the alreadyestablished monitors are all evaluating specific logs or performance data these new monitors are considering(un-)processed documents in the SAP system and provide Throughput and Backlog Indicators.These TBIs should especially provide Automated and early detection of application error situations and backlogs in the core business processes Automated error and backlog analysis tools© 2010 SAP AG page 8/8
  9. 9. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts PlanningFor ERP Logistics, the following monitors are available: Sales and Services (for example, Sales Documents, Invoices) Warehouse Management (for example, Transfer Requirements, Transfer Orders) Inventory Management (for example, Goods Movements) Logistics Execution (for example, Deliveries, Shipments) Procurement (for example, Planned Orders, Purchase Requisitions, Purchase Orders) Manufacturing (for example, Planned Orders, Production or Process Orders, Autom. Goods Movements posted with error, Confirmation Pool errors) Plant Maintenance (for example, PM/CS Notifications, PM/CS Orders)For further information on the different TBIs refer to the document ‘Setup Guide - Application Monitoring’(URL http://www.service.sap.com/BPM Media Library).1.7.4.1.2 Data Consistency ChecksThe DCC collectors are a subset of the Application Monitors used to retrieve a stored comparison result fromdata comparison check reports for SAP systems.There are certain consistency check programs that are able to not only output their check result to a list orinto the spool, but can also permanently store a summary in database tables. Corresponding monitoringobjects can be configured to retrieve the number of found inconsistencies out of the stored summaryinformation and display them as alerts within the SAP Solution Manager Business Process Monitoring(Consistency Monitoring).For further information, refer to the document Setup Guide – Data Consistency Monitoring (URLhttp://www.service.sap.com/ -> Technical Information).1.7.4.2 Background JobThe background job monitoring should be part of a Job Scheduling Management concept (go tohttp://service.sap.com/solutionmanagerbp Topic Area “Business Process Operations” to find a BestPractice document ‘Job Scheduling Management’). Because of several restrictions regarding background jobscheduling, for example, time restrictions, restriction of hardware resources (CPU, main memory, …) orexisting dependencies between different activities (for example, invoices can only be created after thecorresponding goods issue is posted, or Back Order Processing and Material Requirements Planning shouldnot run at the same time) it is very important to ensure the stable running of background jobs. A cancelledbackground job should be identified as soon as possible so you can react as quickly as possible. Therefore, itis also necessary to define restart procedures and escalation paths.1.7.4.2.1 Monitoring Objects and AlertsBefore setting up monitoring, the monitoring objects must be clearly defined. A monitoring object is a singlebackground job or a group of background jobs. There are four different possibilities to identify a specialbackground job or a group of background jobs. This information needs to be maintained in the sub-node‘Background Job’ below a business process step.A more detailed description (than provided in this document) on the subject of what kind of alerts make senseor what kind of alerts are possible are discussed in the Best Practice document “Background Job Monitoringwith SAP Solution Manager”, which can be found on the SAP Marketplacehttp://service.sap.com/solutionmanagerbp Topic Area “Business Process Operation”.© 2010 SAP AG page 9/9
  10. 10. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts Planning1.7.4.3 ABAP Dump CollectorThis provides monitoring features for alerting on occurrences of ABAP dumps of specified runtime errors or tocollect statistical data of ABAP dumps for reporting reasons.1.7.4.3.1 Monitoring Objects and AlertsThe monitoring object is an ABAP runtime error. This runtime error can be specified via the runtime errorname, the user who is responsible for the runtime error, the Client on which the runtime error occurs, or theProgram which leads to the runtime error.The following alerts are available:- Number of ABAP Dumps (Delta) (all dumps since the last collector run)- Number of ABAP Dumps (Reporting) (all runtime errors of specified type, client and program for this day orfor the previous day)1.7.4.4 Dialog PerformanceDialog Performance implies the monitoring of the dialog transaction performance of any transaction in theSAP System. This could be a standard transaction or a self-developed transaction.1.7.4.4.1 Monitoring Objects and AlertsThe monitoring object is the transaction itself. The customizing has to be done in the node ‘DialogPerformance’. In the table ‘Transactions’, all transactions that are already configured to that business processstep are listed. The relevant transactions need to be selected for monitoring. It is also possible to add or toremove transactions within table ‘Add/Remove Transactions’. The monitoring can be performed for each SAPinstance. Therefore, the respective instances have to be selected in table ‘SAP Instances’. All instancesthat are maintained for a system are listed there. Table ‘Alert Types’ shows the dialog response timeand all parts of the response time, like queue time, load and generation time, database request time, and thefront-end response time, which can be monitored. Those times that are relevant for monitoring have to beselected.After saving this node, a sub-node ‘Performance Alerts’ will appear where the threshold values have to beentered.Monitoring Objects – Dialog PerformanceEach table in the sub-node ‘Performance Alerts’ corresponds to an alert type chosen in the higher-level node,and lists the combinations of the specified transaction code and SAP instance.For each combination of transaction code and instance that should be included in the monitoring, the© 2010 SAP AG page 10/10
  11. 11. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts Planningthreshold values resulting in alert messages for changes from GREEN to YELLOW, from YELLOW to RED,back from RED to YELLOW, and back from YELLOW to GREEN have to be specified.Since the Monitoring Object for Performance Monitoring is created on the satellite system, it might bepossible that the object already exists there. Therefore, you can load the current threshold values from therespective systems via the button "Load thresholds from XYZ", where “XYZ” represents the SID.If successfully retrieved for an SAP instance, the values are filled in columns. If no active settings for thethreshold values were found for a certain transaction code, default values are set (indicated in column"Default"). To transfer the threshold values for a single line from right to left, the copy icon can be used. Totransfer all at once (all thresholds for all columns and tables), there is an additional button "Copy all".Monitoring Alerts - Dialog Performance1.7.4.5 Update ErrorsChanges to the data in an SAP system caused by a business process should be written to the database in fullor not at all. If the operation is canceled while the transaction is being executed, or if an error occurs, thetransaction should not make any changes to the database. These activities are handled by the SAP updatesystem.The SAP System makes a distinction between primary, time-critical (V1) and secondary, non-time-critical (V2)update errors. This distinction allows the system to process critical database changes before less criticalchanges.V1 modules describe critical or primary changes; these affect objects that have a controlling function in theSAP System, for example, order creation or changes to material stock.V2 modules describe less critical secondary changes. These are pure statistical updates, for example, resultcalculations.1.7.4.5.1 Monitoring Objects and AlertsMonitoring of Update Errors can be configured for online transactions and/or ABAP programs relevant in abusiness process. This is the object type. The name of the object is the name of a transaction or the name ofthe ABAP program itself. If desired a user executing the transaction or the ABAP program can be specified.If no user is specified explicitly, all users (represented by *) will be considered in monitoring data evaluation.© 2010 SAP AG page 11/11
  12. 12. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts PlanningMonitoring Objects - Update ErrorsSince update errors are usually very critical, the default configuration is to raise a yellow alert as soon as oneupdate error occurs. This is valid for V1 and for V2 update errors. To raise a red alert for a V1 or a V2 updateerror, a threshold must be specified.1.7.4.6 Due List LogA due list is a list that contains several entries (documents) depending on selection criteria. There aredifferent types of due lists in an SAP system, of which the following three are most important: delivery (L),billing (F) and picking (K). The delivery due list can be accessed directly via transaction V_SA, and the billingdue list via transaction V.21. In the case of a billing due list, the list contains, for example, a number of salesdocuments that need to be billed. If the billing due list was processed previously and it is important to knowwhich billing documents were created from this billing due list, it can be displayed in the due list log for thisbilling run.1.7.4.6.1 Monitoring Objects and AlertsThe monitoring object is the respective due list type. That can be ‘Delivery’, ‘Billing’, or ‘Picking’. If a certainuser is processing the due list, the name of the user can be specified here. If it is user independent, a wildcard ‘*’ can be used. The aggregation level needs to be defined. This could be ‘per day’, ‘per hour’ or ‘perlog’.For the monitoring of due list log messages, four different alert types can be used: 1. ‘DocumentCreation’ refers to the status of the document creation itself. The alert rating (YELLOW or RED) will be raised if no documents were created during a Due List run. 2. ‘MinQuantityDocs’ refers to a minimum number of documents that should be created during a Due List run. The threshold values for the number of documents that result in a change from GREEN to YELLOW (or back) and from YELLOW to RED (or back) must be maintained. 3. ‘TotalQuantityMsgs’ refers to the total number of message created during a Due List run. 4. The threshold values for the number of messages that result in a change from GREEN to YELLOW (or back) and from YELLOW to RED (or back) must be maintained.© 2010 SAP AG page 12/12
  13. 13. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts Planning 5. ‘DLLogMsgs’ refers to specific due list log messages. The message type, the message ID and the number can be specified. It is also possible to use wild cards. The threshold values for the number of messages that result in a change from GREEN to YELLOW (or back) and from YELLOW to RED (or back) must be maintained.1.7.4.7 Application LogThe Application Log provides an infrastructure for collecting messages, saving them in the database anddisplaying them as a log. Situations can arise at runtime in application programs that must be brought to theattention of the user in some way. These are usually errors. It can also be useful to report a successfulcompletion. The information that arises is called a message. The set of messages is a log. A log usually alsohas header information (log type, creator, creation time, and so on). A transaction can generate several logs.The Application Log is not written consecutively but as a whole at one point in time.1.7.4.7.1 Monitoring Objects and AlertsThe Application Log allows an application-oriented or object-oriented recording of events. An object, and anysubobject that belongs to it, classify each event. The analysis of the logs is similarly object (or sub-object)oriented. The name of an object (and/or subobject) can be found in transaction /nSLG1 together with all otherspecific information to that log.Monitoring Objects and Alerts - Application LogIt is possible to monitor for the total number of messages belonging to an object. Therefore, the number ofmessages that raises a YELLOW alert and the number of messages changing from a YELLOW to a REDalert must be maintained.It is also possible to monitor specific messages that are considered as critical in table CriticalMsgs. To© 2010 SAP AG page 13/13
  14. 14. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts Planningconfigure the monitoring of critical application log messages, the relevant object-sub object combinationsneed to be selected. For each of these combinations, the message type, the message ID, the messagenumber and the threshold values for the number of critical messages that are supposed to result in changesfrom GREEN to YELLOW and from YELLOW to RED can be specified. It is also possible to use wild cards.Monitoring Alerts - Application Log / Critical Messages1.7.4.8 Other CCMS MonitorsWith other CCMS Monitors, it is possible to assign any CCMS monitoring tree element (MTE) to a businessprocess step. Therefore, it is necessary to call transaction RZ20 in the Satellite System and to open a monitorthat contains the required alert(s).The name of the monitoring tree element (MTE) can be found by choosing F1. The MTE name needs to becopied into the corresponding column of the table below (See screenshot “Other CCMS Monitors” below).Under column Monitor Name, it is possible to assign an individual name. The MTE used for monitoring should be an MTE on the lowest leaf-level, that is, on attribute level. If an MTE of a higher branch-level (collective MTE) is chosen, then the current and open view in the graphics will show the right alerts but it isn’t possible to process these alerts within the Business Process Monitoring session as the alerts are not replicated there.In order to load the threshold values that are currently valid in the corresponding system, the button can be used.If successfully retrieved, the values are filled in the right-hand columns. If no active settings for the thresholdvalues were found these columns remain empty.To transfer the thresholds values for a single line from right to left, double-click the copy icon.© 2010 SAP AG page 14/14
  15. 15. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts PlanningOther CCMS Monitors Unlike all other Monitoring Types the Other CCMS Monitoring provides the opportunity to assign MTEs from other systems than the one system the actual business process step is assigned to.As an example, you could be interested in monitoring the availability from a Portal system that possesses noCCMS but is included as one business process step in your business process. Now, you could use one MTEin the CCMS of the SAP Solution Manager to monitor the heartbeat of the Portal. You could then assign thecorresponding alert via Other CCMS Monitoring to business process step running on the Portal system.1.7.4.9 Analysis and Monitoring ToolsIt is possible to specify analysis transactions or URL addresses (including file directories) per monitoringobject. In the case of analysis transactions, these should be used to analyze errors or problems either locallyin the SAP Solution Manager system itself (Call Option “1”), or directly in the respective satellite systems (CallOption “2”). By default, some standard transactions are maintained, for example, transaction SM37, thatprovides a job overview in an SAP System, is maintained for Background Jobs or transaction SLG1 to have alook into the application log.It is also possible to add new transactions; this could be standard transactions or customer self-writtentransactions.© 2010 SAP AG page 15/15
  16. 16. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts PlanningAnalysis & Monitoring TransactionsOn the second tab strip, it is possible to specify a URL which should be called to further analyze the givenproblem. This is especially interesting if you have some knowledge documents linked to a portal. You define aShort text and the URL to be called. For web pages to be called, specify the full URL, for example, http://help.sap.com. For content available on file servers specify the full file path, using the nomenclature: file://<server>..., for example, file://server1operations_documentsoperations-handbook.txtAnalysis & Monitoring URLThe specified transactions or URLs will be available in the form of buttons within a business process stepwhen using the monitoring later on inside the Business Process Monitoring Session. By pressing thesebuttons (for example, ), the user will jump directly into the correspondingtransaction either in the SAP Solution Manager system (here: SAT) or the connected satellite system (here:CT1) for further analysis. For URLs, the button (for example, ) contains the short text(limited to 20 characters) from the set-up session and leads the user to the defined URL in a newly openedbrowser window.© 2010 SAP AG page 16/16
  17. 17. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts Planning1.7.4.10 Monitoring ActivitiesMonitoring activities should be set up for every Monitoring Object within a business process step. Allmonitoring objects defined within a business process step are listed here. To ensure effective monitoring andefficient problem resolution, the responsibilities should be assigned and problem resolution proceduresshould be defined as described in the following table. Some information is taken from the previous node‘Solution Support Organization’. Monitoring Team Defines the team that is responsible for monitoring the relevant Monitoring Object. Use value help [F4]. Person Resp. Defines the Person who is responsible for monitoring the Monitoring Object. Use value help [F4]. Frequency Describes how often the responsible person should process the required monitoring activity. Start Time Describes at which time the responsible person should process the required monitoring activity. Problem Indicator A description about what indicates a problem. Error Handling Describes how to react on problems or errors, that is, how to solve the problem/correct the error. Escalation Path Describes the escalation path in case that the person responsible could not solve the problem. Persons who can be contacted should be maintained here.Additional information related to this business process step can be entered in the tables ‘MonitoringActivities’, ‘Error Handling’, ‘Restart of Step’ and ‘Escalation Path’. This information would be valid for thewhole business process step and helps users who have to carry out the monitoring and who are not sofamiliar with that particular business process.1.7.4.11 NotificationsNotifications can be set up for the whole business process or for each business process step individually.There are two types of notifications: Workflow notifications and Support notifications. Workflow notificationsallow sending messages in case of alerts to a specified Recipient. This could be an e-mail or an SAPOfficemail.Support notifications allow the setting up of a service desk message in case of an alert. The informationentered for the service desk message serves as a template. The service desk message can be createdmanually or automatically.On business process level, it is possible to define notifications for the whole business process, that is, assoon as the business process gets an alert status, notifications will be triggered. Alternative notifications canbe defined for every Monitoring Type individually, for example, all alerts related to all background jobs of thebusiness process are forwarded to a defined e-mail address.Notifications defined on business process step level will overrule the configuration made on business processlevel for this particular step.1.7.4.11.1 Workflow Notification Sender Must be a user within in the monitoring client of SAP Solution Manager. This user can be even a system user without any roles or profiles, but the user must have a valid e-mail address that is known by the used mail-server Recipient Depending on the Recipient Type the recipient name is required. This could© 2010 SAP AG page 17/17
  18. 18. Best Practice for Solution Operations Manage Operations for SAP APO: Service Parts Planning Address be any e-mail address, an SAP user name in the same system, a Remote SAP name or a shared distribution list. In the case of an SMS, you need to enter “SMS:<cell phone or pager number>” Reci. Type There are currently 5 different Recipient Types: U (e-mail), K (for SMS and Pager), B (SAP user name), R (Remote SAP name) and C (shared distribution list). No. of Yellow The number of YELLOW alerts that may occur before an automatic Alerts notification is triggered No. of Red Alerts The number of RED alerts that may occur before an automatic notification is triggered Max Wait Time Once the maximum wait time [hours] has elapsed, a notification is created, [h] even if the thresholds are not exceeded RED Only To restrict this mechanism only to red alerts, the flag in column RED Only must be set. Detailed Triggers a long text for e-mails or SAPOffice mails, for example, name of the solution, name of the business process step, …)1.7.4.11.2 Support Notifications Priority Defines the priority of the Support Notification. Queue Defines the support component on which the message is put. This component must exist within the service desk. Processor Defines a default processor who should process the message. The processor must be known within the service desk and must be an SAP user name that is defined as a Business Partner with the role “Employee”. Text Template Text templates can be defined that will then be available for service desk messages manually created for alerts. Automatic Support Notifications will be created automatically depending on the alert thresholds. Reporter Necessary when service desk messages are created automatically. Must be an SAP user name who is defined as a Business Partner with the role “General”. Num. of YELLOW Necessary when service desk messages are created automatically, for Alerts example, after 10 yellow alerts a service desk message should be created. Num. of RED Necessary when service desk messages are created automatically, for Alerts example, after 5 red alerts a service desk message should be created. If, in addition to queue, processor, priority, and reporter, either one of the columns “Num of YELLOW Alerts” or “Num of RED Alerts” is filled with a value the automatic Support Notification creation is configured. If both columns are filled with a value, the automatic Support Notification creation works with a logical OR operation. Hence, with the figures in the table above the system would create a Support Notification if either more than 9 yellow alerts OR more than 4 red alerts exist, for which no Support Notification has been created yet. 1.7.5 Business Process Monitoring Process For a successful and efficient implementation of a Business Process Monitoring concept, a process for the execution of the monitoring concept has to be defined. This includes the definition and assignment of the © 2010 SAP AG page 18/18
  19. 19. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts Planningroles and responsibilities involved. It has to be defined who is supposed to carry out which activity within theprocess and how communication between the different roles within the support organization is supposed totake place.A Business Process Monitoring concept has to be tightly integrated with the support organization. Thisincludes the integration with the Incident/Problem Management process and the Change Managementprocess. These processes have to be adjusted to the Business Process Monitoring concept so thatcommunication and escalation procedures are adequate to support the Business Process Monitoring conceptincluding the final communication of open alerts to SAP.Wherever communication connected with Business Process Monitoring happens outside these supportprocesses, separate communication and escalation paths and procedures have to be defined.Please see the above mentioned separate Best Practice for General Business Process Management forfurther details.© 2010 SAP AG page 19/19
  20. 20. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts Planning2 Business Process Monitoring for Service Parts PlanningService Parts Management (SPM) is a comprehensive, end-to-end solution for supporting and managing theextended service parts network. It encompasses the entire range of service parts management activities,including planning, procurement, warehousing, order fulfillment, collaboration and analytics.The SAP solution for service parts management was developed in a system landscape containing SAP ECC,SAP CRM, SAP SCM (including SAP Advanced Planning and Optimization (APO) – Service Parts Planning(SPP)), SAP Supply Network Collaboration (SNC), and SAP Extended Warehouse Management (EWM)),SAP GRC Global Trade Services (GTS) and SAP NetWeaver (including SAP Process Integration (SAP PI)and SAP Business Information Warehouse (SAP BI)).This section will show you, based on an example scenario, what business process monitoring for ServiceParts Planning (SPP) with SAP SCM APO should look like. It will introduce you to generic thoughts and ideashow to identify a business process step you could keep an eye on and makes you familiar with how to choosethe most promising monitoring possibilities from the available ones.To make this clearer to you, we have situated the example process in the fictional company “AutoMan”.2.1 Sample ScenarioAutoMan is a car service parts provider. Its main business is to sell service parts of cars. AutoMan getsservice parts from different suppliers, distributes them through its supply chain network – warehouses atdiverse levels, and provides them finally to customers – car dealers.To improve the service level and optimize its operation costs, AutoMan needs a planning tool to enable itsservice parts distribution network: to forecast parts demand to derive optimal stocking levels for each location based on installed base and service levels to plan parts replenishment and to rebalance the inventory within the networkThe planning tool AutoMan uses is Service Parts Planning (SPP). The following chapter takes you step bystep through the 10 core business processes steps, explaining where and how you can identify focus pointsfor Business Process Monitoring. For each business process step, the most effective way for BusinessProcess Monitoring in the context of the example is highlighted.2.2 Business Process Service Parts PlanningThe graphic below shows the standard 10 steps in SPP process.SPP is a component of SAP SCM APO. It receives sales order data from SAP CRM. This data is maintainedas demand history in the BI (Business Intelligence) part of APO. It is used to plan inventory for products atlocations (step 2 and step 5) and to calculate forecasts (step 4). With these results, SPP can evaluate surplusor obsolete stocks (step 6). Further, DRP run (step 7) organizes replenishment planning within a bill ofdistribution (BOD) – distribution network for a product. The planned procurement will then be approved andsent to SAP ECC, where the procurement can be executed. The results return to SPP and then deployment(step 9) controls the distribution of incoming goods within the BOD on the basis of current demand.Afterwards, inventories within a BOD are balanced. The planned stock transfers are sent to ECC forexecution.In SPP, Planning Service Manager (PSM) is used for planning in background in general. Users can schedulethe planning services, which are needed for a business process, in a planning profile. The PSM then runs thisplanning profile in the background according to the settings. The program for PSM is /SAPAPO/PE_EXEC,transaction /SAPAPO/PE_RUN, the results can be reviewed in PSM application log (transaction:/SAPAPO/PE_LOG_DISP).© 2010 SAP AG page 20/20
  21. 21. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts PlanningNote: Each section about a business step will be structured in the following way, where the “X” stands for theBusiness Process Step number:2.2.X.1 Description2.2.X.2 Monitoring Requirements2.2.X.3 Monitoring Objects in SAP Solution Manager2.2.X.4 Further Monitoring Objects (if applicable)2.2.X.5 Monitoring without SAP Solution Manager2.2.X.6 How to Find Meaningful Thresholds per Monitoring Object2.2.X.7 Background Job Scheduling Requirements (if applicable)SPP Business process SAP CRM Host - MOBILE SAP APO SAP ECC Sales Orders (1) Capture Demand History (7) Distribution Requirements Planning (2) Stocking and De- (8) Procurement Approval Stocking Procurement (3) Manage Demand History Execution (4) Forecasting (9) Deployment (5) Economic Order Quantity (10) Inventory Balancing & Safety Stock Stock Transfer (6) Surplus & Obsolescence Execution PlanningPlease note that this chapter only focuses on describing Business Process Monitoring for the steps carriedout in SAP APO as shown in the graphic above. Business Process Monitoring for the steps executed in SAPCRM or SAP ECC is not part of it.Available Monitoring objects for the scenario “Procure-to-stock” (using further solutions like SNC, EWM andERP) are briefly described in section 4.2 in the Appendix of this document.2.2.1 Business Process Step 1: Capture Demand History2.2.1.1 DescriptionGeneral Information:AutoMan uses SAP CRM to manage customers. With the BI workbench (transaction: RSA1) in APO, thesystem extracts SAP CRM sales order data to SAP APO BI and saves it in the DataStore object0CRM_SALO. The InfoSource 80CRM_SALO takes its data from this DataStore object. This data transferbetween CRM and APO uses standard IDOCS with RFC connection. Then the system uses update rules to© 2010 SAP AG page 21/21
  22. 22. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts Planningprocess and check the data, and saves it as demand history in the InfoCube 9ADEMAND, together with theraw data in the DataStore object 9ARAWDAT (also see step 3).The system captures the demand history in the InfoCube 9ADEMAND as follows:- The system aggregates the demand in weeks.- The system aggregates the demand in months.- The system aggregates the demand in posting periods.- The system aggregates the demand along the BOD.In doing so, the system captures both the demand history of a product at each stockholding location and ateach entry location. However, the system only uses the demand history of the stockholding location forforecasting.The system creates the yearly demand history that both phase-out planning and surplus and obsolescenceplanning require. To do so, the system uses the data in the InfoCube 9ADEMAND and extracts it into theInfoCube 9ADEMANN.Specific InformationAs an alternative to the process described above, you can also load sales order data from other sources,such as from a flat file or a CSV file, or from SAP ECC. If the sales orders come from an external flat or CSVfile, the InfoSource 9A_SPP_CD_CSV_LOAD is used instead of 80CRM_SALO.AutoMan processes sales orders loading at a monthly base, always at the beginning of a month. In RSA1, theprocesses can be scheduled as background job.2.2.1.2 Monitoring Requirements:Error Monitoring:It is important to monitor if the data from CRM are loaded to APO BI successfully. That means if the dataloaded is complete and if all data is correct.Performance Monitoring:The data load should be finished in a timely manner. Whether performance monitoring is necessary dependson the individual business requirements. It depends on the data volume and the time window for the load.Usually, the initial load takes the most time. Later, if the data load only aims to update, the load time could bemuch shorter.Data Consistency Requirements:The data loaded to APO BI should be consistent to the original data in CRM.© 2010 SAP AG page 22/22
  23. 23. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts Planning2.2.1.3 Monitoring Objects in SAP Solution Manager Monitoring Selection Alert Analysis Tool on Monitoring Object Criteria Satellite System Frequency / Data CollectionIDoc Monitoring On object level: ‚Delta‘ monitor: BD87, WE05 “Delta” Check: every(IMIDOC01) Direction, Port, number of suitable two hours(For data exchange Partner number, IDocs since the lastbetween CRM and Partner type, data collection “Total” Check forAPO BI via IDoc) Partner function, erroneous Idocs: Message type, ‚Total number‘ Daily before data Basic type, monitor: number of processing in BI Message code, suitable IDocs for starts with a Message function, the last x days considerable time IDoc age. (in hours) frame between the Data Collector run On key-figure and the start of data level: processing in BI in order to have Status number(s), enough time to Status message solve any errors qualifier, Status Monitoring might message ID, Status detect message number, Status age (in min) (IDoc types are RSREQ, RSSEND and RSINFO)qRFC Monitor qRFC direction, Number of entries SMQ1, SMQ2, Hourly (or even(IMQRFCMO) RFC destination, with critical status in SM59 more often)(Status Monitoring Queue group, groupof the queue set up Command string of Age of oldestfor data exchange SMD qRFC backlog critical status inbetween the CRM coll., Command groupsystem and the BI- string of SMD qRFC Combination ofpart of SAP APO) status coll. "Entries" and "Age"(The queue names in critical statestart with CF*) Number of entries with interim status in group Age of oldest interim status in group Combination of "Entries" and "Age" in interim state© 2010 SAP AG page 23/23
  24. 24. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts PlanningqRFC Monitor qRFC direction, Number of SMQ1, SMQ2, Hourly (or even(IMQRFCMO) RFC destination, individual queues in SM59 more often)(Backlog Monitoring Queue group, groupof the queue set up Command string of Total number offor data exchange SMD qRFC backlog entries in all queuesbetween the CRM coll., Command of groupsystem and the BI- string of SMD qRFC Average number ofpart of SAP APO) status coll. entries per queue in(The queue names groupstart with CF*) Maximum number of entries per queue in group Age of oldest entry in group Combination of "Total entries" and "Oldest age"BI Query Alert RFC Destination KPI in BI Query Once per dayCollector - KPI in BI (from managed (single value), KPIQuery (BOBIQUAC) system to BI in BI Query (max.(To check data system), Info values), KPI in BIstored in APO BI) Provider (of BI Query (# of values) system), BI queries (of that Info provider), Description of the BI queryBI Consistency Compare Result Differences in result Once per dayCheck Result DSO, Fieldname column 1,Collector and Select-Options Differences in result(DBICCRC) for Filter 1 - 3 column 2, Differences in result column 3, Differences in result column 4, Differences in result column 5, Age of last consistency check resultFile Monitoring File Path, File Creation Time of AL11 Once per day (or(BOFILMON) Name, Pattern, User File, File Size, File more frequently(If flat files are used (File Creator) Age (in min) depending on theto load sales order businessdata into APO BI) requirements – how often data from flat files is imported)Background Job Background Job Start Delay, End SM37 Data Collectors toMonitoring for all Name, Variant, Delay, Maximum be scheduled to runprocesses Event Parameter Duration, Job only duringscheduled in and Event ID (in Cancellation, Job timeframe oftransaction RSA1 in case process chains Log Messages, Job planned Jobthe APO BI system are used) Log Content Execution and to(Job names starting run every 5 minuteswith BI_*) during this time frame© 2010 SAP AG page 24/24
  25. 25. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts Planning2.2.1.4 Monitoring without SAP Solution ManagerIf IDoc transfer is used, you should use transactions BD87 and WE05 to check for erroneous messages atleast every two hours.The status, runtime, and job logs of Background Jobs can be analyzed using transaction code SM37 in themanaged system.If you are using qRFC for data transfer, the status of your qRFC queues can be monitored using transactioncodes SMQ1 or SMQ2. In case of problems with the setup of your qRFC connection, use transaction SM59 tocheck the setup of the respective RFC Connection.If you use Flat Files to import data into your system, you can also use transaction code AL11 to check thefiles directories on your SAP system.2.2.1.5 How to Find Meaningful Thresholds for Each Monitoring ObjectThe definition of meaningful thresholds for each Monitoring Object needs to be done in close cooperation withyour business department. It is important that you clearly define what data the data collectors measure, howoften they run, and what the business requirements are for the analyzed part of the business process step.Furthermore, it is important to review the defined thresholds on a regular basis to ensure that they are setaccording to the business requirements that might change over time.2.2.2 Business Process Step 2: Stocking and De-stocking2.2.2.1 DescriptionGeneral Information:The planning services Stocking and Destocking make a “to stock” or “not to stock” decision for each locationproduct at the start of inventory planning. The result of these planning services is to set a replenishmentindicator on each location product. According to the indicator, the system orientates itself in the furtherplanning: to keep stock or not.During these planning services: The system checks the demand of all customer-facing locations. If a customer-facing location has a highdemand, it is advisable to make a Stocking decision. For low demand, a Destocking decision is advisable. The Destocking decision service checks if there is an exclusion reason for the corresponding locationproduct. If so, the Destocking decision does not perform any more checks and sets the Not Stocked, Lockedindicator, as well as the blocking indicator for the corresponding location product. This means that the systemcannot build up stock of this location product, and the Destocking service cannot change the replenishmentindicator. The system checks the entries in the decision tables. Based on these entries, the system then decideswhether to plan stocking or Destocking for each location product. For the locations for which the system plans stocking according to the decision tables, the stockingservice checks whether this stocking is also allowed according to the exception rules. The system transfers the Stocking and Destocking decisions made for the customer-facing locations tothe corresponding parent locations.These planning services are carried out in PSM - either in background or interactively. A planning profileneeds to be defined for the service.© 2010 SAP AG page 25/25
  26. 26. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts PlanningSpecific Information:Additional triggers for the stocking service can be demanded at a non-stock location or changes to the virtuallocations for consolidated ordering.Important settings:Service Profiles – control the definition of the stocking and de-stocking decisions (in Customizing)Decision tables – define criteria according to which the system decides to either stock or to de-stock(transaction: /SAPAPO/SPPINVPDEC)Location exclusion rules – responsible for the exclusion reasons for the locations (in customizing &transaction: /SAPAPO/PINV_EX_MAIN )2.2.2.2 Monitoring Requirements:Error Monitoring:It is necessary to check if these planning services run successfully in PSM. The results of these planningservices can be seen in the PSM application log (transaction: /SAPAPO/PE_LOG_DISP). And the run statusof a run in PSM can be seen in background job log.Performance Monitoring:If a fixed time window is defined for these planning services, you need to monitor the performance ofcorresponding PSM run.In our experience, the access to historical data in APO BI takes quite a long time.2.2.2.3 Monitoring Objects in SAP Solution Manager Monitoring Selection Alert Analysis Tool on Monitoring Object Criteria Satellite System Frequency / Data CollectionDialog Performance Transaction Code Total Response STAD, ST03N Every two hoursMonitor (Value 1), Function Time, Database(BOPERFMO) Code (Value 2), Call Response Time,(For Monitoring Type, User Pattern, Total Responseresponse time of Instances Time (Data vol.-transaction code depend.)/SAPAPO/PE_RUN)Background Job Background Job Start Delay, End SM37 Daily (or moreMonitoring for Name, Variant, User Delay, Out of Time frequently in caseprogram (Note: The planning Window, Maximum this job is executed/SAPAPO/PE_EXEC profile is visible in Duration, Job more than once per the job log) Cancellation, Job day), Data Log Messages, Job Collectors to run Log Content every 5 minutes during job execution2.2.2.4 Further Monitoring Objects Monitoring Selection Alert Analysis Tool on Monitoring Object Criteria Satellite System Frequency / Data CollectionResults of planning Subobjects PSM Application Transaction Code Dailyservices in PSM (Services), Date and Log Content /SAPAPO/PE_LOG_DISPapplication log Time of Planning Run, User that triggered Log© 2010 SAP AG page 26/26
  27. 27. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts Planning2.2.2.5 Monitoring without SAP Solution ManagerThe Dialog Response Time of transaction code /SAPAPO/PE_RUN can be checked in transaction codeSTAD or ST03N.The status, runtime, and job logs of Background Jobs can be analyzed using transaction code SM37 in themanaged system.2.2.2.6 How to Find Meaningful Thresholds for Each Monitoring ObjectThe definition of meaningful thresholds for each Monitoring Object needs to be done in close cooperation withyour business department. It is important that you clearly define what data the data collectors measure, howoften they run, and what the business requirements are for the analyzed part of the business process step.Furthermore, it is important to review the defined thresholds on a regular basis to ensure that they are setaccording to the business requirements that might change over time.2.2.3 Business Process Step 3: Manage Demand History2.2.3.1 DescriptionIn this step, the system adjusts the captured demand history according to the requirements of SPP.The manual adjustment of demand history can be executed in the system with transaction/SAPAPO/SPPDMDH.To ensure that the demand history reflects changes, the system also adjusts the demand historyautomatically when various events occur and realigns the data.The system initiates data realignment of the demand history either with triggers or you have to havescheduled it as a regular service in the Planning Service Manager (PSM). The following table provides anoverview of the events for which data realignment is necessary and which planning services perform thisrealignment:Event Planning Service Technical Name of Planning Service Triggered byChange to SPP: Data SPP_PDEM_SERPAT_RLG ---location Realignment fordetermination Loc.Det.SchemaprocedureStocking or SPP: Data Real. For SPP_PDEM_STOCKING_RLG SPP_REPL_INDI_CHANGEDestocking Stocking/DestockingdecisionChange to SPP: Data SPP_PDEM_TPOP_RLG SPP_NON_TPOPTPOP status Realignment for and TPOP SPP_TPOPAssignment of SPP: Create Demand SPP_PDEM_BOD_ASSIGN SPP_NEW_BOD_ASSIGNfuture BOD to History Future BODproductDeletion of SPP: Delete Demand SPP_PDEM_BOD_DELETE SPP_BOD_DELETEfuture BOD History Future BOD (assignment© 2010 SAP AG page 27/27
  28. 28. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts PlanningFuture BOD SPP: Data SPP_PDEM_BOD_VALID ---becomes valid Realignment for BOD ChangeSuppression SPP: Data SPP_PDEM_SUPERSESSION_RLG --- Realignment for SuppressionPromotion SPP: Data SPP_PDEM_PROMOTION_RLG --- Realignment for PromotionChange to final SPP: Adjustment of SPP_PDEM_OVR_RLGdemand Demand History2.2.3.2 Monitoring Requirements:Error Monitoring:It is necessary to check the results of the realignment. The status of the realignment can be reviewed withtransaction /SAPAPO/PDEM_RLGSTEP, and the process of realignment can be reviewed in PSM applicationlog or with general application log list (transaction SLG1).Performance Monitoring:If the performance of data realignment needs to be monitored depends on the frequency of this services andthe fixed time window.Data Consistency Requirements:The update of the demand history only takes place in SCM APO, the original data in SCM CRM do not needto be updated accordingly.Monitoring Objects:Triggers need to be activated for regeneration of the demand history (SPP_BOD_DELETE,SPP_NEW_BOD_ASSIGN, SPP_REPL_INDI_CHANGE) and for setting the planning services for demandhistory creation (SPP_RLG_DONE, SPP_RLG_DONE)2.2.3.3 Monitoring Objects in SAP Solution ManagerMonitoring Object Selection Alert Analysis Tool on Monitoring Criteria Satellite System Frequency / Data CollectionDialog Performance Transaction Code Total Response STAD, ST03N Every two hoursMonitor (BOPERFMO) (Value 1), Function Time, Database(For Monitoring Code (Value 2), Call Response Time,response time of Type, User Pattern, Total Responsetransaction code Instances Time (Data vol.-/SAPAPO/SPPDMDH) depend.)Application Log Object, Sub-Object, Total number of SLG1 Every two hours(Transaction Code User, Transaction, messages, numberSLG1) for Object Program of critical messages,« /SAPAPO/PE » and Runtime, Planningcorresponding sub- Scope, Planningobjects Results© 2010 SAP AG page 28/28
  29. 29. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts Planning2.2.3.4 Further Monitoring Objects Monitoring Selection Alert Analysis Tool on Monitoring Object Criteria Satellite System Frequency / Data CollectionResults and status Info Provider, Status of Transaction Code Every two hoursof realignment Realignment Status, realignment steps /SAPAPO/PDEM_RLGSTEP Validity Date, Author, Last Changed by, Generated Realignment Step, Generation ProgramRealignment Subobjects PSM Application Transaction Code Dailyprocessing (Services), Date Log Content /SAPAPO/PE_LOG_DISP and Time of Planning Run, User that triggered Log2.2.3.5 Monitoring without SAP Solution ManagerThe Dialog Response Time of transaction code /SAPAPO/SPPDMDH can be checked in transaction codeSTAD or ST03N respectively.The general application log can be viewed in transaction code SLG1.2.2.3.6 How to Find Meaningful Thresholds for Each Monitoring ObjectThe definition of meaningful thresholds for each Monitoring Object needs to be done in close cooperation withyour business department. It is important that you clearly define what data the data collectors measure, howoften they run and what the business requirements are for the analyzed part of the business process step.Furthermore it is important to review the defined thresholds on a regular basis to ensure that they are setaccording to the business requirements that might change over time.2.2.4 Business Process Step 4: Forecasting2.2.4.1 DescriptionGeneral Information:The forecasting service covers the whole life cycle of a product from phase-in planning for new products,through various types of product interchangeability, to phase-out planning for products in discontinuation. Theforecasting service is flexible in reacting to changing demand, and uses various forecast models to planindividually for future demand for products that have differing sales behavior.You can either schedule the forecast run as a regular PSM planning service or you can start it manually onthe Interactive Forecasting screen (transaction: /SAPAPO/SPPFCST). During the forecast run, the systemcalculates the forecasting results at location product level. If you are not satisfied with the results, you canmake manual corrections or adjustments to the demand history, forecast profiles (transaction/SAPAPO/SPPFCSTPRF), and PSM service profiles, and then restart the forecast run.The results of forecasting are stored in key figure “Final forecasts” in TSDM (database).© 2010 SAP AG page 29/29
  30. 30. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts PlanningComposite ForecastThere are various functions available within the forecast service. If you want to use several of these functions,you must schedule the forecast service more than once and assign a different service profile each time.To achieve a better quality for the forecasts, PSM can execute the functions in figure above in a fixedsequence. This is called composite forecasts. AutoMan uses composite forecasts.Its functions include: Model Evaluation (Automatic Model Evaluation): consists of Trigg’s tracking signal and tripping. Trigg’s tracking signal checks whether the forecast model is still optimal or whether there is a systematic forecasting error. Tripping reinitializes basic values and the deviation of an existing forecast model and shortens the demand history used for forecast creation. Model Selection (Automatic Model Selection): You can use it to automatically determine the forecast model best suited to a specific location product. Smoothing Parameter Tuning (Rough Tuning): For the forecast models that consider smoothing factors during forecast creation, you can automatically optimize these smoothing factors by this function. Forecast Calculation (Forecast Approval): calculates the final forecast for each location product and checks which forecast results require manual approval according to rules that you define. The system automatically approves all other forecast results and provides these results to other SPP planning services. Forecast approval is realized as a PSM planning service. However, the system also performs forecast approval when you save the forecast results on the Interactive Forecasting screen manually.Additional information:Besides the above mentioned functions, forecast services also include the following functions: Historical Forecasts: to ensure an exact planning, the system records all calculated forecast results as historical forecasts. You can also schedule the PSM planning service Recalculation of the Forecast in the Past. If the forecast model changes, the system triggers this planning service so that it creates historical forecasts for the new combination of location product and forecast model. Phase-In Planning: uses values based on experience to calculate forecast values for new products that do not yet have any historical data. Phase-in planning is realized as a PSM planning service. Phase-Out Planning: calculates forecast values at entry location level for products in discontinuation. Phase-out planning is realized as a PSM planning service.© 2010 SAP AG page 30/30
  31. 31. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts Planning2.2.4.2 Monitoring Requirements:Error Monitoring:It is important to check the results of forecasts. They can be reviewed in the Interactive Forecasting screen(transaction: /SAPAPO/SPPFCST) or application log of PSM. If the results are not satisfying, planningparameters and forecast models can be modified, and further forecasts run can be started manually orscheduled via PSM.Performance Monitoring:Whether the performance of forecasting needs to be monitored depends on the frequency of these servicesand the fixed time window. Especially for composite forecast includes several services and it run time shouldbe controlled strictly.2.2.4.3 Monitoring Objects in SAP Solution Manager Monitoring Object Selection Alert Analysis Tool on Monitoring Criteria Satellite System Frequency / Data CollectionBackground Job Background Job Start Delay, End SM37 Daily (or moreMonitoring for program Name, Variant, User Delay, Out of Time frequently in case/SAPAPO/PE_EXEC (Note: The planning Window, Maximum this job is executed profile is visible in Duration, Job more than once per the job log) Cancellation, Job day), Data Log Messages, Job Collectors to run Log Content every 5 minutes during job executionDialog Performance Transaction Code Total Response STAD, ST03N Every two hoursMonitor (BOPERFMO) (Value 1), Function Time, Database(For Monitoring response Code (Value 2), Call Response Time,time of transaction code Type, User Pattern, Total Response/SAPAPO/SPPFCST) Instances Time (Data vol.- depend.)Dialog Performance Transaction Code Total Response STAD, ST03N Every two hoursMonitor (BOPERFMO) (Value 1), Function Time, Database(For Monitoring response Code (Value 2), Call Response Time,time of transaction code Type, User Pattern, Total Response/SAPAPO/SPPFCSTPRF) Instances Time (Data vol.- depend.)2.2.4.4 Further Monitoring Objects Monitoring Selection Alert Analysis Tool on Monitoring Object Criteria Satellite System Frequency / Data CollectionForecast results in Subobjects PSM Application Transaction Code DailyPSM application log (Services), Date and Log Content /SAPAPO/PE_LOG_DISP Time of Planning Run, User that triggered LogForecast results in Detailed forecast Transaction Code DailyInteractive results /SAPAPO/SPPFCSTForecasting Screen© 2010 SAP AG page 31/31
  32. 32. Best Practice for Solution OperationsManage Operations for SAP APO: Service Parts Planning2.2.4.5 Monitoring without SAP Solution ManagerThe Dialog Response Time of transaction codes /SAPAPO/SPPFCST and /SAPAPO/SPPFCSTPRF can bechecked in transaction code STAD or ST03N respectively.The status, runtime, and job logs of Background Jobs can be analyzed using transaction code SM37 in themanaged system.2.2.4.6 How to Find Meaningful Thresholds for Each Monitoring ObjectThe definition of meaningful thresholds for each Monitoring Object needs to be done in close cooperation withyour business department. It is important that you clearly define what data the data collectors measure, howoften they run, and what the business requirements are for the analyzed part of the business process step.Furthermore, it is important to review the defined thresholds on a regular basis to ensure that they are setaccording to the business requirements that might change over time.2.2.5 Business Process Step 5: Economic Order Quantity & Safety Stock2.2.5.1 DescriptionGeneral information:In this step, the system plans the economic order quantity (EOQ) – purchase order, and safety stock (SFT)together, to optimize the stockholding and purchasing costs, as well as to ensure target service level. Thisplanning can either be carried out manually in transaction /SAPAPO/SPPINVP, or planned as a service inPSM (service name: SPP_EOQSFT_SERVICE). The results are stored in key figures “economic orderquantity” and “Location’s own safety stock” in TSDM.The system calculates the EOQ and SFT with mutual dependence. As a basis for the combined calculation,the system chooses whether to use normal distribution or Poisson distribution as the calculation model foreach location product depending on its sales behavior. Normal distribution is suitable for products withconstant demand and Poisson distribution is suitable for products with intermittent demand. The modelselection for a location product is made with transaction /SAPAPO/PINV_MS_MAIN.For normal distribution, the system uses the forecast values for demand in pieces as the basis for thecombined calculation of EOQ and SFT. For Poisson distribution, the system uses the forecast values for thenumber of order items as the basis, and then calculates the demand in pieces using the average demandsize per order item.The system also decides whether to plan the stock of each location product constantly or not constantly.Constantly means that the planned EOQ and SFT are the same for each period. Not constantly means thatresults vary for each period. This is defined in customizing.Important settings:Service Profile – Service profile for EOQ/SFT calculation.Forecast Strategy – Forecast types and decides whether they are to follow constant or non-constantplanningMaster Data– In the location product master data on the SPP Inventory Planning tab:EOQ/SFT Calculation field: indicates whether the system is to use Normal or Poisson distribution as thestatistical calculation model for the combined calculation of EOQ and safety stockFix EOQ Period field: you can choose between EOQ Manually Locked, EOQ POD Manually Locked, andUnlockedMin. EOQ Per. and Max. EOQ Per. Fields: to indicate the minimum and maximum number of days that anEOQ period may last.Safety Stock field: the system considers your manual entry until the next planning run, otherwise this isautomatically filled© 2010 SAP AG page 32/32

×