Manage operations for sap merchandise and assortment planning ( map)

3,282 views
3,167 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
3,282
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
110
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Manage operations for sap merchandise and assortment planning ( map)

  1. 1. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP) Dietmar-Hopp-Allee 16 D-69190 Walldorf CS STATUS customer published DATE VERSION April 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 Operation
  2. 2. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP)Table of Contents1 Management Summary 4 1.1 Goal of Using this Best Practice 4 1.2 Alternative Practices 4 1.3 Staff and Skills Requirements 4 1.4 System Requirements 5 1.5 Duration and Timing 5 1.6 How to Use this Best Practice 5 1.7 Best Practice Procedure 6 1.7.1 Preliminary tasks 6 1.7.2 Monitoring concepts 6 1.7.3 Business Process Monitoring in SAP Solution Manager 6 1.7.4 Monitoring types for Business Process Monitoring in SAP Solution Manager 7 1.7.4.1 Application monitor 8 1.7.4.2 Background job 8 1.7.4.3 Monitoring objects 9 1.7.4.4 ABAP dump collector 9 1.7.4.5 Dialog performance 10 1.7.4.6 Update errors 11 1.7.4.7 Due list log 12 1.7.4.8 Application log 13 1.7.4.9 Other CCMS monitors 15 1.7.4.10 Analysis and monitoring tools 15 1.7.4.11 Monitoring activities 17 1.7.4.12 Notifications 17 1.7.5 Business Process Monitoring Process 19 1.7.6 Legend 192 Business Process Monitoring for a Merchandise and Assortment Planning 21 2.1 Business Processes 21 2.1.1 Business Process Strategic Planning 23 2.1.1.1 Monitoring requirements 24 2.1.1.2 Monitoring objects 24 2.1.2 Business Process Merchandise Planning 25 2.1.2.1 Monitoring Requirements 25 2.1.2.2 Monitoring objects 26 2.1.3 Business Process Store Planning 26 2.1.3.1 Monitoring requirements 27 2.1.3.2 Monitoring objects 27 2.1.4 Business Process Reconciliation Plan 27 2.1.4.1 Monitoring requirements 28 2.1.4.2 Monitoring objects 28 2.1.5 Business Process Assortment Planning Basics 29 2.1.5.1 Monitoring Requirements 30 2.1.5.2 Monitoring objects 30 2.1.6 Business Process Assortment Management Basics 31 2.1.6.1 Monitoring requirements 32© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 2/46
  3. 3. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP) 2.1.6.2 Monitoring objects (optional: in SAP Solution Manager) 32 2.1.6.3 How to find meaningful thresholds per monitoring object 33 2.1.7 Business Process Assortment Planning Fashion 33 2.1.7.1 Monitoring requirements 34 2.1.7.2 Monitoring objects 34 2.1.8 Business Process Assortment Management Fashion 35 2.1.8.1 Monitoring requirements 36 2.1.8.2 Monitoring objects 36 2.2 Monitoring Possibilities for Merchandise and Assortment Planning 37 2.2.1 Monitoring for retail planning within SAP BI 37 2.2.2 Monitoring for Release Workbench within SAP BI 38 2.2.3 Monitoring for Assortment Management Basics within SAP ECC 40 2.2.4 Monitoring for Assortment Management Fashion within SAP ECC 423 Further Information 44 3.1 Related Best Practice Documents 44Index of Figures 45Index of Tables 45© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 3/46
  4. 4. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP)1 Management Summary1.1 Goal of Using this Best PracticeThis Best Practice helps you set up a Business Process Monitoring concept for your SAP Retail solution. Theconcept aims to define procedures for business process oriented monitoring and error handling andescalation procedures for your business process Merchandise and Assortment Planning (MAP). 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 contains the recommended approach from SAP which uses whenever possible the SAPSolution Manager for the monitoring functionalities. But even if you do not use the SAP Solution Manager werecommend to follow the procedures described in this document as much as possible in order to ensure asmooth and reliable flow of your business processes as well as an appropriate response in case ofunforeseen errors.1.2 Alternative PracticesYou can have SAP experts deliver this Best Practice on-site by ordering an SAP Solution ManagementOptimization (SMO) service for SAP Business Process Management (BPM). This service is exclusivelyavailable within SAP’s support engagements SAP MaxAttention and SAP Safeguarding. If your companycurrently does not have any support engagement with SAP, it is also possible to get assistance by SAPexperts from SAP Consulting. If this case, please contact your local SAP Consulting representative.1.3 Staff and Skills RequirementsTo implement this Best Practice, you require the following teams:Application Management teamThis team creates the ERP Business Process Monitoring concept and consists of experts from several areasof your company: Business department Solution support organization (for example the Basis Support or the Application Support) Implementation project teamBusiness process operations teamThe business process operations team will be responsible for applying the resulting procedures derived fromimplementing this best practice. They include the following groups: Persons designated to perform business process oriented monitoring and ensure that the process runs smoothly (e.g. the business process champion for each business process) All parties in your solution support organization and IT department involved in monitoring focused on the application aspects (application support, development support, Job Scheduling Management)© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 4/46
  5. 5. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP)SAP technology operations team All parties in your solution support organization and IT department involved in monitoring focused on the system administration side (program scheduling management, software monitoring team, System administration team including the system administrator)Business Process champion The business process champion is the person in the business department who is responsible for the successful execution of the Business Process. He coordinates all activities necessary for the business process. Therefore, he is usually responsible for the escalation paths in case of problems. Often he is a second level in the escalation procedure, if the application monitoring team needs to escalate an issue.More information about roles and responsibilities of these teams can be found in the super-ordinate BestPractice General Business Process Management, which you can obtain through SAP Solution Manager orthe SAP Service Marketplace, quicklink /BPM.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 Map solution via SAP Solution Manager, the SAPBasis Release of the systems to be monitored have to be at least 4.6C. To have all described monitoringobjects available in SAP Solution Manager, the add-on ST-A/PI01L has to be installed on the SAP for Retailand the SAP BI system.1.5 Duration and TimingDuration Creating a Business Process Monitoring concept could take around one week per business process. Implementing the Business Process Monitoring concept might take approximately an additional week.TimingThe best time to apply this Best Practice is during the planning phase or during the implementation phase ofyour SAP solution.1.6 How to Use this Best PracticeHere you find a brief description of how you should proceed in using this document: Read through the General Business Process Management Best Practice, available on the Sap Service Marketplace. This document explains the procedures you should use to create a general Business Process Management concept. This includes the definition and documentation of the core business processes, definition of monitoring objects, definition of monitoring activities including error handling procedures, monitoring tools and monitoring frequencies, the definition of communication and escalation procedures and the assignment of responsibilities. At the beginning of chapter 2 you will find a typical flow chart of the core business process explained in this Best Practice. It is intended to be used as a guideline for writing down your company specific process documentation.© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 5/46
  6. 6. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP) In chapter 1.7.4 you find further information that is relevant for more than one scenario. In case information from the generic part is relevant for a specific business process step in one of the scenarios you will find a clear link to the corresponding chapter in the generic part.1.7 Best Practice Procedure1.7.1 Preliminary tasksBefore performing this Best Practice, ensure that you perform the following preliminary tasks or checks in thesystem: Complete all installation and post-installation actions and procedures including customizing Ensure that the initial download has been successfully executed Apply all SAP recommendations from SAP service sessions and any SAP recommendations resulting from customer problem messages Implement all current SAP support packages upon availability1.7.2 Monitoring conceptsThe monitoring procedures proposed for each business process step are the core of this Best Practice. Themonitoring procedures help you to ensure that the technical processes meet the requirements for stability,performance and completeness. These procedures cover monitoring for the five areas: Error monitoring Performance monitoring Throughput monitoring Backlog monitoring Data consistency monitoringFor each of the business process steps you will find the following information: A detailed functional description of the process step Identified monitoring requirements for the process step Defined monitoring objects, alerts and selection criteria Description of error handling procedures and restartabilityGeneral monitoring activities that are valid for all or most scenarios are described in the generic part inchapter 1.7.4. Recommendations for performance monitoring can also be found in this chapter. Theperformance of the most important steps of your core business processes should be monitored on a regularbasis. The monitoring procedure for performance monitoring of all steps that are executed in an SAP Retailsolution is generally the same. Therefore, you will only find specific performance monitoringrecommendations on selected business process steps.1.7.3 Business Process Monitoring in SAP Solution ManagerBusiness Process Monitoring (BPMon), as part of Solution Monitoring means the proactive and process-oriented monitoring of the most important or critical business processes including the observation of alltechnical and business application specific functions that are required for a steady and stable flow of thebusiness processes.The core business processes that are implemented in a SAP MAP system or other software and operated bya company are of particular importance, and Business Process Monitoring is intended to ensure a smooth© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 6/46
  7. 7. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP)and reliable operation of the business processes and, thereby, that the core business processes meet acompany’s business requirements in terms of stability, performance, and completeness. The SAP SolutionManager provides a graphic to visualize a company’s (distributed) system and solution landscape and allrelated business processes. By using Business Process Monitoring, it is possible to define and customizealert situations from a basic set of configurable alerts provided by the SAP Solution Manager. These alertsare then visualized by green, yellow, and red alert icons for each individual business process step in thegraphical business process representation. Business Process Monitoring is intended to detect and respond tocritical situations as early as possible in order to solve problems as fast as possible.In addition, the SAP Solution Manager offers extended functionality for error handling and problem resolution.By the definition of contact persons and escalation paths, Business Process Monitoring can be integrated intothe company’s overall strategy for Business Process Management and solution management within theirsolution support organization.In general, a Business Process Monitoring includes the solution-wide observation of: Business process performance (key performance indicators) Background jobs (Job Scheduling Management tasks) Business application logs (such as any error log, general application log, due list logs etc.) Data transfer via interfaces between software components Data consistency Technical infrastructure and components which are required to run the business processes Required periodic monitoring tasksFor further details on Business Process Monitoring please refer to http://service.sap.com/bpm.1.7.4 Monitoring types for Business Process Monitoring in SAP Solution ManagerMonitoring types are part of the functional scope of Business Process Monitoring as it is available in the SAPSolution Manager. The below mentioned monitoring types are available: Application monitor (Throughput and backlog indicators, data consistency checks, mass activity monitors, due list log, MRP key figures, user exit) Background jobs (jobs running on SAP systems with an SAP basis) Dialog performance (dialog transaction performance) Update error (V1 and V2 update errors from SM13 for specific transactions and programs) Due list log (messages for deliveries and billings) Application log (messages from the Application Log SLG1) Document volume (based on table call statistics in ST10) Other CCMS monitor (all alerts that are configured in the CCMS alert monitor)Depending on what is executed during a specific business process step the relevant monitoring types mustbe selected. In order to receive detailed information on how to set up the monitoring objects in the SAPSolution Manager, please refer to the documentation that is available under http://service.sap.com/bpm.One prerequisite for setting up Business Process and Interface Monitoring in the SAP Solution Manager isthat all business processes and business process steps are maintained in the respective solution thatcontains all affected system components. If you want to learn more about how to set this up, please turn to(URL http://help.sap.com) SAP Solution Manager Basic Settings.© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 7/46
  8. 8. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP)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 /installations Entry byApplication 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 respectivesatellite. In case of problems refer to SAP Note 915933. The throughput and backlog indicator functionality available as of ST-A/PI 01J* is only working properly with ST-SER 700_2007_1. This is due to changes in the underlying architecture.More detailed information about the different application monitor functionalities and a detailed description onhow to define self-written monitoring collectors for the user exit are explained in the documents Setup Guide– Application Monitoring and Setup Guide – User Exit respectively (URL http://www.service.sap.com/ AliasBPM Media Library).1.7.4.1.1 Throughput and backlog indicators (TBIs)As of ST-A/PI 01H a completely new set of application monitors has been introduced. While the alreadyestablished monitors are all evaluating specific logs or performance data these new monitors are considering(un-)processed documents in the SAP system and provide so called throughput and backlog indicators.These TBIs should especially provide Automated and early detection of application error situations and backlogs in the core business processes Automated error and backlog analysis toolsFor ERP logistic the following monitors are available: Sales and services (e.g. sales documents, invoices) Warehouse management (e.g. transfer requirements, transfer orders) Inventory management (e.g. goods movements) Logistics execution (e.g. deliveries, shipments) 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 (URLhttp://www.service.sap.com/BPM Media Library).1.7.4.2 Background jobThe background job monitoring should be part of a Job Scheduling Management concept (go tohttp://service.sap.com/solutionmanagerbp, topic area Business Process Operations to find a Best Practicedocument Job Scheduling Management). Because of several restrictions regarding background jobscheduling, e.g. time restrictions, restriction of hardware resources (CPU, main memory, …) or existingdependencies between different activities (e.g. invoices can only be created after the corresponding goodsissue is posted, or back order processing and material requirements planning should not run at the sametime) it is very important to ensure the stable run of background jobs. A cancelled background job should be© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 8/46
  9. 9. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP)identified as soon as possible in order to react as fast as possible. Therefore it is also necessary to definerestart procedures and escalation paths.1.7.4.3 Monitoring objectsBefore setting up monitoring the monitoring objects must be clearly defined. A monitoring object is a singlebackground job or a group of background jobs. There are four different possibilities to identify a specialbackground job or a group of background jobs. This information needs to be maintained in the sub-node‘Background Job’ below a business process step.A more detailed description on the subject what kind of alerts make sense or what kind of alerts are possibleare discussed in the Best Practice document Background Job Monitoring with SAP Solution Manager whichcan be found on the SAP Marketplace http://service.sap.com/solutionmanagerbp, topic area BusinessProcess Operation.1.7.4.4 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.1.7.4.4.1 Monitoring objectsThe monitoring object is an ABAP runtime error. This runtime error can be specified via the runtime errorname, the user who is responsible for the runtime error, the client on which the runtime error occurs or theProgram which leads to the runtime error.1.7.4.4.2 Monitoring alertsPossible Alerts types are the Number of ABAP Dumps (Delta) – all dumps since the last collector run – andNumber of ABAP Dumps (Reporting) – all runtime errors of specified type, client and program for this day orfor the previous day.Figure 1: Alert type Number of ABAP Dumps (Delta)© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 9/46
  10. 10. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP)1.7.4.5 Dialog performanceDialog performance implies the monitoring of the dialog transaction performance of any transaction in theSAP system. This could be a standard transaction or an own developed transaction.1.7.4.5.1 Monitoring objectsThe monitoring object is the transaction itself. The customizing has to be done in node Dialog Performance.In table Transactions all transactions that are already configured to that business process step are listed.The relevant transactions need to be selected for monitoring. It is also possible to add or to removetransactions within table Add/Remove Transactions. The monitoring can be performed per SAP instance.Therefore the respective instances have to be selected in table SAP Instances. All instances that aremaintained for a system are listed there. Table Alert Types shows the dialog response time and all parts ofthe response time, like queue time, load and generation time, database request time and the front-endresponse time, that can be monitored. Those times that are relevant for monitoring have to be selected. Aftersaving this node a sub-node Performance Alerts will appear where the threshold values have to be entered.Figure 2: Monitoring objects – Dialog performance1.7.4.5.2 Monitoring AlertsEach table in the sub-node Performance Alerts corresponds to an alert type chosen in the higher-level node,and lists the combinations of specified transaction code and SAP instance.For each combination of transaction code and instance that should be included in the monitoring, thethreshold values resulting in alert messages for changes from GREEN to YELLOW, from YELLOW to RED,back from RED to YELLOW, and back from YELLOW to GREEN have to be specified.Since the monitoring object for performance monitoring is created on the satellite system, it might be possiblethat the object already exists there. Therefore you can load the current threshold values from the respectivesystems via the button Load thresholds from XYZ, whereas XYZ represents the SID.© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 10/46
  11. 11. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP)If successfully retrieved for an SAP instance, the values are filled in columns. If no active settings for thethreshold values were found for a certain transaction code, default values are set (indicated in columnDefault). To transfer the threshold values for a single line from right to left, the Copy icon can be used. Totransfer all at once (all thresholds for all columns and tables) there is an additional Copy all button.Figure 3: Monitoring alerts – Dialog performance1.7.4.6 Update errorsChanges to the data in an SAP system caused by a business process should be written to the database in fullor not at all. If the operation is canceled while the transaction is being executed, or if an error occurs, thetransaction should not make any changes to the database. These activities are handled by the SAP updatesystem.The SAP system makes a distinction between primary, time-critical (V1) and secondary, non-time-critical (V2)update errors. This distinction allows the system to process critical database changes before less criticalchanges.V1 modules describe critical or primary changes; these affect objects that have a controlling function in theSAP system, for example order creation or changes to material stock.V2 modules describe less critical secondary changes. These are pure statistical updates, for example, suchas result calculations.Monitoring objectsMonitoring of update errors can be configured for online transactions and/or ABAP programs relevant in abusiness process. This is the object type. The name of the object is the name of a transaction or the name ofthe ABAP program itself. If desired a user executing the transaction or the ABAP program can be specified.If no user is specified explicitly, all users (represented by *) will be considered in monitoring data evaluation.© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 11/46
  12. 12. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP)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.7 Due list logA due list is a list that contains several entries (documents) depending on selection criteria. There aredifferent types of due lists in an SAP system of which the following three are most important: delivery (L),billing (F) and picking (K). The delivery due list can be directly accessed via transaction V_SA, the billing duelist via transaction V.21. In case of a billing due list, the list contains e.g. a number of sales documents 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, it can be displayed 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. If a certain user isprocessing the due list, the name of the user can be specified here. If it is user independent a wild card ‘*’ canbe used. The aggregation level needs to be defined. This could be per day, per hour or per log.Monitoring alertsFor the monitoring of due list log messages, four different alert types can be used:1. DocumentCreation refers to the status of the document creation itself. The alert rating (YELLOW or RED) will be raised if no documents were created during a due list run.© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 12/46
  13. 13. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP)2. MinQuantityDocs refers to a minimum number of documents that should be created during a Due List run. The threshold values for the number of documents that result in a change from GREEN to YELLOW (or back) and from YELLOW to RED (or back) must be maintained.3. TotalQuantityMsgs refers to the total number of message created during a due list run.4. The threshold values for the number of messages that result in a change from GREEN to YELLOW (or back) and from YELLOW to RED (or back) must be maintained.5. DLLogMsgs refers to specific due list log messages. The message type, the message ID and the number can be specified. It is also possible to use wild cards. The threshold values for the number of messages that result in a change from GREEN to YELLOW (or back) and from YELLOW to RED (or back) must be maintained.Figure 5: Monitoring objects – Due list log1.7.4.8 Application logThe application log provides an infrastructure for collecting messages, saving them in the database anddisplaying them as a log. Situations can arise at runtime in application programs that must be brought to theattention of the user in some way. These are usually errors. It can also be useful to report a successfulcompletion. The information that arises is called a message. The set of messages is a log. A log usually alsohas header information (log type, creator, creation time, etc.). A transaction can generate several logs.The application log is not written consecutively but as a whole at one point in time.1.7.4.8.1 Monitoring objects and alertsThe application log allows an application- or object-oriented recording of events. An object and any sub-object that belongs to it classify each event. The analysis of the logs is similarly object (or sub-object)oriented. The name of an object (and/or subobject) can be found in transaction /nSLG1 together with all otherspecific information to that log.© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 13/46
  14. 14. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP)Figure 6: Monitoring objects and alerts – Application logIt is possible to monitor for the total number of messages belonging to an object. Therefore the number ofmessages that raises a YELLOW alert and the number of messages changing from a YELLOW to a REDalert must be maintained.It is also possible to monitor specific messages that are considered as critical in table CriticalMsgs. Toconfigure the monitoring of critical application log messages, the relevant object-sub object combinationsneed to be selected. For each of these combinations the message type, the message ID and the messagenumber as well as the threshold values for the number of critical messages that are supposed to result inchanges from GREEN to YELLOW and from YELLOW to RED can be specified. It is also possible to usewild cards.Figure 7: Monitoring alerts – Application log/critical messages© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 14/46
  15. 15. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP)1.7.4.9 Other CCMS monitorsWith other CCMS monitors it is possible to assign any CCMS monitoring tree element (MTE) to a businessprocess step. Therefore it is necessary to call transaction RZ20 in the satellite system and to open a monitorthat contains the required alert(s).The name of the monitoring tree element (MTE) can be found by choosing F1. The MTE name needs to becopied into the corresponding column of the table below (See screenshot “Other CCMS Monitors” below).Under column Monitor Name it is possible to assign an individual name. The MTE used for monitoring should be an MTE on the lowest leaf-level, i.e. on attribute level. If an MTE of a higher branch-level (collective MTE) is chosen then the current and open view in thegraphics will show the right alerts but it isn’t possible to work on these alerts within the Business ProcessMonitoring session as the alerts are not replicated there.In order to load the threshold values that are currently valid in the corresponding system, the button can be used.If successfully retrieved, the values are filled in the right-hand columns. If no active settings for the thresholdvalues were found these columns remain empty.To transfer the thresholds values for a single line from right to left double-click on the copy icon.Figure 8: Other CCMS monitors Unlike all other monitoring types the other ccms monitoring provides the opportunity to assign MTEs from other Systems than the one system the actual business process step is assigned to.As an example you could be interested in monitoring the availability from a portal system that possesses noCCMS but is included as one business process step in your business process. Now you could use one MTEin the CCMS of the SAP Solution Manager to monitor the heartbeat of the portal. You could then assign thecorresponding alert via other CCMS monitoring to business process step running on the portal system.1.7.4.10 Analysis and monitoring toolsIt is possible to specify analysis transactions or URL addresses (including file directories) per monitoringobject. In case of analysis transactions these should be used to analyze errors or problems either locally inthe SAP Solution Manager system itself (Call Option 1) or directly in the respective satellite systems (Call© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 15/46
  16. 16. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP)Option 2). Per default some standard transactions are maintained, e.g. transaction SM37, that provides a joboverview in an SAP system, is maintained for background jobs or transaction SLG1 to have a look into theapplication log.It is also possible to add new transactions; this could be standard transactions or customer self-writtentransactions.Figure 9: Analysis & monitoring transactionsOn the second tab strip it is possible to specify an URL which should be called in order to further analyze thegiven problem. This is especially interesting if you have some knowledge documents linked to a portal. Youdefine a short text and the URL to be called. For web pages to be called, specify the full URL, e.g. http://help.sap.com. For content available on file servers specify the full file path, using the nomenclature: file://<server>..., e.g. file://server1operations_documentsoperations-handbook.txtFigure 10: Analysis & monitoring URL© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 16/46
  17. 17. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP)The specified transactions or URLs will be available in the form of buttons within a business process stepwhen using the monitoring later on inside the Business Process Monitoring session. By pressing thesebuttons (e.g. ), the user will jump directly into the corresponding transactioneither in the SAP Solution Manager system (here: SAT) or the connected satellite system (here: CT1) forfurther analysis. For URLs the push-button (e.g. ) contains the short text (limited to 20characters) from the set-up session and leads the user to the defined URL in a newly opened browserwindow.1.7.4.11 Monitoring activitiesMonitoring activities should be set up for every monitoring object within a business process step. Allmonitoring objects defined within a business process step are listed here. To ensure effective monitoring andefficient problem resolution the responsibilities should be assigned and problem resolution procedures shouldbe defined as described in the following table. Some information is taken from the previous node solutionsupport organization. Monitoring TEAM Defines the team that is responsible for monitoring the relevant monitoring object. Use value help [F4]. Person Resp. Defines the Person who is responsible for monitoring the monitoring object. Use value help [F4]. Frequency Describes how often the responsible person should process the required monitoring activity. Start Time Describes at which time the responsible person should process the required monitoring activity. Problem Indicator A description about what indicates a problem. Error Handling Describes how to react on problems or errors, i.e. how to solve the problem/correct the error. Escalation Path Describes the escalation path in case that the person responsible could not solve the problem. Persons who can be contacted should be maintained here.Table 1: Monitoring activitiesAdditional information related to this business process step can be entered in the tables Monitoring Activities,Error Handling, Restart of Step and Escalation Path. Those information would be valid for the whole businessprocess step and helps users who have to carry out the monitoring and who are not so familiar with thatparticular business process.1.7.4.12 NotificationsNotifications can be set up for the whole business process or for each business process step individually.There are two types of notifications: workflow notifications and support notifications. Workflow notificationsallow sending messages in case of alerts to a specified recipient. This could be an e-mail or SAPOffice mail.© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 17/46
  18. 18. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP)Support notifications allow setting up a service desk message in case of an alert. The information entered forthe service desk message serves as a template. The service desk message can be created manually orautomatically.On business process level it is possible to define notifications for the whole business process i.e. as soon asthe business process gets an alert status, notifications will be triggered. Alternative notifications can bedefined for every monitoring type individually, e.g. all alerts related to all background jobs of the businessprocess are forwarded to a defined e-mail address.Notifications defined on business process step level will overrule the configuration made on business processlevel for this particular step.1.7.4.12.1 Workflow NotificationSender Must be a user within in the monitoring client of SAP Solution Manager. This user can be even a system user without any roles or profiles, but the user must have a valid e-mail address that is known by the used mail-serverRecipient Address Depending on the recipient type the recipient name is required. This could 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 5 different recipient types: U (e-mail), K (for SMS and Pager), B (SAP user name), R (Remote SAP name) and C (shared distribution list).No. of Yellow Alerts Number of YELLOW alerts that may occur before an automatic notification is triggeredNo. of Red Alerts Number of RED alerts that may occur before an automatic notification is triggeredMax Wait Time [h] Once the maximum wait time [hours] has elapsed, a notification is created, even if the thresholds are not exceededRED Only To restrict this mechanism only to red alerts the flag in column RED Only must be set.Detailed Triggers a long text for e-mails or SAPOffice mails, e.g. name of the solution, name of the business process step, …)1.7.4.12.2 Support NotificationsPriority 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© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 18/46
  19. 19. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP) name that is defined as a business partner with role employee.Text Template Text templates can be defined that will then be available for service desk messages manually created for alerts.Automatic Support notifications will be created automatically depending on the alert thresholds.Reporter Necessary when service desk messages are created automatically. Must be a SAP user name that is defined as a business partner with role general.Num. of YELLOW Necessary when service desk messages are created automatically, e.g. afterAlerts 10 yellow alerts, a service desk message should be created.Num. of RED Alerts Necessary when service desk messages are created automatically, e.g. after 5 red alerts, a service desk message should be created. If in addition to queue, processor, priority and reporter either one of the columns Num of YELLOW Alerts or Num of RED Alerts is filled with a value, the automatic support notification creation is configured. In case that both columns are filled with a value, the automatic support notification creation works with a logical OR operation. Hence, with the figures in the table above the system would create a support notification if there either exist more than 9 yellow alerts or more than 4 red alerts for which no support notification has been created yet.1.7.5 Business Process Monitoring ProcessFor a successful and efficient Business Process Monitoring concept, a process for the execution of themonitoring concept has to be defined. This includes the definition of the roles and responsibilities involved. Ithas to be defined who is supposed to carry out which activity within the process and how communicationbetween the different 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/Problem Management process and the Change Managementprocess. These processes have to be adjusted to the Business Process Monitoring concept so thatcommunication and escalation procedures contained within these processes are adequate to support theBusiness Process Monitoring concept. This includes the final communication of open alert to SAP.Wherever communication connected with Business Process Monitoring happens outside these supportprocesses, separate communication and escalation paths and procedures have to be defined.Please see the above mentioned separate Best Practice for General Business Process Management forfurther details.1.7.6 Legend This symbol indicates you a paragraph from where you can navigate to another chapter of this document for more detailed information on a topic.© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 19/46
  20. 20. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP) This symbol indicates you a paragraph from where you can navigate to another document withinthe SAP Service Marketplace for more detailed information on a topic.© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 20/46
  21. 21. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP)2 Business Process Monitoring for a Merchandise and Assortment PlanningThe business scenario Merchandise and Assortment Planning includes different common retail businessprocesses. In general these business processes build an integrated business scenario by using joinedplanning levels and key figures. Which processes are put to practical use is also customer specific as theconcrete process steps and implementation of the business processes.Merchandise and Assortment Planning is characterized by business process steps with manually maintainedkey figures or key figures calculated by planning functions. Based on the planning requirements integratedplanning and the retail specific Master Data Planning (MDP) can be implemented. Master data planning(MDP) is prerequisite to create new specific retail master data within the planning.As the business processes are implemented based on the same technical features, the different processeshave the same possibilities for business process monitoring. Therefore this chapter is divided in twosubchapters. One subchapter describes the business processes and lists the monitoring objects available forthe process steps. The next subchapter then explains these monitoring possibilities then in greater detail. Please note that particularly in MAP implementations due to deviating assortment and categorymanagement practices, the Business Processes realized are most of the time project specific. The usedbusiness processes, key figures and master data for planning and reporting as well as the implemented InfoCubes and the implemented data flows etc. differ from company to company. This guide contains somegeneral aspects common to most MAP implementations. Please note also that a proper BI implementation and a proper MDP configuration are of particularimportance for a stable operating of a Merchandise and Assortment Planning.2.1 Business ProcessesThe following images provide an overview about the common retail planning processes. The first imageshows the process flow for strategic planning, store planning, merchandise planning and plan reconciliation.© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 21/46
  22. 22. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP) Merchandise and Assortment Planning - Process flow for Planning Processes Strategic Planning SAP BI System Strategic Planning Distribution Chain Strategic Division planning Store Planning Merchandise Planning Strategic analytics Store Sales Planning Sales Planning Store Markdown Planning Markdown Planning Store Gross Margin Planning Gross Margin Planning Store Inventory & Receipts Inventory & Receipts Panning Panning Merchandise analytics Store analytics Plan Reconcilation Plan Reconcilation © SAP 2008 / Project RunSAP for Retail / 4Figure 11: Process flow for planning processesThese planning processes are usually performed once or twice a year. The results of the planning processesare usually used as input for the subsequent processes. These processes can be divided in fashion andbasics based on the merchandise characteristics and its specific requirements. The following image showsthe process flow for Fashion Merchandise. Assortment Planning and Assortment Management for Fashion Merchandise (Integrated Scenario) SAP BI System Assortment Planning Fashion Capacity Planning (optional) Store Segmentation (optional) Assortment Definition SAP ERP for Retail Target Planning Assortment Management Fashion Create Planned Article (optional) Add articles to purchase list Execute Quantity Planning (optional) Perform quantity planning Create Prepack Generation Perform detailed article planning Information (optional) Perform Prepack Planning Release to Merchandise System Release © SAP 2008 / Project RunSAP for Retail / 6Figure 12: Process flow for Fashion Merchandise© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 22/46
  23. 23. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP)The process flow for basic merchandise is shown by the next image. Please note that the image shows theprocess including the optional integration of an external Shelf Optimization Program (SOP). Assortment Planning and Assortment Management for Basic Merchandise (Integrated Scenario) SAP BI System Assortment Planning Basics Capacity Planning (optional) Store Segmentation (optional) External SOP System Assortment Definition SAP ERP for Retail Assortment Planning Basics Create planned article (optional) Assortment Management Basics Request for assortment version out of SOP (optional) Create assortment version Create and maintain layout (optional) modules and layout module versions Optimize planogram (assortment version) Assign articles Add article to assortment version Release optimized planogram tp Assign Stores Planning Release assortment version to SOP (optional) Release layout module versions Check optimized assortment version (optional) Release to merchandising system © SAP 2008 / Project RunSAP for Retail / 5Figure 13: Process flow for Basic Merchandise2.1.1 Business Process Strategic PlanningThe goal of this business process is to create strategic objectives for the company and to pass those targetsdown through the organization.The strategic planning process sets high-level financial plans for e.g. sales, markdowns (markdowns onlyapply to RMA planning layouts), gross margin, average inventory and turnover. The strategic plan is usuallydeveloped once a year by the executive in an organization. The result of the strategic planning usuallyprovides input values to the subsequent processes like e.g. merchandise or store planning.More information regarding the business process Strategic Planning and Merchandise and AssortmentPlanning is available within the SAP Knowledge Warehouse under SAP for Retail: Business ScenarioDescriptions Merchandise and Assortment Planning.© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 23/46
  24. 24. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP) Merchandise and Assortment Planning - Process flow for Planning Processes Strategic Planning SAP BI System Strategic Planning Distribution Chain Strategic Division planning Store Planning Merchandise Planning Strategic analytics Store Sales Planning Sales Planning Store Markdown Planning Markdown Planning Store Gross Margin Planning Gross Margin Planning Store Inventory & Receipts Inventory & Receipts Panning Panning Merchandise analytics Store analytics Plan Reconcilation Plan Reconcilation © SAP 2008 / Project RunSAP for Retail / 4Figure 14: Process flow for Planning Processes – Strategic Planning2.1.1.1 Monitoring requirements To implement this planning process usually the planning functionality of integrated planning and the retail specific Master Data Planning (MDP) is used. For more information regarding monitoring of Integrated Planning and Master Data Planning please see subchapter 2.2.1 Monitoring for retailplanning within SAP BI.2.1.1.2 Monitoring objectsMonitoring Selection Alert Analysis Tool on Monitoring FrequencyObject Criteria Satellite System / Data CollectionData extraction Datasources, Canceled process RSAx Defined by uploadingfrom SAP for Process Chains , chains frequencyRetail Cubes required for the planning processWebDynpro Used Runtime above On a regular basis inPerformance Webdynpros SLA planning phaseQuery Selected queries Runtime above On a regular basisPerfomance used SLATable 2: Business Process Strategic Planning – Monitoring objects© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 24/46
  25. 25. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP)2.1.2 Business Process Merchandise PlanningThe objective of creating merchandise plans is to meet the objectives of the company goals and targets, e.g.sales and gross margin. The merchandise planning process requires planners to develop detailed plans toachieve the company goals. The merchandise plan is usually developed once or twice a year by themerchants in an organization.The merchant plans an extended set of key performance indicators (KPIs) and time horizon to match thecompany goals. Once the merchant is satisfied with the plans, the merchant’s manager approves the plansso they can be incorporated into the reconciliation process.More information regarding the business process Merchandise Planning and Merchandise and AssortmentPlanning is available within the SAP Knowledge Warehouse under SAP for Retail: Business ScenarioDescriptions Merchandise and Assortment Planning. Merchandise and Assortment Planning - Process flow for Planning Processes Strategic Planning SAP BI System Strategic Planning Distribution Chain Strategic Division planning Store Planning Merchandise Planning Strategic analytics Store Sales Planning Sales Planning Store Markdown Planning Markdown Planning Store Gross Margin Planning Gross Margin Planning Store Inventory & Receipts Inventory & Receipts Panning Panning Merchandise analytics Store analytics Plan Reconcilation Plan Reconcilation © SAP 2008 / Project RunSAP for Retail / 4Figure 15: Process flow for Planning Process – Merchandise Planning2.1.2.1 Monitoring Requirements Also for the implementation of this business process the planning functionality of Integrated Planning and the retail specific Master Data Planning (MDP) is usually used. For information regarding monitoring of Integrated Planning and Master Data Planning please see subchapter 2.2.1 Monitoringfor retail planning within SAP BI.© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 25/46
  26. 26. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP)2.1.2.2 Monitoring objectsMonitoring Selection Alert Analysis Tool on Monitoring Frequency/Object Criteria Satellite System Data CollectionData extraction Datasources, Canceled RSAx Defined by uploadingfrom SAP for Process Chains , process chains frequencyRetail Cubes required for the planning processWebDynpro Used Runtime above On a regular basis inPerformance Webdynpros SLA planning phaseQuery Selected queries Runtime above On a regular basisPerfomance used SLATable 3: Business Process Merchandise Planning – Monitoring objects2.1.3 Business Process Store PlanningThe objective of store planning is to create store plans to meet the company goals and targets. Previously tothis process the strategic planning and distribution of the relevant key figures down to the store plan is usuallyperformed by a planner.The business process Store Planning designs the strategic plan in detail, taking into account the differentelements in the store hierarchy (company, region, district and store). The store plan is usually developedonce or twice a year by the store planner in an organization. The store planner plans an extended set of keyperformance indicators (KPIs), e.g. Sales, Receipts, Margin, Inventory or Shrinkage, and time horizon tomatch the company goals, e.g. year/season/month/week.More information regarding the business process Store Planning and Merchandise and Assortment Planningin general is available within the SAP Knowledge Warehouse under SAP for Retail: Business ScenarioDescriptions Merchandise and Assortment Planning.© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 26/46
  27. 27. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP) Merchandise and Assortment Planning - Process flow for Planning Processes Strategic Planning SAP BI System Strategic Planning Distribution Chain Strategic Division planning Store Planning Merchandise Planning Strategic analytics Store Sales Planning Sales Planning Store Markdown Planning Markdown Planning Store Gross Margin Planning Gross Margin Planning Store Inventory & Receipts Inventory & Receipts Panning Panning Merchandise analytics Store analytics Plan Reconcilation Plan Reconcilation © SAP 2008 / Project RunSAP for Retail / 4Figure 16: Process flow for Planning Process – Store Planning2.1.3.1 Monitoring requirementsTo implement the business process Store Planning the planning functionality of Integrated Planning and theretail specific Master Data Planning (MDP) is usually used. For information regarding monitoring of IntegratedPlanning and Master Data Planning please see subchapter 2.2.1 Monitoring for retail planning within SAP BI.2.1.3.2 Monitoring objectsMonitoring Selection Alert Analysis Tool on Monitoring Frequency/Object Criteria Satellite System Data CollectionData extraction Datasources, Canceled process RSAx Defined by uploadingfrom SAP for Process Chains , chains frequencyRetail Cubes required for the planning processWebDynpro Used Runtime above On a regular basis inPerformance Webdynpros SLA planning phaseQuery Selected queries Runtime above On a regular basisPerfomance used SLATable 4: Business Process Store Planning – Monitoring objects2.1.4 Business Process Reconciliation PlanThe objective of the reconciliation plan is to reconciling the strategic, merchandise and store plans. When themerchandise and store plans are completed and the results are rolled back to the reconciliation plan, they© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 27/46
  28. 28. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP)need to be compared to the original strategic objectives. The merchandise and store plans are reviewed tosee if changes need to be made before final authorization and “lock-down” of the plans.More information regarding the business process Reconciliation Plan and Merchandise and AssortmentPlanning is available within the SAP Knowledge Warehouse under SAP for Retail: Business ScenarioDescriptions Merchandise and Assortment Planning. Merchandise and Assortment Planning - Process flow for Planning Processes Strategic Planning SAP BI System Strategic Planning Distribution Chain Strategic Division planning Store Planning Merchandise Planning Strategic analytics Store Sales Planning Sales Planning Store Markdown Planning Markdown Planning Store Gross Margin Planning Gross Margin Planning Store Inventory & Receipts Inventory & Receipts Panning Panning Merchandise analytics Store analytics Plan Reconcilation Plan Reconcilation © SAP 2008 / Project RunSAP for Retail / 4Figure 17: Process flow for Planning Process – Plan Reconciliation2.1.4.1 Monitoring requirements Also for the implementation of the business process Reconciliation Plan the planning functionality of Integrated Planning and the retail specific Master Data Planning (MDP) is usually used. Forinformation regarding monitoring of Integrated Planning and Master Data Planning please see subchapter2.2.1 Monitoring for retail planning within SAP BI.2.1.4.2 Monitoring objects Monitoring Selection Alert Analysis Tool on Monitoring Frequency/ Object Criteria Satellite System Data Collection Data extraction Datasources, Canceled process RSAx Defined by uploading from SAP for Process Chains , chains frequency Retail Cubes required for the planning process, Beispiele? WebDynpro Used Runtime above On a regular basis in Performance Webdynpros SLA planning phase© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 28/46
  29. 29. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP) Monitoring Selection Alert Analysis Tool on Monitoring Frequency/ Object Criteria Satellite System Data Collection Query Selected queries Runtime above On a regular basis Perfomance used SLATable 5: Business Process Reconciliation Plan – Monitoring objects2.1.5 Business Process Assortment Planning BasicsThe objective of Assortment Planning Basics is to plan the structure of assortments and their presentation instores at the merchandise area level and for one planning period. This business process allows to createassortments and assortment versions and to plan them. Assortment versions model the different designs ofan assortment with the articles to be presented over time. Additionally the placement data of the articleassignments can be optimized by an external shelf optimization program (SOP). Also the assignment ofassortments to stores can be planned and restricted temporarily in order to plan the presentation ofassortments in stores.The process ends with the transfer of the planning results to the business process Assortment Managementin SAP ECC.More information regarding the business process Assortment Planning Basics and Merchandise andAssortment Planning is available within the SAP Knowledge Warehouse under SAP for Retail: BusinessScenario Descriptions Merchandise and Assortment Planning Assortment Planning AssortmentPlanning Basics. Assortment Planning and Assortment Management for Basic Merchandise (Integrated Scenario) SAP BI System Assortment Planning Basics Capacity Planning (optional) Store Segmentation (optional) External SOP System Assortment Definition SAP ERP for Retail Assortment Planning Basics Create planned article (optional) Assortment Management Basics Request for assortment version out of SOP (optional) Create assortment version Create and maintain layout (optional) modules and layout module versions Optimize planogram (assortment version) Assign articles Add article to assortment version Release optimized planogram tp Assign Stores Planning Release assortment version to SOP (optional) Release layout module versions Check optimized assortment version (optional) Release to merchandising system © SAP 2008 / Project RunSAP for Retail / 5Figure 18: Assortment Planning Basics (External SOP system, SAP BI system)© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 29/46
  30. 30. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP)2.1.5.1 Monitoring Requirements The planning functionality of Integrated Planning and the retail specific Master Data Planning (MDP) is usually used to implement this business process. Also the retail specific Release Workbench is used to implement this business process. For information regarding monitoring of IntegratedPlanning and Master Data Planning please see subchapter 2.2.1 Monitoring for retail planning within SAP BI.For information regarding the release of the planning data and the connection with an external SOP pleasesee subchapter 2.2.2 Monitoring for Release Workbench within SAP BI2.1.5.2 Monitoring objectsMonitoring Objects based on Retail Planning within SAP BI are listed in the table below:Monitoring Selection Alert Analysis Tool on Monitoring Frequency/Object Criteria Satellite System Data CollectionData extraction Datasources, Canceled process RSAx Defined by uploadingfrom SAP for Process Chains , chains frequencyRetail Cubes required for the planning processWebDynpro Used Runtime above On a regular basis inPerformance Webdynpros SLA planning phaseQuery Selected queries Runtime above On a regular basisPerfomance used SLATable 6: Business Process Assortment Planning Basics – Monitoring objectsMonitoring objects based on the Release Workbench within SAP BI are listed in the table below. For detailsplease see subchapter 2.2.2 Monitoring for Release Workbench within SAP BIMonitoring Selection Alert Analysis Tool on Monitoring Frequency/Object Criteria Satellite System Data CollectionBI Outbound Object:W Error status SLG1 Defined by release frequency for each(application Subobject: message typeissues (including MAP_RELEASEpush scenario to (optional) ExternalSOP), RFC ID: technicalconnection name of messageissues) typeBI Outbound Message status SXMB_MONI, Depending on the qRFC, SMQ1, transfer frequency(XI or SOA SMQ2connectionissues, issuesregarding pullscenario to SOP)© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 30/46
  31. 31. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP)Monitoring Selection Alert Analysis Tool on Monitoring Frequency/Object Criteria Satellite System Data CollectionBI Inbound Object: W Error status SXMB_MONI Defined by inbound frequency from SOP(XI or SOA Subobject::connection issues MAP_INBOUNDregarding datareceive fromSOP),BI Inbound Object: W Error status SLG1 Defined by inbound frequency from SOP(application Subobject::issues regarding MAP_INBOUNDdata receive fromSOP)Release Job in Error status SM37 Defined by releasethe Background frequency for each message typeSAP for Retail Object: SLG1 Defined by releaseInbound WRF_MAPINB frequency(applicationissues)Table 7: Monitoring objects based on the Release Workbench within SAP BI2.1.6 Business Process Assortment Management BasicsThe objective of the business process Assortment Management Basics is to create and maintain layoutmodules and layout module versions.A layout module contains articles that will be presented together (products from one merchandise area, forexample). Layout module versions let you model the different designs of a layout module with the articles topresent over time. The maintenance of layout module versions consists of assigning articles and entering theplacement data for these articles. Articles can be assigned by criteria such as merchandise area (category orsubcategory, for example). Also an external space management program can be used to assign articles andmaintain the placement data.The process concludes by releasing the layout module versions. This is usually followed by the creation oflisting conditions and the transfer of specific articles to a purchasing list.More information regarding the business process Assortment Management Basics and Merchandise andAssortment Planning in general is available within the SAP Knowledge Warehouse under SAP for Retail:Business Scenario Descriptions Merchandise and Assortment Planning Assortment ManagementAssortment Management Basics.© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 31/46
  32. 32. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP) Assortment Planning and Assortment Management for Basic Merchandise (Integrated Scenario) SAP BI System Assortment Planning Basics Capacity Planning (optional) Store Segmentation (optional) External SOP System Assortment Definition SAP ERP for Retail Assortment Planning Basics Create planned article (optional) Assortment Management Basics Request for assortment version out of SOP (optional) Create assortment version Create and maintain layout (optional) modules and layout module versions Optimize planogram (assortment version) Assign articles Add article to assortment version Release optimized planogram tp Assign Stores Planning Release assortment version to SOP (optional) Release layout module versions Check optimized assortment version (optional) Release to merchandising system © SAP 2008 / Project RunSAP for Retail / 5Figure 19: Assortment Management Basics (SAP ERP for Retail)2.1.6.1 Monitoring requirements The Layout functionality of SAP ECC is usually used to implement this business process. For information regarding monitoring of Assortment Management Basics please see subchapter 2.2.3Monitoring for Assortment Management Basics within SAP ECC.2.1.6.2 Monitoring objects (optional: in SAP Solution Manager) Monitoring Selection Criteria Alert Analysis Tool on Monitoring Frequency/ Object Satellite System Data Collection Listing condition WSML, program Job in error SM37 Depending on the listing creation job frequency, usually daily. Listing condition Object: W Error codes SLG1 Depending on the listing creation frequency, usually daily. Subobject:: W_SORT_I1 Transaction: WSM4L Size of Data base tables Data base table Depending on the reorganization WRF_WRSZ_DEL, size frequency of the deletion tables WRF_WRS1_DEL, WRF_WLMV_DEL, WRF_ASGMT_DEL and WRF_MALG_DEL© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 32/46
  33. 33. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP) Monitoring Selection Criteria Alert Analysis Tool on Monitoring Frequency/ Object Satellite System Data Collection ABAP Dumps Relevant Occurrence of ST22 Daily transactions dumps Performance Depending on Performance As needed: Depending on project analysis tool, e.g. indicators requirements ST03N relevant determined by transactions project team STAD ST05 ST12Table 8: Monitoring Objects (optional: in SAP Solution Manager)2.1.6.3 How to find meaningful thresholds per monitoring objectDoes not apply to this process.2.1.7 Business Process Assortment Planning FashionThe objective of the business process Assortment Planning Fashion is to create assortments by strategicperspectives, assign them to stores in the BI system, and then release this information for operational use inSAP ECC. This business process considers the characteristics of fashion merchandise as the planningaspect is much more important for assortment creation than for other types of merchandise. Where fashionmerchandise is involved, assortment planning is much more dependent on creativity, the analysis of fashiontrends, and the ability to modify existing plans as quickly as possible. Therefore next to the strategic tasks(like defining assortments, planning of objectives) also operational tasks (e.g. determiningarticles/colors/sizes, planning of quantities, and determining prepack information) can take place withinAssortment Planning Fashion in SAP BI.The business process Assortment Planning Fashion ends with the release of the assortments, storeassignments and targets planned in SAP BI via the Release Workbench to SAP ECC. Within SAP ECC theassortment handling of fashion merchandise can be continued and supplemented with the business processAssortment Management Fashion.More information regarding the business process Assortment Planning Fashion and Merchandise andAssortment Planning in general is available within the SAP Knowledge Warehouse under SAP for Retail:Business Scenario Descriptions Merchandise and Assortment Planning Assortment PlanningAssortment Planning Fashion.© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 33/46
  34. 34. Best Practice for Solution OperationsManage Operations for SAP Merchandise and Assortment Planning (MAP) Assortment Planning and Assortment Management for Fashion Merchandise (Integrated Scenario) SAP BI System Assortment Planning Fashion Capacity Planning (optional) Store Segmentation (optional) Assortment Definition SAP ERP for Retail Target Planning Assortment Management Fashion Create Planned Article (optional) Add articles to purchase list Execute Quantity Planning (optional) Perform quantity planning Create Prepack Generation Perform detailed article planning Information (optional) Perform Prepack Planning Release to Merchandise System Release © SAP 2008 / Project RunSAP for Retail / 6Figure 20: Assortment Planning Fashion (SAP BI system)2.1.7.1 Monitoring requirements The planning functionality of Integrated Planning and the retail specific Master Data Planning (MDP) is usually used to implement this business process. Also the retail specific Release Workbench is used to implement this business process. For information regarding monitoring of IntegratedPlanning and Master Data Planning please see subchapter 2.2.1 Monitoring for retail planning within SAP BI.For information regarding the release of the planning data please see subchapter 2.2.2 Monitoring forRelease Workbench within SAP BI2.1.7.2 Monitoring objectsMonitoring objects based on Retail Planning within SAP BI are listed in the table below: Monitoring Selection Alert Analysis Tool on Monitoring Frequency/ Object Criteria Satellite System Data Collection Data extraction Datasources, Canceled process RSAx Defined by uploading from SAP for Process Chains , chains frequency Retail Cubes required for the planning process WebDynpro Used Runtime above On a regular basis in Performance Webdynpros SLA planning phase Query Selected queries Runtime above On a regular basis Perfomance used SLATable 9: Business Process Assortment Planning Fashion – Monitoring objects© 2009 SAP AG - BP_Retail_MO_for_MAP_V30.doc page 34/46

×