Manage operations for sap for retail global data synchronization
Upcoming SlideShare
Loading in...5
×
 

Manage operations for sap for retail global data synchronization

on

  • 1,787 views

 

Statistics

Views

Total Views
1,787
Views on SlideShare
1,787
Embed Views
0

Actions

Likes
0
Downloads
28
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Manage operations for sap for retail global data synchronization Manage operations for sap for retail global data synchronization Document Transcript

  • Best Practice for Solution Operations Manage Operations for SAP for Retail Global Data Synchronization Dietmar-Hopp-Allee 16 D-69190 Walldorf CS STATUS customer published DATE VERSION Dec-1 2009 3.0 SOLUTION MANAGEMENT PHASE SAP SOLUTION Operations & Continuous Improvement Best Practices for Solution Operations TOPIC AREA SOLUTION MANAGER AREA Application & Integration Management Business Process OperationBP_MO_for_SAP_for_Retail_GDS_V30.docx – 12.01.2010
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Table of Contents1 Management Summary 5 1.1 Goal of Using This Best Practice 5 1.2 Alternative Practices 5 1.3 Staff and Skills Requirements 5 1.4 System Requirements 6 1.5 Duration and Timing 6 1.6 How to Use This Best Practice 7 1.7 Best Practice Procedure 7 1.7.1 Preliminary tasks 7 1.7.2 Monitoring concepts 7 1.7.3 Business Process Monitoring in SAP Solution Manager 8 1.7.4 Monitoring types for Business Process Monitoring in SAP Solution Manager 9 1.7.5 Business Process Monitoring process 21 1.7.6 Legend 212 Business Process Monitoring for Global Data Synchronization 22 2.1 Sample Scenario 23 2.2 Business Process Step 1: Create Subscription 23 2.2.1 Description 23 2.2.2 Monitoring requirements 24 2.2.3 Monitoring objects (optional: in SAP Solution Manager) 24 2.2.4 How to find meaningful thresholds per monitoring object 24 2.2.5 Error handling per monitoring object 25 2.3 Business Process Step 2: Translation Information 28 2.3.1 Description 28 2.3.2 Monitoring requirements 28 2.3.3 Monitoring objects in SAP Solution Manager 29 2.3.4 How to find meaningful thresholds per monitoring object 29 2.3.5 Error handling per monitoring object 29 2.4 Business Process Step 3: Receive and Accept/Refuse Subscription 30 2.4.1 Description 30 2.4.2 Monitoring requirements 31 2.4.3 Monitoring objects in SAP Solution Manager 31 2.4.4 How to find meaningful thresholds per monitoring object 31 2.4.5 Error handling per monitoring object 31 2.5 Business Process Step 4: Translate Information 31 2.5.1 Description 31 2.5.2 Monitoring requirements 32 2.5.3 Monitoring objects in SAP Solution Manager 32 2.5.4 How to find meaningful thresholds per monitoring object 32 2.5.5 Error handling per monitoring object 33 2.6 Business Process Step 5: Update Subscription 34 2.6.1 Description 34 2.6.2 Monitoring requirements 34© 2009 SAP AG page 2/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS) 2.6.3 Monitoring objects in SAP Solution Manager 35 2.6.4 How to find meaningful thresholds per monitoring object 35 2.6.5 Error handling per monitoring object 35 2.7 Business Process Step 6: Transmit Catalogue Item 37 2.7.1 Description 37 2.7.2 Monitoring requirements 37 2.7.3 Monitoring objects in SAP Solution Manager 38 2.7.4 How to find meaningful thresholds per monitoring object 38 2.7.5 Error handling per monitoring object 38 2.8 Business Process Step 7: Translate Information 38 2.8.1 Description 38 2.8.2 Monitoring requirements 38 2.8.3 Monitoring objects in SAP Solution Manager 39 2.8.4 How to find meaningful thresholds per monitoring object 39 2.8.5 Error handling per monitoring object 39 2.9 Business Process Steps 8–10: Receive Catalogue Item Notification / Execute Rule Engine / Update PRICAT 41 2.9.1 Description 41 2.9.2 Monitoring requirements 42 2.9.3 Monitoring objects in SAP Solution Manager 42 2.9.4 How to find meaningful thresholds per monitoring object 42 2.9.5 Error handling per monitoring object 43 2.10 Business Process Step 11: Generate Response to Data Pool 52 2.10.1 Description 52 2.10.2 Monitoring requirements 52 2.10.3 Monitoring objects in SAP Solution Manager 53 2.10.4 How to find meaningful thresholds per monitoring object 53 2.10.5 Error handling per monitoring object 54 2.11 Business Process Step 12: Translate Information 55 2.11.1 Description 55 2.11.2 Monitoring requirements 56 2.11.3 Monitoring objects in SAP Solution Manager 56 2.11.4 How to find meaningful thresholds per monitoring object 56 2.11.5 Error handling per monitoring object 56 2.12 Business Process Step 13: Receive and Accept/Refuse Confirmation Message 57 2.12.1 Description 57 2.12.2 Monitoring requirements 57 2.12.3 Monitoring objects in SAP Solution Manager 57 2.12.4 How to find meaningful thresholds per monitoring object 57 2.12.5 Error handling per monitoring object 57 2.13 Business Process Step 14: Translate Information 57 2.13.1 Description 57 2.13.2 Monitoring requirements 58 2.13.3 Monitoring objects in SAP Solution Manager 58 2.13.4 How to find meaningful thresholds per monitoring object 58 2.13.5 Error handling per monitoring object 58© 2009 SAP AG page 3/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS) 2.14 Business Process Step 15: Response 59 2.14.1 Description 59 2.14.2 Monitoring requirements 59 2.14.3 Monitoring objects in SAP Solution Manager 59 2.14.4 How to find meaningful thresholds per monitoring object 59 2.14.5 Error handling per monitoring object 603 Further Information 61 3.1 Related Best Practice Documents 61 3.2 Background Information and References 61Index of Figures 62Index of Tables 63© 2009 SAP AG page 4/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)1 Management Summary1.1 Goal of Using This Best PracticeThis Best Practice helps you set up a Business Process Monitoring concept for your SAP for Retail solution.The concept aims at defining procedures for business process-oriented monitoring and error handling, andescalation procedures for your business process Global Data Synchronization (GDS) Inbound. Theseprocedures intend to ensure a smooth and reliable flow of this core business process so that your businessrequirements are met.This Best Practice gives orientation for defining suitable application-oriented monitoring objects in order todetect any irregularities or deviations from an ideal business process flow or to detect error situationsconcerning a core business process at an early stage.This Best Practice follows the recommended approach of SAP to use SAP Solution Manager for monitoringfunctionalities whenever possible. But even if you do not use SAP Solution Manager we recommend to followthe procedures described in this document as much as possible in order to ensure a smooth and reliable flowof your business processes as well as an appropriate response in case of unforeseen errors.1.2 Alternative PracticesYou can have SAP experts deliver this Best Practice on-site by ordering an SAP solution managementoptimization (SMO) service for SAP business process management (BPM). This service is exclusivelyavailable within SAP’s support engagements SAP MaxAttention and Safeguarding. If your company currentlydoes not have any support engagement with SAP, it is also possible to get assistance by SAP experts fromSAP Consulting. In this case, please contact your local SAP Consulting representative.1.3 Staff and Skills RequirementsTo implement this Best Practice, you require the following teams:Application management teamThis team creates the ERP Business Process Monitoring concept and consists of experts from several areasof your company: Business department Solution support organization (for example basis support or application support) Implementation project teamBusiness process operations teamThe business process operations team will be responsible for applying the resulting procedures derived fromimplementing this Best Practice. It includes the following groups: Persons designated to perform business process-oriented monitoring and to ensure that the process runs smoothly (e.g. the business process champion for each business process) All parties in your solution support organization and IT department involved in monitoring focused on the application aspects (application support, development support, job scheduling management)© 2009 SAP AG page 5/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)SAP technology operations teamThis team comprises all those in your solution support organization and IT department involved in monitoringfocused on the system administration side (program scheduling management, software monitoring team,system administration team including the system administrator)Business process championThe business process champion is a person in the business department that is responsible for the successfulexecution of a given business process. He or she coordinates all activities necessary for the businessprocess and, therefore, is usually responsible for the escalation paths in case of problems. Often this roleserves as a second level in the escalation procedure if the application monitoring team needs to escalate anissue.More information about roles and responsibilities of these teams can be found in the super-ordinate BestPractice for General Business Process Management, which you can obtain through SAP Solution Manager orthe SAP Service Marketplace, quick link /BPM.Necessary or useful trainings SM300 – Business Process Management and Monitoring E2E300 – End-to-end Business Process Integration and Automation Management1.4 System RequirementsIn order to monitor business processes running in your SAP for Retail solution via SAP Solution Manager, theSAP Basis release of the systems to be monitored has to be at least 4.6C. To have all described monitoringobjects available in SAP Solution Manager, the add-on ST-A/PI01L has to be installed on the SAP for Retailsystem.1.5 Duration and TimingDurationCreating a Business Process Monitoring concept can take approximately one week per business process.Implementing the Business Process Monitoring concept might take approximately another week.TimingThe best time to apply this Best Practice is during the planning phase or during the implementation phase ofyour SAP solution.© 2009 SAP AG page 6/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)1.6 How to Use This Best PracticeHere you find a brief description of how you should proceed in using this document:Read through the Best Practice for General Business Process Management, available on the SAP ServiceMarketplace. The document explains the procedures to be used to create a general Business ProcessManagement concept. This includes the definition and documentation of the core business processes,definition of monitoring objects, definition of monitoring activities including error handling procedures,monitoring tools and monitoring frequencies, the definition of communication and escalation procedures andthe assignment of responsibilities.At the beginning of chapter 2 you will find a typical flow chart of the core business process explained in thisBest Practice. It is intended to be used as a guideline for writing down your company-specific processdocumentation.In chapter 0 you will find further information relevant for more than one scenario. In case information from thegeneric part is relevant for a specific business process step in one of the scenarios, you will find a clear link tothe corresponding chapter of the generic part.1.7 Best Practice Procedure1.7.1 Preliminary tasksBefore performing this Best Practice, ensure that you perform the following preliminary tasks or checks in thesystem: Complete all installation and post-installation actions and procedures, including customizing Ensure that the initial download has been successfully executed Apply all SAP recommendations from SAP service sessions and any SAP recommendations resulting from customer problem messages Implement all current SAP support packages upon availability1.7.2 Monitoring conceptsThe monitoring procedures proposed for each business process step are the core of this Best Practice. Themonitoring procedures help you ensure that the technical processes meet the requirements for stability,performance and completeness. These procedures cover the monitoring for five areas: Error monitoring Performance monitoring Throughput monitoring Backlog monitoring Data consistency monitoringFor each of the business process steps, you will find the following information: A detailed functional description of the process step Identified monitoring requirements for the process step Defined monitoring objects, alerts and selection criteria Description of error handling procedures and restartability© 2009 SAP AG page 7/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)General monitoring activities that are valid for all or most scenarios are described in the generic part inchapter 0. Recommendations for performance monitoring can also be found in this chapter. The performanceof the most important steps of your core business processes should be monitored on a regular basis. Themonitoring procedure for performance monitoring of all steps that are executed in an SAP Retail solution isgenerally the same. Therefore, you will only find specific performance monitoring recommendations onselected business process steps.1.7.3 Business Process Monitoring in SAP Solution ManagerBusiness Process Monitoring (BPMon), as part of Solution Monitoring means the proactive and process-oriented monitoring of the most important or critical business processes, including the observation of alltechnical and business application-specific functions that are required for a steady and stable flow of thebusiness processes.The core business processes that are implemented in an SAP Retail system or other software and operatedby a company are of particular importance, and Business Process Monitoring is intended to ensure a smoothand reliable operation of the business processes and, thereby, that the core business processes meet acompany’s business requirements in terms of stability, performance, and completeness. SAP SolutionManager provides a graphic to visualize a company’s (distributed) system- and solution landscape and allrelated business processes. By using Business Process Monitoring, it is possible to define and customizealert situations from the basic set of configurable alerts provided by SAP Solution Manager. These alerts arethen visualized as green, yellow and red alert icons for each individual business process step in the graphicalbusiness process representation. Business Process Monitoring is intended to detect critical situations andrespond to them as early as possible in order to solve problems as fast as possible.SAP Solution Manager also offers extended functionality for error handling and problem resolution. By thedefinition of contact persons and escalation paths, Business Process Monitoring can be integrated into thecompany’s overall strategy for business process management and solution management within their solutionsupport organization.In general, Business Process Monitoring includes the solution-wide observation of: Business process performance (key performance indicators) Background jobs (Job Scheduling Management tasks) Business application logs (such as any error log, general application log, due list logs, etc.) Data transfer via interfaces between software components Data consistency Technical infrastructure and components required to run the business processes Required periodic monitoring tasksFor further details on Business Process Monitoring, please refer to http://service.sap.com/bpm.© 2009 SAP AG page 8/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)1.7.4 Monitoring types for Business Process Monitoring in SAP Solution ManagerMonitoring types are part of the functional scope of Business Process Monitoring as it is available in SAPSolution Manager. The below mentioned monitoring types are available: Application monitor (throughput and backlog indicators, interface monitoring, data consistency checks, mass activity monitors, due list log, MRP key figures, user exit) Background jobs (jobs running on SAP systems with an SAP basis) Dialog performance (dialog transaction performance) Update error (V1 and V2 update errors from SM13 for specific transactions and programs) Due list log (messages for deliveries and billings) Application log (messages from the application Log SLG1) Document volume (based on table call statistics in ST10) Other CCMS monitor (all alerts that are configured in the CCMS alert monitor)Depending on what is executed during a specific business process step, the relevant monitoring types mustbe selected. In order to receive detailed information on how to set up the monitoring objects in SAP SolutionManager, please refer to the documentation available at http://service.sap.com/bpm. In the followingchapters, monitoring types that are relevant for this Best Practice document are introduced shortly.One prerequisite for setting up Business Process and Interface Monitoring in SAP Solution Manager is that allbusiness processes and business process steps are maintained in the respective solution that contains allaffected system components. If you want to learn more about how to set this up, please turn tohttp://help.sap.com SAP Solution Manager Basic Settings.1.7.4.1 Application monitorThe application monitor is just one of many different monitoring types within the Business 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 /installationsEntry by Application Group Plug-Ins SAP Solution Tools ST-A/PI. Please ensure that the ST-A/PI is installed on the SAP Solution Manager system and on the respective satellite. In case of problems refer to SAP Note 915933. The throughput and backlog indicator functionality available as of ST-A/PI 01J* is only working properly with ST-SER 700_2007_1. This is due to changes in the underlying architecture.More detailed information about the different application monitor functionalities and a detailed description onhow to define self-written monitoring collectors for the user exit are explained in the documents Setup Guide– Application Monitoring and Setup Guide – User Exit, respectively (http://www.service.sap.com Alias BPMMedia Library).Throughput and backlog indicatorsAs of ST-A/PI 01H, a completely new set of application monitors has been introduced. While the alreadyestablished monitors are all evaluating specific logs or performance data, the new monitors are considering(un-)processed documents in the SAP system and provide so-called throughput and backlog indicators (TBI).© 2009 SAP AG page 9/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)These TBIs shall especially provide Automated and early detection of application error situations and backlogs in the core business processes Automated error and backlog analysis toolsFor ERP Logistic the following monitors are available: Sales and Services (e.g. sales documents, invoices) Warehouse Management (e.g. transfer requirements, transfer orders) Inventory Management (e.g. goods movements) Logistics Execution (e.g. deliveries, shipments) 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(http://www.service.sap.com/BPM Media Library).SAP for Retail data consistencyNo data consistency requirements exist for the GDS scenario. Information about the other data consistencychecks are available in detail in Setup Guide – Data Consistency Monitoring (http://www.service.sap.com/ ->Technical Information).1.7.4.2 Background jobThe background job monitoring should be part of a Job Scheduling Management concept. Go tohttp://service.sap.com/solutionmanagerbp, topic area Business Process Operations to find the BestPractice for Job Scheduling Management. Because of several restrictions regarding background jobscheduling, e.g. time restrictions, restriction of hardware resources (CPU, main memory, …), or existingdependencies between different activities (e.g. invoices can only be created after the corresponding goodsissue is posted, or backorder 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 beidentified as soon as possible in order to react as fast as possible. Therefore it is also necessary to definerestart procedures and escalation paths.Monitoring objectsBefore setting up monitoring, the monitoring objects must be clearly defined. A monitoring object is a singlebackground job or a group of background jobs. There are four different possibilities to identify a special back-ground job or a group of background jobs. This information needs to be maintained in the sub-nodeBackground Job below a business process step.A detailed description of what kinds of alerts make sense or what kinds of alerts are possible is provided inthe Best Practice for Background Job Monitoring with SAP Solution Manager document, which can be foundon the SAP Marketplace http://service.sap.com/solutionmanagerbp, topic area Business Process Opera-tion.© 2009 SAP AG page 10/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)1.7.4.3 ABAP dump collectorThe dump collector provides monitoring features for alerting on occurrences of ABAP dumps of specifiedruntime errors and collects statistical data of ABAP dumps for reporting reasons.Monitoring objectsThe monitoring object is an ABAP runtime error. This runtime error can be specified via the runtime errorname, the user who is responsible for the runtime error, the client on which the runtime error occurs or theprogram that leads to the runtime error.Monitoring alertsPossible alert types are the Number of ABAP Dumps (Delta) – all dumps since the last collector run – andNumber of ABAP Dumps (Reporting) – all runtime errors of specified type, client and program for this day orfor the previous day.Figure 1: Alert type Number of ABAP Dumps (Delta)1.7.4.4 Dialog performanceDialog performance implies the monitoring of the dialog transaction performance of any transaction in theSAP system. This can be a standard transaction or a custom-developed transaction.Monitoring objectsDialog performance implies the monitoring of the dialog transaction performance of any transaction in theSAP system. This can be a standard transaction or a custom-developed transaction.Monitoring objectsThe monitoring object is the transaction itself. The customizing has to be done in the Dialog Performancenode. The Transactions table lists all transactions that are already configured to that business process step.The relevant transactions need to be selected for monitoring. It is also possible to add or to removetransactions within the Add/Remove Transactions table.© 2009 SAP AG page 11/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)The monitoring can be performed per SAP instance. To this end, select the respective instances in the SAPInstances table, which lists all instances that are maintained for a system. The Alert Types table shows thedialog response time and all parts of the response time that can be monitored, like queue time, load andgeneration time, database request time and the front-end response time. Select those times that are relevantfor monitoring. After saving this node, a sub-node Performance Alerts will appear where you can enter thethreshold values.Figure 2: Monitoring objects – Dialog performanceMonitoring alertsEach table in the Performance Alerts sub-node corresponds to an alert type chosen in the higher-level node,and lists the combinations of specified transaction code and SAP instance.For each combination of transaction code and instance that you want to include in the monitoring, specify thethreshold values resulting in alert messages for GREEN to YELLOW, YELLOW to RED, RED to YELLOW,and YELLOW to GREEN.Since the monitoring object for performance monitoring is created on the satellite system, it might be possiblethat the object already exists there. Therefore you can load the current threshold values from the respectivesystems via the Load thresholds from <XYZ> button, with <XYZ> representing the SID. If successfullyretrieved for an SAP instance, the values are filled in columns. If no active settings for the threshold valueswere found for a certain transaction code, default values are set (indicated in column Default). To transfer thethreshold values for a single line from right to left, the Copy icon can be used. To transfer all at once (allthresholds for all columns and tables) there is an additional Copy all button.© 2009 SAP AG page 12/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Figure 3: Monitoring alerts - Dialog performance1.7.4.5 Update errorsChanges to the data in an SAP system caused by a business process should be written to the database in fullor not at all. If the operation is canceled while the transaction is being executed or if an error occurs, thetransaction should not make any changes to the database. These activities are handled by the SAP updatesystem.The SAP system makes a distinction between primary, time-critical (V1), and secondary, non-time-critical(V2), update errors. This distinction allows the system to process critical database changes prior to lesscritical changes.V1 modules describe critical or primary changes, that affect objects with a controlling function in the SAPsystem, for example order creation or changes to material stock.V2 modules describe less critical secondary changes. These are pure statistical updates, for example, suchas result calculations.Monitoring objectsYou can configure the monitoring of update errors for online transactions and/or ABAP programs relevant in abusiness process. This is the object type. The name of the object is the name of a transaction or the name ofthe ABAP program itself. If desired, you can specify a user executing the transaction or the ABAP program.If no user is specified explicitly, all users (represented by *) will be considered in monitoring data evaluation.© 2009 SAP AG page 13/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Figure 4: Monitoring objects – Update errorsMonitoring alertsSince update errors are usually very critical, the default configuration is to raise a yellow alert as soon as oneupdate error occurs. This is valid for V1 and for V2 update errors. To raise a red alert for a V1 or a V2 updateerror, a threshold must be specified.1.7.4.6 Due list logA due list is a list that contains several entries (documents) depending on selection criteria. There aredifferent types of due lists in an SAP system of which the following three are the most important: Delivery (L),Billing (F) and Picking (K). The delivery due list can be directly accessed via transaction V_SA, the billing duelist via transaction V.21. In case of a billing due list, the list contains e. g. a number of sales documents thatneed to be billed. If the billing due list was processed previously and it is important to know which billingdocuments were created from this billing due list, you can display it in the due list log for this billing run.Monitoring objectsThe monitoring object is the respective due list type. That can be Delivery, Billing or Picking. You can specifythe name of the user that is responsible to process the due list. If it is user-independent, you can use thewildcard ‘*’. You also need to define the aggregation level needs to be defined, which can be per day, perhour or per log.© 2009 SAP AG page 14/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Monitoring alertsFor the monitoring of due list log messages, you can use four different alert types:1. DocumentCreation refers to the status of the document creation itself. The alert rating (YELLOW or RED) will be raised if no documents were created during a due list run.2. MinQuantityDocs refers to a minimum number of documents that should be created during a due list run. The threshold values for the number of documents that result in a change from GREEN to YELLOW (or back) and from YELLOW to RED (or back) must be maintained.3. TotalQuantityMsgs refers to the total number of message created during a due list run. 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. DLLogMsgs refers to specific due list log messages. The message type, the message ID and the number can be specified. It is also possible to use wildcards. 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.Figure 5: Monitoring objects – Due list log1.7.4.7 Application logThe application log provides an infrastructure for collecting messages, saving them in the database anddisplaying them as a log. At runtime, situations can arise in application programs that must be brought to theattention of the user. These are usually errors. It can also be useful to report a successful completion. Theinformation that arises is called a message. A set of messages is a log. A log usually also has headerinformation (log type, creator, creation time, etc.). A transaction can generate several logs. The applicationlog is not written consecutively but as a whole at one point in time.Monitoring objects and alertsThe application log allows an application- or object-oriented recording of events. An object and any sub-object that belongs to it classify each event. The analysis of the logs is similarly object- (or sub-object-)oriented. The name of an object (or sub-object) can be found in transaction /nSLG1 together with all otherinformation specific to that log.© 2009 SAP AG page 15/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Figure 6: Monitoring objects – Application logIt is possible to monitor the total number of messages belonging to an object. For each object, the number ofmessages that raise a YELLOW alert and the number of messages changing from YELLOW to RED must bemaintained.It is also possible to monitor specific messages that are considered as critical in the N° of Critical Messagestab. To configure the monitoring of critical application log messages, select the relevant object-sub objectcombinations. For each of these combinations, you can specify the message type, the message ID and themessage number as well as the threshold values for the number of critical messages that are supposed toresult in changes from GREEN to YELLOW and from YELLOW to RED can be specified. It is also possible touse wildcards.Figure 7: Monitoring alerts – Application log/critical messages1.7.4.8 Other CCMS monitorsWith other CCMS monitors it is possible to assign any CCMS monitoring tree element (MTE) to a businessprocess step. Therefore it is necessary to call transaction RZ20 in the satellite system and to open a monitorthat contains the required alert(s).The name of the MTE can be found by choosing F1. The MTE name needs to be copied into thecorresponding column (see Figure 8). Under column Monitor Name you can assign an individual name.© 2009 SAP AG page 16/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS) The MTE used for monitoring should be an MTE on the lowest leaf-level, i. e. on attribute level. If an MTE of a higher branch-level (collective MTE) is chosen, then the current and open view in the graphics will show the right alerts but without the possibility to process these alerts within the Business Process Monitoring session as the alerts are not replicated there.In order to load the threshold values that are currently valid in the corresponding system, use the button .If successfully retrieved, the values are filled in the right-hand columns. If no active settings for the thresholdvalues were found, these columns remain empty.To transfer the thresholds values for a single line from right to left, double-click the Copy icon.Figure 8: Other CCMS monitors Unlike all other monitoring types, Other CCMS Monitors provides the opportunity to assign MTEs from other systems than the system the actual business process step is assigned to.Example: If you are interested in monitoring the availability from a Portal system that possesses no CCMSbut is included as one business process step in your business process, you can use one MTE in the CCMS ofSAP Solution Manager to monitor the heartbeat of the portal. You can then assign the corresponding alert viaOther CCMS Monitors to business process step running on the portal system.1.7.4.9 Analysis and monitoring toolsIt is possible to specify analysis transactions or URL addresses (including file directories) per monitoringobject. In case of analysis transactions these should be used to analyze errors or problems either locally inSAP Solution Manager system (Call Option “1”) or directly in the respective satellite systems (Call Option“2”). Per default some standard transactions are maintained. For instance, transaction SM37, that provides ajob overview in an SAP system, is maintained for background jobs, and transaction SLG1, which is used tohave a look into the application log.It is also possible to add new transactions. These can be standard transactions or transactions written by thecustomer.© 2009 SAP AG page 17/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Figure 9: Analysis and monitoring transactionsOn the second tab, you can specify an URL that should be called in order to further analyze the givenproblem. This is especially interesting if you have knowledge documents that are linked to a portal. You candefine a short text and the URL. For Web pages to be called, specify the full URL, e.g. http://help.sap.com. For content available on file servers specify the full file path, using the nomenclature: file://<server>..., for instance, file://server1operations_documentsoperations-handbook.txtFigure 10: Analysis and monitoring URLWhen using the monitoring during a Business Process Monitoring session, the specified transactions or URLsare available as buttons within a business process step. When you press these buttons, for instance , you jump directly into the corresponding transaction, either in SAP SolutionManager (here: SAT) or the connected satellite system (here: CT1), for further analysis.In case of URLs, the button (e.g. ) contains the short text (limited to 20 characters)from the setup session and opens the defined URL in a new browser window.© 2009 SAP AG page 18/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)1.7.4.10 Monitoring activitiesMonitoring activities should be set up for every monitoring object within a business process step. Allmonitoring objects defined within a business process step are listed there. To ensure effective monitoring andefficient problem resolution, assign responsibilities and define problem resolution procedures as described inthe following table. Some information has been taken from the previous Solution Support Organization node. Monitoring Team Defines the team that is responsible for monitoring the relevant monitoring object. Use value help F4. Person Resp. Defines the person who is responsible for monitoring the monitoring object. Use value help F4. Frequency Describes how often the responsible person should process the required monitoring activity. Start Time Describes at which time the responsible person should process the required monitoring activity. Problem Indicator A description about what indicates a problem. Error Handling Describes how to react on problems or errors, i.e. how to solve the problem or correct the error. Escalation Path Describes the escalation path in case that the person responsible could not solve the problem. Persons who can be contacted should be maintained here.You can enter additional information related to this business process step in the tables MonitoringActivities, Error Handling, Restart of Step and Escalation Path. That information is valid for the wholebusiness process step and helps users who have to carry out the monitoring and who are not familiar withthat particular business process.1.7.4.11 NotificationsYou can set up notifications for the whole business process or for each business process step individually.There are two types of notifications: Workflow notifications and support notifications. Workflow notificationsallow sending messages to a specified recipient in case of alerts, for instance, an e-mail or SAPOffice mail.Support notifications allow setting up a service desk message in case of an alert. The information entered forthe service desk message serves as a template. The service desk message can be created manually orautomatically.On business process level, you can define notifications for the whole business process, i.e. as soon as thebusiness process gets an alert status, notifications will be triggered. Alternatively, notifications can be definedfor every monitoring type individually, e.g. all alerts related to background jobs of the business process areforwarded to a defined e-mail address.Notifications defined on business process step level will overrule the configuration made on business processlevel for this particular step.© 2009 SAP AG page 19/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Workflow notification Sender Must be a user within in the monitoring client of SAP Solution Manager. This user can even be a system user without any roles or profiles, but the user must have a valid e-mail address which the used mail server knows. Recipient Address Depending on the recipient type, the recipient name is required. This can be any e- mail address, an SAP user name in the same system, a remote SAP name or a shared distribution list. In case of an SMS you need to enter “SMS:<cell phone or pager number>”. Reci. Type There are currently five different recipient types: U (e-mail), K (for SMS and pager), B (SAP user name), R (remote SAP name) and C (shared distribution list). No. of Yellow Alerts Number of YELLOW alerts that can occur before an automatic notification is triggered No. of Red Alerts Number of RED alerts that can occur before an automatic notification is triggered Max Wait Time [h] Once the maximum wait time [hours] has elapsed, a notification is created even if the thresholds are not exceeded. RED Only To restrict this mechanism only to red alerts, the flag in column RED Only must be set. Detailed Triggers a long text for e-mails or SAPOffice mails, e.g. name of the solution, name of the business process step, …)Support notifications Priority Defines the priority of the support notification. Queue Defines the support component on which the message is put. This component must exist within the service desk. Processor Defines a default processor who should process the message. The processor must be known within the service desk and must be SAP user name defined as a business partner with role employee. Text Template Text templates can be defined that will then be available for service desk messages manually created for alerts. Automatic Support notifications will be created automatically depending on the alert thresholds. Reporter Necessary if service desk messages are created automatically. Must be a SAP user name defined as a business partner with role general. Num of YELLOW Necessary when service desk messages are created automatically, e. g. after ten Alerts yellow alerts a service desk message should be created. Num of RED Alerts Necessary when service desk messages are created automatically, e. g. after five red alerts a service desk message should be created.© 2009 SAP AG page 20/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS) If in addition to Queue, Processor, Priority and Reporter either one of the columns Num of YELLOW Alerts or Num of RED Alerts is filled with a value, the automatic support notification creation is configured. In case that both columns are filled with a value, the automatic support notification creation works with a logical OR operation. Hence, with the figures in the table above the system would create a support notification if there are either more than nine yellow alerts or more than four red alerts for which no support notification has been created yet.1.7.5 Business Process Monitoring processFor a successful and efficient Business Process Monitoring, you have to define a process for implementingyour monitoring concept. This includes the definition of the roles and responsibilities involved. You need todefine who is supposed to carry out which activity within the process, and how communication between thedifferent roles within the support organization is supposed to take place.A Business Process Monitoring concept has to be tightly integrated with the support organization. Thisincludes the integration with the Incident- and Problem Management processes and the ChangeManagement process. These processes have to be adjusted to the Business Process Monitoring concept sothat communication and escalation procedures defined within these processes support the Business ProcessMonitoring concept. This includes the final communication of open alerts to SAP.Wherever communication connected with Business Process Monitoring happens outside these supportprocesses, separate communication and escalation paths and procedures have to be defined.Please see the separate Best Practice for General Business Process Management for further details.1.7.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. 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.© 2009 SAP AG page 21/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)2 Business Process Monitoring for Global Data SynchronizationFigure 11: Business processes in GDSGlobal Data Synchronization (GDS) offers the possibility to mass transfer article data from external datapools.For retail companies, the transfer and efficient processing of this data is particularly important because of thehigh volume of data.The GS1 Global Data Synchronization Network (GDSN) is a standardized global environment that allowstrading partners (suppliers and retailers) to exchange data securely and synchronously. As the networkcommunication is based on the GDSN standards, the trade item information is uniformly published across thenetwork, ensuring that all partners have consistent data in their system at the same time.The GDS network is composed of five different actors:1. Supplier: The supplier is the product seller who would like to publish his products and company information to the retailer (product buyer).2. Retailer: The retailer is the product buyer who would like to acquire the data that the supplier published on its data pool.3. GS1 global registry: Orchestrates the data pool interoperability and hold a repository of all the items or party subscribed to by each retailer© 2009 SAP AG page 22/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)4. Source data pool: Acts as an entry point for the supplier into the GDS network, allowing the supplier to publish his data. The source data pool also acts as a repository which contains the published item’s complete data.5. Recipient data pool: Acts as an entry point for the retailer into the GDS network, allowing the retailer to subscribe, confirm and receive published item data.The general GDS process flow occurs as follows:1. A data supplier loads his product data in a source data pool which then registers this information into the GS1 global registry.2. A retailer can then submit a subscription to the recipient data pool for a particular article, article category, supplier, etc. The subscription is then forwarded to GS1 global registry which then notifies the source data pools that contain data matching the retailer’s subscription criteria.3. The source data pools then publishes the data to the recipient data pool for all the trade items that match criteria of the newly created subscription. The recipient then forwards this information to the retailer.4. After the data has been processed, the retailer can send a confirmation to the supplier to inform the latter of what action has been taken on the item information provided. The confirmation is forwarded to the supplier through the recipient and source data pools.5. When item data is modified or new items are loaded onto the source data pool by a supplier, the data is again published to the retailer if the items match the retailer’s subscription criteria.2.1 Sample ScenarioA retailer has listed a new supplier. He wants to receive selected article data via his primary data pool.2.2 Business Process Step 1: Create Subscription2.2.1 DescriptionThe subscription is a stand-alone application that allows users to send a subscription message to the datapool as well as request data for subscribed items.You can submit three types of subscriptions: Subscription: Subscribe to items registered in the GS1 Global Registry for which the user would like to receive updates Request to resend current state on data pool for a subscription: Will resend already subscribed information to be able to handle lost data. Delete subscription: Will remove the information request from the network, so that no new item information will be sent for the deleted subscription.You have the following options when creating a GDSN subscription: GTIN: Article global trade item number Classification Code: Code used to identify a grouping of linked articles Target Market Country: Country for which the information is requested Target Market Subdivision: Country subdivision for which the information is requestedSample scenario-specific information: A retailer sends a subscription for a specific supplier and for aspecific classification level to an external data pool.© 2009 SAP AG page 23/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)2.2.2 Monitoring requirementsProcessing is time-critical as the end user is waiting for the data resulting from the subscription he has carriedout. As the end user cannot decide whether problems are located in the internal or external systems, anoperator needs to closely monitor the communication of the subscription.If the problem is located in the data pool, the end user might need to contact the provider directly.Error monitoringErrors occurring in the process can be: Error by the end user during subscription creation Unaccessible target system Message rejection by the data poolUser errors are treated directly online, the other errors are visible in the XML message processing.Sample scenario-specific information: The retailer wants to have information on a certain article. Healready contacted the supplier who said he is going to release the information. Now the responsible buyercreates a subscription in the system and waits for the information to arrive.Performance monitoring Not applicableThroughput monitoring Not applicableBacklog monitoringErrors should not mount up. Processing is time-critical as the end user is waiting for the data resulting fromthe subscription. Therefore error messages should be treated in a timely manner.2.2.3 Monitoring objects (optional: in SAP Solution Manager)Monitoring Selection Criteria Alert Analysis Tool on Monitoring Frequency /Object Satellite System Data CollectionXML Message types (see Messages in SXI_Monitor In short intervals whenMessage chapter 2.1.1.5) error subscriptions are treatedUnreplied Transactions in Transactions in TWGDS_SUBSCRI Several times a day whensubscriptions status requested and this status exist PTION subscriptions are treated sent date in the pastTable 1: Business process step 1 – Monitoring objects2.2.4 How to find meaningful thresholds per monitoring objectIn the subscription process, each error is important, so there is no threshold for importance.Processing is time critical as the end user is waiting for the data resulting from the subscription.© 2009 SAP AG page 24/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)2.2.5 Error handling per monitoring object2.2.5.1 Monitor for processed XML messages on ERP sideThe transaction SXI_MONITOR provides analysis of all error- or success messages, e.g. that the targetsystem is unavailable.You can restrict the selection of messages via three message types: TradeItemCatalogueSubscriptionRequestMessage_async_Out (Subscription) TradeItemCatalogueTransmissionRequestRequestMessage_async_Out (Request) TradeItemCatalogueTransmissionRequestRequestMessage_async_Out (Reset & Request)You can enter one of the three messages types in the field Interface Name in the subscreen Sender.Figure 12: Business process step 1 – Standard selection criteriaIn the next screen you see a status overview. Red flag = error Black and white flag = success Green flag = message not yet processed. In this case, you should check the inbound queue and activate it if necessary.© 2009 SAP AG page 25/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Figure 13: Business process step 1 – Status overviewThere is the possibility to get more details per message by double-clicking on a message.Figure 14: Business process step 1 – Display message details© 2009 SAP AG page 26/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)The inbound message tree element contains, under Payloads • MainDocument, the relevant content of themessage:Figure 15: Business process step 1 – Display message content2.2.5.2 Subscription displaySubscriptions without replyThe end user can use transaction TWGDS_SUBSCRIPTION to display when a message has been issuedwithout answer. In subscreen Subscriptions Message Area the message appears with a yellow triangle andthe status is Requested. There is no corresponding success or error message in subscreen XI messages.This means that the answer by the data pool is missing, and so the IT operator needs to check SXI-Monitoron ERP- and PI side for errors. If no errors are shown, the purchaser should directly ask at the data pool forfurther information on the missing response.In transaction TWGDS_SUBSCRIPTION, there is an option to re-schedule the subscription, either as a job ormanually. An XML message cannot be edited. If errors occur within a subscription, it needs to be createdagain.© 2009 SAP AG page 27/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Figure 16: Business process step 1 – Subscription display2.3 Business Process Step 2: Translation Information2.3.1 DescriptionPI translates the sent XML message through an XSLT mapping into a format which can be understood by thereceiving data pool system.Sample scenario-specific information: The subscriptions created by the user are translated to the CIS(Catalogue Item Subscription) message of GS1.2.3.2 Monitoring requirementsProcessing is time-critical as the end user is waiting for the data resulting from the subscription.As the end user cannot decide whether problems are located in the internal or external systems, an IToperator needs to closely monitor the communication of the subscription.If the problem is located in the data pool, the end user might need to contact the provider directly.Error monitoringErrors in this process may indicate that a system involved is inaccessible, that a java mapping error occurred,that the adapter framework contains an error, or that there is a problem with the AS2 adapter. As the proxyand interfaces are rather fixed, the mapping issues should not occur once the process is set up and tested.Errors should not mount up. Processing is time-critical as the end user is waiting for the data resulting fromthe subscription.Performance monitoring Not applicableThroughput monitoring Not applicable© 2009 SAP AG page 28/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Backlog monitoringErrors should not mount up. Processing is time-critical as the end user is waiting for the data resulting fromthe subscription.2.3.3 Monitoring objects in SAP Solution ManagerMonitoring Selection Criteria Alert Analysis Tool on Monitoring Frequency /Object Satellite System Data CollectionXML message Message types (see Messages in SXI_MONITOR/Runtime In short intervals when chapter 2.3.5) error exist Workbench on PI subscriptions are treatedTable 2: Business process step 2 – Monitoring objects in SAP Solution Manager2.3.4 How to find meaningful thresholds per monitoring objectIn the subscription process, each error is important, so there is no threshold for importance.Processing is time-critical as the end user is waiting for the data resulting from the subscription.2.3.5 Error handling per monitoring objectProcessing is time-critical as the end user is waiting for the data resulting from the subscription.As the end user cannot decide whether problems are located in the internal or external systems, an IToperator needs to closely monitor the communication of the subscription.If the problem is located in the data pool, the end user might need to contact the provider directly.Monitor for processed XML messages on PI sideIn transaction SXI_MONITOR, you can analyze all error or success messages.It is possible to restrict the selection of messages via three message types: TradeItemCatalogueSubscriptionRequestMessage_async_Out (Subscription) TradeItemCatalogueTransmissionRequestRequestMessage_async_Out (Request) TradeItemCatalogueTransmissionRequestRequestMessage_async_Out (Reset & Request)© 2009 SAP AG page 29/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Figure 17: Business process step 3 – Monitor for processed XML messagesYou can also track the status of the messages with the Runtime Workbench using the same interface names.2.4 Business Process Step 3: Receive and Accept/Refuse Subscription2.4.1 DescriptionThe data pool can either accept the subscription by sending a successful response or reject it by sending anexception message.The reason for a rejection can be the following: Format not valid Invalid values Invalid combination of values in several fieldsSample scenario-specific information: The subscriptions are usually carried out on GTIN level by thebuyer.© 2009 SAP AG page 30/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)2.4.2 Monitoring requirementsError monitoring Error handling within the data pool itself is not controlled by SAP.Performance monitoring Error handling within the data pool itself is not controlled by SAP.Throughput monitoring Error handling within the data pool itself is not controlled by SAP.Backlog monitoring Error handling within the data pool itself is not controlled by SAP.2.4.3 Monitoring objects in SAP Solution ManagerMonitoring Selection Alert Analysis Tool on Monitoring Frequency /Object Criteria Satellite System Data CollectionNot applicableTable 3: Business process step 3 – Monitoring objects in SAP Solution Manager2.4.4 How to find meaningful thresholds per monitoring objectError handling within the data pool itself is not controlled by SAP.2.4.5 Error handling per monitoring objectError handling within the data pool itself is not controlled by SAP.2.5 Business Process Step 4: Translate Information2.5.1 DescriptionPI translates the message sent from the data pool into the inbound proxy format which can be understood bythe receiving SAP for Retail system.Most likely, the PI system of the retailer is not accessible to an external business partner like the data pool.Additional architecture components might be involved. In order to get the full picture of processing, thesecomponents need to be included in the monitoring concept.Sample scenario-specific information: For the subscription issued by the data pool, an acceptancemessage is sent by the data pool.© 2009 SAP AG page 31/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)2.5.2 Monitoring requirementsProcessing is time-critical as the end user is waiting for the data resulting from the subscription.As the end user cannot decide whether problems are located in the internal or external systems, an IToperator needs to closely monitor the communication of the subscription.If the problem is located in the data pool, the end user might need to contact the provider directly.Error monitoringErrors should not mount up. Processing is time critical as the end user is waiting for the data resulting fromthe subscription.Performance monitoring Not applicableThroughput monitoring Not applicableBacklog monitoringErrors should not mount up. Processing is time-critical as the end user is waiting for the data resulting fromthe subscription.2.5.3 Monitoring objects in SAP Solution ManagerMonitoring Selection Criteria Alert Analysis Tool on Monitoring Frequency /Object Satellite System Data CollectionXML message Message types (see Messages in SXI_Monitor In short intervals when chapter 2.5.5.1) and error exist subscriptions are treated date of the messageTable 4: Business process step 4 – Monitoring objects in SAP Solution Manager2.5.4 How to find meaningful thresholds per monitoring objectEach message is important so there is no threshold for importance.Processing is time-critical as the end user is waiting for the data resulting from the subscription.© 2009 SAP AG page 32/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)2.5.5 Error handling per monitoring object2.5.5.1 Monitor for processed XML messages on PI sideIn transaction SXI_Monitor you can analyze all error- or success messages.It is possible to restrict the selection of messages via the message type: TradeItemCatalogueItemStatusNotificationMessage_async_InYou can enter one of the message type in the field Interface Name in the subscreen Receiver:Figure 18: Business process step 4 – Monitor for processed XML messages© 2009 SAP AG page 33/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)2.6 Business Process Step 5: Update Subscription2.6.1 DescriptionThe data pool can either accept the subscription by sending a successful response or reject it by sending anexception message. This result needs to be propagated to the subscription UI. This is carried out in theinbound processing of the incoming message in ERP.Sample scenario-specific information: The subscription is accepted by the data pool. This result is thenvisible in the subscription UI.2.6.2 Monitoring requirementsProcessing is time-critical as the end user is waiting for the data resulting from the subscription.As the end user cannot decide whether problems are located in the internal or external systems, an IToperator needs to closely monitor the communication of the subscription.If the problem is located in the data pool, the end user might need to contact the provider directly.Error monitoringThe errors that can occur are the following:1. Message error Errors should not mount up. Processing is time-critical as the end user is waiting for the data resulting from the subscription.2. Subscription unanswered If the subscription has been sent out correctly but the data pool has failed to send a response, no error message will be visible in the subscription UI.3. Subscriptions in status Failed If the subscription has been refused by the data pool due to incorrect subscription content or another error, the subscription is set to status Failed.Performance monitoring Not applicableThroughput monitoring Not applicableBacklog monitoringErrors should not mount up. Processing is time-critical as the end user is waiting for the data resulting fromthe subscription.© 2009 SAP AG page 34/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)2.6.3 Monitoring objects in SAP Solution ManagerMonitoring Selection Criteria Alert Analysis Tool on Monitoring Frequency /Object Satellite System Data CollectionXML message Message type (see Messages in SXI_Monitor chapter 2.6.5.1) error existSubscriptions Subscriptions in See above TWGDS_SUBSCRIPT In short intervals whenwithout a response status “requested” ION subscriptions are treatedfor longer than xdaysSubscriptions in Subscriptions in Messages TWGDS_SUBSCRIPT In short intervals whenstatus failed status failed older than 3 ION subscriptions are treated days existTable 5: Business process step 5 – Monitoring objects in SAP Solution Manager2.6.4 How to find meaningful thresholds per monitoring objectEach message is important so there is no threshold for importance.Processing is time-critical as the end user is waiting for the data resulting from the subscription.2.6.5 Error handling per monitoring object2.6.5.1 Monitor for processed XML messages on ERP sideIn the transaction SXI_MONITOR you can analyze all error- or success messages.It is possible to restrict the selection of messages to the message type: TradeItemCatalogueItemStatusNotificationMessage_async_InYou can enter the message type in the field Interface Name in the subscreen Receiver.© 2009 SAP AG page 35/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Figure 19: Business process step 5 – Monitor for processed XML messages2.6.5.2 Subscription displayIn transaction TWGDS_SUBSCRIPTION, the end user can see when a message has been issued withoutanswer. In subscreen Subscriptions Message Area the message appears with a yellow triangle. There is nocorresponding success or error message in subscreen XI Messages. This means that the answer by the datapool is missing, and so the operator needs to check SXI-Monitor on ERP- and PI side for errors. If no errorsare shown, the purchaser should directly ask at the data pool for further information.In transaction TWGDS_SUBSCRIPTION, there is an option to re-schedule the subscription, either as a job ormanually. An XML message cannot be edited. If errors occur within a subscription, it needs to be createdagain.© 2009 SAP AG page 36/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Figure 20: Business process step 5 – Subscription displaySubscriptions set to status Failed in the subscription UIIf the data pool replies with a status notification that indicate an error, the messages is updated in thesubscription UI. In order to get more details on the reason of the subscription, the payload part of themessage display contains more details.2.7 Business Process Step 6: Transmit Catalogue Item2.7.1 DescriptionOnce the supplier has released the article data for the retailer for which a valid subscription exists in the datapool, the data pool directly sends the article data to the retailer. In case the vendor has not released thearticle data, the retailer has to wait for it and a potential valid subscription remains unanswered.Sample scenario-specific information: The vendor has already released information that matches thesubmitted subscription elements issued by the retailer. Immediately after the subscription, the containedmessages are sent to the retailer.2.7.2 Monitoring requirementsError monitoring Error handling within the data pool itself is not controlled by SAP.Performance monitoring Error handling within the data pool itself is not controlled by SAP.Throughput monitoring Error handling within the data pool itself is not controlled by SAP.Backlog monitoring Error handling within the data pool itself is not controlled by SAP.© 2009 SAP AG page 37/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)2.7.3 Monitoring objects in SAP Solution ManagerMonitoring Selection Alert Analysis Tool on Monitoring Frequency /Object Criteria Satellite System Data CollectionNot applicableTable 6: Business process step 6 – Monitoring objects in SAP Solution Manager2.7.4 How to find meaningful thresholds per monitoring objectError handling within the data pool itself is not controlled by SAP.2.7.5 Error handling per monitoring objectError handling within the data pool itself is not controlled by SAP.2.8 Business Process Step 7: Translate Information2.8.1 DescriptionPI translates the message sent from the data pool into the inbound proxy format which can be understood bythe receiving SAP for Retail system.Sample scenario-specific information: The submitted catalog item notification messages matching thesubscriptions are immediately transmitted to SAP.2.8.2 Monitoring requirementsProcessing is time-critical as the end user is waiting for the data resulting from the notification.As the end user cannot decide whether problems are located in the internal or external systems, an IToperator needs to closely monitor the communication of the notification.If the problem is located in the data pool, the end user might need to contact the provider directly.If the data pool cannot find problems in the transmission, maybe the data has not yet been released by thesupplier. The end user can decide if he wants to contact the supplier directly.Error monitoringErrors should not mount up. Processing is time-critical as the end user is waiting for the data resulting fromthe notification.Performance monitoring Not applicableThroughput monitoring Not applicable© 2009 SAP AG page 38/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Backlog monitoringErrors should not mount up. Processing is time-critical as the end user is waiting for the catalogue data.2.8.3 Monitoring objects in SAP Solution ManagerMonitoring Selection Criteria Alert Analysis Tool on Monitoring Frequency /Object Satellite System Data CollectionXML message Message type (see Messages in SXI_Monitor Several times a day when chapter 2.8.5.1) status error subscriptions are treatedTable 7: Business process step 7 – Monitoring objects in SAP Solution Manager2.8.4 How to find meaningful thresholds per monitoring objectEach message is important so there is no threshold for importance.Processing is time-critical as the end user is waiting for the catalogue data.2.8.5 Error handling per monitoring object2.8.5.1 Monitor for processed XML messages on PI sideIn transaction SXI_MONITOR, you can analyze all error- or success messages.You can restrict the selection of messages using the receiver interface name: TradeItemCatalogueTransmissionRequestMessage_async_InYou can enter the message type in the field Interface Name in the subscreen Receiver.If the corresponding trace level is set, the different stages of the message can be displayed. A type tag in themessage StandardBusinessDocument transmitted by the data pool tells you what type of messages has beensent.Figure 21: Business process step 7 – Monitor for processed XML messages© 2009 SAP AG page 39/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)2.8.5.2 Integration Engine: AdministrationIn order to be able to analyze the message state in its different stages on PI, the trace level in PI needs to beset to 1 (see below). Otherwise not all stages of the message before and after mapping are visible within themonitoring transaction. Once the process is reliable enough, the trace level can be lowered again. The tracelevel is defined in the following way:Figure 22: Business process step 7 – Integration Engine configuration 1Figure 23: Business process step 7 – Integration Engine configuration 2© 2009 SAP AG page 40/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Add the following entry:Figure 24: Business process step 7 – Integration Engine configuration 32.9 Business Process Steps 8–10: Receive Catalogue Item Notification / Execute Rule Engine / Update PRICAT2.9.1 DescriptionYou receive initial catalogue messages or updates from the data pool for the catalog items that you havesubscribed to. The data pool sends a notification message if a subscribed catalog item has been released, ischanged or if the receivers request a message.It is possible to display and process the received data in the storage monitor.The rule engine executes three steps: Check of the mandatory fields, e.g. if there already exists a catalog or if the vendor exists Mapping of the data pool fields to PRICAT fields and additionally enrichments of PRICAT fields Writing of the data into the corresponding PRICAT tables (step 10).Check data in PRICATManually check the information received with W_SYNC. Correct the errors or reject the item to ask for anupdate from the supplier.Update PRCIATAfter saving the data into PRICAT tables, you can continue working with an existing catalogue.There are three possibilities to post the catalogue: Manually Transaction W_SYNC Automatically In customizing, you can set up an automatic processing of the catalogue per vendor. After a PRICAT catalogue has been created, each item receives the status 03 – check. The items are written in the table WRF_PRICAT_TRIG and the report RWRF_PRICAT_TERMINATION loops over this table and posts each entry automatically. Semi-automatic You can set the status for each item in the catalogue to 03 – check manually. The items are written in the table WRF_PRICAT_TRIG and the report RWRF_PRICAT_TERMINATION loops over this table and posts each entry automatically.© 2009 SAP AG page 41/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Sample scenario-specific information: The supplier released some article information matching sub-scriptions transmitted by the retailer. The articles are translated and written to the PRICAT tables. From here,the user checks the correctness of the transmitted information and creates the articles in SAP ECC.2.9.2 Monitoring requirementsProcessing is time-critical as the end user is waiting for the data transmitted through the notification.As the end user cannot decide whether problems are located in the internal or external systems, an IToperator needs to closely monitor the communication of the notification.If the problem is located in the data pool, the end user might need to contact the provider directly.If the data pool cannot find problems in the transmission, maybe the data has not yet been released by thesupplier. The end user can decide to contact the vendor directly.Error monitoringErrors should not mount up. Processing is time-critical as the end user is waiting for the notification.Performance monitoring Not applicableThroughput monitoring Not applicableBacklog monitoringErrors should not mount up. Processing is time-critical as the end user is waiting for the notification.2.9.3 Monitoring objects in SAP Solution ManagerMonitoring Selection Criteria Alert Analysis Tool on Monitoring FrequencyObject Satellite System / Data CollectionXML messages Message types (see Messages in SXI-Monitor In short intervals when chapter 2.9.5.1) error notifications are treatedStatus of CIN Processing date CIN messages WGDS_STORAGE_ In short intervals whenmessages in in status error MONI notifications are treatedStorage MonitorApplication log of Processing date Log state red SLG1 / Object: In short intervals whenCIN messages WGDS_PROCESS notifications are treatedTable 8: Business process step 8–10 – Monitoring objects in SAP Solution Manager2.9.4 How to find meaningful thresholds per monitoring objectEach message is important so there is no threshold for importance.Processing is time-critical as the end user is waiting for the notification.© 2009 SAP AG page 42/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)2.9.5 Error handling per monitoring object2.9.5.1 Monitor for processed XML messagesIn transaction SXI_MONITOR, you can analyze all error- or success messages concerning the receivedcatalogue item notifications (step 8).You can restrict the selection of messages to the message type: TradeItemCatalogueTransmissionRequestMessage_async_InYou can enter the message type in the field Interface Name in the subscreen Receiver.2.9.5.2 Storage monitorSelection screenYou can restrict the selection to structure type WGDS_CAT_ITEM_NOTIF_STY. This selection will open anadditional selection screen where you can restrict the selection using a GTIN.Figure 25: Business process step 8–10 – Storage monitor© 2009 SAP AG page 43/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)In addition to the GTIN, a processing date can be defined after implementing note 1416330. You can displaythe time stamp in the result screen and sort in ascending/descending order.Figure 26: Business process step 8–10 – Sort by time stampFor more information you have to double-click on the message.Unit of measuresIf several units of measure have been sent for one article, they are divided into several items in the storagemonitor. In order to display related items of the current item, press button Main Object.Figure 27: Business process step 8–10 – Display related items© 2009 SAP AG page 44/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Article dataThe button Data will show all fields that have been sent for this article.Figure 28: Business process step 8–10 – Display article data© 2009 SAP AG page 45/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Figure 29: Business process step 8–10 – Display stored data© 2009 SAP AG page 46/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Application logThere is an option to branch to the application log by pressing the Log button. Here, you see the processingsteps of the rule engine (check, mapping, enrichment, save) carried out for this item. This log is alsoaccessible directly via SLG1, but there the log does not allow access to the content of the item (article andsupplier information)Figure 30: Business process step 8–10 – Access application log© 2009 SAP AG page 47/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)2.9.5.3 Rule engineThe rule engine executes three steps:Check of the mandatory fields: Vendor doesn’t exist – GLN cannot be assigned - The reasons can be that there is no GLN maintained in the vendor master - Transaction XK02, subscreen Control DataFigure 31: Business process step 8–10 – Check mandatory fields Catalogue is blocked - You have to restart the update of the catalogue either per job or manually. - Manually, the restart can be triggered by the storage monitor (transaction WGDS_STORAGE_MONI) - Double-click on the corresponding message and then press button Reprocess.Please note the following note: 1351797 WGDS Cannot reprocess a complete messageInstalling the note will send a pop-up to select for either a group or single item. You should always reprocessthe whole group, as processing in rule engine may require to have access to the corresponding unitsbelonging to the same CIN hierarchy. Without the note only individual selection is possible.© 2009 SAP AG page 48/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Figure 32: Business process step 8–10 – Reprocess messageThe restart by job can be triggered by the program RWGDS_PROCESS_ITEMS (transaction SE38).You can select the messages by status. All messages per status are reprocessed now. It’s not possible toselect specific messages within the status. For this reason it is recommended to set undesired messages tostatus Complete in order to keep them out of the selection. To do so, use the storage monitor where youselect the corresponding message, double-click on the message and then press the button Complete.Figure 33: Business process step 8–10 – Set undesired messages to status CompleteMapping of the data pool fields to PRICAT fields and additional enrichment of PRICAT fieldsIf errors occur during the mapping of the CIN message content to the PRICAT tables, the log containsinformation on which mapping rule the error occurred. This rule then needs to be checked.© 2009 SAP AG page 49/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Writing data into the corresponding PRICAT tablesIf errors occur during the writing to PRICAT tables, potentially a key field has been violated. In this case youneed to check the content of the transmitted CIN.2.9.5.4 Update PRICATManual postingIf you post the catalogue manually you get the status and the corresponding traffic light directly after posting.Double-click on yellow or red traffic light to get more details about the potential error. You should be able tosolve the problem directly in the catalogue.Figure 34: Business process step 8–10 – Manual postingApplication logIf you post the catalogue automatically via job, you can see the resulting messages in the application log(transaction SLG1).You can restrict the selection of messages filtering by transaction W_PRICAT_TERMINATION.Double-click on the error message to get more details about the error. You should be able to solve theproblem directly in the catalogue.© 2009 SAP AG page 50/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Figure 35: Business process step 8–10 – Application log© 2009 SAP AG page 51/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)2.10 Business Process Step 11: Generate Response to Data Pool2.10.1 DescriptionIf required, the retailer can use the confirmation functions to inform the data pool about what he has done withthe received data. You do this using a Catalog Item Confirmation message.A change to the processing status in price catalog processing can update the confirmation status of an item.If the status has changed to Changed, Forwarded, Excluded or Check, you can send a confirmationmessage for the relevant items to the data pool.This following table indicates the mapping of the status in PRICAT and the corresponding confirmation status:Corresponding Cata- Confirmation Descriptionlogue Workbench Status State03 (checked) Accepted Data has been received by the data recipient, but no business decision has been made on the data.04 (Forwarded) Synchronized Data is integrated and synchronized.07 (Review) Review Request to the data source to review their data and take action (applies to adds & changes) because the data recipient has received discrepant data which they cannot synchronize.06 (Excluded) Rejected Data will no longer be synchronized or updated.Table 9: Business process step 11 – Status mappingYou use the confirmation status to document the processing status towards the supplier. The confirmationstate in Confirmation Manager should reflect the confirmation state as seen by the vendor. When theconfirmation is initially created at the retailer, the status of the confirmation is set to Unknown. Once theconfirmation is sent out and accepted by the data pool the status set for the confirmation is updated in theConfirmation Manager.In order to send out the confirmation, you can either send the messages manually in the ConfirmationManager or run a background job which sends all messages that still need to be sent.Sample scenario-specific information: The retailer has adopted several of the submitted articles in hissystem. Some articles have been rejected by the retailer. In order to update the supplier with the adoptionstatus in his system, the retailer wants to send confirmation messages of status Accepted for adoptedarticles, messages of status Review for the articles where errors were found in the submitted data, andmessages of status Rejected where data was not adopted.2.10.2 Monitoring requirementsMessages are created for relevant changes in the PRICAT transaction. Usually these messages should besent in a timely matter. Therefore unsent messages should be sent.Processing is time-critical as the end user is waiting for the confirmation.© 2009 SAP AG page 52/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)As the end user cannot decide whether problems are located in the internal or external systems, an IToperator needs to closely monitor the communication of the confirmation.If the problem is located in the data pool, the end user might need to contact the provider directly.Error monitoringErrors should not mount up. Processing is time-critical as the end user is waiting for the confirmation.Performance monitoring Not applicableThroughput monitoring Not applicableBacklog monitoringErrors should not mount up. Processing is time-critical as the end user is waiting for the confirmation.2.10.3 Monitoring objects in SAP Solution ManagerMonitoring Selection Criteria Alert Analysis Tool on Monitoring Frequency/Object Satellite System Data CollectionUnsent messages Confirmation status Messages WGDS_CONFIRM In short intervals whenin Confirmation Unknown and with this MANAGER confirmations are treatedManager message status New status existConfirmation job Job with the Job fails JOB corresponding name (WGDS_CONFIRM) Sends all unsent messagesXML message Message types (see Messages SXI-Monitor chapter 2.10.5) in errorTable 10: Business process step 11 – Monitoring objects in SAP Solution Manager2.10.4 How to find meaningful thresholds per monitoring objectEach message is important so there is no threshold for importance.Processing is time-critical as the end user is waiting for the confirmation from the data pool.© 2009 SAP AG page 53/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)2.10.5 Error handling per monitoring objectConfirmation ManagerAn entry in a confirmation message table is created upon setting a status in PRICAT as explained above. Thepresence of a message for a confirmation state entry is symbolized by the letter icon.Figure 36: Business process step 11 – Identify messages for a confirmationPress button Selection.You can filter the messages via following selection criteria:Figure 30: Business process step 11 – Filter messages for confirmation© 2009 SAP AG page 54/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Press button Execute.Figure 37: Business process step 11 – Select message for confirmationDouble click on the message. Here you see the current status of the message.Figure 38: Business process step 11 – Check message statusMonitor for processed XML messagesIn transaction SXI_MONITOR, you can analyze all error- or success messages concerning the confirmationsent.You can restrict the selection of messages to the message type: TradeItemCatalogueAcceptanceNotificationMessage_async_OutYou can enter the message type in the field Interface Name in the subscreen Sender.Job WGDS_CONFIRMThis job is used to send out all trailing confirmation messages. The program does not have a selectionscreen.2.11 Business Process Step 12: Translate Information2.11.1 DescriptionPI translates the message sent from the data pool into the inbound proxy format which can be understood bythe receiving SAP for Retail system.© 2009 SAP AG page 55/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)2.11.2 Monitoring requirementsProcessing is time-critical as the end user is waiting for the confirmation.As the end user cannot decide whether problems are located in the internal or external systems, an IToperator needs to closely monitor the communication of the confirmation.If the problem is located in the data pool, the end user might need to contact the provider directlyError monitoringErrors should not mount up. Processing is time-critical as the end user is waiting for the confirmation.Performance monitoring Not applicableThroughput monitoring Not applicableBacklog monitoringErrors should not mount up. Processing is time-critical as the end user is waiting for the confirmation.2.11.3 Monitoring objects in SAP Solution ManagerMonitoring Selection Criteria Alert Analysis Tool on Monitoring Frequency /Object Satellite System Data CollectionXML message Message type (see Messages in SXI_Monitor In short intervals when chapter 2.11.5) status error confirmations are treatedTable 11: Business process step 12 – Monitoring objects in SAP Solution Manager2.11.4 How to find meaningful thresholds per monitoring objectEach message is important so there is no threshold for importance.Processing is time-critical as the end user is waiting for the confirmation.2.11.5 Error handling per monitoring objectMonitor for processed XML messages on PI sideIn the transaction SXI_MONITOR you can analyze all error or success messages.You can restrict the selection of messages to the message type: TradeItemCatalogueAcceptanceNotificationMessage_async_OutYou can enter the message type in the field Interface Name in the subscreen Sender.© 2009 SAP AG page 56/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)2.12 Business Process Step 13: Receive and Accept/Refuse Confirmation Message2.12.1 DescriptionData pool checks format and consistency. In case of an error, the data pool sends a rejection messageotherwise an acceptance where it repeats the status of the GTIN transmitted by the retailer.2.12.2 Monitoring requirementsError monitoring Error handling within the data pool itself is not controlled by SAP.Performance monitoring Error handling within the data pool itself is not controlled by SAP.Throughput monitoring Error handling within the data pool itself is not controlled by SAP.Backlog monitoring Error handling within the data pool itself is not controlled by SAP.2.12.3 Monitoring objects in SAP Solution ManagerMonitoring Selection Alert Analysis Tool on Monitoring Frequency /Object Criteria Satellite System Data CollectionNot applicableTable 12: Business process step 13 – Monitoring objects in SAP Solution Manager2.12.4 How to find meaningful thresholds per monitoring objectError handling within the data pool itself is not controlled by SAP.2.12.5 Error handling per monitoring objectError handling within the data pool itself is not controlled by SAP.2.13 Business Process Step 14: Translate Information2.13.1 DescriptionPI translates the message sent from the data pool into the inbound proxy format which can be understood bythe receiving SAP for Retail system.© 2009 SAP AG page 57/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)2.13.2 Monitoring requirementsProcessing is time-critical as the end user is waiting for the confirmation.As the end user cannot decide whether problems are located in the internal or external systems, an IToperator needs to closely monitor the communication of the confirmation.If the problem is located in the data pool, the end user might need to contact the provider directly.Error monitoringErrors should not mount up. Processing is time-critical as the end user is waiting for the confirmation.Performance monitoring Not applicableThroughput monitoring Not applicableBacklog monitoringErrors should not mount up. Processing is time-critical as the end user is waiting for the confirmation.2.13.3 Monitoring objects in SAP Solution ManagerMonitoring Selection Criteria Alert Analysis Tool on Monitoring Frequency /Object Satellite System Data CollectionXML Message Message type (see SXI_Monitor ? chapter 2.13.5)Table 13: Business process step 14 – Monitoring objects in SAP Solution Manager2.13.4 How to find meaningful thresholds per monitoring objectEach message is important so there is no threshold for importance.Processing is time critical as the end user is waiting for the confirmation.2.13.5 Error handling per monitoring objectMonitor for processed XML messages on PI sideIn transaction SXI_MONITOR, you can analyze all error or success messages.You can restrict the selection of messages to the message type: TradeItemCatalogueItemStatusNotificationMessage_async_InYou can enter the message type in the field Interface Name in the subscreen Receiver.This message type is the same as used for the feedback of a subscription. Unfortunately, there is no option todistinguish the two kinds of feedback messages through selection in SXI_MONITOR.© 2009 SAP AG page 58/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)2.14 Business Process Step 15: Response2.14.1 DescriptionWhen the data pool accepts the confirmation message sent to the supplier by sending the status notification,the status transmitted to the data pool is set as the processing status in the confirmation message. You cansee the confirmation status in the Confirmation Manager.2.14.2 Monitoring requirementsProcessing is time-critical as the end user is waiting for the confirmation.As the end user cannot decide whether problems are located in the internal or external systems, an IToperator needs to closely monitor the communication of the confirmation.If the problem is located in the data pool, the end user might need to contact the provider directlyError monitoringErrors should not mount up. Processing is time-critical as the end user is waiting for the confirmation.Performance monitoring Not applicableThroughput monitoring Not applicableBacklog monitoringErrors should not mount up. Processing is time-critical as the end user is waiting for the confirmation.2.14.3 Monitoring objects in SAP Solution ManagerMonitoring Selection Criteria Alert Analysis Tool on MonitoringObject Satellite System Frequency / Data CollectionConfirmation Status of sent Status remains WGDS_CONFIRM_Manager messages unknown MANAGERXML messages Message type (see SXI_MONITOR chapter 2.14.5.2)Table 14: Business process step 15 – Monitoring objects in SAP Solution Manager2.14.4 How to find meaningful thresholds per monitoring objectEach message is important so there is no threshold for importance.Processing is time-critical as the end user is waiting for the confirmation.© 2009 SAP AG page 59/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)2.14.5 Error handling per monitoring object2.14.5.1 Confirmation ManagerIf the status remains unknown despite a confirmation being sent, then an error has potentially occurred in thecommunication. This needs to be checked.2.14.5.2 Monitor for processed XML messagesIn transaction SXI_MONITOR, you can analyze all error- or success messages concerning the receivedconfirmationYou can restrict the selection of messages to the message type: TradeItemCatalogueItemStatusNotificationMessage_async_InYou can enter the message type in the field Interface Name in the subscreen Receiver.© 2009 SAP AG page 60/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)3 Further Information3.1 Related Best Practice DocumentsThere are several other Best Practice documents that relate to this Best Practice document. They areavailable on SAP Service Marketplace at https://service.sap.com/solutionmanagerbp. These documents are: Best Practice General Business Process Management: This document explains the procedures you should use to create a general Business Process Management concept. This includes the definition and documentation of the core business processes, definition of monitoring objects, definition of monitoring activities including error handling procedures, monitoring tools, monitoring frequencies, the definition of communication and escalation procedures and the assignment of responsibilities. ALE Monitoring: This Best Practice helps you set up an Interface Monitoring concept with the focus on ALE monitoring for your SAP solution. This document will outline possibilities on how to optimally monitor ALE-based interfaces manually as well as automated by using SAP Solution Manager. Both monitoring approaches aim to detect any irregularities or deviations or to detect error situations at an early stage. Job Scheduling Management: This Best Practice provides a detailed description of what SAP recommends as a standardized formal process to support a job request process, including an end user job request form and an approval process. This integrated process will avoid error-prone and time-intensive manual processes of copying redundant data from one data source to another (for example, MS Excel to job scheduling tool). SAP Business Process Management for ERP Logistics: This Best Practice helps you set up a Business Process Monitoring concept for your SAP ERP solution. The concept aims at defining procedures for business process-oriented monitoring and error handling and escalation procedures for your company’s ERP core business processes. These procedures intend to ensure a smooth and reliable flow of the core business processes so that your business requirements are met. Background Job Monitoring with SAP Solution Manager: This Best Practice will help you to set up back- ground job monitoring properly in the Business Process Monitoring framework of SAP Solution Manager.Please note that these documents are also available in the SAP Service Marketplace using alias RunSAPRun SAP Best Practices.3.2 Background Information and ReferencesFor further information about the GDS scenario, please visit the following links: Connectivity Kit (implementation wiki): https://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=58985 GDS for Retail wiki: https://wiki.sdn.sap.com/wiki/x/hyw GDS user guides: https://sapneth4.wdf.sap.corp/~form/sapnet?_SHORTKEY=01200252310000081520& help.sap.com: Distributed data processing Optimized master data exchange using SAP Enterprise Services: http://help.sap.com/erp2005_ehp_04/helpdata/en/4c/420a4e470a11d1894a0000e8323352/frameset.htm© 2009 SAP AG page 61/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Index of FiguresFigure 1: Alert type Number of ABAP Dumps (Delta) 11Figure 2: Monitoring objects – Dialog performance 12Figure 3: Monitoring alerts - Dialog performance 13Figure 4: Monitoring objects – Update errors 14Figure 5: Monitoring objects – Due list log 15Figure 6: Monitoring objects – Application log 16Figure 7: Monitoring alerts – Application log/critical messages 16Figure 8: Other CCMS monitors 17Figure 9: Analysis and monitoring transactions 18Figure 10: Analysis and monitoring URL 18Figure 11: Business processes in GDS 22Figure 12: Business process step 1 – Standard selection criteria 25Figure 13: Business process step 1 – Status overview 26Figure 14: Business process step 1 – Display message details 26Figure 15: Business process step 1 – Display message content 27Figure 16: Business process step 1 – Subscription display 28Figure 17: Business process step 3 – Monitor for processed XML messages 30Figure 18: Business process step 4 – Monitor for processed XML messages 33Figure 19: Business process step 5 – Monitor for processed XML messages 36Figure 20: Business process step 5 – Subscription display 37Figure 21: Business process step 7 – Monitor for processed XML messages 39Figure 22: Business process step 7 – Integration Engine configuration 1 40Figure 23: Business process step 7 – Integration Engine configuration 2 40Figure 24: Business process step 7 – Integration Engine configuration 3 41Figure 25: Business process step 8–10 – Storage monitor 43Figure 26: Business process step 8–10 – Sort by time stamp 44Figure 27: Business process step 8–10 – Display related items 44Figure 28: Business process step 8–10 – Display article data 45Figure 29: Business process step 8–10 – Display stored data 46Figure 30: Business process step 8–10 – Access application log 47Figure 31: Business process step 8–10 – Check mandatory fields 48Figure 32: Business process step 8–10 – Reprocess message 49Figure 33: Business process step 8–10 – Set undesired messages to status Complete 49Figure 34: Business process step 8–10 – Manual posting 50Figure 35: Business process step 8–10 – Application log 51Figure 36: Business process step 11 – Identify messages for a confirmation 54Figure 37: Business process step 11 – Select message for confirmation 55Figure 38: Business process step 11 – Check message status 55© 2009 SAP AG page 62/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)Index of TablesTable 1: Business process step 1 – Monitoring objects 24Table 2: Business process step 2 – Monitoring objects in SAP Solution Manager 29Table 3: Business process step 3 – Monitoring objects in SAP Solution Manager 31Table 4: Business process step 4 – Monitoring objects in SAP Solution Manager 32Table 5: Business process step 5 – Monitoring objects in SAP Solution Manager 35Table 6: Business process step 6 – Monitoring objects in SAP Solution Manager 38Table 7: Business process step 7 – Monitoring objects in SAP Solution Manager 39Table 8: Business process step 8–10 – Monitoring objects in SAP Solution Manager 42Table 9: Business process step 11 – Monitoring objects in SAP Solution Manager 53Table 10: Business process step 12 – Monitoring objects in SAP Solution Manager 56Table 11: Business process step 13 – Monitoring objects in SAP Solution Manager 57Table 12: Business process step 14 – Monitoring objects in SAP Solution Manager 58Table 13: Business process step 15 – Monitoring objects in SAP Solution Manager 59© 2009 SAP AG page 63/64
  • Best Practice for Solution OperationsManage Operations for SAP for Retail Global Data Synchronization (GDS)© Copyright 2009 SAP AG. All Rights ReservedNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries,zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBMCorporation.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of CitrixSystems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented byNetscape.MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as theirrespective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. Allother product and service names mentioned are the trademarks of their respective companies. Data contained in this document servesinformational purposes only. National product specifications may vary.The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any formor for any purpose without the express prior written permission of SAP AG.This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This documentcontains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP toany particular course of business, product strategy, and/or development. Please note that this document is subject to change and maybe changed by SAP at any time without notice.SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of theinformation, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind,either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages thatmay result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you mayaccess through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide anywarranty whatsoever relating to third-party Web pages.© 2009 SAP AG page 64/64