Best Practice for Solution Operations

Manage Operations for SAP for Retail POS Download

Dietmar-Hopp-Allee 16 D-69190 Walldorf
CS STATUS

customer
DATE

published
VERSION

June 10 2009
SOLUTION MANAGEMENT PHASE

3.0
SAP SOLUTION

Operations & Continuous Improvement Best Practices for Solution Operations
TOPIC AREA SOLUTION MANAGER AREA

Application & Integration Management Business Process Operations

Best_Practice_POS_Outbound_V30_upd.doc – 10.06.2009

Best Practice for Solution Operations
Manage Operations for SAP for Retail – POS Download

Table of Contents
1 Management Summary 1.1 Goal of Using This Best Practice 1.2 Alternative Practices 1.3 Staff and Skills Requirements 1.4 System Requirements 1.5 Duration and Timing 1.6 How to Use This Best Practice 1.7 Best Practice Procedure 1.7.1 Preliminary tasks 1.7.2 Monitoring concepts 1.7.3 Business Process Monitoring in SAP Solution Manager 1.7.4 Monitoring types for Business Process Monitoring in SAP Solution Manager 1.7.4.1 Application monitor 1.7.4.2 Background job 1.7.4.3 ABAP dump collector 1.7.4.4 Dialog performance 1.7.4.5 Update errors 1.7.4.6 Due list log 1.7.4.7 Application log 1.7.4.8 Other CCMS monitors 1.7.4.9 Analysis and monitoring tools 1.7.4.10 Monitoring activities 1.7.4.11 Notifications 1.7.5 Business Process Monitoring process 1.7.6 Legend 2 Business Process Monitoring for a Point of Sale (POS) Download Data Transmission 2.1 Sample Scenario 2.2 Business Process POS Outbound with POS Interface IDocs 2.2.1 Business process step 1: Initialize or dummy initialize new store 2.2.1.1 Description and general information 2.2.1.2 Monitoring requirements 2.2.1.3 Further monitoring objects 2.2.1.4 How to find meaningful thresholds per monitoring object 2.2.2 Business process step 2: Evaluate master data changes, collect and prepare data, create IDoc 2.2.2.1 Description and general information 2.2.2.2 Monitoring requirements 2.2.2.3 Monitoring objects in SAP Solution Manager 2.2.2.4 Further monitoring objects 2.2.2.5 How to find meaningful thresholds per monitoring object 2.2.2.6 Scheduling of background jobs 2.2.3 Business process step 3: Copy IDocs within ECC retail (optional) and send out IDocs from ECC retail 2.2.3.1 Description and general information 2.2.3.2 Monitoring requirements 6 6 6 6 7 7 7 8 8 8 8 9 10 10 11 12 13 14 15 17 17 19 19 21 21 22 25 26 28 28 29 29 30 30 30 30 31 31 31 32 32 32 33

© 2009 SAP AG

page 2/82

Best Practice for Solution Operations
Manage Operations for SAP for Retail – POS Download

2.2.3.3 Monitoring objects in SAP Solution Manager 2.2.3.4 How to find meaningful thresholds per monitoring object 2.2.3.5 Scheduling of background jobs 2.2.4 Business process step 4: Monitor, correct, and repeat POS outbound 2.2.4.1 Description 2.2.4.2 Monitoring requirements 2.2.4.3 Monitoring objects in SAP Solution Manager 2.2.4.4 Further monitoring objects 2.2.4.5 How to find meaningful thresholds per monitoring object 2.2.4.6 Error handling per monitoring object 2.2.4.7 Scheduling of background jobs 2.2.5 Business process step 5: Reorganize change pointers, status records, and WIND entries 2.2.5.1 Description and general information 2.2.5.2 Monitoring requirements 2.2.5.3 Monitoring objects in SAP Solution Manager 2.2.5.4 How to find meaningful thresholds per monitoring object 2.2.5.5 Error handling per monitoring object 2.2.5.6 Scheduling of background jobs 2.2.6 Business process step 6: Delete change pointers and status records 2.2.6.1 Description and general information 2.2.6.2 Monitoring requirements 2.2.6.3 Monitoring objects in SAP Solution Manager 2.2.6.4 How to find meaningful thresholds per monitoring object 2.2.6.5 Error handling per monitoring object 2.2.6.6 Scheduling of background jobs 2.2.7 Business process step 7–9: Middleware (enterprise application integration tool): Receive, transform, and send information 2.2.7.1 Description 2.2.7.2 Monitoring requirements 2.2.7.3 Monitoring objects in SAP Solution Manager 2.2.7.4 Further monitoring objects 2.2.7.5 How to find meaningful thresholds per monitoring object 2.2.7.6 Error handling per monitoring object 2.2.8 Business process step 10–11: POS system: Receive information and update database 2.2.8.1 Description and general information 2.2.8.2 Monitoring requirements 2.2.8.3 Monitoring objects in SAP Solution Manager 2.2.8.4 Further monitoring objects 2.2.8.5 How to find meaningful thresholds per monitoring object 2.2.8.6 Error handling per monitoring object 2.3 Business Process POS Outbound with Assortment List 2.3.1 Business process step 1: Run full version to initialize or dummy initialize new store 2.3.1.1 Description and general information 2.3.1.2 Monitoring requirements 2.3.1.3 Further monitoring objects 2.3.1.4 How to find meaningful thresholds per monitoring object

34 34 35 35 35 36 42 43 43 43 43 44 44 45 45 45 46 46 46 46 47 47 47 47 47 48 48 48 48 49 49 49 49 49 49 49 50 50 50 50 52 52 52 53 53

© 2009 SAP AG

page 3/82

Best Practice for Solution Operations
Manage Operations for SAP for Retail – POS Download

2.3.1.5 Error handling per monitoring object 2.3.2 Business process step 2: Run change version to evaluate master data changes, collect and prepare data, create IDoc 2.3.2.1 Description and general information 2.3.2.2 Monitoring requirements 2.3.2.3 Monitoring objects in SAP Solution Manager 2.3.2.4 Further monitoring objects 2.3.2.5 How to find meaningful thresholds per monitoring object 2.3.2.6 Error handling per monitoring object 2.3.2.7 Scheduling of background jobs 2.3.3 Business process step 3: Copy IDocs within ECC retail (optional) and send out IDocs from ECC retail 2.3.3.1 Description and general information 2.3.3.2 Monitoring requirements 2.3.3.3 Monitoring objects in SAP Solution Manager 2.3.3.4 How to find meaningful thresholds per monitoring object 2.3.3.5 Error handling per monitoring object 2.3.3.6 Scheduling of background jobs 2.3.4 Business process step 4: Monitor, correct, and repeat data transfer of assortment list 2.3.4.1 Description and general information 2.3.4.2 Monitoring requirements 2.3.4.3 Monitoring objects in SAP Solution Manager 2.3.4.4 Further monitoring objects 2.3.4.5 How to find meaningful thresholds per monitoring object 2.3.4.6 Error handling per monitoring object 2.3.4.7 Scheduling of background jobs 2.3.5 Business process step 5: Reorganize change pointers, status records, and WIND entries 2.3.5.1 Description and general information 2.3.5.2 Monitoring requirements 2.3.5.3 Monitoring objects in SAP Solution Manager 2.3.5.4 How to find meaningful thresholds per monitoring object 2.3.5.5 Error handling per monitoring object 2.3.5.6 Scheduling of background jobs 2.3.6 Business process step 6: Delete change pointers and status records 2.3.6.1 Description and general information 2.3.6.2 Monitoring requirements 2.3.6.3 Monitoring objects in SAP Solution Manager 2.3.6.4 Scheduling of background jobs 2.3.6.5 How to find meaningful thresholds per monitoring object 2.3.6.6 Error handling per monitoring object 2.3.7 Middleware (enterprise application integration tool): Receive, transform, and send information 2.3.7.1 Description 2.3.7.2 Monitoring requirements 2.3.7.3 Monitoring objects in SAP Solution Manager 2.3.7.4 Further monitoring objects 2.3.7.5 How to find meaningful thresholds per monitoring object
© 2009 SAP AG

53 54 54 54 55 55 55 55 55 56 56 57 58 58 58 58 59 59 60 65 66 66 66 66 67 67 68 68 68 69 69 69 69 69 70 70 70 70 71 71 71 71 71 71

page 4/82

8.6 Error handling per monitoring object 2.8 POS system: Receive information and update database 2.4 Background Jobs Index of Figures Index of Tables 72 72 72 72 72 72 72 72 73 73 73 74 74 76 76 79 81 81 © 2009 SAP AG page 5/82 .2 Example PI Message Process Monitoring 4.8.1 Example Background Job Monitoring 4.2 Monitoring requirements 2.5 How to find meaningful thresholds per monitoring object 2.1 Description and general information 2.3.8.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 2.3.3.3.1 Troubleshooting 3.8.8.3.3.3 Monitoring objects in SAP Solution Manager 2.3 Example ALE/IDoc Monitoring 4.3.6 Error handling per monitoring object 3 Further Information 3.2 Related Best Practice Documents 4 Appendix 4.7.8.3.4 Further monitoring objects 2.

1 Management Summary Goal of Using This Best Practice This Best Practice helps you set up a Business Process Monitoring concept for your SAP for Retail solution. 1. please contact your local SAP Consulting representative. This service is exclusively available within SAP’s support engagements SAP MaxAttention and SAP Safeguarding. Job Scheduling Management) © 2009 SAP AG page 6/82 . The concept aims to define procedures for business process oriented monitoring and error handling and escalation procedures for your business process point of sale (POS) download. These procedures intend to ensure a smooth and reliable flow of this core business process so that your business requirements are met.2 Alternative Practices You can have SAP experts deliver this Best Practice on-site by ordering an SAP Solution Management Optimization (SMO) service for SAP Business Process Management (BPM).g. If your company currently does not have any support engagements with SAP. it is also possible to get assistance by SAP experts from SAP Consulting. This Best Practice contains the recommended approach from SAP which uses whenever possible SAP Solution Manager for the monitoring functionalities. This Best Practice gives orientation for defining suitable application oriented monitoring objects in order to detect any irregularities or deviations from an ideal business process flow or to detect error situations concerning a core business process at an early stage. But even if you do not use SAP Solution Manager we recommend to follow the procedures described in this document as much as possible in order to ensure a smooth and reliable flow of your business processes as well as an appropriate response in case of unforeseen errors. 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.3 Staff and Skills Requirements To implement this Best Practice.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 1 1. 1. They include the following groups: Persons designated to perform business process oriented monitoring and ensure that the process runs smoothly (e. you require the following teams: Application Management team This team creates the SAP ERP Business Process Monitoring concept and consists of experts from several areas of your company: Business department Solution support organization (for example the basis support or the application support) Implementation project team Business process operations team The business process operations team will be responsible for applying the resulting procedures derived from implementing this Best Practice. In this case. development support.

Necessary or useful trainings SM300 Business Process Management and Monitoring E2E300 End-to-End Business Process Integration and Automation Management 1. the SAP basis release of the systems to be monitored have to be at least 4.4 System Requirements In order to monitor business processes running in your SAP for Retail solution via SAP Solution Manager. software monitoring team. and monitoring frequencies). if the application monitoring team needs to escalate an issue. This includes the definition and documentation of the core business processes. 1. and the assignment of responsibilities. 1. To have all described monitoring objects available in SAP Solution Manager. He coordinates all activities necessary for the business process. definition of monitoring objects. Therefore. monitoring tools. © 2009 SAP AG page 7/82 . 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. which you can obtain through SAP Solution Manager or the SAP Service Marketplace. He often serves as a second level in the escalation procedure. This document explains the procedures you should use to create a general Business Process Management concept. More information about roles and responsibilities of these teams can be found in the super-ordinate Best Practice General Business Process Management. available on the SAP Service Marketplace. quick link/BPM.5 Duration Duration and Timing Creating a Business Process Monitoring concept takes approximately one week per business process. he is usually responsible for the escalation paths in case of problems. Implementing the Business Process Monitoring concept takes approximately an additional week.6C.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 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. definition of monitoring activities (including error handling procedures. the add-on ST-A/PI01L has to be installed on the SAP for Retail system. system administration team. the definition of communication and escalation procedures.6 How to Use This Best Practice Here you find a brief description of how you should proceed in using this document: Read through the General Business Process Management Best Practice. Timing The best time to apply this Best Practice is during the planning phase or during the implementation phase of your SAP solution.

Best Practice for Solution Operations
Manage Operations for SAP for Retail – POS Download

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
1.7.1

Best Practice Procedure
Preliminary tasks

Before performing this Best Practice, ensure that you perform the following preliminary tasks or checks in the system: 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 availability 1.7.2 Monitoring concepts

The monitoring procedures proposed for each business process step are the core of this Best Practice. The monitoring 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: 1. Error monitoring 2. Performance monitoring 3. Throughput monitoring 4. Backlog monitoring 5. Data consistency monitoring For 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 restartability General monitoring activities that are valid for all or most scenarios are described in the generic part in chapter 1.7.4 Recommendations for performance monitoring can also be found in this chapter. The performance of the most important steps of your core business processes should be monitored on a regular basis. The monitoring procedure for performance monitoring of all steps that are executed in an SAP for Retail solution is generally the same. Therefore, you will only find specific performance monitoring recommendations on selected business process steps. 1.7.3 Business Process Monitoring in SAP Solution Manager

Business Process Monitoring (BPMon), as part of Solution Monitoring means the proactive and processoriented monitoring of the most important or critical business processes, including the observation of all technical and business application specific functions that are required for a steady and stable flow of the business processes.

© 2009 SAP AG

page 8/82

Best Practice for Solution Operations
Manage Operations for SAP for Retail – POS Download

The core business processes that are implemented in a SAP for Retail system or other software and operated by a company are of particular importance, and Business Process Monitoring is intended to ensure a smooth and reliable operation of the business processes and, thereby, that the core business processes meet a company’s business requirements in terms of stability, performance, and completeness. SAP Solution Manager provides a graphic to visualize a company’s (distributed) system and solution landscape and all related business processes. By using Business Process Monitoring, it is possible to define and customize alert situations from a basic set of configurable alerts provided by SAP Solution Manager. These alerts are then visualized by green, yellow, and red alert icons for each individual business process step in the graphical business process representation. Business Process Monitoring is intended to detect and respond to critical situations as early as possible in order to solve problems as fast as possible. In addition, 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 into the company’s overall strategy for Business Process Management and solution management within their solution 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 tasks For 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 Manager

Monitoring types are part of the functional scope of Business Process Monitoring as it is available in SAP Solution Manager. The below mentioned monitoring types are available: 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 must be selected. In order to receive detailed information on how to set up the monitoring objects in SAP Solution 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 SAP Solution Manager is that all business processes and business process steps are maintained in the respective solution that contains all

© 2009 SAP AG

page 9/82

Best Practice for Solution Operations
Manage Operations for SAP for Retail – POS Download

affected system components. If you want to learn more about how to set this up, please turn to (URL http://help.sap.com) 1.7.4.1 SAP Solution Manager Basic Settings.

Application monitor

The application monitor is just one of many different monitoring types within the 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 Application Group Plug-Ins SAP Solution Tools ST-A/PI. Entry by

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 on how 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://service.sap.com/BPM 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 already established 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 tools For SAP 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) 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://service.sap.com/BPM 1.7.4.2 Media Library).

Background job

The background job monitoring should be part of a Job Scheduling Management concept (URL http://service.sap.com/solutionmanagerbp, topic area Business Process Operations to find a Best Practice document Job Scheduling Management). Because of several restrictions regarding background job scheduling, e.g. time restrictions, restriction of hardware resources (CPU, main memory, …) or existing

© 2009 SAP AG

page 10/82

Best Practice for Solution Operations
Manage Operations for SAP for Retail – POS Download

dependencies between different activities (e.g. invoices can only be created after the corresponding goods issue is posted, or back order processing and material requirements planning should not run at the same time) it is very important to ensure the stable run of background jobs. A cancelled background job should be identified as soon as possible in order to react as fast as possible. Therefore it is also necessary to define restart procedures and escalation paths. Monitoring objects Before setting up monitoring the monitoring objects must be clearly defined. A monitoring object is a single background job or a group of background jobs. There are four different possibilities to identify a special background 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 on the subject what kind of alerts make sense or what kind of alerts are possible are discussed in the Best Practice document Background Job Monitoring with SAP Solution Manager which can be found on the SAP Service Marketplace http://service.sap.com/solutionmanagerbp, topic area Business Process Operation. 1.7.4.3 ABAP dump collector

The dump collector provides monitoring features for alerting on occurrences of ABAP dumps of specified runtime errors and collects statistical data of ABAP dumps for reporting reasons. Monitoring objects The monitoring object is an ABAP runtime error. This runtime error can be specified via the runtime error name, the user who is responsible for the runtime error, the client on which the runtime error occurs or the program that leads to the runtime error. Monitoring alerts Possible alert types are the Number of ABAP Dumps (Delta) – all dumps since the last collector run – and Number of ABAP Dumps (Reporting) – all runtime errors of specified type, client, and program for this day or for the previous day.

Figure 1: Alert type Number of ABAP Dumps (Delta)

© 2009 SAP AG

page 11/82

load and generation time. The relevant transactions need to be selected for monitoring. The Transactions table lists all transactions that are already configured to that business process step. RED to YELLOW. Monitoring objects The monitoring object is the transaction itself. If no active settings for the threshold values were found for a certain transaction code. Select those times that are relevant for monitoring. This can be a standard transaction or a custom-developed transaction. Therefore you can load the current threshold values from the respective systems via the Load thresholds from <XYZ> button. a subnode Performance Alerts will appear where you can enter the threshold values. and lists the combinations of specified transaction code and SAP instance. database request time and the front-end response time.7. It is also possible to add or to remove transactions within the Add/Remove Transactions table. select the respective instances in the SAP Instances table. default values are set (indicated in column Default). it might be possible that the object already exists there. The customizing has to be done in the Dialog Performance node. The Alert Types table shows the dialog response time and all parts of the response time that can be monitored. For each combination of transaction code and instance that you want to include in the monitoring. the values are filled in columns. Since the monitoring object for performance monitoring is created on the satellite system.4 Dialog performance Dialog performance implies the monitoring of the dialog transaction performance of any transaction in the SAP system. YELLOW to RED. and YELLOW to GREEN. which lists all instances that are maintained for a system. To this end. like queue time.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 1. If successfully retrieved for an SAP instance. specify the threshold values resulting in alert messages for GREEN to YELLOW. To transfer the © 2009 SAP AG page 12/82 .4. with <XYZ> representing the SID. Figure 2: Monitoring objects – Dialog performance Monitoring alerts Each table in the Performance Alerts sub-node corresponds to an alert type chosen in the higher-level node. After saving this node. The monitoring can be performed per SAP instance.

V1 modules describe critical or primary changes. If the operation is canceled while the transaction is being executed. If no user is specified explicitly. time-critical (V1). These activities are handled by the SAP update system. non-time-critical (V2) update errors. Figure 3: Monitoring alerts . If desired. This is the object type.4.7.Dialog performance 1. This distinction allows the system to process critical database changes before less critical changes. or if an error occurs.5 Update errors Changes to the data in an SAP system caused by a business process should be written to the database completely or not at all. The name of the object is the name of a transaction or the name of the ABAP program itself. the transaction should not make any changes to the database. for example order creation or changes to material stock. and secondary. To transfer all at once (all thresholds for all columns and tables) there is an additional Copy all button. the Copy icon can be used. the transaction or the ABAP program can be specified. a user executing. © 2009 SAP AG page 13/82 .Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download threshold values for a single line from right to left. for example result calculations. relevant in a business process. These are pure statistical updates. these affect objects that have a controlling function in the SAP system. all users (represented by *) will be considered in monitoring data evaluation. The SAP system makes a distinction between primary. V2 modules describe less critical secondary changes. Monitoring objects Monitoring of update errors can be configured for online transactions and/or ABAP programs.

the name of the user can be specified here.21. it can be displayed in the due list log for this billing run.g. 1.6 Due list log A due list is a list that contains several entries (documents) depending on selection criteria. the list contains e. If it is user independent. a wild card (*) can be used. billing or picking. the billing due list via transaction V.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Figure 4: Monitoring objects – Update errors Monitoring alerts Since update errors are usually very critical the default configuration is to raise a yellow alert as soon as one update error occurs. In case of a billing due list. There are different types of due lists in an SAP system of which the following three are most important: Delivery (L). a number of sales documents that need to be billed. This is valid for V1 and for V2 update errors. This could be per day. Monitoring objects The monitoring object is the respective due list type. per hour or per log. If a certain user is processing the due list.4. The aggregation level needs to be defined. The delivery due list can be directly accessed via transaction V_SA. a threshold must be specified. © 2009 SAP AG page 14/82 . That can be delivery.7. billing (F) and picking (K). To raise a red alert for a V1 or a V2 update error. If the billing due list was processed previously and it is important to know which billing documents were created from this billing due list.

Figure 5: Monitoring objects – Due list log 1.7.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Monitoring alerts 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 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. 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. 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. creation time. An object and any subobject that belongs to it classify each event. creator. and displaying them as a log. The application log is not written consecutively but as a whole at one point in time. The analysis of the logs is similarly object. A transaction can generate several logs. Situations can arise at runtime in application programs that must be brought to the attention of the user in some way. It can also be useful to report a successful completion. The information that arises is called a message.7 Application log The application log provides an infrastructure for collecting messages.4. Monitoring objects and alerts The application log allows an application. © 2009 SAP AG page 15/82 . The message type. 5 DLLogMsgs refers to specific due list log messages.or object-oriented recording of events. The name of an object (and/or sub-object) can be found in transaction /nSLG1 together with all other specific information to that log. etc.(or sub-object) oriented. 2 MinQuantityDocs refers to a minimum number of documents that should be created during a Due List run. The alert rating (YELLOW or RED) will be raised if no documents were created during a Due List run. the message ID and the number can be specified. It is also possible to use wild cards. A log usually also has header information (log type. saving them in the database. 3 TotalQuantityMsgs refers to the total number of message created during a due list run. The set of messages is a log.). These are usually errors.

and the message number as well as the threshold values for the number of critical messages that are supposed to result in changes from GREEN to YELLOW and from YELLOW to RED can be specified. the message ID.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Figure 6: Monitoring objects and alerts – Application log It is possible to monitor for the total number of messages belonging to an object. It is also possible to monitor specific messages that are considered as critical in table CriticalMsgs. Figure 7: Monitoring alerts – Application log/Critical messages © 2009 SAP AG page 16/82 . It is also possible to use wild cards. To configure the monitoring of critical application log messages. the relevant object-/sub-object combinations need to be selected. Therefore the number of messages that raises a YELLOW alert and the number of messages changing from a YELLOW to a RED alert must be maintained. For each of these combinations the message type.

In case of analysis transactions. To transfer the thresholds values for a single line from right to left double-click on the copy icon. the values are filled in the right-hand columns.9 Analysis and monitoring tools It is possible to specify analysis transactions or URL addresses (including file directories) per monitoring objects.g. The name of the monitoring tree element (MTE) can be found by choosing F1.4. then the current and open view in the graphics will show the right alerts but it is not possible to work on these alerts within the Business Process Monitoring session as the alerts are not replicated there. Therefore it is necessary to call transaction RZ20 in the satellite system and to open a monitor that contains the required alert(s).7. you could be interested in monitoring the availability from a portal system that possesses no CCMS but is included as one business process step in your business process. You could then assign the corresponding alert via other CCMS monitoring to business process step running on the portal system. In order to load the threshold values that are currently valid in the corresponding system. As an example. e.4.7.8 Other CCMS monitors With other CCMS monitors it is possible to assign any CCMS monitoring tree element (MTE) to a business process step. on attribute level. The MTE name needs to be copied into the corresponding column of the table below (see screenshot Other CCMS monitors below). If successfully retrieved.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 1. Per default some standard transactions are maintained. i. the button can be used. Figure 8: 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. these should be used to analyze errors or problems either locally in the SAP Solution Manager system itself (Call Option 1) or directly in the respective satellite systems (Call Option 2). that provides a job © 2009 SAP AG page 17/82 . The MTE used for monitoring should be an MTE on the lowest leaf-level. If no active settings for the threshold values were found these columns remain empty. Under column Monitor Name it is possible to assign an individual name. transaction SM37.e. Now you could use one MTE in the CCMS of SAP Solution Manager to monitor the heartbeat of the portal. 1. If an MTE of a higher branch-level (collective MTE) is chosen.

http://help. For web pages to be called.sap. specify the full file path.. For content available on file servers. It is also possible to add new transactions.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download overview in an SAP system. is maintained for background jobs or transaction SLG1 to have a look into the application log..txt Figure 10: Analysis & monitoring URL © 2009 SAP AG page 18/82 . file://\\\server1\operations_documents\operations-handbook.com. You define a short text and the URL to be called.. e.g. Figure 9: Analysis and monitoring transactions On the second tab strip it is possible to specify a URL which should be called in order to further analyze the given problem.g. e. using the nomenclature: file://\\\<server>\. this could be standard transactions or customer self-written transactions. specify the full URL. This is especially interesting if you have some knowledge documents linked to a portal.

Support notifications allow setting up a service desk message in case of an alert.10 Monitoring activities Monitoring activities should be set up for every monitoring object within a business process step. To ensure effective monitoring and efficient problem resolution. an e-mail or SAPOffice mail. Persons who can be contacted should be maintained here. Person Resp. Describes at which time the responsible person should process the required monitoring activity.4. Describes the escalation path in case that the person responsible could not solve the problem. the button (e. ) contains the short text (limited to 20 characters) from the setup session and opens the defined URL in a new browser window.7. When you press these buttons.11 Notifications You can set up notifications for the whole business process or for each business process step individually.7. Defines the person who is responsible for monitoring the monitoring object. i. for instance .g. 1. That information is valid for the whole business process step and help users who have to carry out the monitoring and who are not familiar with that particular business process.4. Frequency Start Time Problem Indicator Error Handling Escalation Path Table 1: Problem resolution procedures You can enter additional information related to this business process step in the tables Monitoring Activities. 1. The information entered for © 2009 SAP AG page 19/82 . Use value help F4. All monitoring objects defined within a business process step are listed there. for further analysis. for instance. In case of URLs.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download When using the monitoring during a Business Process Monitoring session. assign responsibilities and define problem resolution procedures as described in the following table. Restart of Step and Escalation Path.e. Some information has been taken from the previous Solution Support Organization node. Use value help F4. you jump directly into the corresponding transaction. Error Handling. Describes how often the responsible person should process the required monitoring activity. There are two types of notifications: Workflow notifications and support notifications. Describes how to react on problems or errors. either in SAP Solution Manager (here: SAT) or the connected satellite system (here: CT1). the specified transactions or URLs are available as buttons within a business process step. A description about what indicates a problem. how to solve the problem or correct the error. Workflow notifications allow sending messages to a specified recipient in case of alerts. Monitoring Team Defines the team that is responsible for monitoring the relevant monitoring object.

Alternatively. R (remote SAP name) and C (shared distribution list). Defines the support component on which the message is put. Defines a default processor who should process the message. Number of YELLOW alerts that can occur before an automatic notification is triggered Number of RED alerts that can occur before an automatic notification is triggered Once the maximum wait time [hours] has elapsed. notifications can be defined for every monitoring type individually. To restrict this mechanism only to red alerts. Triggers a long text for e-mails or SAPOffice mails. There are currently five different recipient types: U (e-mail). all alerts related to background jobs of the business process are forwarded to a defined e-mail address. name of the solution. name of the business process step.g. but the user must have a valid e-mail address which the used mail server knows. i. the flag in column RED Only must be set.e.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download the service desk message serves as a template. you can define notifications for the whole business process. In case of an SMS you need to enter SMS:<cell phone or pager number>. K (for SMS and pager).g. e. of Yellow Alerts No. a remote SAP name or a shared distribution list. Processor © 2009 SAP AG page 20/82 . Workflow notification Sender Must be a user within in the monitoring client of SAP Solution Manager. This can be any email address. …) Recipient Address Reci. as soon as the business process gets an alert status. notifications will be triggered. an SAP user name in the same system. Notifications defined on business process step level will overrule the configuration made on business process level for this particular step. This user can even be a system user without any roles or profiles. the recipient name is required. of Red Alerts Max Wait Time [h] RED Only Detailed Table 2: Workflow notification Support notifications Priority Queue Defines the priority of the support notification. e. This component must exist within the service desk. The service desk message can be created manually or automatically. B (SAP user name). Depending on the recipient type. Type No. a notification is created even if the thresholds are not exceeded. On business process level. The processor must be known within the service desk and must be SAP user name defined as a business partner with role employee.

You need to define 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. Automatic Reporter Num of YELLOW Alerts Num of RED Alerts Table 3: Support notifications If in addition to Queue. Necessary if service desk messages are created automatically. In case that both columns are filled with a value. after five red alerts a service desk message should be created. This includes the definition of the roles and responsibilities involved. the automatic support notification creation works with a logical OR operation. Support notifications will be created automatically depending on the alert thresholds. 1. © 2009 SAP AG page 21/82 .and Problem Management processes and the Change Management process. This symbol indicates a paragraph from where you can navigate to another document within the SAP Service Marketplace for more detailed information on a topic. This includes the final communication of open alerts to SAP. A Business Process Monitoring concept has to be tightly integrated with the support organization. the automatic support notification creation is configured. after ten yellow alerts a service desk message should be created.7. e. separate communication and escalation paths and procedures have to be defined. e.7. 1.6 Legend This symbol indicates a paragraph from where you can navigate to another chapter of this document for more detailed information on a topic. Wherever communication connected with Business Process Monitoring happens outside these support processes. Must be a SAP user name defined as a business partner with role general. Priority and Reporter either one of the columns Num of YELLOW Alerts or Num of RED Alerts is filled with a value. Processor. Hence. This includes the integration with the Incident.g. with the figures in the table above the system would create a support notification if there are either more than nine yellow alerts or more than four red alerts for which no support notification has been created yet. Necessary when service desk messages are created automatically. you have to define a process for implementing your monitoring concept. These processes have to be adjusted to the Business Process Monitoring concept so that communication and escalation procedures defined within these processes support the Business Process Monitoring concept.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Text Template Text templates can be defined that will then be available for service desk messages manually created for alerts.g. Please see the separate Best Practice for General Business Process Management for further details.5 Business Process Monitoring process For a successful and efficient Business Process Monitoring. Necessary when service desk messages are created automatically.

calculation of promotions and bonus buys and so on. First option is to use the standard POS outbound interface which is a set of functionalities and IDocs to transmit master data to POS systems with key focus on article. prepares and sends the relevant data to the stores. The initialization usually needs to be done once for the stores concerned. The second option is the so called assortment list. The relevant IDoc type is WP_PLU which can be accompanied by other data objects (IDocs) for merchandise categories. An option for data mapping tools is SAP PI to be used and also for POS system to use SAP POS or SAP EPOS with both integrated standard content © 2009 SAP AG page 22/82 . currencies. This chapter deals with both available business process variants to support information exchange with POS systems.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 2 Business Process Monitoring for a Point of Sale (POS) Download Data Transmission Point of sale (POS) outbound processing or so called POS download is the business process where the central SAP ERP system in head office. which is the key system for maintenance of retail related master data such as articles and prices. the central SAP ERP system in head office with the local point of sale systems using data transfer tools via internet and phone and also middleware for data mapping and data conversion. and price. change message. stock etc. customers. three processing modes are possible: Initialization. Then you only have to plan at regular intervals (usually daily) the program for evaluating changes. and manual request. The manual request usually is for exceptions or error handling and does not interfere with change message. goods receipting. So this document uses the POS download term when referring to the business process independent from the process variants which are POS outbound IDoc types and assortment list IDoc types. This is a set of functionalities around the IDoc WBBDLD which is able to transmit more complex information related to article like source of supply. so called IDocs. The assortment list is usually also known with relevance to other business processes like supporting printed list of SKUs in stores on paper or to support SAP for Retail Store online connectivity of back office in store. These changes are done by business persons in head office and are relevant for a specific store. POS download business scenario is usually the pre-condition to be able to run POS inbound or so called POS upload processing to record sales performed. it sends the full set of all articles listed in the store. But for that BPM procedure these business processes are out of scope. taxes. And very often that information needs to fit to advertisements published. Therefore. The POS outbound process links usually at least three technical systems/ platforms. Common to both business process variants for POS download is the task to send out data changes. EAN. This is recommended if additional retailing functions (such as the entry of a goods receipt) also have to be carried out in a store retailing system. Only the transmission of IDoc for assortment list is in scope. EAN references. The POS download process is extremely critical in a retail environment because it ensures that the local POS systems in stores have the right information to be able to perform necessary tasks like selling. and bill of materials. promotions and bonus buys. You can recognize this in two different resulting data record types.

an additional transaction WPER2. also the required system performance and throughput is critical in retail environment. This is because of the potentially high number of Stock Keeping Units (SKUs) in a store and SKUs changing in seasons and also usually a high number of stores in a retail chain. and store formatting need a good and lean set up in project mode and a strong monitoring in production mode. The POS interface monitor transaction indicates for which stores preparation and transfer of data was completed and IDocs have been created. The POS interface monitor uses information from the status tables of POS download. © 2009 SAP AG page 23/82 . To enable you to monitor SAP ERP POS download processes even better. Also technical abilities and functions like performance monitoring. This is the POS interface monitor. and also error logs for faulty IDocs are displayed in order to allow corrective actions. pricing. It also indicates which IDocs contain errors. providing several individual reports for troubleshooting. data volume management. Moreover. how many errors are in an IDocs. in the real monitoring procedure it does not make a difference. In the year 2000 the high performance retailing initiative (HPR) which has been an SAP program to deliver bundled performance enhancements in SAP for Retail and ship to customers had been able to achieve a higher data throughput with SAP for Retail for key business processes. In fact. and data archiving need to have a strong focus in production mode. and the HPR assortment list processing are considered. These checking tools are able to be executed after a POS download run periodically to indicate further issues with POS outbound and assortment list. The following table highlights the improvements delivered with the HPR version in bold and the possible use: Condition Change Document Index in Table WIND Normal assortment list HPR assortment list POS outbound WP_PLU Not possible Mandatory (see OSS 603472) Enabled Enhanced Change Pointers Table BDCP2 Enabled Enabled Enabled Table 4: HPR version improvements In this document. SAP ERP provides a separate monitoring transaction to monitor the success of the transmission of data changes. But this BPM concentrates on monitoring requirements inside SAP ERP and handles data mapping and POS as black box. Also the business process of POS download for both variants. POS outbound and assortment list had been key areas of improvements. It can be used to track each transfer and type of preparation. Therefore the POS download and its related areas like listing. the normal assortment IDOC processing. all this can go along with more or less complex price rules up to store specific pricing. Therefore. No customizing settings are necessary to execute these reports but the monitoring team needs to carefully study the background of reports provided. In addition to the business importance of that process.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download delivered. these reports available in transaction WPER2 are discussed in greater detail within this document. both. has been delivered by SAP.

The reports and features (mentioned in the following chapter) and the OSS notes (mentioned in chapter Further Information) together with online help are that detailed and comprehensive to enable a project team to migrate to new HPR improvements if operator recommends to increase performance. you need to follow the procedures described in the online help for POS outbound. © 2009 SAP AG page 24/82 . When intending to use WIND technology for POS outbound. The system only updates a new work list table as soon as conditions are saved. Another result of HPR improvements is the use of the condition document index to find and send changed price conditions. The improvement is facilitated by the new table WIND. They need to understand the background why this BPM gives for assortment list business process different reports and transactions. Please keep in mind the background of OSS note 603472 (WIND is mandatory for using HPR assortment list). An achievement of the HPR initiative was the introduction of the HPR assortment list which facilitates the creation of WBBDLD IDoc with modified scope/ content through new SAP transactions. SAP provides migration reports and procedures. the setup of these tools is not in the scope of this solution operations document. using this monitoring BPM need to be aware of possible potential to increase performance using the improvements from high performance retailing. Hence. the introduction in chapter 2 highlights the HPR improvements to the audience of this document. The change message of IDocs refers to that table. For POS outbound. see OSS note 720514. Report RWDBBMIG (see OSS note 603472) to migrate change pointers for condition changes from either BDCP/BDCPV or BDCP2 (depends on setting in table TBDA2) into WIND. Using the WIND table change pointers must not be used anymore for price changes. The WIND technology is enabled through IMG configuration as follows: Select Retail Pricing • Pricing Worklist • Direct Entry for Creating Worklist For customers already using POS download business process and having change pointers for condition changes in tables BDCP and BDCPS. For more information see chapter Further Information with OSS notes mentioned. A further improvement of HPR initiative is a new table for change pointers for non-condition-related changes – instead of BDCP and BDCPS the new table BDCP2 is used. For details regarding the modified scope and especially reduced business functionalities to accommodate for performance. But also the operators. See OSS note 305462. The description includes the use of report RMEBEIN4 and especially of report RMEBEMIG to set the migrated flag. The evaluation of conditions changes is also described in OSS note 519685. you may not forget to delete all records for message type WP_PLU and object COND_A with transaction BD52.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Tools like WIND and BDCP2 are typically set up during the implementation project. Therefore. describing the necessary steps with migration transaction BDCPMIG and necessary customizing in BD60 for POS outbound and for assortment list. who wants to increase performance by introducing WIND.

Maintain (new) store as master data called site in SAP ERP 2. Monitor the data transfer. is a multi channel retailer founded in Switzerland running stores all over USA and Europe.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download The following steps need to be done if you want to use full advantage of high performance retailing: Archive (delete) processed or old change pointers Activate BDCP2 for IDocs. Wonderful Food & Clothes Ltd. transform with data mappings and send off files from middleware to POS 9.1 Sample Scenario Wonderful Food & Clothes Ltd. Therefore. List articles to new store 5. Receive IDocs. Copy the IDocs for the US stores and transmit all IDocs 4. The franchisees use different kinds of EPOS systems from various vendors. In Germany. In the USA they have a lot of small corner stores because Americans like good food from Switzerland. decided to use POS outbound IDocs (among others WP_PLU) to give their franchisees the possibility to support the various requirements of different EPOS systems. They also plan to use SAP for Retail Store starting next year. new listings. Archive the IDocs 8. Spain. and again run change message as well as send IDocs off 5. Switzerland they run company owned stores offering also a wide range of services especially for brides. correct the data. Portugal. Wonderful Food & Clothes Ltd. Delete the processed change pointers 7. Maintain merchandise categories and assign to store 3. If a store is a new store in SAP ERP. according note 305462 Migrate BDCP to BDCP2 Activate WIND Migrate BDCP2 to WIND 2. For their own stores they use a POS solution from SAP with integrated content and SAP PI. especially main EAN 4. Data mapping from IDocs to the various POS solutions is done with various tools in the responsibility of franchisees. They use the POS outbound process with assortment list IDoc. So they run the following core business processes: 1. runs an initialization or dummy initialization 2. Austria. new prices with the created IDocs 3. Eastern Europe and in Scandinavia they are present using franchisee business. they decided to use HPR assortment list for the US stores. 1. In Italy. Reorganize change pointers with deletion of status records in table WDLS to keep next change run smooth and avoid change pointers to be processed a second time 6. Run change message for stores to send off daily new articles. Maintain prices for articles in store The above mentioned process steps are processes done by the business as master data maintenance in category management and are not described on the current BPM but they are the trigger and input for POS outbound process. POS system receiving files via phone line and update central store back office server © 2009 SAP AG page 25/82 . Maintain articles as master data in SAP ERP. Because of a bigger number of stores and their smaller range of processes.

explaining where and how you can identify focus points for Business Process Monitoring. which means each store only receives data that is relevant to that store. The system formats data specifically for individual stores.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download The following chapters takes you step by step through these business processes. The system determines which data have changed up to the current date and which data are going to change during the configured lead time. The SAP ECC system formats the data in question in IDoc format for the POS outbound interface. Please see following process flow: Figure 11: Process flow point of sale outbound variant 1 with POS interface IDocs © 2009 SAP AG page 26/82 . For each business process step the most effective ways for Business Process Monitoring in the context of the example are highlighted. taking account of the current store assortment and transfers these IDocs to the store systems using ALE (application link enabling) technology. This is usually done in the evenings and covers a specific lead time period (usually a few days to prepare data changes ahead). 2.2 Business Process POS Outbound with POS Interface IDocs As stated above the POS outbound IDocs are used to supply simple POS systems in stores with updated data at regular intervals.

In this case. Other objects have data that does not change during the lead time. POS outbound does not work with one. but with nine message types simultaneously. note the following correlations for the activation of change pointers: Logical Message Type That Is to Be Sent WPDWGR WP_PLU WP_EAN Object Message Type to Be Activated Merchandise categories Article master EAN/UPC References WPDWGR WP_PLU WP_EAN WP_PLU WPDSET WP_PLU WPDSET (!) WP_PLU WP_PER No activation required as no change pointer analysis is necessary No activation required as no change pointer analysis is necessary No activation required as change pointers are created directly from the application and not using the ALE layer WPDSET Set assignments WDPNAC Follow-On Items WP_PER WPDTAX Personnel Data Taxes WPDCUR Exchange rates WPDREB Promotion discount Table 5: Correlations for activation of change pointers © 2009 SAP AG page 27/82 . Unlike standard ALE master data distribution.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Special messages and intermediate documents (IDocs) for POS systems are defined for the following objects: Merchandise categories (IDoc category: WPDWGR01) Articles (IDoc category: WP_PLU02 or WP_PLU03 if article hierarchy is used) EAN/UPC references (IDoc category: WP_EAN01) Set assignments (IDoc category: WPDSET01) Follow-on items (IDoc category: WPDNAC01) Exchange rates (IDoc category: WPDCUR01) Taxes (IDoc category: WPDTAX01) Person data (IDoc category: WP_PER01) Bonus buys (IDoc category: WPDBBY01) Promotion discount (IDoc type: WPDREB01) Some of these objects are time-dependent which means that their data can change within the lead time. It is important to be aware of this fact if you do not want to send certain message types.

2.1.1.1. Scenario-specific sample Usually you select one store by the other by creating a job variant per store if you would need to initialize more than one store in one point in time.1 2.5 2.1. 2. It transmits all listed articles in a store with all related data. If the POS system contains all the necessary data in the first start-up of the POS outbound – maybe the database of an already existing store back office server was copied to the new store back office server – a dummy initialization can be done. but only creates special entries in the status table WDLS of the POS outbound.1.) Scheduling of background jobs (in this table you find all relevant information to schedule the jobs in the recommended way) 2.1. using program RWDPOSDU.3 Description and general information Monitoring requirements Monitoring objects in SAP Solution Manager (in this table you will find all monitoring objects in SAP Solution Manager you should use to monitor your solution) Further monitoring objects (in this table you find the monitoring objects you should monitor using special reports or transactions) How to find meaningful thresholds per monitoring object (all aspects which are described within this subsection are hints how you could find thresholds for the monitoring objects you should monitor.1.3.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Note: Each chapter will be structured in the following way: 2.2 2.1. These entries allow the system to start creating change messages after the dummy initialization. In most cases several IDocs are created. To run initialization start transaction WPMI and plan the program RWDPOSIN initialization in the background as you can expect a long runtime.2.4 2.6 It is a strongly recommended Best Practice to use SAP Solution Manager to monitor these objects as described in section 2.1 2. when a new store opens and gets a new store back office server you would expect the store back office server to be empty and therefore needing this data provided by SAP ECC.1 Business process step 1: Initialize or dummy initialize new store Description and general information The initialization is the prerequisite for transferring change messages.1. Normally.1. © 2009 SAP AG page 28/82 .1.1.1.1.1. The system does not transfer any data to the POS systems.

Throughput monitoring In case the time window for an initialization run might be not sufficient for the relevant article data volume. job cancellation . when job is running.1. there is the possibility to run manual requests with article number ranges. The dummy initialization is not critical at all because it just sets a flag in a table and it is very likely that no error will occur.3 Monitoring Object Report RWDPOSIN (initialization execution) Further monitoring objects Selection Criteria RWDPOSIN. For error monitoring for initialization mainly the POS monitor transaction WPER is used. After job execution Long job runtime.2.1. If initialization failed you need to correct data and repeat the execution at a later point in time if necessary.2 Monitoring requirements Error monitoring It is very important to know that the program must be completed with the status X (error free) or H (notes). While the job runs for a store. The only thing you can do in advance is to plan no other system resource consuming jobs at the same time and optionally. time out. date of job (usually current date) Alert Analysis Tool on Satellite System SM37 Monitoring Frequency/ Data Collection Runs usually once when new store opened. Otherwise no change messages will be created. After that you run dummy initialization to set the status correctly. Backlog monitoring See comments on throughput monitoring. job canceled or delayed Report RWDPOSDU (dummy initialization execution) RWDPOSDU. 2. it needs to create and find all articles. This means preparation is OK (field WDLS-GESST is X or H). Performance monitoring For performance monitoring of an initialization you need to watch the runtime of the job.2. long runtime is not likely as this job just creates one table entry in table WDLS. apply extraordinary basis parameters. monitor in periodic intervals system/runtime performance Usually once when new store opened (as an alternative to RWDPOSIN when store database has full data already copied from other store back office server etc. Background job for RWDPOSIN and RWDPOSDU Check the job log SM37 for cancellations. It neither can run in parallel nor can it be split by article number ranges. Check POS monitor WPER for status and error logs. You see the status in POS monitor as Format Status. SM37 Processing status of initialization in POS monitor Date of job finished and outbound application POS Look for tree branch in outbound processing – not fully processed – preparation mode I = initializations: Double click to read system log text with error message WPER © 2009 SAP AG page 29/82 . error messages in job log.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 2. This allows providing the store back office server database with IDocs. date of job (usually current date) Job cancellation.

Throughput monitoring To increase throughput. It is also necessary to monitor the job in SM37. For more information please refer to chapter 2. listing. A processing without errors or hints is indicated by X in this field. Performance monitoring For performance monitoring of a change message you need to watch the runtime of the job.e.2 Business process step 2: Evaluate master data changes. 2.4. The data.2. select relevant stores. come from configuration of POS outbound profiles which is assigned to the store. what kind of IDocs should be prepared. the distinction depending on configuration takes place if HPR features like WIND or BDCP2 are evaluated. So in most cases WP_PLU IDoc plus several others are created with that job according to POS outbound profile.1. the distinction depending on configuration takes place if HPR features like WIND or BDCP2 are evaluated. i. Here too. enter a server group on which a parallel process shall run.1 This step runs the job for the daily change message which collects the changes becoming valid in future in the lead time or done by business in daily online transactions like article maintenance.2.2. 2. Scenario-specific sample The data are prepared for the stores selected in the job variant. Errors occurred if table WDLS shows in field GESST H. © 2009 SAP AG page 30/82 .2. If the job finishes correctly it will not show application errors in job log as the application errors will be shown in POS monitor transaction with long text and description.4 How to find meaningful thresholds per monitoring object Every error that occurred is critical as it will lead to wrong information in the registers of the stores. create IDoc Description and general information 2.2. In the report RWDPOSUP you can set the flag for parallelization. parallelization should be used. and enter the maximum number of parallel processes. price maintenance.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 2.2 Monitoring requirements Error monitoring For error monitoring of change messages mainly the POS monitor transaction WPER is used. customer maintenance.2. Background job for RWDPOSUP Check the job log for cancellations and runtime. collect and prepare data.2. The changes are evaluated and the data which needs to be transferred is prepared and completed and saved in an IDoc. Here too.

2. This is critical since IDocs are not created and the prices and other data cannot be sent to the store in time. Then you need to work out with business how many changes they do on average and look how long a job takes on average and work backwards. So if stores open at 08:00 clock. Transmission and conversion need about one hour.2. © 2009 SAP AG page 31/82 . you need to work backwards on your timetable under consideration of the time for conversion and for transmission as well as some security time to determine when RWDPOSUP has to be finished at the latest. So business can make the operating team aware when they are going to change lots of data at one point in time and POS outbound is likely to work with much more changes than normal.2. The operator also needs to be in touch with the business process champion. when a new season with new prices starts or new collections are listed.4 Monitoring Object Further monitoring objects Selection Criteria Alert Analysis Tool on Satellite System Monitoring Frequency/ Data Collection After job execution Processing status of change message in POS monitor Date of job finished and outbound application POS Look for tree branch in outbound processing – not fully processed – preparation mode u = update doubleclick to read system log text with error message WPER 2.2.3 Monitoring Object Monitoring objects in SAP Solution Manager Selection Criteria Alert Analysis Tool on Satellite System Monitoring Frequency/ Data Collection Every five minutes during every job execution Background job S_DE_R_RWDPOSUP_D (Report RWDPOSUP) (changes message execution) S_DE_R_RWDPOS UP_D. it is not finished.5 How to find meaningful thresholds per monitoring object You can determine the threshold when POS outbound needs to be finished depending on your business needs. For example. That increases risk that stores are selling articles being priced incorrect. it must be assured that RWDPOSUP is finished at 07:00. the operator would need to change starting time of RWDPOSUP to accommodate for longer runtime because of a larger amount of data. If a job takes too much time. job cancellation . If business leaves average due to business reason you need again to accommodate threshold and start the job earlier.2. 2. Therefore. time out. Scenario-specific sample It is import that RWDPOSUP finished in time before stores are opening and require correct prices.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Backlog monitoring It is important to watch the runtime of the job regularly. error messages in job log SM37 2. RWDPOSUP Long job runtime.2.

if the stores can be grouped and a reference store can be determined. the SAP system logs these reference IDocs in table WDLCOPY. This means to optimize performance and decrease runtime it is not necessary to generate IDocs for all stores but just for certain reference stores. The partner profiles for the recipients must be maintained in such a way that IDocs are collected first.2.6 Scheduling of background jobs This job is usually scheduled on a daily basis in the evening after all master data changes have been carried out in the system. Job scheduling requirements Recommended or Generated Job Name ABAP Report Variant Scheduling Predecessor Job Successor Job Scheduling Restriction Error Handling in Case of Cancellation Root cause analysis required.3.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 2. DE for the involved organizational information. The name is defined in accordance with the naming convention specified in the Best Practice document Job Scheduling Management to be found under https://service. It can significantly improve performance.2.sap. Then these IDocs created for the reference stores with RWDPOSUP can be distributed according to certain rules.1 From many stores the POS download IDocs (POS outbound IDocs and assortment list IDocs) are identical or only differ very slightly. Please note that this solution is optional and does not apply for customers where for example store individual prices exist.3 Business process step 3: Copy IDocs within ECC retail (optional) and send out IDocs from ECC retail Description and general information 2.2. All recipients that are assigned to a reference must be assigned to one and the same file port. The nam e indicates: S for SAP standard coding. The following chapter describes how this copying mechanism is set up. Define an ABAP programming interface port in the port description (IDoc and EDI basis) and assign it to the function module WDL_COPY_LOG. RWDPOSUP is the ABAP report. Using the programming interface port. Then for the stores which are able to get a copied IDoc only a dummy initialization is required. which is assigned to each reference customer within the partner profile. 1 © 2009 SAP AG page 32/82 . In addition. Various applications generate outbound IDocs for the reference recipients. To enable copy management for IDocs there must be a copy rule in the SAP system.com/solutionmanagerbp. R for the involved business/application area. D for the daily job frequency. you can use IDoc copy management as a one-off for the initialization as described in step 1 for the initial supply of a new store.2. A programming interface port must be assigned to the reference recipient. potentially a restart might be sufficient Restart job S_DE_R_RWDP RWDPOSUP 1 OSUP_D To be defined Runs usually daily. The IDoc copy management tool uses this log. The IDoc copy management tool sends the IDocs automatically. File ports must be assigned to the recipients of the copies. monitor when job is running in periodic intervals system/ runtime performance Daily S_DE_R_RW DPOSUP_D S_DE_R_RS EOUT00_D if IDocs are not sent automatically S_DE_R_RSEO UT00_D RSEOUT00 2.

See screenshot how the job’s log for the report RWDLCOPY_MANAGEMENT looks like: Figure 12: Results of IDoc copy management tools Performance monitoring You need to monitor the runtime of jobs for both reports but usually they are not performance critical.2. You also have to monitor the job for report RSEOUT00 and check in the log if everything is alright. The most performance critical job is RWDPOSUP which is described earlier in this document.3. It then generates trigger files for the individual recipients for each message type if this is set in the copy rule.2 Monitoring requirements Error monitoring You need to monitor the job for report RWDLCOPY_MANAGE and check the log for potential errors.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Program RWDLCOPY_MANAGE copies the reference IDocs to the recipients (customers) that are assigned to it using the copy rule. SAP strongly recommends this for performance and monitoring reasons and as stated above mandatory for the IDoc copy management tool. which sends out the collected IDocs in ECC database as files to the following conversion tool. RSEOUT00 is required if in the partner agreement configuration in WE20 the IDocs are set to collect IDocs. 2. © 2009 SAP AG page 33/82 . Another program is RSEOUT00. The tool optimizes its performance internally using asynchronous processes. Multiple scheduling is therefore not recommended.

partner type. WPDNAC. error messages in job log S_DE_R_RSEOUT00_D. error messages in job log SM37 Every five minutes during every job execution Direction. partner number. WPDREB in an error-status WE05 or WE02 Every 15 minutes 2. Therefore. 2. job cancellation. © 2009 SAP AG page 34/82 . time out. WPDSET. WP_PLU. job cancellation. WP_PER.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Throughput monitoring Here you only have to make sure that RWDLCOPY_MANAGE and RSEOUT00 are planned in time – before data are required in store for selling and under consideration of the required time for data conversion and transmission outside ECC.2.3 Monitoring Object Monitoring objects in SAP Solution Manager Selection Criteria Alert Analysis Tool on Satellite System SM37 Monitoring Frequency/ Data Collection Every five minutes during every job execution Background job S_DE_R_RWDLCOPY_ MANAGE_D (report RWDLCOPY_MANAGE ) Background job S_DE_R_RSEOUT00_ D (Report RSEOUT00) (IDoc transmission off ECC ) IDoc processing status in case of IDoc interface S_DE_R_RWDLCOPY_M ANAGE_D. message type.2. IDoc age Number of IDocs of type WPDWGR. message code. RWDLCOPY_MANAGE. message function. Long job runtime.4 How to find meaningful thresholds per monitoring object You can determine the threshold when the POS assortment list needs to be finished depending on your business needs. port. under consideration of the time for conversion and transmission and some security time to determine when RWDLCOPY_MANAGE and RSEOUT00 must be finished at the latest. partner function. WP_EAN. you need to work backwards on the timetable from when you need the data. time out. basic type. WPDCUR. Long job runtime. WPD_TAX. RSEOUT00.3. Backlog monitoring Make sure that RWDLCOPY_MANAGE and RSEOUT00 are planned in time before data are needed in store.3.

and how many errors occurred (you can display an error log for incorrect IDocs) Which data areas are contained in the IDoc (smallest and largest object key) Which data an IDoc contains © 2009 SAP AG page 35/82 . Scenario-specific sample You can verify the following information using the POS monitor: The recipient of the IDoc The system type the IDocs belongs to (POS outbound or assortment list) When IDocs are created for the recipient The type of preparation (for example initialization. and repeat POS outbound Description General information The business process for POS download has a separate transaction for the operator role. change message) Whether preparation and transfer of data was completed How many IDocs were created for each recipient Whether the IDocs were created completely for each recipient To which IDoc type the IDoc in question belongs (for example. the POS monitor.4. the jobs are scheduled after the POS download on a daily basis. This can be valuable for tracking a request and the corresponding IDoc number through the process steps outside SAP ECC. it is also a good tool to check for successful transmissions.3. Job scheduling requirements Recommended or Generated Job Name S_DE_R_RWDLC OPY_MANAGE_D S_DE_R_RSEOU T00_D ABAP Report Variant Scheduling Predecessor Job Successor Job Scheduling Restriction Error Handling in Case of Cancellation RWDLCOPY_M ANAGE RSEOUT00 Daily S_DE_R_RW DPOSUP_D S_DE_R_RW DLCOPY_MA NAGE_D S_DE_R_RS EOUT00_D Daily 2.4 2. correct.2. article master.2. The POS monitor is not only used to view errors. The POS monitor transaction should be viewed daily after processing the report RWDPOSUP change message and report RWDPOSIN initialization and a manual request report RWDPOSAN. Moreover. EAN/UPC references) The key (IDoc number) under which the IDocs can be found in the database How many segments the IDoc contains Which IDocs contain errors.5 Scheduling of background jobs If copy management is used.1 Business process step 4: Monitor.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 2. it is used to find the corresponding IDocs after a report or request for POS outbound was performed.2.as it helps you to find out when and with which content the IDoc was created.

4. An IDoc was created and the operator has to decide if the business needs to be involved for a change. These requests are visible in the sub-tree for not fully processed requests.2 Monitoring requirements Error monitoring using POS monitor transaction WPER Mainly the operator has to deal with the not successful transmissions.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Screenshot of POS monitor (POS outbound): Figure 13: Screenshot of POS monitor (POS outbound) 2. The error message can just be a warning. The operator has to view error messages to delegate the actions to either IT or business to get business errors and data corrected. © 2009 SAP AG page 36/82 .2. Another possibility is to use the transaction SLG1. no IDoc will be created. If there was a problem – classified as error in format status with data preparation (in step 2 with RWDPOSUP or already in step 1 with RWDPOSIN) – mostly. The error text can be read from system log by a double click. Then the operator is able to repeat transmission.

which had been displayed for POS download messages in POS monitor. Therefore it is very important to solve the occurring issues and to save the entire record successfully into the status tables (WDLS tables). which will include the data that was not transferred. As a result. a price is sent down four days in advance. This has an enormous impact on performance of RWDPOSUP. In this case. will be repeated on the next day.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Figure 14: Display logs Once all errors. This highlights the necessity of correcting the errors every day: If an error is not corrected and the error status remains for a long time all the data from the previous days will be analyzed and transmitted. all data that were not transferred because of errors will be re-processed and transferred. In terms of performance this procedure is a better way than preparing all the data again. It is possible to wait for the next day if there is enough lead time: The lead time sends down data becoming valid in future. You can do this by executing the relevant batch report RWDPOSUP immediately during day time. If a large number of errors occurred. which were not successfully transmitted. have been corrected. If you wait for the next change message (running one day later than the current change message). © 2009 SAP AG page 37/82 . including the current day. a runtime error may cancel the preparation. choose Repeat preparation in the POS outbound log. it is only three days in advance at the store back office server but still early enough. If the lead time is five. Scenario-specific sample Transmission of data. you should repeat the entire POS outbound processing RWDPOSUP. Or you can wait for the next change message.

there is a central group report that you can run to analyze data constellations for generating POS outbound IDocs and assortment list IDocs. This report can be used for specific sites and/or articles. which need to be prepared and sent by the POS outbound within certain IDoc types. © 2009 SAP AG page 38/82 . WPER2: Object analysis in the POS outbound This report checks the IDoc types to be exported via POS outbound processing and determines whether the program will encounter any errors. Scenario-specific sample If an article for a store is not sent in the POS outbound IDoc. the article and store numbers can be entered and the report started. If the article has not been correctly maintained. This means this program enables you to check whether objects. This group report is accessible through transaction WPER2 and consists of several individual reports. The individual reports can be seen in this screenshot: Figure 15: Individual reports Please note that dummy initialization has been discussed already in step 1 and will not be discussed in this chapter. are correctly and completely maintained from master data management.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download It has also an impact on outstanding steps of business process step 5 and 6 as the change pointers and status records are not reorganized and deleted. The highlighted column provides information as to why the object (material) was not prepared. at least one indicator appears in the output list. Error monitoring using POS object analysis in transaction WPER2 In addition to the daily monitoring on POS monitor.

The article is also not listed in the store selected and has no price for the store selected. This report provides a quick and easy way to search for such an object. if necessary.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download For example. so EAN is marked as missing since this is mandatory for creation of WP_PLU IDoc. the reorganization program of POS outbound can fail while running the retail-specific report RWDPOSRS (see coming step 5 below). Figure 17: POS outbound reorganization check WPER2: IDoc analysis in the POS outbound It often happens that you need to find a specific object among thousands of IDocs and in the segments of the IDoc. the article chosen in the screenshot has no EAN. This leads among other things to a dramatic increase in the volume of data and therefore a reduction of performance. The alternative transaction WE09 would be less easy to handle in this case. the elimination of the reason. That is why WLK1 table for listing and price is marked. © 2009 SAP AG page 39/82 . Figure 16: Object analysis POS outbound WPER2: Reorganization check in the POS outbound For various reasons. This report enables a reason analysis and.

For POS outbound and for assortment lists this is hard to find since IDocs are generated daily for each store. you can use this report. Figure 18: IDoc analysis POS outbound selection screen Figure 19: IDoc analysis POS outbound result © 2009 SAP AG page 40/82 . So the required article has to be found inside of many IDocs. The report enables a quick and simple object search with regard to the POS outbound basis IDoc. which is maintained in master data management in SAP ECC. and connectivity. This information is required to search in the other subsystems for issues related to data mapping. conversion.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Scenario-specific sample If you need to search for a special article and its price in an IDoc segment because the store back office server does not show the correct price. using various selection criteria and combinations from a set selection of any size. It helps you to find out in which IDoc and at which point in time an article left the SAP ECC system.

Scenario-specific sample The background is that the processing of the change pointers keeps change pointers valid until the change had been transmitted to all stores. None of the previous data will be omitted. no performance monitoring is necessary since these are online monitoring transactions themselves. you have to reproduce errors. the change pointer table keeps growing due to the fact that this one store has not been processed. In that case. The following status changes are possible: Changing the status from X or H to status W means that all objects from the last download. two things will happen: For this store. Backlog monitoring using reorganization check option in transaction WPER2 Please see comments on performance monitoring. during which time the system may detect new change pointers. You can reverse unwanted status changes without any consequences under condition that a download in the form of a change analysis has not taken place in the meantime. This enables you to determine how to fix them. There is usually some time delay (perhaps a few days) between the POS run and the analysis. This report does not work if the change pointers were already deleted after the previous run. you can resend data or prevent redundant data from being sent. If for any reason a store did not have a change run for a longer time (POS outbound profile assigned and initialization done so that valid WDLS entry exists with I for initialization but then no update RWDPOSUP done for long or failed) this change pointer does not get set processed in step 5. the changes starting from that point in time in the past when the error happened are processed every day until the error is resolved. So the change pointer will not be deleted. will be resent in the next download. Performance monitoring During actions described in this chapter. This may cause the reprocessing report to include more articles than the original download. This new data is in addition to all the previous data. Throughput monitoring Please see comments on performance monitoring. especially the reorganization check. If a store has an error message for a topic which is not solved. The Report RWDREPROCESS2 enables this. which were triggered by change pointers. The change pointers related to that erroneous business change cannot be deleted and thus influence – because of a higher number of change pointers – the processing for the other stores as well. Changing the status from W or E to status H means that only those objects that have been changed since the previous download will be sent. Using these reports regularly. This report allows you to do a test rerun using the same change pointers that were handled in the previous download.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download WPER2: Reprocess in the POS outbound When troubleshooting. is essential since this has a positive impact on performance of RWDPOSUP. © 2009 SAP AG page 41/82 . By changing the status.

time out. message function. partner function. error messages in job log WPMU SM37 If several data had been corrected and are also needed in store quickly and can not wait until processing next day or if lead time is too short. idoc age If report shows an object with WPER2. Every five minutes during every job execution Background job S_DE_R_RWDPOSUP (Report RWDPOSUP) S_DE_R_RWDPOSUP. job cancellation .2. WPDCUR. time out.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 2. basic type. action to perform need to SM37 make decision how to act Every five minutes during every job execution Background job S_DE_R_ S_DE_R_ RWDREPROCESS2_M. RWDPOSAN Long job runtime. error messages in job log WPMA SM37 If corrected data are urgently needed at POS back office server in store. WPDSET. port. WP_EAN. cancellation . job cancellation . error RWDLCOPY_MANAGE messages in job log Background job S_DE_R_RWDPOSAN (report RWDPOSAN) S_DE_R_RWDPOSAN. RWDREORGCHECK If report shows an object with WPER2. WPDREB in an error-status WE05 or W E02 Every 15 minutes © 2009 SAP AG page 42/82 . message type. WP_PER.4. WPDNAC. WP_PLU. partner number. WPD_TAX. action to perform need to SM37 make decision how to act Every five minutes during every job execution Number of IDocs of type WPDWGR. RWDPOSUP Long job runtime. partner type. time out.3 Monitoring Object Monitoring objects in SAP Solution Manager Selection Criteria Alert Analysis Tool on Satellite System SM37 Monitoring Frequency/ Data Collection Every five minutes during every job execution Background job S_DE_R_RWDLCOPY _MANAGE_D (report RWDLCOPY_MANAG E) S_DE_R_RWDLCOPY_MA Long job runtime. message code. RWDREPROCESS2_M WDREPROCESS2 (Report RWDREPROCESS2) IDoc processing status in case of IDoc interface Direction. Every five minutes during every job execution Background job S_DE_R_ RWDREORGCHECK _M (Report RWDREORGCHECK) S_DE_R_ RWDREORGCHECK _M. job NAGE_D.

The POS outbound does only transmit an article and create an IDoc when the article is listed.6 Error handling per monitoring object Use transaction WPER and WPER2 like described above.4 Monitoring Object Further monitoring objects Selection Criteria Alert Analysis Tool on Satellite System WPER Monitoring Frequency/ Data Collection Daily after RWDPOSUP and RWDPOSIN and WPMA transaction WPER POS monitor Date of job (usually current date). When corrections have been carried out. The error message in POS outbound often says Intermediate Document missing which means no IDoc has been created. application POS and look for store in question Object to be checked Appear in tree branch for Not fully processes Report RWDDOWNLOAD Object analysis If the report shows an object with an action to be performed. but scheduled by request after manual interventions have been necessary.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 2. a job chain containing the change analysis and IDoc creation program.4. © 2009 SAP AG page 43/82 . and a sales price.4. the copy management.2. This is one reason why SAP has developed the report for the object analysis in transaction WPER2.2. and the IDoc distribution program can be started. 2. a decision needs to be taken on how to react WPER2 As required Report RWDIDOCPOS IDoc analysis Object to be checked WPER2 As required 2. 2.4. a decision needs to be taken on how to react If the report shows an object with an action to be performed.5 How to find meaningful thresholds per monitoring object An error mostly indicates that the master data has not been maintained correctly by the business users. Usually errors are shown when the system has not been able to create IDocs.7 Scheduling of background jobs If manual corrections have been finished. It is to supply more details why the intermediate document has not been created. These jobs are usually not scheduled daily at a certain time. has a main EAN.4. the involved article(s) might either be sent out again explicitly using program RWDPOSAN or by re-executing the change run with program RWDPOSUP.2.2.

status records.1 As stated already above. As mentioned before. When all stores have received the information the change pointers are no longer required and can be deleted. It only keeps the latest successful transmission record in order to give the next run of the report RWDPOSUP information from where to start. change pointer can be valid for several objects (IDoc types) and also for several stores.2. The report RWDPOSRS checks for a change pointer if it is still needed for above reasons or not. It also reorganizes the WIND table entries. At the same time. then the flag for the change pointer is set to the status processed.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Job scheduling requirements Recommended or Generated Job Name S_DE_R_RW DPOSAN_R ABAP Report Variant Scheduling Predecessor Job Successor Job Scheduling Restriction Error Handling in Case of Cancellation RWDPOSA N Manual by article On request restriction S_DE_R_RWD After manual LCOPY_MANA variant GE_D or adjustment S_DE_R_RSE OUT00_R S_DE_R_RWD LCOPY_MANA GE_D or S_DE_R_RSE OUT00_R S_DE_R_RSE OUT00_R S_DE_R_RW DPOSUP_R RWDPOSU P On request S_DE_R_RW DLCOPY_MA NAGE_D RWDLCOP Y_MANAGE On request S_DE_R_RWDP OSUP_R or S_DE_R_RWDP OSAN_R On request S_DE_R_RWDL COPY_MANAG E_D or S_DE_R_RWDP OSUP_R 1 or 2 times a month 1 or 2 times a month S_DE_R_RSE OUT00_R RSEOUT00 S_DE_R_ RWDREOR RWDREORGC GCHECK HECK _M S_DE_R_ RWDREPROC ESS2_M RWDREPR OCESS2 2. and WIND entries Description and general information 2. if condition changes are recorded using the WIND improvement from the HPR initiative.2. These change pointers indicate that change had been performed and master data need to be transmitted to stores in question.5. If the report comes to the conclusion that the change pointer is not needed anymore. the report reorganizes the status records in table WDLS*. changes are recorded using change pointers in table BDCP or BDCP2. © 2009 SAP AG page 44/82 .5 Business process step 5: Reorganize change pointers.

then please use immediately the transaction WPER2 for reorganization check in order to find out whether one store is blocking change pointers to be set to processed. In order to ensure smooth performance. This allows seeing possible reasons why change pointers were not set to status processed and thus were not deleted. it is also possible to check with transaction SE16 directly in the table BDCP/BDCPS or BDCP2 how many change pointers without processed flag exist in total. In addition.3 Monitoring Object Monitoring objects in SAP Solution Manager Selection Criteria Alert Analysis Tool on Satellite System SM37 Monitoring Frequency/ Data Collection Every five minutes during every job execution Report RWDPOSRS (Reorganize POS Interface) Job Date (usually current date) Long Job Runtime. It also allows setting an old erroneous WDLS record explicitly to the status successful in order to avoid that this erroneous WDLS record is blocking the reorganization of further change pointers.4 How to find meaningful thresholds per monitoring object Ideally. they will be deleted in next step 6 Backlog monitoring It is not immediately observable if all change pointers are set in time to the status processed. it makes sense to use report WPER2 for reorganization check from time to time. It should say that at least some numbers of change pointers are set to processed and some status records are deleted. Throughput monitoring Ideally. Time Out.2. Error messages in Job Log 2. all change pointers are set to processed if for all stores the changed data had been transmitted successfully and if no errors are shown in POS monitor (transaction WPER). all change pointers from previous days should be set to reprocessed.5. 2.2.2 Monitoring requirements Error monitoring Please read the error log of the background job for report RWDPOSRS. In the backlog monitoring. Job Cancellation . If all change pointers are set to to be processed.5. If no change pointers have been set to the status processed.5. It can be analyzed backwards at which date those change pointers had been created and it can be checked if a data object like an article is not maintained correctly. © 2009 SAP AG page 45/82 . Scenario-specific sample See comments on WPER2 report for reorganization check. the reprocess report can also be used to identify stores with problems in the past. Performance monitoring Read the log of the background job for RWDPOSRS.2. The report also allows seeing the stores which were affected.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 2.

The report deletes change pointers from the change pointer table. In case of errors.2. in order to ensure that no changes are deleted which might still be needed.2. © 2009 SAP AG page 46/82 . the change pointer table has to be kept as small as possible.5. if all process steps are carefully executed. to processed.6 Scheduling of background jobs The job sets the processing status of change pointers. Scenario-specific sample The report has two options to delete change pointers: Either with the status processed or obsolete change pointers. This job should be carried out after all IDocs have been created. Normally. If change pointers are deleted regularly the change pointer table becomes smaller.e.2. The job log says if change pointers and how many of them have been reorganized.6. i. 2. In order to guarantee a high throughput for the POS outbound process. they will be finally deleted with report RBDCPCLR.1 Business process step 6: Delete change pointers and status records Description and general information When change pointers are set to status processed in step 5. According to the customer’s specific business it needs to be decided how many days are appropriate for X days.5 Error handling per monitoring object Background job for report RWDPOSRS Check the job log for cancellations and errors. the process of reorganization and deletion of change pointers works automatically to keep change pointer table slim. everything is fine. In case no change pointers would have been reorganized it makes sense to turn to transaction WPER2 and check the reports Reprocess and Reorganization Check. Nevertheless. If this is the case.6 2.5. that have been successfully used. Job scheduling requirements Recommended or Generated Job Name S_DE_R_ RWDPOSRS_D ABAP Report Variant Scheduling Predecessor Job Successor Job Scheduling Restriction Error Handling in Case of Cancellation RWDPOSRS Daily 2. the change message job runs regularly for all stores every day without errors. a job should be scheduled regularly with the task to delete obsolete change pointers older then X days.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 2.2. An increase in its size should therefore be discovered at an early stage. it is important that the errors are corrected for all stores and the change message run is repeated. For deletion it is recommended to choose option processed because they are surely not in use anymore since the system has set the status in the previous step.

6.5 Error handling per monitoring object Background job for RBDCPCLR Check the job log for cancellations. Throughput monitoring See comments on performance monitoring. 2. SAP strongly recommends performing step 6 at least once a week. 2. In case no deletion it makes sense to start the report to reorganize change pointers. Depending on the data volume the job might be scheduled daily or weekly.3 Monitoring Object Monitoring objects in SAP Solution Manager Selection Criteria Alert Analysis Tool on Satellite System SM37 Monitoring Frequency/ Data Collection Every five minutes during every job execution Background Job S_DE_R_ RBDCPCLR _W. Job Date Long job runtime.2.6. (Report RBDCPCLR) S_DE_R_ RBDCPCLR _W. it makes sense to turn to transaction WPER2 and check the reports Reprocess and Reorganization Check. the processed change pointers can be deleted.6.2.2. © 2009 SAP AG page 47/82 . Therefore. job cancellation . Performance monitoring The deletion of change pointers improves the performance of RWDPOSUP.4 How to find meaningful thresholds per monitoring object See comments on performance monitoring. 2. error messages in job log. RBDCPCLR .2.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 2.2 Monitoring requirements Error monitoring View job log for report RBDCPCLR in SM37. The job log says if change pointers and how many of them have been deleted. time out.5).6.2. Backlog monitoring See comments on performance monitoring.6 Scheduling of background jobs After having set the status of the change pointers to processed. The corresponding program RBDCPCLR should therefore be scheduled after the job RWDPOSRS explained earlier in business process step 5 (2. If reorganization is done and still no change pointers were deleted. If you regularly delete change pointers with RBDCPCLR.2. you will also encounter no problems with RWDPOSUP. delayed 2.6.

7 Business process step 7–9: Middleware (enterprise application integration tool): Receive. It has to be mapped (equal to pure conversion of data formats) or transformed (for example business-oriented conversion of specific EANs.7. the monitoring of this process step depends on the tool used and is therefore not detailed in this document. 2.2.2.7.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Job scheduling requirements Recommended or Generated Job Name S_DE_R_ RBDCPCLR _W ABAP Report Variant Scheduling Predecessor Job Successor Job Scheduling Restriction Error Handling in Case of Cancellation RBDCPCL R Daily or weekly S_DE_R_ RWDPOSR S_D 2. the collected POS download data.7.2. transform. as they are contained in the IDocs. SAP PI offers tools for monitoring success of transformation.2 Monitoring requirements Error monitoring No general statement possible since it depends on the chosen platform. which is necessary to enable the POS system to data in the POS database). SAP PI offers tools for monitoring success of transformation.3 Monitoring Object Monitoring objects in SAP Solution Manager Selection Criteria Alert Analysis Tool on Satellite System N/A Monitoring Frequency/ Data Collection N/A N/A N/A N/A © 2009 SAP AG page 48/82 . and send information Description 2.1 General information In most cases. SAP PI offers tools for monitoring success of transformation. Throughput monitoring No general statement possible since it depends on the chosen platform. Backlog monitoring No general statement possible since it depends on the chosen platform.2. Performance monitoring No general statement possible since it depends on the chosen platform. SAP PI offers tools for monitoring success of transformation. are not yet ready for direct processing in the POS store system. 2. As initially stated.

7.8. But if the look-up tables are not completely maintained errors can occur.2. Performance monitoring No general statement possible since it depends on chosen store POS system used. 2. Now the POS cash registers can use the new data.3 Monitoring Object Monitoring objects in SAP Solution Manager Selection Criteria Alert Analysis Tool on Satellite System N/A Monitoring Frequency/ Data Collection N/A N/A N/A N/A © 2009 SAP AG page 49/82 .Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 2.7.7.2. 2.8 2. Backlog monitoring No general statement possible since it depends on chosen store POS system used.4 Monitoring Object Further monitoring objects Selection Criteria Alert Analysis Tool on Satellite System N/A Monitoring Frequency/ Data Collection N/A N/A N/A N/A 2.5 How to find meaningful thresholds per monitoring object Usually.8. SAP PI offers tools for monitoring success of transformation. These files update the local POS back office server database. So the target is zero errors.2 Monitoring requirements Error monitoring No general statement possible since it depends on chosen store POS system used.6 Error handling per monitoring object No general statement possible since it depends on the chosen platform. each transformation should be error free as urgently required on EPOS system.2.2.2.2.2. 2. 2.1 Business process step 10–11: POS system: Receive information and update database Description and general information After data mapping and conversion is finished (which is probably done in a kind of central head office system). the files has to be transmitted physically to each store. Throughput monitoring No general statement possible since it depends on chosen store POS system used.8.

8.3 Business Process POS Outbound with Assortment List Information about listed articles in a store together with additional information like prices.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 2. errors can occur. So the target is zero errors. stocks. Please see the following process steps diagram which is very similar to POS outbound: Figure 20: Process flow point of sale outbound variant 2 with assortment list IDoc © 2009 SAP AG page 50/82 . the assortment list fulfills this function. In SAP for Retail. or EDI message) for all articles in an assortment and for articles for which changes have been made. But if the look-up tables are not completely maintained. often has to be made available in a variety of media (printout.8.8.4 Monitoring Object Further monitoring objects Selection Criteria Alert Analysis Tool on Satellite System N/A Monitoring Frequency/ Data Collection N/A N/A N/A N/A 2.2.2.2. shelf-edge labels etc.5 How to find meaningful thresholds per monitoring object Usually. PC file. each transformation should be error free as data are urgently required on EPOS system. 2. 2.6 Error handling per monitoring object No general statement possible since it depends on chosen store POS system used. or for an even more specific subset of data.

Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Conventionally. Like already stated in the introduction. SAP for Retail also supports assortment list output in the form of an electronic message for distributed retailing purposes (when a store-based merchandise management system is in place). If you require this missing data (specifically: classification data. you have a September price for school notebooks and you change this price in October. A message creation cycle is. In the example above. but also contains a segment for the article hierarchy assignment. An advantage of the HPR assortment list therefore is that it allows a higher processing speed. IDoc type WBBDLD05 is the same as IDoc type WBBDLD04. the system generates two article data record segments for the same article. the assortment list in SAP for Retail is a standard solution that can be configured with a high degree of flexibility. each with a different price sub segment. Depending on the version. The recipient (site) of the message is assigned to an assortment list profile that controls the assortment list mode (this determines how the message is used for version management or for data interchange). an assortment list is produced as a printout. file transfer) An assortment list can therefore easily be tailored to fit your individual company requirements. Please refer once more to OSS note 720514. If you want to use the assortment list. The exact date on which an assortment list is created. for example. The assortment list type divides articles contained in the same message creation cycle into groups. you can choose between the classic version and the high performance retailing version (HPR). To allow both ways. is calculated from the last creation date for the site plus the cycle time defined for the relevant assortment list type. for example. GAP list of HPR assortment list to finally decide about using the HPR assortment list. An article is assigned to one assortment list type at client level. When using the assortment list IDoc to provide data to POS systems. old labeling data. So if. you must implement a user exit to include this additional data. the interval in which a message is created. the SAP ERP system uses different IDoc categories: The older (classic) IDoc type WBBDLD03 permits only one price per data record. © 2009 SAP AG page 51/82 . This reduces the total number of IDoc segments that need to be transmitted and therefore the amount of time needed to run the assortment list. IDoc type WBBDLD06 is the same as IDoc type WBBDLD03. please note that the cycle time is usually not considered. This is because SAP recommends to run the report for creation of the assortment list change version with the flag do not consider cycle time activated. EDI. but also contains a segment for the article hierarchy assignment.. explanations on HPR assortment list and gap list as well as OSS note 808776. and layout modules for space management). The newer (HPR) IDoc type WBBDLD04 can handle multiple prices. Different assortment list types can be defined (e. The reduced data are sufficient for most retailers. food and non-food) Assortment list profiles can be assigned to sites Different creation and transmission cycles can be defined The assortment list can generate an output using a number of different media (printout. the system only uses this IDoc type to generate one article segment for school notebooks that contains both price segments.g. the high performance retailing assortment list (HPR assortment list) processes most – but not all – master data that are processed by the normal assortment list.

© 2009 SAP AG page 52/82 . you usually select one store by the other by creating a job variant per store. when a new store opens and gets a new store back office server.3.1 2. It cannot be split by article number ranges and parallelized.1. no change messages will be created. There are different transactions and reports available for the full version depending on the fact if you use the classic or the HPR assortment list. The job itself runs for all articles of a store. It transmits all listed articles in a store with all related data. but only creates special entries in the status table WDLS.2 Monitoring requirements Error monitoring It is very important to know that the program must finish with the status X (error free) or H (notes). the POS monitor transaction WPER is used mainly. Normally. For both types of assortment lists. The only thing to do in advance is to make sure that no other resource consuming jobs are running at the same time.1 Business process step 1: Run full version to initialize or dummy initialize new store Description and general information The initialization is the prerequisite for transferring change messages. Classic assortment list To run initialization. you have to correct the data and repeat the execution at a later point in time if necessary. The system does not transfer any data to the POS systems. start transaction WDBI_HPR and plan the program RWDBBINI_HPR initialization in the background as you can expect a long runtime. For error monitoring of an initialization. This means the preparation is OK (field WDLS-GESST is X or H). You see the status in the POS monitor as Format Status. Otherwise. You may also want to assign extraordinary basis parameters. you would expect the store back office server to be empty and therefore needing this data provided by SAP ECC. If the POS system contains all the necessary data in the first start-up of the POS download (maybe the database of an already existing store back office server was copied to new store back office server). start transaction WDBI and plan the program RWDBBINI initialization in the background as you can expect a long runtime.3. several IDocs are created. a dummy initialization can be executed by using the program RWDSLDUM.1. Performance monitoring For performance monitoring of an initialization you have to watch the runtime of the job.3. These entries allow the system to start creating change messages after the dummy initialization. HPR assortment list To run initialization. If initialization failed. Scenario-specific sample If you have to initialize more than one store at once. use the program RWDSLDUM for the dummy initialization. 2. In most cases.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 2.

If you try to meet the maximum allowed time window because of a high volume of articles. delayed Report RWDSLDUM (dummy initialization execution) Date of job (usually current date) Job cancellation. Backlog monitoring See comments on throughput monitoring. long runtime is not likely as this job just creates one table entry in table WDLS SM37 Usually once when new store opened (as alternative to RWDPOSIN when store database has full data already copied from other store back office server etc. error messages in job log.3.1.3. Check the POS monitor WPER for status and error logs.1.5 Error handling per monitoring object Background job for RWDBBINI and RWDBBINI_HPR Check the job log SM37 for cancellations.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Throughput monitoring The throughput can be critical in times of a high number of changes.3. 2. monitor when job is running in periodic intervals system/runtime performance During runtime Report RWDBBINI or RWDBBINI_HPR (initialization execution) Date of job (usually current date) Long job runtime.4 How to find meaningful thresholds per monitoring object All items should be error free (field WDLS-GESST is X or H). 2. After that you run dummy initialization to set the status correctly. © 2009 SAP AG page 53/82 . After job execution Processing status of initialization in POS monitor Date of job finished and outbound application SL Look for tree branch in outbound processing – not fully processed – preparation mode I = initializations: Double click to read system log text with error message WPER 2. time out.1.3 Monitoring Object Further monitoring objects Selection Criteria Alert Analysis Tool on Satellite System SM37 Monitoring Frequency/ Data Collection Runs usually once when new store opened. job cancellation. you can only run manual requests with article number ranges to fill store back office server database with IDocs.

Throughput monitoring To increase throughput. as long as it is not finished.2 Monitoring requirements Error monitoring For error monitoring of a change message.2. price maintenance. The operator has to be in touch with the business process champion so the business can inform the operating team about large data changes at one time. create IDoc Description and general information 2.2 Business process step 2: Run change version to evaluate master data changes. listing. This is not required for the work with the assortment list sent to the POS system. a daily data update to POS is usually the best business practice. are prepared.3. customer maintenance. the distinction depending on configuration takes place if HPR features like WIND or BDCP2 are evaluated. If a job takes too long. The following transactions and reports are used: Classic assortment list: WDBU Report RWDBBUPD HPR assortment list: WDBU_HPR Report RWDBBUPD: HPR Scenario-specific sample The data are prepared for the stores selected in the job variant. POS outbound is likely to work with much © 2009 SAP AG page 54/82 .3. It is also necessary to monitor the job in SM37. and saved in an IDoc. because the POS system needs the changes daily or even immediately. which need to be transferred. Performance monitoring For performance monitoring of a change message. it must be considered that. completed.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 2. parallel processing should be used. Therefore. The changes are evaluated and the data.2. both reports for the change version have the option to ignore the cycle time of the assortment list. For the process of the assortment list supporting the data transmission to a POS system. the POS monitor transaction WPER is used mainly. It selects the changes done recently and the changes becoming valid in the customized relevant period.1 This step runs the job for the daily change version which collects the changes done by business in daily online transactions like article maintenance. The cycle time is usually only important for the printed assortment list and if full versions and change version follow each other or get together in a mixed version. That would increase the risk that stores are selling articles which are incorrectly priced. the IDocs are not created and the prices and other data cannot be sent to the store in time. you have to watch the runtime of the job. Otherwise. 2. The reports for creating change versions allow you to select several stores and to set the flag for parallelization and enter a server group where parallel process can run on and also the maximum number of parallel processes.3. Backlog monitoring It is important to watch the runtime of the job regularly. Here too. collect and prepare data.

Depending on the version used.3. Therefore. So if stores open at 8. you need to work backwards on your timetable under consideration of the time for conversion and for transmission as well as some security time to determine when RWDPOSUP has to be finished latest. time out. Scenario-specific sample It is import that RWDPOSUP finishes in time before stores are opening and require correct prices.2. 2. 2. For example.3.3.7 Scheduling of background jobs This job is usually scheduled on a daily basis in the evening after all master data changes have been carried out in the system.6 Error handling per monitoring object Background job for RWDBBUPD or RWDBBUPD_HPR Check the job log for cancellations and runtime. when a new season with new prices starts or new collections are listed.3. monitor when job is running in periodic intervals system/ runtime performance Date of job (usually current date) Long job runtime.2.00 o’clock.3. error messages in job log 2.2.00 o’clock and transmission and conversion need around one hour it must be ensured that the report RWDBBUPD or RWDBBUPD_HPR is finished not later than 7. © 2009 SAP AG page 55/82 .2.5 How to find meaningful thresholds per monitoring object You can determine the threshold when POS outbound needs to be finished depending on your business needs. Then you need to work out with business how many changes they do on average and look how long job takes on average and work backwards. job cancellation . If business leaves average due to business reason.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download more changes than necessary. the operator has to change the starting time of the report RWDBBUPD or RWDBBUPD_HPR to accommodate for longer runtime caused by a larger amount of data.2. either the program RWDBBUPD or the program RWDBBUPD_HPR is used. 2. you have to accommodate threshold once more and start the job earlier.3 Monitoring Object Report RWDBBUPD or RWDBBUPD_HPR (changes message execution) Monitoring objects in SAP Solution Manager Selection Criteria Alert Analysis Tool on Satellite System SM37 Monitoring Frequency/ Data Collection Runs usually daily.4 Monitoring Object Further monitoring objects Selection Criteria Alert Analysis Tool on Satellite System Monitoring Frequency/ Data Collection After job execution Processing status of change message in POS monitor Date of job finished and outbound application SL WPER Look for tree branch in outbound processing – not fully processed – preparation mode U = update double click to read system log text with error message 2.

3.3. if store individual prices exist).1 The POS download IDocs (POS outbound IDocs and assortment list IDocs) from many stores are identical or only differ very slightly. Then for the stores which are able to get a copied IDoc only a dummy initialization is required. The following chapter describes how this works. Using the programming interface port. The partner profiles for the recipients must be maintained in such a way that IDocs are collected first. To optimize performance and decrease runtime it is not necessary to generate IDocs for all stores but just for certain reference stores. The IDoc copy management tool uses this log. It then generates trigger files for the individual recipients for each message type if this is set in the copy rule. IDoc copy management is not possible for all customers (for example. To enable copy management for IDocs. Multiple scheduling is therefore not recommended. File ports must be assigned to the recipients of the copies. which is assigned to each reference customer within the partner profile. The program RWDLCOPY_MANAGE copies the reference IDocs to the recipients (customers) that are assigned to it using the copy rule. the SAP system logs these reference IDocs in table WDLCOPY. All recipients that are assigned to a reference must be assigned to one and the same file port. Then.3 Business process step 3: Copy IDocs within ECC retail (optional) and send out IDocs from ECC retail Description and general information 2. The tool optimizes its performance internally using asynchronous processes. This can significantly improve performance. A programming interface port must be assigned to the reference recipient. can be copied according to certain rules. that this is optional. Various applications generate outbound IDocs for the reference recipients. for the initial supply of a new store you can use IDoc copy management as a one-off for the initialization (as described in step 1) if the stores can be grouped and a reference store can be determined.3. there must be a copy rule in the SAP system. © 2009 SAP AG page 56/82 .Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Job scheduling requirements Recommended or Generated Job Name S_DE_R_ RWDBBUPD_D ABAP Report Variant Scheduling Predecessor Job Successor Job Scheduling Restriction Error Handling in Case of Cancellation RWDBBUPD or RWDBBUPD _HPR Daily 2. Define an ABAP programming interface port in the port description (IDoc and EDI basis) and assign it to the function module WDL_COPY_LOG. Note. In addition. The IDoc copy management tool sends the IDocs automatically. those IDocs created for the reference stores with RWDPOSUP in step before.

2. RSEOUT00 is only necessary if in the partner agreement configuration in WE20 the IDocs are set to collect IDocs.2 Monitoring requirements Error monitoring You have to control the logs and monitor the jobs for the reports RWDLCOPY_MANAGE and RSEOUT00 See screenshot how the job’s log for the report RWDLCOPY_MANAGEMENT looks like: Figure 21: Result of IDoc copy management tools Performance monitoring You need to monitor the runtime of jobs for both reports but usually they are not performance critical.3.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download A second program. © 2009 SAP AG page 57/82 .3. Throughput monitoring Just make sure that RWDLCOPY_MANAGE and RSEOUT00 are planned in time before the data are required in the store for selling and under consideration of required time for data conversion and transmission outside SAP ECC. is the program RSEOUT00 which sends out the collected IDocs in the SAP ECC database as files to the following conversion tool. which is mandatory. The most performance critical is RWDBBUPD or RWDBBUPD_HPR POSUP in the step before. it is mandatory for the IDoc copy management tool. SAP strongly recommends this because of performance and monitoring reasons and as stated above.

idoc age WE05 or WE02 every 15 minutes 2.5 Error handling per monitoring object Background job for RWDLCOPY_MANAGE and RSEOUT00 Check the job log for cancellations and runtime. port.3. partner number. time out. partner function. partner type. message type.3. basic type. job cancellation .6 Scheduling of background jobs If copy management is used.3.3. © 2009 SAP AG page 58/82 .Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Backlog monitoring Just make sure that RWDLCOPY_MANAGE and RSEOUT00 are planned in time before the data are needed in the store. error messages in job log Long job runtime. error messages in job log Number of IDocs of type WBBDLD in an error-status Date of job (usually current date) SM37 Runs daily IDoc processing status in case of IDoc interface Direction.3. time out. 2.3. message code. the jobs are usually scheduled daily after the assortment list was generated.3. job cancellation .4 How to find meaningful thresholds per monitoring object You have to determine the thresholds depending on your business needs when POS outbound has to be finished. So if necessary. 2.3 Monitoring Object Report RWDLCOPY_MA NAGE (optional: copy IDoc from reference store) Report RSEOUT00 (IDoc transmission off ECC ) Monitoring objects in SAP Solution Manager Selection Criteria Date of job (usually current date) Alert Analysis Tool on Satellite System SM37 Monitoring Frequency/ Data Collection Runs daily Long job runtime. you can backwards schedule the jobs RWDLCOPY_MANAGE and RSEOUT00 under consideration of the time needed for conversion and transmission and with some security time reserve 2. message function.3.

4. change message) Whether preparation and transfer of data was completed Number of IDocs which were created for each recipient Whether the IDocs were created completely for each recipient To which IDoc type the IDoc in question belongs (for example.1 Business process step 4: Monitor.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Job scheduling requirements Recommended ABAP or Generated Report Job Name Variant Scheduling Predece. This can be valuable also to track a request and the corresponding IDoc number through the process steps outside SAP ECC that you know when and with which content IDoc was created. initialization. and repeat data transfer of assortment list Description and general information For the operator role. This transaction should be viewed daily after processing of the change version.3. The POS monitor is not only to view errors. Scenario-specific sample You can verify the following information using the POS monitor: The recipient of the IDoc The system type that the IDocs belong to (POS outbound or assortment list) When IDocs are created for the recipient The type of preparation (for example. and how many errors (you can display an error log for incorrect IDocs) Which data areas are contained in the IDoc (smallest and largest object key) Which data an IDoc contains © 2009 SAP AG page 59/82 . EAN/UPC references) The key (IDoc number) under which the IDocs can be found in the database How many segments the IDoc contains Which IDocs contain errors.3.Successor Scheduling Error Handssor Job Job Restriction ling in Case of Cancellation Daily S_DE_R_RWDL RWDLCO COPY_MANAG PY_MAN AGE E_D S_DE_R_RSEO RSEOUT UT00_D 00 Daily 2. the business process for the assortment list has a separate transaction. article master.4 2. correct. after initialization and after manual request. it is also a great tool to view the successful transmissions and also to enable to find the corresponding IDocs after a report or request for POS assortment list has been performed. the POS monitor.

With double click or transaction SLG1.4. article). In most cases.g. An IDoc is created but the operator has to decide if the business must be involved for changing (e. © 2009 SAP AG page 60/82 .Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download See screenshot how POS monitor looks like for assortment list: Figure 22: POS monitor for assortment list 2.2 Monitoring requirements Error monitoring using POS monitor transaction WPER Mainly the operator has to deal with the unsuccessful transmissions and needs to view error messages to delegate the actions to either IT or to business. Then you see these requests in the sub-tree for not fully processed requests. The error message can be a warning only.3. then mostly no IDoc will be created (as a result if the problem is classified as an error in the format status). the error text can be read from the system log. if there has been a problem with data preparation in step 2 with RWDPOSUP or even in step 1 with RWDPOSIN. To get business errors and data corrected is necessary for a transmission repeat.

it has an impact on outstanding steps of the business process step 5 and step 6 since the change pointers and status records are not reorganized and deleted. Moreover. It is also possible to wait for the next day’s change version of the assortment list. This has a noticeable impact on performance of RWDBBUPD or RWDBBUPD_HPR. have been processed and data have been corrected you can rerun the change version. which will include the data that was not transferred. will be repeated on the next day. © 2009 SAP AG page 61/82 . Error monitoring using POS object analysis in transaction WPER2 In addition to the daily monitoring on POS monitor. All uncorrected errors accumulate every day so the number of errors which have to be analyzed and transmitted increases. This group report is accessible through transaction WPER2. It comprises several individual reports. It is very important and demonstrates the need of an every-day error correcting and consequently of getting the whole record successfully into the status tables (WDLS). which have been displayed for the assortment list messages in the POS monitor. You can do this by executing the relevant batch report RWDBBUPD or RWDBBUPD_HPR immediately during day time or with the next change message. which was not successfully transmitted.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Figure 23: Display logs Once all errors. there is a central group report that you can run to analyze data for generating the POS outbound and the assortment lists. Scenario-specific sample Data.

if necessary. WPER2: Reorganization check in the assortment list For various reasons a reorganization in the assortment list sometimes fails if you use the retail-specific report RWDPOSRS (see Business Process step 5). © 2009 SAP AG page 62/82 .Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download The individual reports can be seen in this screenshot: Figure 24: Individual reports Please note that dummy initialization has already been discussed in step 1. This report enables a reasonable analysis and. the elimination of the reason. This could lead among other things to a dramatic increase in the volume of data and therefore a reduction in performance.

The alternative transaction WE09 would be less easy to handle in this case. This information is necessary to let the search run through other subsystems for data mapping .conversion. So the required article has to be found among thousands of IDocs. © 2009 SAP AG page 63/82 . For the POS outbound and for the assortment lists this is difficult since IDocs are generated daily for each store. The report enables a quick and simple object search with regard to the POS outbound basis IDoc. Scenario-specific sample You search for a specific article and its price in an IDoc because the store back office server does not show the correct price which is maintained in master data management in SAP ECC. This report provides a quick and easy way to search for such an object. and connectivity.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Figure 25: Assortment list reorganization check WPER2: IDoc analysis in the assortment list It often happens that you are looking for a specific object among thousands of IDocs and in the segments of the IDoc. using various selection criteria and combinations from a set selection of any size. You have to find out in which IDoc and at which point in time the article left the SAP ECC system.

will be resent in the next download. Usually. You can reverse unwanted status changes without any consequences. Therefore the change pointer table remains large which can be caused by one store not being in use anymore. This may cause the reprocessing report to include more articles than the original download. This report allows you to do a test rerun using the same change pointers that were handled in the previous download. you can resend data or avoid sending redundant data. Scenario-specific sample The background is that the processing of the change pointers works with one change pointer for several objects. which were triggered by change pointers. The following status changes are possible: Changing the status from X or H to status W means that all objects from the last download. during which time the system may detect new change pointers. Especially the reorganization check can have enormous impact on the performance. provided a download in the form of a change analysis has not taken place in the meantime. Performance monitoring During actions described in this chapter. Another possibility is. This new data is added to all the previous data. If for any reason a store did not have a change run for a longer time and initialization had been done. Two things can happen: © 2009 SAP AG page 64/82 . for which reason valid WDLS entry exists. no performance monitoring is necessary as this is monitoring online transactions themselves. this change pointer does not get set processed in step 5 and not deleted.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Figure 26: IDoc analysis assortment list WPER2: Reprocess in the assortment list When troubleshooting. Using these reports regularly has a positive effect on the performance of RWDPOSUP. This change pointer is kept valid until the change had been transmitted to all stores. there is some time delay (perhaps even a few days) between the POS run and the analysis. By changing the status. a store had an error message for a topic which is not solved. This enables you to determine how to fix them. Changing the status from W or E to status H means that only those objects that have been changed since the previous download will be sent. None of the previous data will be omitted. So it is essential to work with these reports. you have to reproduce errors. This report does not work if the change pointers were already deleted after the previous run.

4. basic type.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download For this store the changes starting from that point in time in the past when the error happened are processed every day until the error is resolved. job WDBM date). error messages in job log If corrected data are urgently needed at POS back office server in store. message code. message function. On demand – but to avoid performance issues once or twice a month On demand – but to avoid performance issues once or twice a month Every 15 minutes RWDBBUPD or RWDBBUPD_HPR (change version) Date of job (usually current Long job runtime. a decision needs to be taken on how to react If the report shows an object WPER2 with an action to be performed. IDoc age WE05 or WE02 © 2009 SAP AG page 65/82 . 2. AGE (optional: Copy error messages in job log IDoc from reference store) Manual request of corrected data Date of job (usually current Long job runtime.3 Monitoring objects in SAP Solution Manager Selection Criteria Alert Analysis Tool on Monitoring Frequency/ Satellite System Data Collection Runs daily Monitoring Object Date of job (usually current Long job runtime. Partner type. partner function. time out. Throughput monitoring Please see comments on performance monitoring. job Report SM37 RWDLCOPY_MAN date) cancellation . job WDBU or date). time out. The change pointers related to that erroneous business change cannot be deleted and thus influence – because of a higher number of change pointers – the processing for the other stores as well. cancellation . port. message status type. time out.3. a decision needs to be taken on how to react Report RWDREPROCESS 2 Reprocess IDoc processing status in case of IDoc interface Number of IDocs of type Direction. corrected data cancellation . If several data had been corrected and is also needed in store quickly and cannot wait until processing next day or if lead time is too short. WDBU_HPR error messages in job log Reorganization check Report RWDREORGCHEC K2 If the report shows an object WPER2 with an action to be performed. partner WBBDLD in an Error number. Backlog monitoring using reorganization check option in transaction WPER2 Please see comments on performance monitoring.

4.3.2.3.Z Article has no sales price 2. The transaction WPER.4.6 Error handling per monitoring object Use transaction WPER and WPER2.4. These jobs are usually not scheduled daily at a certain time. for example: Article not listed in period X.7 Scheduling of background jobs If corrections have been made. In this case. See comments about error handling in chapter 2. what means that business maintained master correctly.4. which is the POS monitor. The manual request program RWDBBMAN or transaction WDBM might also be carried out online and not as a job. a job chain containing the change analysis and IDoc creation program. but scheduled by request after manual interventions have been necessary. In that sense.4 Further monitoring objects Selection Criteria Alert Analysis Tool on Satellite System WPER Monitoring Frequency/ Data Collection Daily after RWDPOSUP and RWDPOSIN and WPMA transaction Monitoring Object WPER POS monitor Date of job (usually current date).5 How to find meaningful thresholds per monitoring object Ideally would be no error at all. the changes need to be evaluated and transmitted to the stores. the copy management and the IDoc distribution program can be started.6.Y. the assortment list is more detailed then POS outbound using POS IDocs.3. © 2009 SAP AG page 66/82 . only the copy management and the IDoc distribution might be started as jobs.4. gives sophisticated indications about incorrect master data for the assortment list to the user.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 2. For assortment list errors the system states clearly. a decision needs to be taken on how to react WPER2 On Need 2. 2. Application SL and look for store in question IDoc analysis Appear in tree branch for Not fully processes Report RWDIDOCSL If the report shows an object with an action to be performed. To do this.3.

3.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Job scheduling requirements Recommended or Generated Job Name S_DE_R_RWDBBM AN_R ABAP Report Variant Scheduling Predecessor Job Successor Job Scheduling Restriction Error Handling in Case of Cancellation RWDBBMAN Manual by article restriction On request S_DE_R_RWDLC OPY_MANAGE_D or S_DE_R_RSEOUT 00_R S_DE_R_RWDLC OPY_MANAGE_R After manual variant adjustment S_DE_R_RWDBBU PD_R or S_DE_R_RWDBBU PD_HPR_R S_DE_R_RWDLCO PY_MANAGE_R RWDBBUPD or RWDBBUPD_H PR On request RWDLCOPY_M ANAGE On request S_DE_R_RW DBBUPD_R or S_DE_R_RW DBBUPD_HP R_R S_DE_R_RW DLCOPY_MA NAGE_R S_DE_R_RSEOUT 00_R S_DE_R_RSEOUT0 0_R RSEOUT00 On request S_DE_R_RWDREO RGCHECK2_M RWDREORGC HECK2 Once or twice a month Once or twice a month S_DE_R_RWDREP ROCESS2_M RWDREPROC ESS2 2. changes are recorded by using change pointers in table BDCP or BDCP2.3. The report RWDPOSRS checks for a change pointer if it is still needed for above reasons or not. If the report comes to the conclusion that the change pointer is not needed anymore. then the flag for the change pointer is set to the status processed. status records. These change pointers indicate that changes have been performed and master data need to be transmitted to stores in question. As aforementioned. and WIND entries Description and general information 2. © 2009 SAP AG page 67/82 . the report reorganizes the status records in table WDLS*.5 Business process step 5: Reorganize change pointers. It only keeps the latest successful transmission record in order to give the next run of the assortment list information from where to start. the change pointers are not needed anymore and can be deleted. After all stores have received the information. if condition changes are recorded using the WIND improvement from the HPR initiative.5.1 As already stated above. a change pointer can be valid for several objects (IDoc types) and also for several stores. At the same time. It also reorganizes the WIND table entries.

all change pointers from the previous days are set to processed.3. Check if one store is blocking the change pointers to be set to status processed. The report also allows seeing the stores which were affected. It also allows to set an old erroneous WDLS record explicitly to the status successful in order to avoid that this erroneous WDLS record is blocking the reorganization of further change pointers. In order to ensure smooth performance. In the backlog monitoring.5. Throughput monitoring Ideally. all change pointers should be set to status processed if all stores have transmitted changed data successfully and if no uncorrected errors are in the WPER POS monitor visible.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 2.3. it makes sense to use report WPER2 for reorganization check from time to time.2 Monitoring requirements Error monitoring Read the error log of the background job for report RWDPOSRS. If all change pointers are set to processed they will be deleted in the following step. job cancellation .5.3. the reprocess report can also be used to identify stores with problems in the past. time out.4 How to find meaningful thresholds per monitoring object Ideally. It can be analyzed backwards at which date those change pointers had been created and it can be checked if a data object like an article is not maintained correctly. error messages in job log 2. This allows seeing possible reasons why change pointers were not set to status processed and thus were not deleted. 2.3 Monitoring Object Monitoring objects in SAP Solution Manager Selection Criteria Alert Analysis Tool on Satellite System SM37 Monitoring Frequency/ Data Collection Daily Report RWDPOSRS (Reorganize POS Interface) Job date (usually current date) Long job runtime. Backlog monitoring It is not immediately observable if all change pointers are set in time to the status processed. it is also possible to check with transaction SE16 directly in the table BDCP/BDCPS or BDCP2 how many change pointers without processed flag exist in total. Scenario-specific sample See the comments on report WPER2 for reorganization check. If nothing is set to processes. Performance monitoring Read the log of the background job for RWDPOSRS. © 2009 SAP AG page 68/82 .5. turn immediately to transaction WPER2 for reorganization. It should say that at least some numbers of change pointers are set to processed and some status records are deleted. In addition.

2 Monitoring requirements Error monitoring View the job log for the report RBDCPCLR in SM37.5. Scenario-specific sample The report has two options to delete change pointers: Either the processed or obsolete change pointers. 2. In case of errors. The report deletes change pointers from the change pointer table. In case no change pointers have been reorganized it makes sense to turn to transaction WPER2 and check the reports Reprocess and Reorganization Check.3. The job log says whether change pointers and how many of them has been reorganized.6 Scheduling of background jobs The job sets the processing status of change pointers.6 2. the change pointer table becomes smaller.3. Nevertheless.5 Error handling per monitoring object Background job for report RWDPOSRS Check the job log for cancellations and errors. a job should be planned (preferable in a test version first) to delete obsolete change pointers elder then X days.5. If change pointers are deleted regularly. This job should be carried out after all IDocs have been created. there are no errors messages. If all process steps are carefully done. They are surely not used anymore because the system has set the status in the step before. 2. Then the process of reorganization and deletion of change pointers works automatically to keep the change pointer table slim. It is recommended to choose the first option. to delete processed change pointers. The business has to decide how many days X days are to be sure to delete no changes that are still required. they are corrected for all stores and the change message is repeated. © 2009 SAP AG page 69/82 .3. which have successfully been set to processed. Job scheduling requirements Recommended or Generated Job Name S_DE_R_RWDPOSRS_D ABAP Report RWDPOSRS Variant Scheduling Daily Predecessor Job Successor Job Scheduling Restriction Error Handling in Case of Cancellation 2.3.1 Business process step 6: Delete change pointers and status records Description and general information After the change pointers were set to the status processed in step 5 they are finally deleted by the report RBDCPCLR.6.3.6.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 2. Keeping the change pointer table small has a positive impact on the performance of the POS download.

In case of no deletion. If you regularly delete change pointers with RBDCPCLR.5 How to find meaningful thresholds per monitoring object See the comments on performance monitoring. © 2009 SAP AG page 70/82 . job cancellation .3. delayed 2. use the transaction WPER2 and check the reports Reprocess and Reorganization Check. Backlog monitoring See the comments on performance monitoring.3 Monitoring Object Monitoring objects in SAP Solution Manager Selection Criteria Alert Analysis Tool on Satellite System SM37 Monitoring Frequency/ Data Collection At least once a week. during runtime Report RBDCPCLR (Deletion change pointer) Job date Long job runtime.6.3. 2.3.6. time out. The job log says if change pointers and how many change pointers have been deleted. it makes sense to start the report to reorganize change pointers. error messages in job log. Job scheduling requirements Recommended or Generated Job Name S_DE_R_ RBDCPCLR_D ABAP Report RBDCPC LR Variant Scheduling Predecessor Job Successor Job Scheduling Restriction Error Handling in Case of Cancellation Daily or weekly 2. So BPM strongly recommends performing step 6 at least once a week.6.4 Scheduling of background jobs After having set the status of the change pointers to processed. Throughput monitoring See the comments on performance monitoring. If reorganization is done and still no deletion of change pointers took place.3.6. The corresponding program RBDCPCLR should therefore be scheduled after the job (as explained before). the processed change pointers can be deleted. you will also encounter no issues with RBDCPCLR.6 Error handling per monitoring object Background job for RBDCPCLR Check the job log for cancellations. 2.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Performance monitoring The deletion of change pointers improves the performance of a changed version.

SAP PI offers tools for monitoring the success of transformation. Backlog monitoring No general statement possible as this depends on the chosen platform in use. the collected POS download data in form of IDocs is not ready yet for direct processing in the POS store system. It is necessary to enable the POS system to load data into the POS database.7 Middleware (enterprise application integration tool): Receive.5 How to find meaningful thresholds per monitoring object Usually. 2. and send information Description 2.7.3. transform.7.3.3.7. It has to be mapped (equal to pure conversion of data formats) or transformed (for example business-oriented conversion of specific EANs. each transformation should be absolutely error free since data are urgently required on EPOS system.4 Monitoring Object Further monitoring objects Selection Criteria Alert Analysis Tool on Satellite System N/A Monitoring Frequency/ Data Collection N/A N/A N/A N/A 2. SAP PI offers tools for monitoring the success of transformation.7.2 Monitoring requirements Error monitoring No general statement possible as this depends on the chosen platform in use.1 General information In most cases. SAP PI offers tools for monitoring the success of transformation.3. © 2009 SAP AG page 71/82 . Throughput monitoring No general statement possible as this depends on the chosen platform in use. SAP PI offers tools for monitoring the success of transformation.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 2.7.3. Performance monitoring No general statement possible as this depends on the chosen platform in use. 2.3.3 Monitoring Object Monitoring objects in SAP Solution Manager Selection Criteria Alert Analysis Tool on Satellite System N/A Monitoring Frequency/ Data Collection N/A N/A N/A N/A 2.

8.8.8. These files update the local POS back office server database.3.8. © 2009 SAP AG page 72/82 .3. 2. 2. SAP PI offers tools for monitoring the success of transformation. 2.3.8.8 2.3.6 Error handling per monitoring object No general statement possible as this depends on the chosen platform in use.8. Throughput monitoring No general statement is possible as this depends on the chosen store POS system in use. But if the look-up tables are not completely maintained. each transformation should be error free since data are urgently required on the EPOS system.5 How to find meaningful thresholds per monitoring object Usually. the files have to be transmitted physically to each store.6 Error handling per monitoring object No general statement is possible as this depends on the chosen store POS system in use.1 POS system: Receive information and update database Description and general information After data mapping and conversion is finished (which is probably done in a kind of central head office system).3.3. Now the POS cash registers can use the new data. Performance monitoring No general statement is possible as this depends on the chosen store POS system in use. 2. Backlog monitoring No general statement is possible as this depends on the chosen store POS system in use.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 2.3. So the target is zero error.4 Monitoring Object Further monitoring objects Selection Criteria Alert Analysis Tool on Satellite System N/A Monitoring Frequency/ Data Collection N/A N/A N/A N/A 2.3 Monitoring Object Monitoring objects in SAP Solution Manager Selection Criteria Alert Analysis Tool on Satellite System N/A Monitoring Frequency/ Data Collection N/A N/A N/A N/A 2.7.2 Monitoring requirements Error monitoring No general statement is possible as this depends on the chosen store POS system in use.3. errors can occur.

Please note that these documents are also available at SAP Service Marketplace.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 3 3. These procedures intend to ensure a smooth and reliable flow of the core business processes so that your business requirements are met.com/solutionmanagerbp that relate to this Best Practice document. RunSAP © 2009 SAP AG page 73/82 .sap. MS excel to MS Excel or MS Excel to job scheduling tool). Job Scheduling Management: This Best Practice provides a detailed description what SAP recommends as a standardized formal process to support a job request process. and escalation procedures for your company’s SAP ERP core business processes. SAP Business Process Management for ERP Logistics: This Best Practice helps you set up a Business Process Monitoring concept for your SAP ERP solution. alias RunSAP Best Practices. This includes the definition and documentation of the core business processes. Both monitoring approaches aim to detect any irregularities or deviations or to detect error situations at an early stage. monitoring tools. Background Job monitoring with SAP Solution Manager: This Best Practice will help you to set up background job monitoring properly in the framework of Business Process Monitoring in SAP Solution Manager. ALE Monitoring: This Best Practice helps you set up an interface monitoring concept with the focus on ALE monitoring for your SAP solution. including error handling procedures. These documents are: General Business Process Management: This document explains the procedures you should use to create a general Business Process Management concept. you can find additional information about specific implementation or upgrade project related topics for POS outbound and for assortment list high performance retail features and for migration topics: 1167070 380814 603472 720514 519685 513454 305462 208669 3. definition of monitoring objects.2 Related Best Practice Documents There are several other Best Practice documents available on the SAP Service Marketplace under https://service. This document will outline possibilities on how to optimally monitor ALE-based interfaces manually as well as automated by using SAP Solution Manager. The concept aims to define procedures for business-process-oriented monitoring. error handling. This integrated process will avoid error-prone and time-intensive manual processes of copying redundant data from one data source to another (for example.1 Further Information Troubleshooting In the following notes on the SAP Service Marketplace. monitoring frequencies. the definition of communication and escalation procedures and the assignment of responsibilities. including an end user job request form and an approval process. definition of monitoring activities.

4. 2. Check Business Processes: Select a business process for application monitoring. 3. 5. Check for your chosen step: Choose the type of monitor. Check for your chosen business process: Choose the process steps to monitor.1 Example Background Job Monitoring Background job monitoring of the background job RWDPOSUP in SAP Solution Manager: The setup for the other jobs is. Figure 27: Customize the background job monitoring with ABAP program name RWDPOSUP Figure 28: Customize the delay time for starting © 2009 SAP AG page 74/82 . Go to Operation Setup and navigate to Solution Monitoring • Business Process Monitoring. Call SAP Solution Manager (trx DSWP or SOLUTION_MANAGER). here Background Job. It demonstrates how you can set up the monitoring within SAP Solution Manager. besides the job specific parameters. in this case the job name _S_DE_R_RWDPOSUP_D or the ABAP program name RWDPOSUP. 7. Choose your solution.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 4 Appendix In the following section you find one example for each of the monitoring tools. 4. Enter the information to be used to identify the job. 6. 1. quite similar.

leave this field blank or set it to a value that will never be reached. If you want to receive YELLOW alerts. A wildcard can be used for the other parameters. Figure 31: Message class. Choose the key figures the job cancellation and the job log messages to monitor error messages in the job log. If you do not want to receive RED alerts. leave this field blank or set the same value as the threshold for RED.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Figure 29: Job cancellation 8. Figure 30: Customize the job log monitoring You find the information about the message class and message number in the job log of the job you want to monitor. message number Choose the job from the F4 input help and specify the message type E for error. © 2009 SAP AG page 75/82 .

IDoc-. JMS-. WPDREB and WBBDLD in SAP Solution Manager . integration engines with their pipeline processing. WP_PER. business process engine) and using different adapter types (such as file-. At least one business process with steps on different systems and defined interfaces must be available before it is possible to configure IDoc monitoring.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 9. WPDNAC. generate the monitoring customizing and activate the monitoring within the Business Process Monitoring session. © 2009 SAP AG page 76/82 .3 Example ALE/IDoc Monitoring Example: IDoc monitoring for IDocs WPDWGR. RNIF-adapters etc. WPDCUR. The information how you can set up the Business Process Monitoring for PI messages for all different scenarios you can find in chapter 9 SAP PI Message Processing Monitoring in the Setup Guide Interface Monitoring in the SAP Solution Manager. 4.2 Example PI Message Process Monitoring The message flow via SP PI can be very complex passing different components (such as adapter engines with the module processor and messaging system. WP_EAN. including Java and ABAP proxies. The complexity makes it difficult to track and monitor the flow of a specific message. The setup for other IDoc types is very similar. WPDSET.). WP_PLU. The monitoring schedule should be once a day. Figure 32: Monitoring schedule 10. WPD_TAX. 4. The setup of IDoc monitoring will be done in the setup session of Business Process Monitoring. Once you have entered all relevant information for the monitoring objects. Please look into the Setup Guide Interface Monitoring if you need more information regarding the setup procedure.

Select monitoring type Navigate to the business process you intend to monitor and go to node Interface Monitoring. Figure 33: Select monitoring type © 2009 SAP AG page 77/82 . Select the interface to be monitored by flagging the checkbox in the field Select.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 1.

the column Period [min] determines the frequency how often the measured value is evaluated. It is therefore recommended to set that value higher or equal to 15 minutes. However. Parameters Direction and IDoc Age (in hours) are mandatory. The flag for Data Collection in Background is set automatically. Select key figures The next open node (Monitoring object name) lists the available key figures. Double click on the counter 001 opens a selection screen where you maintain header information of this monitoring object. Select Delta number monitor and/or Total number monitor depending on your IDoc monitoring concept. Figure 35: Select key figures II © 2009 SAP AG page 78/82 . Here. dialog processing of the data collection would impact the performance of the satellite system too much. you can adjust time and frequency of the data collection. Thus. In tab Detail Information the selection criteria of the key figures have to be specified. The data collection frequency for IDoc monitoring is hard coded to 15 minutes. as the data collector reads EDI tables which can grow very large.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 2. Figure 34: Select key figures I The customizing of the data collection can be done in tab Monitoring Schedule.

Return to tab Delta number monitor/Total number monitor to specify the thresholds for alerting. Note that a daily monitoring of the job log using SAP Solution Manager is recommended. © 2009 SAP AG page 79/82 .g.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download 3. E. for example. Specify key figures After saving the sub-nodes. You can define threshold values in both directions. SAP messages are identified with SAP. deleting obsolete jobs or spool objects. the jobs must be scheduled manually. Therefore. If these periodic jobs do not run.g. If only one direction should be evaluated. five minutes Status Counter: E.g. Customizing example Status Number(s): E. A double click on the counter in tab Key Figures shows further details of the monitoring. leave the other field blank! 4. 2 (This means.g. E0 Status Message Number: E.4 Background Jobs Certain jobs must run periodically in a production SAP for Retail system. there is currently no easy-to-use support for such jobs in basis customizing. 099 Status Age (in min): E. Unfortunately. 51 for IDoc in error Status Message Qualifier: The field identifies the origin of the messages which are transmitted in the status. see SAP note 16083. For more information. Delta number monitor and/or Total number monitor will appear. system performance may get worse over time.) Figure 36: Specify key figures After you have entered and confirmed your selection criteria. Generate and activate the customizing afterwards. the tab Parameter Value Ranges will appear where an overview of your customizing is displayed. Status Message ID: E. for more than and less than at the same time.g. 4.g. the IDoc has to be at least 2 times in status 51 before being alerted. The parameter Status Number(s) is mandatory.

component BC-CCM. check for the current job status (refer to SAP R/3 documentation CD. The start of succeeding jobs might be also delayed due to the restart of the aborted job. which can happen in two ways: First. Second. if one of the necessary jobs is not scheduled. Job restartability In case of the cancellation of a background job. Check if the job is within the given timeframe. including a start condition and waits for the condition to fulfill. Status finished: All steps that make up this job have successfully been executed. Status cancelled: The job has terminated abnormally. If the job exceeded the given timeframe. chapter background processing) and proceed as follows: Status scheduled: The job steps have already been defined but the start condition has not yet been defined.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Error handling procedures for batch jobs In case one of the scheduled jobs fails. Program scheduling management has to check whether the job ran in the given timeframe and software monitoring team and/ or application support have to check the respective job results (such as spool output lists. contact the software monitoring team. contact the software monitoring team and investigate why the error occurred. A job scheduler has put the job in line to wait for an available background work process.). if an administrator intentionally cancelled the job. possible succeeding jobs or dependencies on other jobs must be considered when restarting the aborted job. Contact the program scheduling management in order to clarify when the job will be fully defined. if a program in a job step produced an error such as issuing an E or A error message. updates. Status active: The job is currently running and cannot be modified or deleted anymore. Status ready: The start condition of a released job has been met. Check for particular dependencies on other jobs. it is recommended to open a customer problem message in the SAPNet R/3 front-end system. © 2009 SAP AG page 80/82 . Status released: The job has been fully defined. when) the job has to be re-run. clarify why he did so and whether (and if. Escalation procedures If it is not possible for any of your support levels to provide a solution for a particular problem. or even if a scheduled job has finished. In case of an SAP standard program search for appropriate messages at SAP portal and open a customer message if you cannot solve the problem. etc. depending on the data volume to be processed. message logs.

message number Figure 32: Monitoring schedule Figure 33: Select monitoring type Figure 34: Select key figures I Figure 35: Select key figures II Figure 36: Specify key figures 11 12 13 14 15 16 16 17 18 18 26 33 36 37 38 39 39 40 40 50 57 60 61 62 63 64 74 74 75 75 75 76 77 78 78 79 Index of Tables Table 1: Problem resolution procedures Table 2: Workflow notification Table 3: Support notifications Table 4: HPR version improvements Table 5: Correlations for activation of change pointers 19 20 21 23 27 © 2009 SAP AG page 81/82 .Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download Index of Figures Figure 1: Alert type Number of ABAP Dumps (Delta) Figure 2: Monitoring objects – Dialog performance Figure 3: Monitoring alerts .Dialog performance Figure 4: Monitoring objects – Update errors Figure 5: Monitoring objects – Due list log Figure 6: Monitoring objects and alerts – Application log Figure 7: Monitoring alerts – Application log/Critical messages Figure 8: Other CCMS monitors Figure 9: Analysis and monitoring transactions Figure 10: Analysis & monitoring URL Figure 11: Process flow point of sale outbound variant 1 with POS interface IDocs Figure 12: Results of IDoc copy management tools Figure 13: Screenshot of POS monitor (POS outbound) Figure 14: Display logs Figure 15: Individual reports Figure 16: Object analysis POS outbound Figure 17: POS outbound reorganization check Figure 18: IDoc analysis POS outbound selection screen Figure 19: IDoc analysis POS outbound result Figure 20: Process flow point of sale outbound variant 2 with assortment list IDoc Figure 21: Result of IDoc copy management tools Figure 22: POS monitor for assortment list Figure 23: Display logs Figure 24: Individual reports Figure 25: Assortment list reorganization check Figure 26: IDoc analysis assortment list Figure 27: Customize the background job monitoring with ABAP program name RWDPOSUP Figure 28: Customize the delay time for starting Figure 29: Job cancellation Figure 30: Customize the job log monitoring Figure 31: Message class.

XHTML and W3C are tradem arks or registered trademarks of W3C®. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages. MaxDB is a trademark of MySQL AB. special. fitness for a particular purpose. or other items contained within this material. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. or noninfringem ent. This document contains only intended strategies. Program Neighborhood. VideoFrame. text. OS/400. World Wide Web Consortium. R/3.com. The statutory liability for personal injury and defective products is not affected. This document is provided without a warranty of any kind. Inc. Massachusetts Institute of Technology. mySAP. used under license for technology invented and implemented by Netscape. pSeries. SAP assumes no responsibility for errors or omissions in this document. links. Netfinity. This document is a preliminary version and not subject to your license agreement or any other agreem ent with SAP. Java is a registered trademark of Sun Microsystems. and MultiWin are trademarks or registered trademarks of Citrix Systems. OSF/1. iSeries. The information in this document is proprietary to SAP. copied. Inc. Inc. HTML. SAP does not warrant the accuracy or completeness of the information. DB2. indirect. graphics. Please note that this document is subject to change and may be changed by SAP at any time without notice. and/or development. and Informix are trademarks or registered trademarks of IBM Corporation. No part of this document may be reproduced. and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business. Windows. or transmitted in any form or for any purpose without the express prior written permission of SAP AG. WinFrame. JavaScript is a registered trademark of Sun Microsystems. AS/400. ICA. developments. OS/390. z/OS. X/Open.Best Practice for Solution Operations Manage Operations for SAP for Retail – POS Download © Copyright 2009 SAP AG. MVS/ESA. and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. zSeries. and Motif are registered trademarks of the Open Group. or consequential damages that may result from the use of these materials. xApps. UNIX. All other product and service names mentioned are the trademarks of their respective companies. OS/2. IBM. xApp. AIX. either express or implied. This limitation shall not apply in cases of intent or gross negligence. Oracle is a registered trademark of Oracle Corporation. All Rights Reserved No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. XML. Data contained in this document serves informational purposes only. National product specifications may vary. product strategy. S/390. Citrix. Outlook. MetaFrame. SAP. and PowerPoint are registered tradem arks of Microsoft Corporation.. DB2 Universal Database. Parallel Sysplex. AFP. WebSphere. Sweden. including but not limited to the implied warranties of merchantability. xSeries. The information contained herein may be changed without prior notice. SAP shall have no liability for damages of any kind including without limitation direct. © 2009 SAP AG page 82/82 . mySAP. Microsoft. Tivoli. Intelligent Miner. SAP NetWeaver.

Sign up to vote on this title
UsefulNot useful