011000358700001130032008 e manage operations for sap for retail pos inbound

3,092 views

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,092
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
117
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

011000358700001130032008 e manage operations for sap for retail pos inbound

  1. 1. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS Inbound Dietmar-Hopp-Allee 16 D-69190 Walldorf CS STATUS internal final DATE VERSION DEC -17 2007 1.0 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 for Retail: POS InboundDate Alteration Reason VersionDec 1, 2008 Creation 0.1Dec 17, 2008 Finalization 1.0Table of Contents1 Management 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 7 1.7.4.1 Application Monitor 8 1.7.4.2 Background Job 9 1.7.4.3 ABAP Dump Collector 9 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 18 1.7.6 Legend 192 Business Process Monitoring for POS Inbound 20 2.1 Business Process POS Inbound 20 2.1.1 Business Process Step 1: Poll and Send Sales Data 21 2.1.1.1 Description 21 2.1.2 Business Process Step 2: Receive, Transform and Send Information 21 2.1.2.1 Description 21 2.1.3 Business Process Step 3: Process Sales Data (P01) 21 2.1.3.1 Description 21 2.1.3.2 Monitoring Requirements: 22 2.1.3.3 Monitoring Objects in SAP Solution Manager 22 2.1.3.4 Monitoring without SAP Solution Manager 23 2.1.3.5 Scheduling of Background Jobs 23 2.1.4 Business Process Step 4: PIPE Processing (P02) 23© 2008 SAP AG page 2/53
  3. 3. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS Inbound 2.1.4.1 Description 23 2.1.5 Business Process Step 4a: Checks and Verification in PIPE 24 2.1.5.1 Description 24 2.1.5.2 Monitoring Requirements 24 2.1.5.3 Monitoring Objects in SAP Solution Manager 24 2.1.5.4 Further Monitoring Objects 25 2.1.5.5 Monitoring without SAP Solution Manager 25 2.1.6 Business Process Step 4b: Jobs in One-step Processing 25 2.1.6.1 Description 25 2.1.6.2 Monitoring Requirements: 26 2.1.6.3 Monitoring Objects in SAP Solution Manager 26 2.1.6.4 Monitoring without SAP Solution Manager 26 2.1.6.5 Scheduling of Background Jobs 26 2.1.7 Business Process Step 4c: Jobs in 2-step Processing 27 2.1.7.1 Description 27 2.1.7.2 Monitoring Requirements: 27 2.1.7.3 Monitoring Objects in SAP Solution Manager 27 2.1.7.4 Monitoring without SAP Solution Manager 28 2.1.7.5 Scheduling of Background Jobs 28 2.1.8 Business Process Step 4d: The Message Log Application 28 2.1.8.1 Description 28 2.1.8.2 Monitoring Requirements: 29 2.1.8.3 Monitoring Objects in SAP Solution Manager 29 2.1.8.4 Further Monitoring Objects 29 2.1.8.5 Monitoring without SAP Solution Manager 30 2.1.8.6 Scheduling of Background Jobs 32 2.1.9 Business Process Step 4e: Data Consistency between POS System and PIPE 33 2.1.9.1 Description 33 2.1.9.2 Monitoring Requirements: 33 2.1.9.3 Monitoring Objects in SAP Solution Manager 34 2.1.9.4 Further Monitoring Objects 34 2.1.9.5 Monitoring without SAP Solution Manager 34 2.1.9.6 Scheduling of Background Jobs 35 2.1.10 Business Process Step 5: Send Data to SAP for Retail (P03) 35 2.1.10.1 Description 35 2.1.10.2 Monitoring Requirements: 36 2.1.10.3 Monitoring Objects in SAP Solution Manager 36 2.1.10.4 Further Monitoring Objects 37 2.1.10.5 Monitoring without SAP Solution Manager 37 2.1.10.6 Scheduling of Background Jobs 37 2.1.11 Business Process Step 6: Post data within SAP for Retail (PO4) 37 2.1.11.1 Description 37 2.1.11.2 Monitoring Requirements: 38 2.1.11.3 Monitoring Objects in SAP Solution Manager 38 2.1.11.4 Monitoring without SAP Solution Manager 39 2.1.11.5 Scheduling of Background Jobs 39© 2008 SAP AG page 3/53
  4. 4. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS Inbound 2.1.12 Business Process Step 7: Update BI Info Cubes (P05) 39 2.1.12.1 Description 39 2.1.12.2 Monitoring Requirements: 40 2.1.13 Business Process Step 8: Update SAP F&R (P06) 40 2.1.13.1 Description 40 2.1.13.2 Monitoring Requirements: 40 2.1.13.3 Monitoring Objects in SAP Solution Manager 41 2.1.13.4 Further Monitoring Objects 41 2.1.13.5 Monitoring without SAP Solution Manager 41 2.1.13.6 Scheduling of Background Jobs 41 2.1.14 Business Process Step 9: Extraction of Master Data for BI (P07) 42 2.1.14.1 Description 423 Further Information 43 3.1 Troubleshooting 43 3.2 Related Best Practice Documents 43 3.3 Literature 43 3.4 Feedback and Questions 444 Appendix 45 4.1 Example Background Job Monitoring 45 4.2 Example PI Message Process Monitoring 46 4.3 Example ALE / IDoc Monitoring 46 4.4 Example Dialog Performance Monitoring 49 4.5 Example Application Log Monitoring 50 4.6 Background Jobs 51© 2008 SAP AG page 4/53
  5. 5. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS Inbound1 Management Summary1.1 Goal of Using this Best PracticeThis Best Practice helps you to set up a Business Process Monitoring concept for your SAP Retail solution.The concept aims to define procedures for business process oriented monitoring and error handling andescalation procedures for your business process “POS Inbound”. These procedures intend to ensure asmooth and reliable flow of this core business process so that your business requirements are met.This Best Practice gives orientation for defining suitable application oriented monitoring objects in order todetect any irregularities or deviations from an ideal business process flow or to detect error situationsconcerning a core business process at an early stage.This Best Practice contains the recommended approach from SAP which uses whenever possible the SAPSolution Manager for the Monitoring functionalities. But even if you do not use the SAP Solution Manager werecommend to follow the procedures described in this document as much as possible in order to ensure asmooth and reliable flow of your business processes as well as an appropriate response in case ofunforeseen errors.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 ensure that the process runs smoothly (e.g. 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 that is responsible for the successful execution of the business process. He coordinates all activities necessary for the business process. Therefore, he is usually responsible for the escalation paths in case of problems. Often he is a second level in the escalation procedure, if the application monitoring team needs to escalate an issue.More 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.© 2008 SAP AG page 5/53
  6. 6. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS InboundNecessary or Useful Trainings SM300 Business Process Management and Monitoring E2E300 End-to-end Business Process Integration and Automation Management1.4 System RequirementsIn order to monitor business processes running in your SAP Retail solution via SAP Solution Manager, theSAP Basis Release of the systems to be monitored have to be at least 4.6C. To have all described monitoringobjects available in SAP Solution Manager, the add-on ST-A/PI01L has to be installed on the SAP Retailsystem.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.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 Chapter 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 Chapter 1.7.4 you find further information that is relevant for more than one scenario. In case 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 download 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 Throughput monitoring© 2008 SAP AG page 6/53
  7. 7. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS Inbound 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 inChapter 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 Retailsolution is generally the same. Therefore, you will only find specific performance monitoringrecommendations 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 a SAP Retail system or other software and operated bya company are of particular importance, and Business Process Monitoring is intended to ensure a smoothand reliable operation of the business processes and, thereby, that the core business processes meet acompany’s business requirements in terms of stability, performance, and completeness. The SAP SolutionManager provides a graphic to visualize a company’s (distributed) system and solution landscape and allrelated business processes. By using Business Process Monitoring, it is possible to define and customizealert situations from a basic set of configurable alerts provided by the SAP Solution Manager. These alertsare then visualized by green, yellow, and red alert icons for each individual business process step in thegraphical business process representation. Business Process Monitoring is intended to detect and respond tocritical situations as early as possible in order to solve problems as fast as possible.In addition, the SAP Solution Manager offers extended functionality for error handling and problem resolution.By the 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, a 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 etc.) 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.1.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. The below mentioned Monitoring Types are available:© 2008 SAP AG page 7/53
  8. 8. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS Inbound Application Monitor (Throughput and Backlog Indicators, Data Consistency Checks, Mass Activity Monitors, Due List Log, MRP key figures, User Exit) Background Jobs (Jobs running on SAP Systems with an SAP Basis) Dialog Performance (Dialog transaction performance) Update Error (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. In order to receive detailed information on how to set up the Monitoring Objects in the SAPSolution Manager, 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, please turn to(URL http://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 the Business ProcessMonitoring. The latest Monitoring objects are only provided if the latest ST-A/PI plug-in is installed on thesatellite system. The Service Tool for ST-A/PI is available via the SAP Service Marketplace Quick Link/installations Entry by Application Group -> Plug-Ins SAP Solution Tools ST-A/PI. Please ensure that the ST-A/PI is installed on the SAP Solution Manager system and on the respective satellite. 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 so called 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 toolsFor ERP Logistic the following monitors are available: Sales and Services (e.g. Sales Documents, Invoices) Warehouse Management (e.g. Transfer Requirements, Transfer Orders) Inventory Management (e.g. Goods Movements) Logistics Execution (e.g. Deliveries, Shipments)© 2008 SAP AG page 8/53
  9. 9. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS Inbound Procurement (e.g. Planned Orders, Purchase Requisitions, Purchase Orders) Manufacturing (e.g. Planned Orders, Production or Process Orders, Autom. Goods Movements posted with error, Confirmation Pool errors) Plant Maintenance (e.g. 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 SAP Retail Data ConsistencyThe DCC collectors for Retail are data collectors to retrieve a stored comparison result from an SAP ERPRetail system.There are certain consistency check programs, that can compare Retail-specific data between the SAP ERPRetail system and an SAP SCM system. These comparison programs are able to output their check result notonly to a list or into the spool, but can also permanently store a summary to the ST-A/PIs cluster table. Thesemonitoring objects can be configured to retrieve the number of found inconsistencies out of the storedsummary information and display that as alerts within the SAP Solution Manager Business ProcessMonitoring (Consistency Monitoring).Information about Data Consistency Checks are described in detail in the Setup Guide – Data ConsistencyMonitoring (URL http://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, e.g. time restrictions, restriction of hardware resources (CPU, main memory, …) or existingdependencies between different activities (e.g. invoices can only be created after the corresponding goodsissue is posted, or Back Order Processing and Material Requirements Planning should not run at the sametime) it is very important to ensure the stable run of background jobs. A cancelled background job should beidentified as soon as possible in order to react as fast as possible. Therefore it is also necessary to definerestart procedures and escalation paths.1.7.4.2.1 Monitoring ObjectsBefore 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 what kind of alerts make sense orwhat 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”.1.7.4.3 ABAP Dump CollectorTo provide monitoring features for alerting on occurrences of ABAP dumps of specified runtime errors or tocollect statistical data of ABAP dumps for reporting reasons.© 2008 SAP AG page 9/53
  10. 10. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS Inbound1.7.4.3.1 Monitoring ObjectsThe 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.1.7.4.3.2 Monitoring AlertsPossible Alerts types are the Number of ABAP Dumps (Delta) – all dumps since the last collector run – andNumber 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 an own developed transaction.1.7.4.4.1 Monitoring ObjectsThe monitoring object is the transaction itself. The customizing has to be done in node ‘Dialog Performance’.In table ‘Transactions’ all transactions that are already configured to that business process step are listed.The relevant transactions need to be selected for monitoring. It is also possible to add or to removetransactions within table ‘Add/Remove Transactions’. The monitoring can be performed per SAP instance.Therefore the respective instances have to be selected in table ‘SAP Instances’. All instances that aremaintained for a system are listed there. Table ‘Alert Types’ shows the dialog response time and all parts ofthe response time, like queue time, load and generation time, database request time and the front-endresponse time, that can be monitored. Those times that are relevant for monitoring have to be selected.After saving this node a sub-node ‘Performance Alerts’ will appear where the threshold values have to beentered.© 2008 SAP AG page 10/53
  11. 11. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS InboundMonitoring Objects – Dialog Performance1.7.4.4.2 Monitoring AlertsEach table in the sub-node ‘Performance Alerts’ corresponds to an alert type chosen in the higher-level node,and lists the combinations of specified transaction code and SAP instance.For each combination of transaction code and instance that should be included in the monitoring, thethreshold 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", whereas “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.© 2008 SAP AG page 11/53
  12. 12. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS InboundThe 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, suchas result calculations.1.7.4.5.1 Monitoring ObjectsMonitoring 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.Monitoring Objects - Update Errors1.7.4.5.2 Monitoring AlertsSince 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 directly accessed via transaction V_SA, the billing duelist via transaction V.21. In case of a billing due list, the list contains e.g. a number of sales documents that© 2008 SAP AG page 12/53
  13. 13. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS Inboundneed to be billed. If the billing due list was processed previously and it is important to know which billingdocuments were created from this billing due list, it can be displayed in the due list log for this billing run.1.7.4.6.1 Monitoring ObjectsThe 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’.1.7.4.6.2 Monitoring AlertsFor 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. 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, etc.). 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- or object-oriented recording of events. An object and any sub-object 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.© 2008 SAP AG page 13/53
  14. 14. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS InboundMonitoring 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. Toconfigure 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 and the messagenumber as well as the threshold values for the number of critical messages that are supposed to result inchanges from GREEN to YELLOW and from YELLOW to RED can be specified. It is also possible to use wildcards.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.© 2008 SAP AG page 14/53
  15. 15. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS Inbound The MTE used for monitoring should be a MTE on the lowest leaf-level, i.e. on attribute level. If a 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 work on 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 on the copy icon.Other 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 case of analysis transactions these should be used to analyze errors or problems either locally inthe SAP Solution Manager system itself (Call Option “1”) or directly in the respective satellite systems (CallOption “2”). Per default some standard transactions are maintained, e.g. transaction SM37, that provides ajob overview in an SAP System, is maintained for Background Jobs or transaction SLG1 to have a look intothe application log.It is also possible to add new transactions; this could be standard transactions or customer self-writtentransactions.© 2008 SAP AG page 15/53
  16. 16. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS InboundAnalysis & Monitoring TransactionsOn the second tab strip it is possible to specify an URL which should be called in order to further analyze thegiven problem. This is especially interesting if you have some knowledge documents linked to a portal. Youdefine a Short text and the URL to be called. For web pages to be called, specify the full URL, e.g. http://help.sap.com. For content available on file servers specify the full file path, using the nomenclature: file://<server>..., e.g. 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 (e.g. ), the user will jump directly into the corresponding transactioneither in the SAP Solution Manager system (here: SAT) or the connected satellite system (here: CT1) forfurther analysis. For URLs the push-button (e.g. ) contains the Short text (limited to20 characters) from the Set-up session and leads the user to the defined URL in a newly opened browserwindow.© 2008 SAP AG page 16/53
  17. 17. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS Inbound1.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 procedures shouldbe defined as described in the following table. Some information is taken from the previous node ‘SolutionSupport 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, i.e. 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’. Those 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 SAPOffice mail.Support notifications allow setting up a service desk message in case of an alert. The information entered forthe service desk message serves as a template. The service desk message can be created manually orautomatically.On business process level it is possible to define notifications for the whole business process i.e. as soon asthe business process gets an alert status, notifications will be triggered. Alternative notifications can bedefined for every Monitoring Type individually, e.g. all alerts related to all background jobs of the businessprocess 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 Address be any e-mail address, an SAP user name in the same system, a Remote© 2008 SAP AG page 17/53
  18. 18. Best Practice for Solution Operations Manage Operations for SAP for Retail: POS Inbound SAP name or a shared distribution list. In 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 Number of YELLOW alerts that may occur before an automatic notification is Alerts triggered No. of Red Alerts 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, e.g. 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 SAP user name who is defined as a Business Partner with 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 a SAP user name who is defined as a Business Partner with role “General”. Num. of YELLOW Necessary when service desk messages are created automatically, e.g. after Alerts 10 yellow alerts a service desk message should be created. Num. of RED Necessary when service desk messages are created automatically, e.g. after Alerts 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. In case that 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 there either exist more than 9 yellow alerts OR more than 4 red alerts for which no Support Notification has been created yet. 1.7.5 Business Process Monitoring Process For a successful and efficient Business Process Monitoring concept, a process for the execution of the monitoring concept has to be defined. This includes the definition of the roles and responsibilities involved. It has to be defined who is supposed to carry out which activity within the process and how communication between the different roles within the support organization is supposed to take place. © 2008 SAP AG page 18/53
  19. 19. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS InboundA 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 contained within these processes are adequate to support theBusiness Process Monitoring concept. This includes the final communication of open alert 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.1.7.6 Legend This symbol indicates you a paragraph from where you can navigate to another chapter of this document for more detailed information on a topic. This symbol indicates you a paragraph from where you can navigate to another document within the SAP Service Marketplace for more detailed information on a topic.© 2008 SAP AG page 19/53
  20. 20. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS Inbound2 Business Process Monitoring for POS Inbound2.1 Business Process POS InboundPOS Inbound is the process in which data collected at the Point of sale (POS) is transferred to a centralsystem for subsequent processing. The POS Inbound process is extremely critical in a Retail environmentbecause the core function of a retail system is to manage the distribution of goods to the customer. Thedistribution is mainly influenced by stock levels in the Point of sale (POS) and the calculated requirements foreach POS. The stock levels are managed in SAP ERP for Retail and updated by goods movements andsales activities carried out at the POS. Based on this data, replenishment requirements are calculated on acentral system. In order to avoid expensive surplus or out of stock situations at the store, it is obvious that thepassage of the sales information from the POS System to ERP and to potentially a Forecast &Replenishment tool has to be secured and closely monitored. Besides the update of stock levels, financialaspects also play an important role in this process as it is at the POS where retailers earn their money.Missing data can therefore cause serious irritations in subsequent applications as the turnover reporting maynot reflect the real life showing mainly lower results and results in FI are also not correct. It is vital to theretailers business that no data is lost on the way.The complexity of this process involving various systems and processes underlines the importance of a welldefined monitoring and scheduling landscape. Sales transactions are usually registered at the POS Systemlocated in the stores. This information is extracted on a regular basis (ranging from every x seconds to once aday) and transferred via an EAI middleware and transformation tool to POS Data Management’s centralcomponent called PIPE (POS Inbound processing engine). Within this tool the incoming data is verified andposted to subsequent applications. The design of PIPE allows to process data for each subsequentapplication either immediately or as a bulk process with a self-defined frequency and a customizedaggregation level. Whereas data is mostly transferred in detail to SAP BI to enable detailed analysis and datamining, the data is aggregated by date, store and article in order to update follow-on applications such asSAP for Retail. The most common subsequent applications are SAP BI, SAP ERP and SAP F&R. The flexibledesign of PIPE however enables the possibility to provide other applications in an efficient way. Apart fromsales data, other data generated at the POS such as goods movements or financial transactions as well asstatistical information can be transferred using the same path as the sales data.© 2008 SAP AG page 20/53
  21. 21. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS Inbound2.1.1 Business Process Step 1: Poll and Send Sales Data2.1.1.1 DescriptionGeneral Information:POS Data is generated at a cash desk system in the store. Depending on the product chosen, the recordingapplication can be a thin client without an own database or a full-blown backend system. The sales data canbe either transferred real-time, near real-time meaning every couple of minutes or once a day in a bulkprocess.Depending on the chosen solution and scenario, monitoring requirements can vary. The most commonchallenge in this part of the process is the ability to remotely monitor the high number of cash desk systems inthe environment. It is important to know whether the stores are capable of sending data to the central system.This is why an efficient availability monitoring should be set up that regularly reaches out to the disparateend-points.Example:A Retailer having 800 stores that transfer sales data every 3 minutes in order to enable near real-time stockavailability checks would need an almost unmanageable effort to identify missing transactions if no efficientavailability and status monitoring is set up. The result would be inaccurate stock information.Due to the large variety of possible implementations no general documentation of monitoring can be madeavailable.2.1.2 Business Process Step 2: Receive, Transform and Send Information2.1.2.1 DescriptionGeneral Information:Most cash desk systems are not capable of managing data collection and transfer to a central system in aformat supported by PIPE. That is why in most cases an EAI tool such as SAP PI serves as the middlewareto connect to the disparate stores and takes care of the mapping between the cash desk system’s format andthe PIPE Inbound format. Errors in the actual data transfer and data transformation (mapping) need to betightly monitored to alert expected delays in processing.Example:The local cash desk system stores the transaction data in an own database. SAP PI can be used to transferthe data to a central system and to take care of the mapping. Error messages due to erroneous content ortechnical issues need to be monitored and problems solved as soon as possible.Due to the large variety of possible implementations no general documentation of monitoring can be madeavailable.2.1.3 Business Process Step 3: Process Sales Data (P01)2.1.3.1 DescriptionGeneral Information:Depending on the cash desk systems’ capabilities to send data and the EAI tool used, the following inboundpossibilities can be used to send data to PIPE: 1. IDoc /POSDW/POSTR_CREATEMULTIPLE (other IDoc types such as WPUBON for detailed sales data or WPUUMS for aggregated sales data are possible in PIPE Inbound but not recommended as they do not support the full potential of analysis that can be carried out on detailed POS data) 2. BAPI /POSDW/BAPI_POSTR_CREATE 3. RFC enabled Function Module /POSDW/CREATE_TRANSACTIONS_EXT 4. Webservice generated and implemented for function module /POSDW/CREATE_TRANSACTIONS_EXT 5. Generated and implemented Proxy wrapping function module /POSDW/CREATE_TRANSACTIONS_EXT© 2008 SAP AG page 21/53
  22. 22. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS InboundPIPE stores the transactions in the so called TLOG tables.Example:The cash desk system is connected to a central PI system that collects the point of sale data every 5 minutes.The data is posted to PIPE via RFC. The aim of this near real-time scenario is to enable a near real-timeavailability check and near real-time reporting (a so-called Flash-reporting) in BI., Near real-time data canonly be accurate if the way and the processing are monitored and problems are handled and escalated in anefficient way.2.1.3.2 Monitoring Requirements:Error Monitoring:Depending on the uploading frequency and the technique used, monitoring needs to be enabled on thesending system in case of real-time interfaces (“trickle feed”) or can be carried out in the receiving system(BI) in case of messages stored in bulk, e.g. once every evening.Performance Monitoring:In order to fulfill the requirements for the typically critical time window for processing POS sales data, keyperformance indicators for the performance of processing an average sales transaction (per line item) shouldbe defined and closely monitored. This KPI will also be a basis for throughput monitoring. Depending on thebusiness process implemented, POS inbound processing is the foundation for follow-up processes likereplenishment and logistics execution, whose disruption may jeopardize the flow of merchandise which is aserious negative impact for retailing business.Throughput Monitoring:Based on performance measurements for every single POS transaction line item, throughput keyperformance indicators should be deduced which can be assessed to have an overview of the ability of thesystem to cope with current and future data volume within the critical path of nightly processing, e.g. peaktransactions for retail business during xmas holiday season.Backlog Monitoring:Unprocessed sales transaction data due to erroneous information or interface failures threatens the businessflow in case of subsequent replenishment and logistics process steps. A backlog of information having failedto process therefore needs to be alerted and addressed accordingly.2.1.3.3 Monitoring Objects in SAP Solution Manager Monitoring Object Selection Criteria Alert Analysis Tool on Monitoring Satellite System Frequency / Data CollectionIDoc processing status in Direction, Port, Partner Number of IDocs of WE05 or WE02 every 15 minutescase of IDoc interface number, Partner type, type /POSDW/… Partner function, in an error-status Message type, Basic type, Message code, Message function, IDoc ageXML message status in Depends on the special Number of XML SXMB_MONI orEAI in case of XML Scenario messages in error SXI_MONITORinterfaceXML message status in Depends on the special Number of XML SXMB_MONI orBI in case of XML Scenario messages in error SXI_MONITORTORinterface© 2008 SAP AG page 22/53
  23. 23. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS InboundInbound BAPI call via /POSDW/BAPI_POSTR_ Response time of ST03N, ST05,RFC: CREATE RFC-enabled STAD/POSDW/BAPI_POSTR_ function callCREATE(Application Monitor:Dialog PerformanceMonitor)Background Job POSDW POS2PIPE Job Runtime, job SM37 every 5 minutesPOSDW POS2PIPE POSLOG, or cancellation, error during every jobPOSLOG (Report /POSDW/IDIS, Start messages in Job execution/POSDW/IDIS, variant Time LogTRANS)2.1.3.4 Monitoring without SAP Solution ManagerMonitoring Objects:In the case of IDocs used to transfer POS Data to PIPE, the processing of incoming data can be monitoredusing transaction WE05 or transaction WE02. The IDoc type is should be/POSDW/POSTR_CREATEMULTIPLE, as this IDoc type offers the full functionality of PIPE. If IDocs arecollected and processed with a job, the corresponding job (an instance of program /POSDW/IDIS) shouldthen be monitored in order to identify potential problems.If XML messages are used, transaction SXI_MONITOR or SXMB_MONITOR can be used to see themessage status.2.1.3.5 Scheduling of Background JobsJob Scheduling Requirements:If POS transactions are posted to PIPE via asynchronous messages based on IDocs or XML messages, a jobis required to post this data to PIPE. In the case of IDocs that need to be processed the IDoc Dispatcherwithin PIPE can be used.During PIPE inbound and outbound processing locks are held on date/store level. If an external schedulingtool is used that offers the possibilities of setting logical locks, periodic jobs for inbound and task processingshould not run in parallel. Also user activity such as changing data in the PIPE monitor can temporarily lockdata.Job Scheduling Requirements Recommended ABAP Variant Schedu- Prede- Suc- Scheduling Error Handling in or Generated Report ling cessor cessor Restriction Case of Job Name Job Job CancellationPOSDW /POSDW TRANS Between - Task Not in parallel Can be restarted ifPOS2PIPE /IDIS every x processi with PIPE system errorPOSLOG minutes ng jobs task and daily processing2.1.4 Business Process Step 4: PIPE Processing (P02)2.1.4.1 DescriptionGeneral Information:PIPE processing steps can be classified according to their purpose of 1) Checking and verifying the received data in PIPE, 2) Processing jobs in one-step processing and© 2008 SAP AG page 23/53
  24. 24. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS Inbound 3) Processing jobs in two-step processing. Details about monitoring objects and job setup can be found in the following chapters. You will always find a combination of these types of processing steps according to actual customer requirements. The last subchapter describes how to use the message log program to recognize occurring issues 4) Message log applicationAfter loading the transactional data to SAP POS DM the incoming data needs to be validated by use ofverification tasks. After this successful validation the data processing needs to be triggered for eachprocessing step (or so called task) relevant for the actual information. Additionally the reprocessing for datawhich originally had been loaded with missing master data or other issues needs to be triggered.2.1.5 Business Process Step 4a: Checks and Verification in PIPE2.1.5.1 DescriptionGeneral Information:In most common cases, first several validation tasks are executed automatically by PIPE (via immediate taskprocessing) to validate the incoming data: These tasks include one or several task(s) to check the masterdata, the balancing of each ticket (the accumulated sales amount for one transaction must correspond to theamount of the payment types of the same transaction) and duplicate checking (to make sure data is onlyloaded once).After the verification tasks, processing tasks are executed as described in the following chapters.Depending on the nature of the validation tasks, they might be executed immediately (recommended forupdate frequencies below 5 minutes) or scheduled for later processing once or several times a day (Job(POSDW PIPECHECK). This is described in chapter 2.1.6 as this type of processing complies to 1-step-processing). In order to only process correct transactions the result of the verification tasks are usually usedas conditions for the execution of the following processing tasks. These conditions are maintained in PIPEcustomizing for each task to be executed.2.1.5.2 Monitoring RequirementsError Monitoring:In order to check the status of the processing, the PIPE monitor (or POS Workbench) should be opened orrefreshed every x minutes if data is processed on a real-time or near real-time basis. If POS data istransferred only once a day, the monitor should be checked during and after processing.Performance, Throughput and Backlog Monitoring:The requirements of chapter 2.1.3.2 apply for PIPE processing as well.2.1.5.3 Monitoring Objects in SAP Solution Manager Monitoring Selection Alert Analysis Tool on Monitoring Object Criteria Satellite System Frequency / Data CollectionApplication log Object, Sub-object, Error messages SLG1 Every 60 min user, transaction, provided by PIPE Program Dispatcher© 2008 SAP AG page 24/53
  25. 25. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS Inbound2.1.5.4 Further Monitoring Objects Monitoring Object Selection Alert Analysis Tool on Satellite Monitoring Criteria System Frequency / Data CollectionOnline message Error /POSDW/MON0 ormonitoring messages /POSDW/MON2 provided by POS DM validation frameworkTask processing status as Store, Error /POSDW/DISPLAY_MESSAper chapter 2.1.8 Posting messages GELOG Date, provided Message during Class, Message PIPE Type, processing Message number, Message Category, Rule, Message Priority2.1.5.5 Monitoring without SAP Solution ManagerMonitoring Objects:For monitoring the status of the processed transactions, the following monitoring tools can be used: POS Workbench /POSDW/MON0 to provide an online status for all transactions and drill down into the transactions details The application log for details about the actual processing of the outbound data. The job log to identify issues around job processing Report /POSDW/DISPLAY_MESSAGELOG with specific variants to provide summarized processing messages (including error messages). This is described in more detail in chapter 2.1.8.2.1.6 Business Process Step 4b: Jobs in One-step Processing2.1.6.1 DescriptionGeneral Information:After loading the transactional data to SAP POS DM the data processing needs to be triggered for processingsteps (or tasks) configured for batch processing or for data which had been loaded with missing master dataor other issues. Validation tasks are in most cases executed immediately when data arrives (this is set in thecustomizing of the task). In this case a job (job POSDW PIPECHECK) for these validation tasks is onlyrequired to reprocess transaction in error.There can be multiple occurrences of this job depending on the business scenarios configured. In the end itcomes down to four different types of variants: - processing of data directly to the target system or without impact to batch processes - processing of data during batch processing - processing of validation steps© 2008 SAP AG page 25/53
  26. 26. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS Inbound - processing of data into the POS DM aggregate storage, triggering job for outbound processing (check for additional chapter about 2-step processing)Used variants should be configured for the following processing settings: - to process incorrect tasks - to use parallel processing2.1.6.2 Monitoring Requirements:Error Monitoring:The monitoring requirements of chapter 2.1.5 apply for the jobs POSDW PIPECHECK and POSDWPIPESALES.Performance, Throughput and Backlog Monitoring:The requirements of chapter 2.1.3.2 apply for PIPE one-step processing as well.2.1.6.3 Monitoring Objects in SAP Solution Manager Monitoring Object Selection Criteria Alert Analysis Monitoring Tool on Frequency / Satellite Data System CollectionBackground Job POSDW POSDW PIPECHECK, or Job Runtime, SM37 Every 5PIPECHECK (Report /POSDW/PIPE_DISPATCHER, job minutes/POSDW/PIPE_DISPATCHER) Start Time cancellation, during every error job execution messages in Job LogBackground Job POSDW POSDW PIPESALES, or Job Runtime, SM37 Every 5PIPESALES (Report /POSDW/PIPE_DISPATCHER job minutes/POSDW/PIPE_DISPATCHER) Start Time cancellation, during every error job execution messages in Job Log2.1.6.4 Monitoring without SAP Solution ManagerMonitoring Objects:The monitoring objects of chapter 2.1.5 apply for the jobs POSDW PIPECHECK and POSDW PIPESALES2.1.6.5 Scheduling of Background JobsJob Scheduling Requirements:The processing within PIPE is triggered by PIPE Dispatcher. There are two variants possible for the 1-step-processing: (Re-)Processing of validation tasks using job POSDW PIPECHECK as part of the daily batch or on a reoccurring basis Processing of 1-step tasks like the supply of data to SAP BI (job POSDW PIPESALES)© 2008 SAP AG page 26/53
  27. 27. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS InboundScheduling of Background Jobs Recommended ABAP Variant Schedu- Prede- Suc- Scheduling Error Handling in or Generated Report ling cessor cessor Restriction Case of Job Name Job Job CancellationPOSDW /POSD CHECK Daily as Data - - Can be restartedPIPECHECK W/PIPE S part of loading _DISPA batch to SAP TCHER proces- POS sing DMPOSDW /POSD DAILY Daily as Data - - Can be restartedPIPESALES W/PIPE SALES part of loading _DISPA batch to SAP TCHER proces- POS sing DM2.1.7 Business Process Step 4c: Jobs in 2-step Processing2.1.7.1 DescriptionGeneral Information:The data aggregated into the aggregate tables inside POS DM using the PIPE Dispatcher needs to beprovided to the outbound interfaces. This is done using the outbound dispatcher report collecting theaggregated (condensed) data and transforming it into the interface format.Monitoring of the processing is done by checking the processing results in the POS Workbench restricting onaggregates. From a basis perspective the availability of system resources can be monitored as the data isonly mapped and not touched functionally. Errors will only occur on the system level.2.1.7.2 Monitoring Requirements:Error Monitoring:The monitoring objects of chapter 2.4.1 apply for the jobs POSDW PIPEAGG and POSDW OUTBOUND.Performance, Throughput and Backlog Monitoring:The requirements of chapter 2.1.3.2 apply for PIPE two-step processing as well.2.1.7.3 Monitoring Objects in SAP Solution Manager Monitoring Object Selection Criteria Alert Analysis Monitoring Tool on Frequency / Satellite Data Collection SystemBackground Job POSDW POSDW PIPEAGG, or Job Runtime, SM37 Every 5 minutesPIPEAGG (Report /POSDW/PIPE_DISPATCHER, job cancel- during every job/POSDW/PIPE_DISPATCHE Start Time lation, error executionR, variant AGGREGATE) messages in Job LogBackground Job POSDW POSDW OUTBOUND, or Job Runtime, SM37 Every 5 minutesOUTBOUND (Report /POSDW/OUTBOUND_DISPATC job cancel- during every job/POSDW/OUTBOUND_DISP HER, Start Time lation, error executionATCHER, variant DAILY messages inSALES) Job Log© 2008 SAP AG page 27/53
  28. 28. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS Inbound2.1.7.4 Monitoring without SAP Solution ManagerMonitoring Objects:The monitoring requirements of chapter 2.1.5 apply for the jobs POSDW PIPEAGG and POSDWOUTBOUND.2.1.7.5 Scheduling of Background JobsJob Scheduling Requirements:The process of adding data to the aggregate tables (job POSDW PIPEAGG) can be done throughout the day.This means that the aggregate tables are built up during intraday processing. At the end of day (during theactual batch run) the POS data is picked up from the aggregates tables and processed to, for example, ERPfor Retail using job POSDW OUTBOUND. This job is running once during batch processing.Scheduling of Background Jobs Recommended ABAP Variant Schedu- Prede- Suc- Scheduling Error Handling in or Generated Report ling cessor cessor Restriction Case of Job Name Job Job CancellationPOSDW /POSD AGGRE Hourly Data POSD - Can be restartedPIPEAGG W/PIPE GATE loading W _DISPA to SAP OUTBO TCHER POS UND DMPOSDW /POSD DAILY Daily as POSD Not in Can be restartedOUTBOUND W/OUT SALES part of W parallel with BOUND batch PIPEA data loading _DISPA proces- GG TCHER sing2.1.8 Business Process Step 4d: The Message Log Application2.1.8.1 DescriptionGeneral Information:After validating and processing the data inside SAP POS DM, the results need to be provided to variousgroups of recipients to follow up occurring errors, either from a business or a technical point-of-view.During task processing, errors are logged as messages in the individual transactions. The program/POSDW/DISPLAY_MESSAGELOG allows to display these messages based on the filter criteria entered.Example:Problems typically occurring in a productive POS DM environment are: - Master data issues (for example, business: missing or incorrect maintenance of articles and sites, technical: missing master data extraction to BI) - POS DM configuration issues - Data consistency issues (for example, store sending transactions where the payments value does not equal the sales value, duplicate transaction postings) - Data completeness issues (for example, transaction sequence number gaps, imbalance of total value of sales and payments against eon of day data provided by the POS) - Technical issues (for example, missing initialization of BI delta queue, table space extension issues, connectivity issues)© 2008 SAP AG page 28/53
  29. 29. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS Inbound2.1.8.2 Monitoring Requirements:Error Monitoring:Transactions reporting errors within the data validation framework of POS DM (which comprises the tasksand checks as described in the previous chapters) need to be followed up because a detected error stops theactual processing of this single sales ticket. With an increasing number of issues identified the total revenuepostings as well as follow on processes like replenishment or store analytics are heavily affected.This leads to a requirement to automatically distribute the detected errors to the responsible departmentsafter the nightly batch run or within defined repetition periods and trigger follow up activities.Performance, Throughput and Backlog Monitoring:These requirements do not apply for message log review.2.1.8.3 Monitoring Objects in SAP Solution Manager Monitoring Object Selection Criteria Alert Analysis Monitoring Tool on Frequency Satellite / Data System CollectionBackground Job POSDW ERRLOG POSDW ERRLOG MC01, or Job SM37 Every 5MC01 (Report /POSDW/DISPLAY_MESSAGELOG, Runtime, minutes/POSDW/DISPLAY_MESSAGELOG, Start Time job cancel- during everyvariant MC01) lation, error job messages execution in Job LogBackground Job POSDW ERRLOG POSDW ERRLOG MC02, or Job SM37 Every 5MC02 (Report /POSDW/DISPLAY_MESSAGELOG, Runtime, minutes/POSDW/DISPLAY_MESSAGELOG, Start Time job cancel- during everyvariant MC02) lation, error job messages execution in Job LogBackground Job POSDW ERRLOG POSDW ERRLOG MC03, or Job SM37 Every 5MC03 (Report /POSDW/DISPLAY_MESSAGELOG, Runtime, minutes/POSDW/DISPLAY_MESSAGELOG) Start Time job cancel- during every lation, error job messages execution in Job LogBackground Job POSDW ERRLOG POSDW ERRLOG MC04, or Job SM37 Every 5MC04 (Report /POSDW/DISPLAY_MESSAGELOG, Runtime, minutes/POSDW/DISPLAY_MESSAGELOG) Start Time job cancel- during every lation, error job messages execution in Job Log2.1.8.4 Further Monitoring Objects Monitoring Selection Alert Analysis Tool on Monitoring Object Criteria Satellite System Frequency / Data CollectionTechnical - task Store, Posting Date, Error messages /POSDW/ After night batchprocessing status Message Class, provided by POS DISPLAY_ or after Message Type, DM validation MESSAGE periodically Message number, framework LOG, Variant for executed Message Category, MC01 processing steps Rule, Message Priority© 2008 SAP AG page 29/53
  30. 30. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS InboundBusiness -task Store, Posting Date, Error messages /POSDW/ After night batchprocessing status Message Class, provided by POS DISPLAY_ or after Message Type, DM validation MESSAGE periodically Message number, framework LOG, Variant for executed Message Category, MC02 processing steps Rule, Message PriorityApplication - task Store, Posting Date, Error messages /POSDW/ After night batchprocessing status Message Class, provided by POS DISPLAY_ or after Message Type, DM validation MESSAGE periodically Message number, framework LOG, Variant for executed Message Category, MC03 processing steps Rule, Message PriorityData consistency Store, Posting Date, Error messages /POSDW/ After night batch- task processing Message Class, provided by POS DISPLAY_ or afterstatus Message Type, DM validation MESSAGE periodically Message number, framework LOG, Variant for executed Message Category, MC04 processing steps Rule, Message Priority2.1.8.5 Monitoring without SAP Solution ManagerMonitoring Objects: 1. Program /POSDW/DISPLAY_MESSAGELOG Project specific enhanced version of the error report Within the provided SAP POS DM delivery an error report for more detailed error reporting is provided as a template. Due to the nature of the report it has not been fully implemented and needs to be adopted to the project requirements, providing for example capabilities to identify sales values related to errors. All statements mentioned above keep their validity. This report can be found under the following report name: /POSDW/DISPLAY_MESSAGES_AGG If you need help in adopting this report please contact SAP Consulting. 2. Task processing status of transactions and related error log messages. 3. Use POS DM message customizing to define message categories and assign messages, additionally a criticality level can be defined per message using the message priority field. Example: (list is not complete, assignment can change for different projects) /POSDW/IMG/ POS Inbound Processing Messages Message Category MC01Technical or system messages (for example, missing delta queue init) MC02Business related messages (for example, master data) MC03Application related messages (for example, missing configuration) MC04Data consistency messages (for example, missing data or store software issues) /POSDW/IMG/ POS Inbound Processing Messages Error Messages for Error Category MC01 Message ID Msg No. Message /POSDW/COMMON 000 System Error - Please Inform System Administration /POSDW/COMMON 000 Error during archiving /POSDW/COMMON 022 Error decrypting payment card number /POSDW/COMMON 023 Invalid payment card GUID during decryption of payment card number© 2008 SAP AG page 30/53
  31. 31. Best Practice for Solution OperationsManage Operations for SAP for Retail: POS Inbound /POSDW/COMMON 024 Error encrypting payment card number /POSDW/COMMON 025 Duplicate payment card GUID during save of encrypted number /POSDW/COMMON 026 Posting error during save of encrypted payment card number MC02 Message ID Msg No. Message /POSDW/CORE 003 Unknown store number &1 /POSDW/CORE 004 Unknown EAN/UPC number &1 /POSDW/CORE 025 Unknown material number &1 MC03 Message ID Msg No. Message /POSDW/AGGREGATION All All messages /POSDW/CORE 007 Unknown sales item type &1 /POSDW/CORE 008 Unknown tax type &1 /POSDW/CORE 009 Unknown discount type &1 /POSDW/CORE 010 Unknown means of payment type &1 /POSDW/CORE 011 Unknown financial transaction type &1 /POSDW/CORE 012 Unknown goods movement type &1 /POSDW/CORE 013 Unknown reason &1 /POSDW/OUTPUT 005 Other internal errors that occurred during preparation of IDoc /POSDW/OUTPUT 006 Message type WPUBON can only contain sales transactions /POSDW/OUTPUT 007 Transactions can only contain data from the same store /POSDW/OUTPUT 008 No logical system exists /POSDW/OUTPUT 009 Message type WPUWBW can only contain goods movement transactions /POSDW/OUTPUT 010 Only sales or goods receipt transactions may be used for the F&R Engine /POSDW/OUTPUT 011 No connection to remote system or destination not maintained /POSDW/OUTPUT 012 Function module does not exist in the remote system /POSDW/OUTPUT 013 Message type WPUTAB can only contain sales transactions /POSDW/OUTPUT 014 Message type WPUFIB can only contain financial transactions /POSDW/OUTPUT 015 Message type WPUUMS can only contain sales transactions MC04 Message ID Msg No. Message /POSDW/ACTION 000 Sum of items does not equal the payment sum /POSDW/CONDITIONS 000 POS transaction for &1, index &2 already exists for &3© 2008 SAP AG page 31/53

×