This action might not be possible to undo. Are you sure you want to continue?
Best Practice for Solution Management
Version Date: April 2004 This version is valid for SAP APO 3.0A , 3.1 and mySAP SCM 4.0 The newest version of this Best Practice can always be obtained through the SAP Solution Manager Contents Applicability, Goals, and Requirements ....................................................................................................2 Preliminary Information ......................................................................................................................3 Procedure ...........................................................................................................................................9 Business Process Step 1: Initialize Planning Version ..................................................................9 Business Process Step 2: Load Data.........................................................................................10 Business Process Step 3: Safety Stock Planning ......................................................................11 Business Process Step 4: SNP Heuristic Run ...........................................................................12 Business Process Step 4a: CTM Planning Run.........................................................................14 Business Process Step 5: SNP Optimizer Run..........................................................................19 Business Process Step 6: Capacity Leveling.............................................................................21 Business Process Step 7: SNP Interactive Planning .................................................................22 Business Process Step 8: Execute Batch Macros .....................................................................23 Business Process Step 9: Exchange Requirements with Supplier ............................................25 Business Process Step 10: Load Data into BW .........................................................................26 Business Process Step 11: Create/Update Planned Orders, Transfer Orders, and Purchase Requisitions................................................................................................................................28 Business Process Step 12: Release SNP to DP........................................................................29 Business Process Step 14: Deployment Heuristic .....................................................................30 Business Process Step 15: Deployment Optimizer....................................................................31 Business Process Step 16: Transport Load Builder (TLB).........................................................31 Business Process Step 17: Delete Transaction Data.................................................................32 Further Information .................................................................................................................................33
Best Practice: Manage Supply Network Planning & CTM in SAP APO (3.x) / mySAP SCM (4.0)
Applicability, Goals, and Requirements
To ensure that this Best Practice is the one you need, consider the following goals and requirements.
Goal of Using this Service
This Best Practice enables you to set up a business-process management and monitoring concept for the business process "Supply Network Planning" which is part of the mySAP Supply Chain Management (SCM) solution using the SAP Advanced Planning and Optimizing (APO). This business-process management and monitoring concept aims to: • • Define procedures for business-process oriented monitoring, error handling, and escalation management for Supply Network Planning Define the roles and responsibilities for all persons involved in the customers’ support and monitoring organization with respect to Supply Network Planning
These procedures ensure the smooth and reliable flow of the core business process in order to meet your business requirements.
You can get SAP experts to deliver this Best Practice on-site if you order a Solution Management Optimization (SMO) service, known as the SAP Business Process Management service.
Staff and Skills Requirements
To implement this Best Practice, you require the following teams: Application Management Team The SCM / APO business process management concept (which this Best Practice aims to produce) should be created by the Application Management Team. This team combines experts from your company:
Business department Solution support organization (for example, the IT department and the Help Desk) Implementation project team
Execution Teams The execution teams are the following groups, which taken together form the customer’s Solution Support Organization:
The Business Process Champion for each business process Application Support Development Support Program Scheduling Management Software Monitoring Team System Monitoring Team
More information about roles and responsibilities of these teams can be found in the superordinate Best Practice General Business Process Management, which you can obtain through the SAP Solution Manager.
© 2004 SAP AG
Best Practice: Manage Supply Network Planning & CTM in SAP APO (3.x) / mySAP SCM (4.0)
Duration and Timing
Duration Creating a business-process management concept may take around one week per business process. Implementing the business-process management concept may take around one additional week. Timing The best time to apply this Best Practice is during the planning phase or during the implementation phase of your mySAP solution.
How to Use this Best Practice
Firstly read the whole document to get an overview of its structure, contents, and details. Determine the APO SNP core business process to be monitored. If you use the APO Core Interface (CIF) within this process, you should also see the respective Manage APO Core Interface in mySAP SCM Best Practice. Record all the relevant steps in your core business process; use the example business process as a template. Exclude template process steps that you do not perform. For every process step, take the monitoring elements from the tables and insert them into your own template. Complete the information according to your specific requirements, for example, frequency and time of monitoring activity. If the process step includes CIF data transfer, add the information from the CIF document, section Operation and Monitoring of the APO CIF. Do not forget to include the respective information for interfaces other than CIF and for business process steps performed with your own (Y-, Z-) programs. Determine the related monitoring activities, tools, and responsible teams and fill in the table accordingly. For activities that are not directly related to a business process step, like those mentioned in section System Administration Related to the APO CIF in the CIF best practice, create a separate table. Proceed in the same way with all your other core business processes and other activities you want to monitor.
The SCM System Landscape
The substantial components of an SAP SCM system landscape are summarized in the following table and shown schematically in the subsequent illustration. SAP APO System The SAP Advanced Planning and Optimization system facilitates the strategic, tactical, and operational planning processes. APO consists of several software components: a relational database system (RDBMS) just as there is in any R/3 system, known as the APO DB; an SAP Web Application Server (or for releases up to APO 3.1 an R/3 Basis); the APO application programs; a separate, very fast objectoriented SAP DB database called liveCache; application programs running in liveCache – the COM routines; and a number of programs that execute elaborated optimization algorithms, called the optimization engines. These components can run on the same or on different servers. OLTP System The Online Transaction Processing system covers functionality for sales and distribution, material and inventory management, controlling, shop floor control, logistic execution, and so on. An Online Analysis Processing system, such as SAP Business Information Warehouse (BW), provides cumulated historical data as a basis for future extrapolation purposes in APO Demand Planning.
© 2004 SAP AG
Best Practice: Manage Supply Network Planning & CTM in SAP APO (3.x) / mySAP SCM (4.0)
SAP R/3 Plug-In RDBMS
SAP APO System
SAP R/3 Plug-In RDBMS
The various strategies for using SAP APO, SAP R/3, SAP Business Information Warehouse (BW), and possibly other data processing systems in combination are called integration scenarios. Data for planned independent demand can enter the Supply Network Planning (SNP) module either through the Demand Planning (DP) module, or from external systems. Since SNP can have some or all of its Key Figures in the time series liveCache, data can enter it in the same manner as they enter Demand Planning. Usually, an APO system is connected to one or several systems that provide historical and actual data, for example, sales figures, for your Supply Network Planning business process. These systems can be SAP R/3, SAP BW, and / or third party and legacy systems or a combination of these. As APO comprises a complete SAP BW, the tools for extracting data from other systems and transferring them to APO for demand planning purposes are the same as those used by SAP BW. The APO BW reads the data using remote function call (RFC) techniques, IDocs, or OS file access. In addition, data such as sales orders, stock, production orders or purchase orders can be sent from R/3 to SNP as order objects through the Core Interface Function (CIF), which is described in the corresponding Best Practice Manage APO Core Interface in mySAP SCM. On the other hand, the planning results of the supply network planning process are fed into other applications for further planning or execution purposes. The system types that can be used here are APO itself - in particular its modules DP and / or PP/DS -, SAP R/3, or again third party, or legacy, systems. The latter is not considered in this Best Practice document. This Best Practice is therefore based on a general and common integration scenario for setting up a mySAP Supply Chain Management solution using SAP APO. As data sources, SAP BW, SAP R/3, and flat files can be connected to the SAP APO system. SAP Advanced Planning and Optimization (APO) is the planning component of mySAP SCM, the Supply Chain Management solution provided by SAP. SAP APO is used to make strategic, tactical, and operational decisions and supports you in performing the following planning activities:
© 2004 SAP AG
Best Practice: Manage Supply Network Planning & CTM in SAP APO (3.x) / mySAP SCM (4.0) • • • • • • • • Demand Planning (DP) Supply Network Planning (SNP) Production Planning (PP) Detailed Scheduling (DS) Deployment Transport Load Builder (TLB) Transport Planning and Vehicle Scheduling (TP/VS) Global Available-to-Promise (gATP)
SAP APO is most of all a planning tool, although some industry specific execution functions are available, for example, production backflush for repetitive manufacturing. In standard business scenarios, execution functions, such as confirmations, goods receipt, purchasing, and so on are performed in the SAP R/3 OLTP system, which contains all functionality for, among many others, Material Management MM, Sales and Distribution SD, Production Order Processing PP-SFC, Logistics Execution LES, and Controlling CO.
© 2004 SAP AG
a planning area and planning version must be created and initialized. time series key figures. by CIF transfer from R/3. from where later a release to SNP can be done). or both. it is calculated by a macro during the heuristic or optimizer run. Before data can be loaded into Supply Network Planning. In other cases. The planning version can consist of order key figures.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. © 2004 SAP AG . After initialization.0) 6 Supply Network Planning The individual core business process and its modeling in SNP for planning your supply network. depending on which safety stock planning method used. may differ more or less from the canonical process described and illustrated as follows. or from a flat file using a BAPI (Data from BW can only come to SNP either via BAPI or by transferring it through the APO data mart into a DP planning area. Description: The process flow above describes a typical SNP process flow.x) / mySAP SCM (4. Many customers then execute a batch job to calculate safety stock: in some cases this is done separately from the main planning run using report /SAPAPO/MSDP_SB. data can be loaded into SNP in several ways: by releasing a forecast from Demand Planning.
Please consider the following overview part for better understanding. Of course your specific process might differ more or less from this canonical process: Description: The process flow is quite similar to the process flow of SNP above and therefore not described in detail again. After the run is complete. as is the case with traditional planning approaches. At some point in the planning flow. depending on the size of the problem and whether they can meet their needs with the infinite planning considered by the Heuristic. the constrained forecast calculated by SNP can be released back to DP. planners usually check the results in interactive planning. a detailed transport load is needed to consider transport load building constrains (min-max load) and to ensure that loading of the transportation resources for multiple products is feasible. the search is performed through the supply chain and the first possible way to fulfill the demand element is determined.either a heuristic or an optimizer based approach are available . and to implement fair share rules. some SNP customers use remote InfocCubes in a BW system for reporting on the SNP plan.can be used to plan transfers of single location-products from one location to another. and used in evaluating the feasibility of a forecast. while taking the current production capacities and transport capabilities into consideration. it uses algorithms similar to the SNP heuristic or optimizer. Of course one has to keep in mind that CTM can also be used with PP/DS orders and PP/DS PPMs. After the PP/DS run occurs. the deployment algorithms . not production resource-centric. Although deployment is a short-term planning. 7 Often customers perform a variety of tasks via batch macros: these can be used to generate alerts and perform further calculations on the data either before or after the planning run. where a more deta iled.0) Most customers then run either the SNP Optimizer or the SNP Heuristic. single-location planning is performed. Capable to Match If you are using CTM as a planning tool within your Supply Network Planning network – please also consult the above picture and paragraph – there are usually some differences to the SNP standard process. Many SNP process flows then exchange requirements with suppliers – often using collaborative planning. Still another use for the SNP data is to transfer it to PP/DS.x) / mySAP SCM (4. The numbering of the process is oriented on the SNP process to make finding of relating chapters in this document easier. but considers all possible paths through the distribution and production levels together. many customers also use this report to clean the order objects from the planning version used for SNP Planning after the results of the planning run have been sent to their respective destinations. In some cases. that in interactive planning transaction /SAPAPO/RRP3 is used more often than /SAPAPO/SNP94. For this purpose we provide here also a typical business process involving CTM. SDM's approach is production flow-centric.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. If the SNP Heuristic has been run. Overview: Multilevel Supply and Demand Matching (SDM) is the umbrella for the SAP APO solution for matching prioritized customer demands and forecasts to a set of supplies.g. possibly using alerts. © 2004 SAP AG . The SNP planning results can also be sent to R/3 using the CIF interface. For each demand element. SDM does not consider the individual distribution and production levels of the supply chain one after the other. Some comment is also needed about the use of /SAPAPO/RLCDELETE: since SNP alone is not an execution system. In other cases. Capacity Leveling is often performed on bottleneck resources to ensure that a feasible plan is created. This than implies differences in the processes e. where the planned orders and purchase requisitions produced by SNP planning are then further processed using MRP. so it is classed within SNP.
transport options and existing supplies into consideration. as well as a tool that provides a graphical. It uses constraint-based heuristics to conduct cross-plant checks of production capacities and transportation capabilities based on predefined supply categories and demand priorities. there are also customers using CTM in the PP/DS environment. distribution. existing supplies are cleared when matching them with demands. complements this application. SDM complements the cross-plant supply chain planning strategies of the SAP APO applications Supply Network Planning (SNP) and Production Planning and Detailed Scheduling (PP/DS). Therefore it is also necessary to read especially the SNP Feasibility Check Assessment Guide for understanding the entire business process. please also refer to the Best Practice document Manage Production Planning in SCM / APO. manufacturing. Supply Chain Planning Creating feasible plans for purchasing. CTM then matches the supplies and demands on a first come. At the same time. The CTM engine runs on an extra optimizer server. and transportation planning for the midterm Making sourcing decisions through the Supply Network Categorizing supply to meet prioritized demands Synchronizing activities and plan material flow throughout the supply chain Capable-to-Match (CTM) planning is the planning tool of SDM. flow-oriented view of the supply chain.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. which must be based on Windows NT/2000/XP. first served basis while taking the production capacities.x) / mySAP SCM (4.0) 8 Multilevel Supply and Demand Matching (SDM) is the umbrella for the SAP APO solution for matching prioritized customer demands and forecasts to a set of supplies. In addition. Because SDM is order-based. However. For such cases. an order-based method of Supply Distribution. The business area Multilevel Supply and Demand Matching – similarly to SNP – covers the following activities. while taking the current production capacities and transport capabilities into consideration. This will connect to an APO application server using Remote Function Calls (RFC). During installation or after configuration changes. The aim of the CTM planning run is to propose a feasible solution for fulfilling demands. Customers often use CTM as an alternative to the SNP heuristic or SNP optimizer. triggering flow only when necessary. make sure that the connection to the optimizer server maintained in SM59 still works correctly. SDM aims at a medium to long-term planning horizon and guarantees a timely multilevel synchronous production flow. Capable-to-Match (CTM) is the central planning tool of SDM. manufacturing. distribution and transportation Integrating purchasing. © 2004 SAP AG . CTM first prioritizes the demands then schedules them one after the other in the prioritization sequence. it requires a tool that also supports a multilevel dynamic order split.
the monitoring frequency can be decreased. the monitoring frequency in these monitoring object tables is partly only a rough estimate and has to be adapted to your particular business process. For planning versions with significant amounts of master data.0) 9 Procedure In applying this Best Practice procedure. Restartability and Escalation. Right click on the planning area. error occurrences. Important planning jobs usually have to be monitored after each run. or whether some or all key figures are time series key figures. you create a company-specific process-oriented monitoring concept. you must specify the times. After becoming more experienced with system behavior. and escalation paths (teams) for the monitoring activities associated with each business-process step and its monitoring objects. initializing the planning area is straightforward: execute transaction /SAPAPO/MSDP_ADMIN and find the planning area of interest. you need to take measures to ensure that this is done manually in a reliable and timely manner. For example. restartability. daily jobs can be checked weekly. the jobs for deleting outdated jobs or spool objects. For status “cancelled”. select the “execute in © 2004 SAP AG . showing the: o Monitoring object o Monitoring transaction or tool o Monitoring frequency o Monitoring time (intentionally left blank. Business Process Step 1: Initialize Planning Version Before a new planning version can be used in SNP. The following seems obvious but should nevertheless be mentioned: Besides the monitoring of jobs described in the business process steps below. and execute. You should investigate and correct these terminations appropriately. During the Going Live and stabilization phase of your APO implementation project. listing each relevant monitoring object. and application operations. When adapting this concept for your company.x) / mySAP SCM (4. to be filled in according to your schedule) o Indicator or error o Monitoring activity or error handling procedure o Responsible team o Escalation procedure As the frequency of SNP planning processes varies from daily activities at certain companies to only monthly or quarterly at others. In each of the business process steps described below. For order objects only. the standard 9ASNP02 is used for order objects. for example. If you have no automatic notification in place that informs the people responsible for Program Scheduling Management in your Support Organization of abnormally terminated jobs. choose “initialize planning version”. This concept consists of monitoring activities to be performed for each business-process step and its respective monitoring objects. This check can be done easily. How the planning area is initialized depends on whether it contains only order objects. the planning version must be initialized for an SNP planning area. Regular jobs of minor priority. but should never be reduced to zero unless you do not use the respective function. can be checked less frequently than the actual scheduled run times. see Error Handling.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. for instance. responsible teams. certain clean-up jobs. and escalation A monitoring object table. Type in the name of the planning version. see SAP Note 16083. For details and comments. all items listed in this document should be monitored tightly. with transaction SM37 by entering the time interval since the latest check and selecting all jobs with status “cancelled”. A number of jobs must run periodically in a live R/3 installation. you will find the following information: • • • • A detailed functional description of the process step Monitoring activities for the process step Error handling. it is essential that you check all jobs that are running in your system at least several times per day for abnormal terminations. in most cases. for example.
the data must be initialized for SNP planning. The difference between the two reports is simply that /SAPAPO/TS_LCM_CONS_CHECK_ALL runs the report in display mode for all TS planning objects. When the planning area does not contain any time series key figures. Transactional data is usually loaded into SNP by a release from Demand Planning to SNP. monitor the messages in the job log to ensure that no errors occurred See general issues of Error Handling. you should perform a model consistency check using transaction /SAPAPO/CONSCHK: in many cases it is preferable to use this transaction to launch a batch job and check the output in SM37 afterwards. it is preferable to use the option “Execute in Background”. For large data volumes. After loading new master data.0) 10 background” option. Monitoring Activities Jobs for Running and Monitoring "Initialize Planning Version" (APO) If the planning area used for SNP contains time series key figures.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. The profile used should be restricted to the functionality and data which you are actually using. product. which is described in the Best Practice Manage Demand Planning in mySAP SCM / SAP APO. resource. simply enter transaction /SAPAPO/MSDP_ADMIN. When the planning area contains time series key figures. Then enter the existing planning version and the new start and end dates for the time series that are desired. and choose “Create Time Series”. Business Process Step 2: Load Data Depending upon your business process. If new master data are loaded into a model. by running report /SAPAPO/TS_PAREA_INITIALIZE. © 2004 SAP AG . PPM and transportation lane which are assigned to the model as the characteristic combinations. you should periodically check for inconsistent time series objects using report /SAPAPO/TS_LCM_CONS_CHECK_ALL or /SAPAPO/TS_LCM_CONS_CHECK. while /SAPAPO/TS_LCM_CONS_CHECK has a parameter screen that allows the user to choose a planning area and to decide whether to correct the inconsistencies. When you need to change the validity period on a planning area with time series objects. this has to be done by reinitializing the SNP planning area in /SAPAPO/MSDP_ADMIN or alternatively. Report /SAPAP O/TS_L CM_CO NS_CH ECK SM37 As often as you change master data Depending on business process Depending on business process Monit or Time Indicator or Error Status Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure Contact application support Run the job periodically to Program ensure that processes such scheduling as delta initialization of the management planning area have not created extraneous objects in the liveCache Ensure that job completes successfully Program scheduling management Application support Initialize planning version Initialize planning version Status Contact application support Contact process champion SM37 Status/mes sages Whether or not the job completes successfully. Restartability and Escalation below. it may be that you periodically load either only transactional data or both master data changes and transactional data into SNP. SAP Note 358283 gives a description of the report. Master data changes cover the master data objects like location.x) / mySAP SCM (4. Monitoring Object Initialize planning version Monitor Monitor TA/Tool Freq. General information on handling problems with version management is available in SAP Note 519014. both so that the program will not time out and so that the monitoring tools of SM37 are available. this can either be done by reinitializing the SNP planning area or automatically by starting SNP interactive planning or SNP mass processing. right click on the planning area.
All CIF data interchanges should also be monitored as described in the Manage APO Core Interface in mySAP SCM. Spare parts is a business area that usually does not meet this assumption. In the remainder of this section. SAP BW. Check log of consistency check Application support team Master Data Messages See general issues ofError Handling. Monitoring Activities Apart from safeguarding the general availability and consistency of the system components SAP APO. However. the demand quantities are significantly greater than zero and do not fluctuate too much between planning periods. BS).0) 11 Additionally. MZ. BT. no demand gets lost (backorder case).e. see note 504253 for an introduction. The consistency check should also be executed if the master data are changed in APO but not visible or accessible via SNP. Monitoring Object Master data Monitor Monitor Monitor Indicator TA/Tool Freq. Restartability and Escalation below. All uncertainties in the supply chain are statistically independent of each other. The advanced safety stock methods used in SNP are based on the following assumptions (see also note 617567): Demand is regular. and MM) and advanced methods (AT. MB. to safeguard this business step SAP recommends that you monitor the objects listed in the following table. Advanced methods are performed in report /SAPAPO/RSDP_CALC_SAFETY_STOCK (transaction: /SAPAPO/MSDP_SB). Ensure that only delta records are loaded by the BAPI. rush shipments (no delay approach). To do this. In case of shortage. In extreme cases. i. in addition to functions for adding and deleting the functions. Standard methods are performed in macro SAFETY_CALC. master data changes are sent by CIF from R/3 to SNP.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. Usually. Business Process Step 3: Safety Stock Planning There are two types of safety stock methods in SNP: standard methods (SB. For additional information see SAP Note 577038. there is demand in almost every planning period. © 2004 SAP AG . i. the missing parts can always be delivered belatedly. If this is the case. the consistency check report can be used in repair mode. for example. and SAP R/3 OLTP. execute report /SAPAPO/MCPSH_GEN_SELTAB_MGM. Please be aware that the safety stock values calculated may differ significantly from the correct ones if one or more of these assumptions are violated. the remainder is made available using alternative arrangements. Some customers also load data using a BAPI. only advanced methods are considered. If large amounts of data are loaded by BAPI. please read Note 332812 carefully before using this report to automatically correct inconsistencies. SM. it is possible that tables /SAPAPO/TSQ* can become very large and cause performance problems. There exists a consistency check for selections.. and reinitialize the planning area using report /SAPAPO/TS_PAREA_INITIALIZE to prevent this problem. Time or Error /SAPAP When O/CON data are SCHK modified /SAPAP When O/CON data are SSHOW modified Messages Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure Contact process champion Contact process champion Check log of consistency Application check for master data objects support team that display inconsistencies. you need to regularly check and update the selection data tables for the Planning Area(s) used for SNP.. the methods will not calculate any reasonable values.e. AS. If neither regular stock nor safety stock suffice to cover the whole demand. SZ.x) / mySAP SCM (4.
9ASVTTY). When checking the spool file. In Release SCM 4. • APO Report SM37 /SAPAPO/RS DP_CALC_SA FETY_STOCK See general issues of Error Handling. The 9ASNP_SSP folder supports all methods of the safety stock planning in SNP (SB. which contains two specific time series key figures for safety stock planning (9ASAFETY. If you need to improve performance. a cycle is a sequence of PPMs and/or transportation lanes that transform a location product on to its self. you can execute parallel processing by creating separate variants for transaction /SAPAPO/MSDP_SB and run them at the same time. it is advisable not to make changes to the SNP planning version in which safety stock is run.x) / mySAP SCM (4. to avoid lock issues. Safety stock calculations for different location products are independent of each other. Business Process Step 4: SNP Heuristic Run In Release SAP APO 3. for example) only support the methods SB. AT. BS. Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. but a full BOM explosion takes place). schedule the following jobs to run on a regular basis: Calculate safety stocks with advanced methods with report /SAPAPO/RSDP_CALC_SAFETY_STOCK. MB. SM.0. In general. Therefore. AS. SZ and SM for safety stock planning. also look for large values in the field Delay(sec). Responsibility Program scheduling management Escalation Procedure Contact application support team. Please consult SAP Note 646738 for details.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. If such cycles exist Safety Stock Planning will be caught in an endless loop unless note 547049 has been applied. a new 9ASNP_SSP SNP standard planning book exists for the safety stock planning. For such location products no safety stock can be planned since there is no way to procure it.0 Support Package 08.0) 12 Also make sure that the supply chain does not contain "cycles" for the location products to be planned. the results of extended safety stock planning can no longer be saved in auxiliary key figures.x the SNP heuristic performs infinite planning for the supply chain. Most commonly. When checking the job in SM37.0 the handling of heuristic has been enhanced (not for interactive planning). Look for large values of Delay (sec) in SM37. BT). Be aware that with release SCM 4. As of Release SCM 4. SZ. but BOM is only exploded to one level) or Location (all products at one location. which should be corrected by the application support team./snp01 the following changes have been made: © 2004 SAP AG . reorder cycle or reorder point). In this context. the error is caused by a location product with procurement type E (in-house production) for which there is no valid PPM. Monitoring Activities The monitoring activities needed to ensure that safety stock planning runs are executed correctly are indicated in the table below. For transaction /. MZ.. MM. which might indicate that the job had to wait for another process to release locked data. Restartability and Escalation below. Time or Error Each time the report is run Monitoring Activity or Error Handling Procedure Check spool file for errors. It can be run in one of three modes: Multilevel (all products at all locations). Network (all locations. in addition to looking for jobs which cancelled. but in time series key figures only. the previous SNP standard planning folders (9ASNP94. Jobs for Running and Monitoring "Safety Stock Planning" To ensure consistency and good performance of safety stock calculations. look especially for messages in the form of: "Product &1 in location &2 cannot be procured. the order of calculations is arbitrary. In addition.” This indicates an error in the procurement type for the location product. This report calculates the safety stock associated with reorder point methods (either alpha or beta service level. Please also consider notes 599871 and 600766. and make a note of which other processes were running concurrently.
Net change planning is only available in the active version (000). which can cause inconsistencies if not corrected. Also check the column “Delay(sec). Spool file of report /SAPAPO/RS NPDRP1 SM37 As often as heuristic is executed As often as heuristic is executed Log file Check whether the spool file has any error messages. Monitoring Activities Regarding SM37: when several heuristics identify large values of “Delay(sec)”.large values may indicate that another process was locking the job. the inbound or outbound queues in the R/3 system should be locked during the time of the heuristic run: • If you cannot rule out that. transaction data is transferred from SAP R/3 to SAP APO that is ignored by the heuristic. o For this the report /sapapo/rsnpllcset has to be performed to determine the low-levelcode of all products of a version. If the heuristic run is executed in Version 000. Application Support Contact process champion Responsibility Program scheduling management Escalation Procedure Contact application support Application log Slg1 of report /SAPAPO/RS NPDRP1 Log file Application Support Contact process champion © 2004 SAP AG .g. you can use the /SAPAPO/CIFSTOPQUEUES and /SAPAPO/CIFSTARTQUEUES reports in SAP APO. If the report is not scheduled as provided by Application Support. Reports RSTRFCI1 and RSTRFCI3 are available for locking inbound queues. Monitor Monitor TA/Tool Freq. you can lock inbound or outbound queues in the SAP R/3 system from the SAP APO system. See also SAP note 487261 / 528913. this problem can be alleviated by running report RSVCHECK after implementation of a new support package. This should be done on a regular base but has to be done after relevant master data changes (e. during the heuristic run. To lock outbound queues. This should prevent inconsistencies occurring in the planning if. • Occasionally. with the import of a support package. and it waited for the other process to finish. data will be transferred from an SAP R/3 system to the SAP APO system (or from APO to R/3) over the core interface (CIF).0) • • The heuristic can be executed in two modes. locks on the APO database can be seen with transaction SM12. The entries of objects flagged for net change planning can be viewed from transaction /SAPAPO/RRP_NETCH. many orders.g transportation lanes or PPM’s) Use of the Net Change planning flag is not recommended. SM37 Depends on business process Monit or Time Indicator or Error Status Monitoring Activity or Error Handling Procedure Check if job is running as scheduled. schedule it accordingly. Monitoring Object APO report /SAPAPO/RS NPDRP1 This report performs the SNP heuristic run. during the heuristic run. 13 In addition to both modes you can set a flag to perform a full BOM explosion. it is recommended that you investigate the possibility that another process (or several parallel jobs) are locking one another. unless the number of location products is high and the number of changing demands is comparatively small. each with a quantity of 1 for the same locationproduct on the same date) Check whether the spool file has any error messages. Fortunately. While the processes are running. or strange results (e.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. This enables to plan a part of the network but on all levels.x) / mySAP SCM (4. Network (selected products in all locations) or Location (selected products in selected locations). the length of data fields in report variants can change.
all the activities of a PPM need to be planned by CTM. Responsibility Program scheduling management Escalation Procedure Contact process champion Report variants RSVCH ECK List of variants with problems Check if any variants have problems Program scheduling management Contact application support See general issues of Error Handling.0) 14 Monitoring Object SCM report /sapapo/rsnpll cset Monitor Monitor TA/Tool Freq. because . Business Process Step 4a: CTM Planning Run Critical steps in CTM The three critical areas for performance during CTM run are • • • loading and preprocessing of data runtime of the CTM engine writing of the results to liveCache In case of performance problems it is crucial to determine which of the areas are critical -> Please see the section Monitoring Activities for details. .many orders are being selected.x) / mySAP SCM (4. They are not allowed for SNP. resources. Restartability and Escalation below.Verify whether. PPMs. or after importing new support packages Monit or Time Indicator or Error Status Monitoring Activity or Error Handling Procedure Look for error messages like cycles. Possible solutions: .Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. transports) is slow.deletion of orders is taking too long . .pegging is being analysed.Reduce the planning horizon considered. for example. b) Reading further data (products. .Verify whether all the selected location-products really need to be planned for. © 2004 SAP AG . .Filter demands and supplies considered by date.Filter master data by using only objects that are planned actively (by CTM).Optimize the parameter package size for orders selection in /n/SAPAPO/CTMCUST. . Sm37 On a regular base but after relevant master data changes Once a month. – for example try to consider planning runs with a shorter horizon during the week and with a long horizon on weekends. The most common reasons for poor performance are: 1) Slow reading and preprocessing of data: a) Order selection is slow. Possible solutions: .
writing is carried out in parallel to planning. and entries are read to be handed on to the CTM engine. . The table entries are automatically deleted if the planning version is deleted or the CTM profile is deleted. These database tables can grow with every new CTM profile. For more information about this setting refer to note 533457. (In APO 3. This means that the system will certainly delete the order.Reduce horizons for late and early demand fulfillment as much as possible. The best way to improve performance here is to use the setting “Do Not Apply Rules”. If these tables contain many entries they can be deleted by using program /SAPAPO/CTM_DEMSUP_DELETE. 3) Writing to liveCache is slow: Possible solutions: .Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. . If this functionality is used in combination with a master data selection. In cases where liveCache time and engine runtime are • • © 2004 SAP AG .10 this setting must still be carried out via the planning parameter “FAST_DEL”.The time for prioritization is dependent on the amount of selected orders. Also only use this indicator with planning mode Replan all Orders and deletion mode Delete all Non-Firm Orders. all orders which contain at least one location product of the master data selection will be deleted.0A and 3.x) / mySAP SCM (4. the demands and supplies are stored in the database tables /SAPAPO/CTMDEM. With release SCM4. if rules are necessary. This means that after the CTM engine has finished. If all orders lie within the planning horizon. a primary goal should be to only select the orders necessary for the CTM run. Therefore. and new planning version in a CTM profile. Important additional performance settings Some specific performance relevant settings and referral notes are briefly discussed in the following paragraphs: • Set the indicator “Do not Evaluate Pegging Relationships” in the technical settings of the CTM profile. If you do not require these checks. /SAPAPO/CTMMAP. During the demand prioritisation and supply categorisation. If there are many entries in the database tables. checks are not required as the result of the order selection is the same with or without the checks.Optimize package size for creating orders. the system starts writing the whole result to liveCache. 2) CTM engine is slow: Possible solutions: . . Note that this indicator must not be used in connection with subcontracting. . entries are created.The time for prioritization of demands also includes the rule determination and evaluation. try to use “Apply Default Rule” instead of “Apply Rules!” and evaluate whether the planning parameter “DEFAULT_RULE” is applicable (see SAP Note 441723). See also note 375174 for further details. /SAPAPO/CTMSUP. as the system must evaluate pegging relationships for deleting subcontracting orders.Optimize package size for creating pegging relationships.Optimize package size for asynchronous liveCache update. whether a pegging relationship exists between an order and a demand that lies outside the planning horizon. . the result is written to liveCache while the CTM engine continues planning.Use asynchronous liveCache update. . However.Use Aggregation.1 it is possible to decide (customizing setting) if these tables should be updated for a CTM planning run or if the data is to be directly transferred. in order to delete all non-firm orders without any further checks. version entries for demands and supplies are deleted from the database tables. During a CTM planning run for the current CTM profile and planning. When changed to asynchronous update. the delete/read/write accesses can be time consuming. for example. Asynchronous liveCache update: The default setting of the CTM engine is synchronous liveCache update. you can set the indicator to shorten the runtime of the order selection.0) 15 c) Slow prioritization of demands Possible solutions: .) The system then does not check.Filter demands by order category and date. After finishing a certain planning package (a planning package is finished after a specified number of demands were planned by CTM).
• The runtimes of “order selection” and “writing to liveCache” also strongly vary according to the chosen package sizes.start time of selecting orders. from here the times and the warning messages should be regularly analyzed after CTM runs. For this information to be recorded you need to have the “Save CTM messages”-Box on the “Settings”-tab in the CTM profile activated. The setting for the package size for asynchronous liveCache Update considers the existing requirements and creates orders for them. PP/DS orders) existing per location-product. • Please note that using CTM in parallel is not usual and often not practicable. Therefore the parameter does not imply that the package includes 500 orders./SAPAPO/OPT11. The possibility exists that several orders may have been created per requirement or just one.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. Before using CTM in parallel it is crucial to verify that the two (or more) subproblems to be run in parallel are truly and completely independent / non-overlapping! Refer to SAP Note 430688 for more information.2 (each fifth loc-prod. The relevant parameters are maintained in /SAPAPO/CTMCUST. this setting strongly depends on the orders (including fixed orders. then select the appropriate CTM run and click and press on the “Log”-icon. One can then look into the CTM Application log and find the number of orders transferred per package depending on the most relevant categories: a. the result is 50000 orders per package As you can see. If the average amount of orders per location-product combination is a. has on average 10 orders). Monitoring Activities CTM run Monitoring the CTM run includes understanding how long each of those three steps takes approximately to see where possible problems may be situated. If. © 2004 SAP AG . substitution orders The amount of orders per package coming from these categories together should result in at least 5000 orders per package to have optimal performance./SAPAPO/CTM -> result analysis -> display logs and choose the appropriate log from the list. CTM reads the orders for the first 5000 locationproducts in one package from liveCache. has an order).x) / mySAP SCM (4. Therefore it is important to try different settings to clarify performance issues.0) 16 approximately the same this setting can save up to 50% of the time. It means that 500 requirements are considered and the respective orders are sent in one package. or . 0. As a guideline SAP expects values of 10000-50000 orders per package for optimal performance 2. The PackageSize parameter determines here the number of requirements considered before sending the resulting orders to liveCache. 10 (each loc-prod. if this is the current setting. transport orders d. It is only necessary to change this parameter if the CTM engine is waiting for liveCache (the queue for packages to be transferred to liveCache increases as liveCache is not dealing with the necessary updates fast enough). Please consider the following for optimal settings of these parameters: 1. The setting for Order Selection is based on location-products rather than on number orders. for example. which results in a brief application log being written. purchase requisitions c. as those steps will then run in parallel. the result is 1000 orders per package b. However the package size parameter for asynchronous liveCache updates can also be maintained via the variable planning parameter “PackageSize” for each CTM profile. To find the information written in the log go to . planned orders / production orders b. the parameter is set to 5000. 1) Estimates for loading data and preproccesing: end time of reading transports .
This time estimate is more exact. look at the CTM trace file. Determining times here works accordingly. but NEVER concurrently with any optimizer or CTM runs.): end time of entry for CTM Planning run in SM37->Job log . In case of doubt about the runtime estimate for the CTM engine. there are two options to delete locks which prevent a new start of the CTM engine: 1) Delete the CTM engine run manually in transaction /SAPAPO/OPT03 before another run can be started. Enter the planning profile via /SAPAPO/CTM. This will automatically delete the lock table entries 2. e. refer to the monitoring jobs in the table below. 1.end time of reading transports. which should be run once a day. In general it is always good to take the newest available CTM engine. b. Jobs and Tools for Running and Monitoring "CTM Planning Run" To safeguard the functionality of the CTM planning run. Locks are also deleted by the job /SAPAPO/OM_REORG_DAILY.g. 2) Enter the planning profile via /SAPAPO/CTM. For an additional list of transactions used to set up the engine during installation or changes to the optimizer server. 3) A rough estimate for writing data to liveCache: Sum of the differences between End and Start times of each package to be written to liveCache. but also more time consuming. if writing is so slow that the CTM engine stops.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. but NEVER concurrently with any optimizer or CTM runs. 4) A second CTM run will occur after the end of the first one if there is safety stock being built up.0) 17 2) A rough estimate for CTM engine runtime (This might be wrong with asynchronous liveCache update. Lists of users and processes running on the optimizer server can be seen from transactions /SAPAPO/OPT03 and /SAPAPO/OPT12 respectively.x) / mySAP SCM (4. See Note 393634 for details. To run CTM in the background. refer to the section Monitoring APO Optimizers in the Best Practice: Monitoring and Administration for SCM/APO. To verify that the optimizer server is running correctly during the run: a. Also note that you should upgrade your CTM engine in parallel with support package upgrades to ensure optimal functionality and performance. Please see SAP Note 528913 for a full discussion. They are also deleted by the job /SAPAPO/OM_REORG_DAILY. © 2004 SAP AG . With these transactions you can check whether processes are still active on the optimizer server. Deleting locks after short dump during CTM run In the event of a short dump during the CTM run. use the CTM report /SAPAPO/CTMPLRUN. in case of hardware or operating system problems on the optimizer server. See Note 393634 for details. and consider the time stamps for “Engine Start” and “Engine Finished”. Note that this does not apply if the CTM run is executed on an inactive planning version. There are two options for deleting locks which prevent a new start of the CTM run in the event of a short dump during the CTM run: a. which should be run once a day. CIF Queues In addition to those steps please note that the CIF Queues should be locked during the execution of the planning run to prevent inconsistencies. Delete the run manually in transaction /SAPAPO/OPT03 before another run can be started. These transactions are usually only used for problem analysis beyond the CTM engine.
Indicato Monitoring Activity or r Error Handling or Error Procedure Check if job is running as scheduled. Responsibility Escalation Procedure Dependi Status ng on your process. too. Program Contact scheduling application managemen support t /SAPAPO/ After CTM -> every result run analysis -> display logs or /SAPAPO/ CTMAPLO G SM37 After every run Messag Review messages in log Application e Type with stop. If the report is not scheduled as provided by software monitoring team. this job will delete database entries and files on the optimizer server which are no longer needed. schedule it accordingly.x) / mySAP SCM (4.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. file Check for errors and time stamps Display and analyze logs in this section. if there is no result delivered from the optimizer. schedule it accordingly. red or yellow support indicator Contact process champion Spool file Messag Check for application es in errors after the CTM spool run. Program scheduling managemen t Contact software monitoring team support After master data changes Check This job will identify any Application for inconsistent data prior to support inconsis running the CTM run tencies Contact process champion © 2004 SAP AG . Master Data consistency check /SAPAPO/ CTM -> Edit -> Check your data Check if job is running as scheduled. If the report is not scheduled as provided by Application Support.0) 18 Monitoring Object APO report CTM: /SAPAPO/C TMPLRUN This report runs the CTM in the background CTM application log Monitor TA/Tool SM37 Monitor Freq. Application support Contact Process Champion Optimizer Logs /SAPAPO/ OPT11 In case of cancella tion of engine or for perform ance analysis Daily Application support Contact Process Champion /SAPAPO/O SM37 M_REORG_ DAILY Among its other activities.
in addition.0) 19 Monitoring Object User list for Optimizers Running optimizer processes Monitor TA/Tool /SAPAPO/ OPT03 /SAPAPO/ OPT12 Monitor Freq. be sure to set the parameter enque/delay_max in transaction RZ11 as described in consulting note 572996 to avoid lock problems. and the optimizer logs in /SAPAPO/SNPOPLOG and /SAPAPO/OPT11.0A.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. Please see SAP Note 528913 for a full discussion. In the event of a short dump during the optimizer run. • © 2004 SAP AG . Also ensure that you have applied Note 572220 (APO 3. See above See above Indicato Monitoring Activity or r Error Handling or Error Procedure Displays a user list of optimization runs Displays a list of optimizer processes on the optimization server Responsibility Software monitoring team Software monitoring team Escalation Procedure Contact application support Contact application support See general issues of Error Handling. the optimizer run must be manually deleted in transaction /SAPAPO/OPT03 before another run can be started. refer to the section Monitoring APO Optimizers in the Best Practice: Monitoring and Administration for SCM/APO. Monitoring Activities The following table describes how to monitor and ensure the correct functionality of the optimizer run. It will spawn parallel processes during some portions of the data read and model creation of the optimization run. and the resulting costs from the optimization run /SAPAPO/SNP106 to verify that the run was executed without problems. see note 454433. After the planning run is finished: use transactions sm37. but NEVER concurrently with optimizer runs. APO 3. SP23. Business Process Step 5: SNP Optimizer Run The CIF Queues should be locked during the execution of the planning run to prevent inconsistencies. Due to the runtime and memory requirements of the optimization engine. They are also deleted by the job /SAPAPO/OM_REORG_DAILY. Jobs for Running and Monitoring "SNP Optimizer" and “Deployment Optimizer” (APO) To safeguard the continued functionality of the optimizer. refer to the monitoring jobs in the table below. If several optimization runs are carried out in parallel. It is recommended that these be checked periodically to ensure that everything is functioning as expected. refer to note 587407. • • To run the optimizer in the background: use for SNP report /SAPAPO/RMSNPOPT and Deployment report /SAPAPO/RMDPLOPT.x) / mySAP SCM (4. they should never have the same names. To verify that the optimizer is running correctly during the run: Lists of users and processes running on the optimizer server can be seen from transactions /SAPAPO/OPT03 and /SAPAPO/OPT12 respectively. Note that a single optimization-based planning run can use only one CPU on the optimizer server. Care should be taken that the number of processes does not exceed the number of available batch processes for this user on the system. See Note 393634 for details. Restartability and Escalation below. For an additional list of transactions used to help set up the optimizer during installation or changes to the optimizer server. simply set the field “Number of Processes” in the background transactions for the optimizers. To get an overview of the optimization system steps. In addition. Also note that you should upgrade your optimizer in parallel with support package upgrades to ensure optimal functionality and performance. Note that this does not apply if the optimizer is executed on an inactive planning version. if you ever run two optimizer runs simultaneously. which should be run once a day. refer to note 485018. For an optimal performance of the optimization engine. we must also think about the model size and complexity.1A SP13) to prevent loss of optimizer result logs. and that the results are as expected. To improve the performance of an optimization run.
0) 20 Monitoring Object APO report SNP: /SAPAPO/RM SNPOPT Deployment: /SAPAPO/RM DPLOPT This report runs the optimizer in the background Optimizer log Monitor Monitor TA/Tool Freq. monitoring team Application support Contact Process Champion Contact Process Champion Spool file of optimizer run SNP Optimizer Resulting Costs. if there is no result delivered from the optimizer. Program this job will delete database scheduling entries and files on the management optimizer server which are no longer needed. If the report is not scheduled as provided by Application Support.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. Among its other activities. Responsibility Program scheduling management Escalation Procedure Contact application support /SAPAP O/SNP OPLOG SM59 After every run During installatio n or after config changes After every run Status Review messages in log with red or yellow status Check that the TCP/IP connection to the optimizer server is open and functioning correctly.x) / mySAP SCM (4. Also check for application errors after the optimizer run. © 2004 SAP AG . whether the support optimizer run has decided not to produce anything. Monitor Time Indicator or Error Status Monitoring Activity or Error Handling Procedure Check if job is running as scheduled. This job will identify any inconsistent data prior to running the optimizer run Application support /SAPAPO/OM /SAPAP _REORG_DAI O/OM_ LY REORG _DAILY Consistency check /SAPAP O/CON SCHK Contact software monitoring team Contact process champion Optimizer Logs /SAPAP As O/OPT1 required 1 Check for errors Display and analyze logs in this section. also for Deployment SM37 Messages in spool file Results summary of the SNP Optimizer Transac After tion every run /SAPAP O/SNP1 06 During installatio n or after config changes After each change to master data Check for reasonability of the Application results: e. Restartability and Escalation below. schedule it accordingly. System and application monitoring teams Depending on error type: system or application monitoring team User list for Optimizers Running optimizer processes /SAPAP As O/OPT0 required 3 /SAPAP As O/OPT1 required 2 Displays a user list of optimization runs Displays a list of optimizer processes on the optimization server Basis support Contact application team Basis support Contact application team See general issues of Error Handling. SM37 Dependi ng on your process.. Application support Contact process champion Verify and maintain RFC connections Status Program Contact scheduling software management.g.
Due to the improvements made in Capacity Leveling regarding result quality.0) 21 Business Process Step 6: Capacity Leveling The SNP heuristic performs only infinite planning: that is. Among other features. For performance. consider the recommendations in Note 493258. performance. In addition. without considering the available capacities of resources.0. can be found in release note 564702. Further information on the new version. the new version offers three different leveling methods . Ensure that job is scheduled and runs without error. • Capacity Leveling: execute transaction /SAPAPO/SNP94 and change to data view SNP94(2). Capacity Leveling in Background (new version only): in addition to launching the job. Run directly executable macros to measure capacity under load and overload situations. If the Capacity View shows any resource overloads click on the Capacity Leveling icon in change mode.x) / mySAP SCM (4. Responsibility Application support team Escalation Procedure Contact process champion • Monitoring Object Capacity leveling in interactive planning Capacity run in background (new version) SM37 Depends on business process Status Program scheduling management Contact application support team See general issues of Error Handling. SNP Capacity Leveling underwent a complete redesign in SCM 4. and BADI. If necessary. it will sometimes be necessary to adjust the results of the SNP heuristic to change the production times of quantities to ensure that no resource is overloaded. you should monitor the job using SM37. the three alert macros may be run either within interactive planning or in the background to identify exceptional situations such as resource overload or under load. Use an auxiliary table rather than the macro function for getting the date. Restartability and Escalation below.1 as of SP15 as an alternative to the original version. and stability we would like to encourage customers to test the new version for their business scenario and to use it instead of the original if it works well. and use macro function ACT_VERSION instead of macro function KEYFS_VERSION. Both versions can be executed interactively from transaction /SAPAPO/SNP94. © 2004 SAP AG . including full documentation. It is activated by creating a user parameter /SAPAPO/SNPCAP with value 'X'. optimizer.0 as of SP 22 and in APO 3. Monitoring Activities for Capacity Leveling Jobs for Running and Monitoring "Capacity Leveling" (APO) The following table describes how to monitor the capacity run. you can select those planning periods and/or products that should be processed. The new version is also available in APO 3. Monitor Monitor TA/Tool Freq.heuristic. Alerts Depends on business process Monit or Time Indicator or Error Alerts Monitoring Activity or Error Handling Procedure Look for fields which are colored red due to exceptional resource situations.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. The new version can also be executed as a background job using transaction /SAPAPO/SNP05. In order to create a feasible plan. Click on the icon "Capacity Leveling" in Capacity View.
in some cases when using CTM. we also recommend periodically executing report /SAPAPO/TS_GEN_DOCTAB_CHECK to eliminate possible inconsistencies in the notes. © 2004 SAP AG . Supply Network Planning supports online simulation in multiple planning scenarios. and SAP R/3 OLTP. for example. SNP interactive planning defaults to “display” mode when a user enters. • Minimize the number of default macros used for SDP interactive planning. and any other views that are used by that individual user. because they take place at a certain point in the business cycle where real-time feedback to online users is not required. For performance reasons. However it is also possible to use PP/DS transactions like /SAPAPO/RRP3. • Implement composite time bucket profiles with coarser time buckets in the long-term past and future. any interactive processing of data should be restricted to very small data volumes by specifying the selection criteria as far as possible. Some hints on the design and usage of planning books and macros for interactive planning can be found in are listed below: (see also SAP Notes 398726 and 542341): • Create a separate planning book for each user that contains only the views. you may wish to define one or more separate planning books for use with SNP interactive planning. e. Tasks that can be performed without direct user interaction. users who perform more than one task type should consider creating more than one planning book to accommodate each task type. a description of monitoring and managing them is given in Note 376383. In addition. Within transaction /SAPAPO/SNP94. as described in Note 401830. Also in this note it is stated that it is possible to write a BADI to override the default display. This is independent of when this planning step takes place. for instance before or after a planning run. In some cases. Also. While tables of selection variants are usually not a problem in release 3. or drill-down macros. consistent planning throughout your enterprise. If you are using notes management within interactive planning. This can be changed by altering user parameter /SAPAPO/SDP94_D_MODE.x) / mySAP SCM (4.0A and higher.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. • Each online user should create several selection variants to restrict the number of characteristic combinations considered to those which s/he needs for a specific task. correct key figures manually. Monitoring Activities Apart from safeguarding the general availability and consistency of the system components SAP APO. SAP recommends that you monitor the objects listed in the following table in order to safeguard this business step. for instance. as most customers using CTM use this transaction for interactive planning. In particular.0) 22 Business Process Step 7: SNP Interactive Planning In the following we discuss transaction /SAPAPO/SNP94.g. macros. the data must be reread to set the appropriate locks. For systems with large numbers of interactive users. In addition. when a user switches from display to change mode. showing a year as 9 weeks and 10 months will dramatically improve the performance without decreasing the time period shown. you can evaluate planning results. please refer to the Best Practice document Manage Production Planning in SCM / APO. each online user should verify that the macros in her/his planning book are all used regularly as part of the standard business practice and remove any which are not. periodically deleting unused selections may become necessary. for performance reasons. Please note that. should be performed as batch jobs rather than interactively. depending on the customer scenario. you can do almost everything that SAP APO Supply Network Planning offers. any users who do not actively view and use historical data should consider the “history not shown” flag as this allows macros to use the data without loading the data onto the screen. enter management overwrites. compare different scenarios. In such a case. and aggregation. For example. please read Note 332812 carefully before using this report to automatically correct inconsistencies. However. run macros. and create or view alerts. and fine time buckets only near the present time. SAP BW. aggregate data. end. drilling up and down. see if any of these can be executed less frequently as start. You might want to do one of the two for a number of reasons. key figures.
and a different data view whenever the time periods are different. Go support to APO Alert Monitor and process the alerts appropriately. For manual corrections see Business Process Step 7: SNP Interactive Planning. Restartability and Escalation below. it is often desirable to monitor alert situations or calculate quantities in time series key figures using batch macros run in SNP Planning Areas. schedule it to run once a day. Responsibility Application support Escalation Procedure Contact process champion Contact software monitoring team APO report /SAPAPO/AM ON_MAIL_BR OADCAST This report ensures sending of mails about existing alerts. A different planning book should be used whenever different key figures are needed by two macros. Delete Alert Monitor alerts with report /SAPAPO/AMON_REORG. mails are sent with an overview of existing alerts. at least daily. Weekly Status Check if the mail lists alerts Application that are important for you. Information on database alerts and dynamic alerts in Demand Planning can be seen in the APO Alert Monitor and below. Business Process Step 8: Execute Batch Macros In SNP. Some hints on the design and usage of macros for batch processing: • Create a separate planning book for each macro background job. If the report is not scheduled on a regular basis.x) / mySAP SCM (4. Check if job is running as scheduled. It deletes old alerts and is of particular importance if you use alerts stored in the database. Check if job is running as scheduled. or to calculate additional quantities and save them to time series key figures. After the planning run and manual adjustment. The planning book should only contain one planning view. investigate the reasons for the alerts and take corrective actions in order to keep the production plan close to the needs of your company. The responsible persons then should call up the APO Alert Monitor.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. and only macros executed as activities by the mass processing job. • Monitoring Object APO Alert Monitor Monitor Monitor Monitor Indicator TA/Tool Freq. the usual reasons for creating batch macros are either to perform calculations and evaluations of alert situations. Time or Error /SAPAP At least O/AMO daily N1 SM37 Daily Status Monitoring Activity or Error Handling Procedure Check for forecast alerts and SDP alerts and correct the planning for the reported object appropriately. The planning book should contain only key figures used by the macro itself. depending on your requirements. © 2004 SAP AG . schedule the following jobs to run on a regular basis: • 23 Send Alert Monitor mails with report /SAPAPO/AMON_MAIL_BROADCAST. Depending on user profiles. Contact process champion APO report /SAPAPO/AM ON_REORG. Alert Monitor mails Program scheduling management SO01 (or respecti ve email system) SM37 Dependi ng on your require ments.0) Jobs for Running and Monitoring "SNP Interactive Planning (APO)" To ensure a timely and efficient notification of exceptions in Supply Network Planning. Program scheduling management Contact application support See general issues of Error Handling. If the job is not scheduled on a regular basis. schedule it to run from between every hour to at least daily. This report deletes Alert Monitor alerts.
0) • • • 24 • • • • Remove all unused macros from planning books associated with mass processing jobs. You thus save the time needed for loading the data again. put both into one planning book and execute them as two actions within the same background activity (defined with transaction /SAPAPO/MC8T. and SAP R/3 OLTP. Also. and only in the planning book for the mass processing job in which they are used. loading a selection. Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. For dependencies and concurrent execution of jobs. the frequency of monitoring the jobs and deleting the SDP Job Logs depends on how often you run these functions.particularly those related to Deployment and TLB . since default macros are executed upon entry.x) / mySAP SCM (4. Please also refer to Exception based Monitoring of APO Supply Network Planning for the handling of alerts generated by a batch macro. while other jobs. Time or Error Dependi ng on your process. For the high data volumes usually considered in background processing. The planning book used for batch macros should have only the functionality it uses: in the case of SNP macros. and exit. shown Application support Contact process champion © 2004 SAP AG . All macros in mass processing should be defined as manually executable. Make sure that no individual location product belongs to more than one selection variant. as this can cause lock issues. The frequency of executing these Supply Network Planning batch jobs can vary significantly depending upon the business process for which the scenario is built. Accordingly. may only be executed once a month. If the report is not scheduled as provided by Application Support. SDP Job Log /SAPAP After O/MC8 each K run of /SAPAP O/TS_B ATCH_ RUN.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. Furthermore. defining macros as default macros and to be executed at another time is redundant and extremely performanceintensive. you do not need automatic macro execution for mass processing jobs. Responsibility Program scheduling management Escalation Procedure Contact application support SM37 APO report /SAPAPO/TS_ BATCH_RUN. see Operational Management – Parallel and Concurrent Execution of Jobs. changing data. SAP BW. schedule it accordingly. minimize the number of steps which manipulate alerts. please refer to consulting Note 521639. use database alerts rather than dynamic alerts. the planning book should have no macros selected. This report performs specified SDP mass processing activities. such as adjusting data released from DP to SNP. Macros that check for alert situations . In general.may be executed as often as daily. Monitoring Activities Apart from safeguarding the general availability and consistency of the system components SAP APO. Red or According to the warning or yellow error reported (see message traffic lights long text). For general advice on creating alerts in background jobs. and “Add” rather than “Update in Context” whenever possible. to safeguard this business step SAP recommends that you monitor the objects listed in the following table. If you need to run two macros on the same key figures with the same level of aggregation. see below). try to use “Delete” rather than “Delete in Context”. Create several background jobs with roughly equal numbers of location products and run them in parallel. When reading and writing alerts from the alert table in the APO database (table /SAPAPO/AM_ALERT). Status Monitoring Activity or Error Handling Procedure Check if job is running as scheduled. as they can be very performance-intensive and are not helpful to your business process.
These settings are maintained in transactions /SAPAPO/SDP110 and /SAPAPO/C4 (the latter is user specific).x) / mySAP SCM (4. Responsibility Program scheduling management Escalation Procedure Contact software monitoring team SM37 APO report /SAPAPO/TS_ BATCH_LOG FILE This report deletes old SDP Job Logs. See general issues of Error Handling. SM37 Dependi ng on your process Status Check if job is running as scheduled. Time or Error Dependi ng on your process. it is usual to transfer the data periodically. rather than immediately after planning is complete. In addition. Restartability and Escalation below. If the report is not scheduled as provided by Application Support. as the corresponding order changes are not transferred to R/3. while the information is user specific. please refer to the corresponding documentation on CIF functionality regarding transactional data transfers between R/3 and APO. such as planned orders. 206679.0) 25 Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. schedule it accordingly. A number of consulting notes exist regarding the transfer of APO orders to and from R/3 in the context of exchanging information with suppliers. Note that. The jobs mentioned in the Manage APO Core Interface in mySAP SCM. Note: Deleting change pointers may cause inconsistencies.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. Status Monitoring Activity or Error Handling Procedure Check if job is running as scheduled. as is the default setting in PP/DS. The corresponding objects. are sent to R/3. This report verifies that all change pointers are processed by checking that the list displayed in the report /SAPAPO/RDMCPPROCESS is empty. This report evaluates the APO change pointers (not the same as ALE change pointers!) that are written during planning activities. If the report is not scheduled as provided by Application Support. If change pointers remain unprocessed. In SNP. and 432038. contact the application support team to clarify whether these change pointers are needed and why they are not processed. section Operation and Monitoring of the APO Core Interface. APO report /SAPAPO/AM ON_REORG This report deletes old database alerts of various types. for example. • • © 2004 SAP AG . These jobs are: • Publish Planning Results with report /SAPAPO/RDMCPPROCESS. it is desirable to exchange requirements with suppliers. Notes 443500. certain jobs must be scheduled on a regular basis. you cannot use wild cards here. but must either specify the full user ID or user entry ‘*’ for all users not explicitly specified. Check Processing of APO Change Pointers with report /SAPAPO/RDMCPPROCESS. Program scheduling management Contact software monitoring team. Business Process Step 9: Exchange Requirements with Supplier In some cases. schedule it accordingly. Jobs for Monitoring "Exchange Requirements with Suppliers (APO)” To ensure that the planning results are published to R/3 and that the relevant data is consistent in both systems.
a consistency check and test for the remote cube are available through this functionality.0A and onwards (affects SAP APO 4. checking and testing the data source in the APO system can now be performed with report /SAPAPO/TS_PAREA_EXTR_MGM (transaction /SAPAPO/SDP_EXTR). APO Report SM37 /SAPAPO/RD MCPPROCES S to display change pointers Weekly Status Check if job is running as scheduled. schedule it accordingly. and SAP R/3 OLTP. Please see SAP Notes 129252 (Oracle) or 328106 (DB6). This is only relevant for systems running with Oracle. Restartability and Escalation below. Monitoring Activities Apart from safeguarding the general availability and consistency of the system components SAP APO. schedule the job daily.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3.0) the InfoCube statistics can be computed using the BRCONNECT tool as well as the ‘normal’ database statistics. For SAP © 2004 SAP AG . The function of creating. In addition. If the report is not scheduled as provided by Application Support. to safeguard this business step SAP recommends that you monitor the objects listed under Monitoring of Business Warehouse Activities. SAP BW. every SAP APO system comprises a complete SAP Business Information Warehouse System (BW).0) 26 Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. or at least once a week Status Monitoring Activity or Error Handling Procedure Check if job is running as scheduled. which will run report /SAPAPO/TS_PAREA_TO_ICUBE. Note 507810 describes the complete procedure for performing BW reporting on SNP remote cubes. From this report. SAP DB or IBM DB2 UDB (DB6) database (refer to SAP Notes 16083 and 421795). For SAP BW releases prior to 2. Please refer to Note 428147. Time or Error Dependi ng on your needs. all periodic monitoring tasks have to be performed in the APO system as well as job definition and most of the configuration tasks.0B Support Package 17 please notice the dependency to running SAPDBA (optimizer statistics for non-BW tables) described in SAP Note 129252. Please also refer to SAP Note 323090. This report is described in Note 453278. Responsibility Program scheduling management Escalation Procedure Contact Application Support. which discusses limitations of this functionality in detail.x) / mySAP SCM (4. For SAP BW releases 3. and that liveCache data structures (time series) are kept consistent. Business Process Step 10: Load Data into BW As mentioned above. In order to load the data into BW. the data must first be extracted from the SNP planning area. Jobs Necessary to Keep the APO Data Structures in Good Condition (APO) To ensure that database statistics and indices for BW specific data structures are kept up-to-date. SM37 APO Report /SAPAPO/RD MCPPROCES S This report publishes the results of automatic and interactive planning to R/3. schedule the following jobs to run on a regular basis: • Compute Histograms for BW InfoCubes with report SAP_ANALYZE_ALL_INFOCUBES. a background job for the extraction can be generated. Though in this business process step data is extracted from a separate BW system. If job is not scheduled on a regular basis and periodic publishing of data to R/3 is performed on the system. Program scheduling management Contact Application Support See general issues of Error Handling. which should be used exclusively for APO purposes.
Restartability and Escalation below.x) / mySAP SCM (4. Time or Error Weekly Status Monitoring Activity or Error Handling Procedure Check if job is running as scheduled. schedule it to run once a week with parameter percent = 100. Indices of APO InfoCubes.10) this is not recommended. This report creates DB statistics for all InfoCubes. If the traffic light gets yellow or red. Software monitoring team Contact application support See general issues of Error Handling.0A and 3. Responsibility Program scheduling management Escalation Procedure Contact software monitoring team APO report SM37 SAP_ANALYZ E_ALL_INFO CUBES. Only for systems running with Oracle. © 2004 SAP AG . Please refer to SAP Notes 428212 and 535986 for details. RSA1 or Weekly RSRV Red or yellow traffic light Select Check (Aggregate) Indexes.x (affects APO 3.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. SAP DB or IBM DB2/UDB (DB6) database. select Repair Indexes (now) or Delete Index (batch) and Create Index (batch). 27 Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. If the job is not scheduled on a regular basis.0) BW releases 2.
if necessary. certain jobs must be scheduled on a regular basis. are sent to R/3. Note 538046). capacity leveling has been performed. © 2004 SAP AG . as is the default setting in PP/DS These settings are maintained in transactions /SAPAPO/SDP110 and /SAPAPO/C4 (the latter is user specific). In addition. Restartability and Escalation below. This report evaluates the APO change pointers (not the same as ALE change pointers!) that are written during planning activities. and not in the other direction (cf. but must either specify the full user ID or user entry ‘*’ for all users not explicitly specified. Time or Error Dependi ng on your needs. section Operation and Monitoring of the APO Core Interface. For SNP planned orders only some manual changes are transferred from R/3 to APO: changes to output quantity. many customers update the results of SNP i. schedule the job daily. schedule it accordingly. Note: Deleting change pointers may cause inconsistencies. These jobs are: • Publish Planning Results with report /SAPAPO/RDMCPPROCESS. and purchase requisitions. or at least once a week Status Monitoring Activity or Error Handling Procedure Check if job is running as scheduled. If change pointers remain unprocessed.0) 28 Business Process Step 11: Create/Update Planned Orders. you cannot use wild cards here. Responsibility Program scheduling management Escalation Procedure Contact Application Support. The jobs mentioned in the Manage APO Core Interface in mySAP SCM. If the report is not scheduled as provided by Application Support. APO Report SM37 /SAPAPO/RD MCPPROCES S to display change pointers Weekly Status Check if job is running as scheduled. transfer orders. contact the application support team to clarify whether these change pointers are needed and why they are not processed.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. Program scheduling management Contact Application Support See general issues of Error Handling.e. availability date and order fixing. If job is not scheduled on a regular basis and periodic publishing of data to R/3 is performed on the system. while the information is user specific. Jobs for Monitoring "Perform Interactive Planning (APO)” To ensure that the planning results are published to R/3 and that the relevant data is consistent in both systems. In SNP. Note that. as the corresponding order changes are not transferred to R/3. This report verifies that all change pointers are processed by checking that the list displayed in the report /SAPAPO/RDMCPPROCESS is empty. Please note that not all order types may be transferred from R/3 to SNP. rather than immediately after planning is complete. planned independent requirements may only be transferred from APO to R/3. such as planned orders. and. SM37 APO Report /SAPAPO/RD MCPPROCES S This report publishes the results of automatic and interactive planning to R/3. the planned orders. it is usual to transfer the data periodically. In particular. please refer to the corresponding documentation on CIF functionality regarding transactional data transfers between R/3 and APO. Check Processing of APO Change Pointers with report /SAPAPO/RDMCPPROCESS. • • Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. Transfer Orders. and Purchase Requisitions After the planning runs are complete.x) / mySAP SCM (4. The corresponding objects.
With this report. Responsibility Program scheduling management Escalation Procedure Contact application support Output of APO SP01 report /SAPAPO/RT SINPUT. Jobs for Running and Monitoring "Release SNP to DP (APO)" To release the constrained Demand Plan back to DP. an explicit order conversion needs to be executed. In order to convert planned orders within the production horizon from SNP into PP/DS. Time or Error SM37 Dependi ng on your process Status Monitoring Activity or Error Handling Procedure Check if job is running as scheduled. Jobs for Running and Monitoring "Release SNP to PP/DS (APO)" To convert SNP/CTM orders into PP/DS orders: © 2004 SAP AG . Business Process Step 13: Release SNP to PP/DS Many customers using SNP or CTM also use the PP/DS planning functionality.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. Contact Process Champion See general issues of Error Handling. and SAP R/3 OLTP. Check the spool file to ensure Application that all records passed have support a green status light. or for individual productlocations. . If red or yellow traffic lights occur. Restartability and Escalation below. Some of these possibilities are described in note 481906. SAP recommends that you monitor the objects listed in the following table in order to safeguard this business step. Monitoring Activities In order to safeguard the functionality of releasing SNP to PP/DS. There are several possibilities how to integrate SNP with PP/DS. you can release the quantities stored in SNP order objects into DP time series key figures. do the following: • Release SNP Orders to DP time series with transaction /SAPAPO/LCOUT or report /SAPAPO/RTSINPUT. This process can be run in parallel. we recommend the reports listed below. Monitoring Activities Apart from safeguarding the general availability and consistency of the system components SAP APO. releases from SNP to PP/DS may only be executed within the same planning version.g. Monitoring Object APO report /SAPAPO/RT SINPUT. using the online transaction /SAPAPO/RRP_SNP2PPDS.0) 29 Business Process Step 12: Release SNP to DP Many customers who also use Demand Planning release the results of the SNP run (often called the constrained demand plan) back to DP to compare with the original forecast. Note that at this point in time. by selecting properly disjoint data sets for the release. This report copies the quantity stored in an SNP Order Key Figure into a DP time series key figure Monitor Monitor Monitor Indicator TA/Tool Freq. The conversion can be done in one of two ways: either using a mass conversion report launched from transaction /SAPAPO/SNP2PPDS. e. SAP BW. No reverse location or product split is possible. schedule it accordingly. it indicates an error. If the job is not scheduled as provided by Application Support.x) / mySAP SCM (4. After each run Messages in spool list.
The deployment heuristic does this based on any of several distribution methods and fair share rules. The distribution methods and fair share rules are described in detail in the deployment section of the APO documentation. which govern how the orders will be distributed across the network in cases of surplus or shortage.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. the result of deployment is a confirmation of the supply network plan. it should be run with logging set to normal. If the available quantities match required quantities as planned in SNP planning. Time or Error Dependi ng on your process Status Monitoring Activity or Error Handling Procedure Check if job is running as scheduled. Restartability and Escalation below. If you are not monitoring this alert type as part of your business process. Monitoring Activities Jobs for Running and Monitoring "Deployment Heuristic” To execute the deployment heuristic • Execute the deployment heuristic in the background with report /SAPAPO/RMSDPDEP. This converts the SNP orders for the specified location product(s) within the production horizon into PP/DS orders. Fair-share alerts for deployment are automatically generated during the deployment run. Use transaction /SAPAPO/SNP02 for small data volume only. If you are using these alerts. you should save one or more variants and execute them in the background. Business Process Step 14: Deployment Heuristic The purpose of deployment is to calculate replenishment for one product at one location at a time. which creates deployment stock transfers. When this report is run. Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. support application support should check the job log for error messages such as “Component 100-100 of PPM P-102 1000000100000000N500000 0401031 not valid on order dates” Contact Process Champion See general issues of Error Handling. messages Whether or not the job Application finishes without error. Note that parallel processing is possible for variants which contain no overlap in location-product or resources used. © 2004 SAP AG . be sure to delete the old ones regularly using report /SAPAPO/AMON_REORG with appropriate filters. turn off the alerts as described in Note 512797. by following the path Settings-> Planning Log. Responsibility Program scheduling management Escalation Procedure Contact application support APO report SM37 /SAPAPO/RR P_SNP2PPDS This report converts an SNP or CTM order to a PP/DS order Output of APO SM37 report /SAPAPO/RR P_SNP2PPDS Dependi ng on your process Status. For individual product-locations you can also use online transaction /SAPAPO/RRP_SNP2PPDS.e. schedule it accordingly. i. Deployment determines which requirements can be fulfilled by the existing supply. If the job is not scheduled as provided by Application Support.x) / mySAP SCM (4.0) • 30 Release SNP Orders to PP/DS with report /SAPAPO/RRP_SNP2PPDS.
weight and volume. Neither method of executing TLB will automatically create alerts. TLB can be executed either using interactive planning. create a batch macro to create them. Business Process Step 16: Transport Load Builder (TLB) The deployment run generates deployment confirmed stock transfers. number of pallets. the deployment optimizer instead tries to compute the lowest-cost manner in which to distribute the orders. or as a background job by running an appropriately designed variant for report /SAPAPO/RMSNPTLB. Time or Error SM37 Depend s on busines s process Status Monitoring Activity or Error Handling Procedure Check that the job is running as scheduled. the purpose of the deployment optimizer is to create deployment confirmed stock transfers.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. via transaction /SAPAPO/SNPTLB. and which consider the minimum and maximum constraints of the means of transport. The Transport Load Builder (TLB) then uses these stock transfers to generate TLB confirmed stock transfers and build transport loads comprised of multiple products. both firmed and non-firmed and creates deployment confirmed stock transfers independently. Monitoring Activities The following table contains a description of reports and monitoring objects for TLB. if they are desired. The difference is that the optimizer takes the current demand situation in the network into account rather than just the stock transfer demands of the individual location. The monitoring object indicates whether the information refers to TLB run in batch or foreground.e. Business Process Step 15: Deployment Optimizer Like the deployment heuristic. Restartability and Escalation below. Sm37 Depending on business process Depending on business process Monitor Time Indicator or Error Status Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure Contact application support Contact process management Check if job is running as Program scheduled scheduling management Whether or not the job finishes without error. Responsibility Program scheduling management Escalation Procedure Application support © 2004 SAP AG . This means rather than using one of the available fair-share techniques. See Business Process Step 5: SNP Planning Run Optimizer. Another difference is that Deployment Optimizer deletes all from SNP planned transport orders. Monitoring Object APO report /SAPAPO/RM SNPTLB Monitor Monitor Monitor Indicator TA/Tool Freq. i.x) / mySAP SCM (4. It is identical. application support should check the job log and spool file for error messages Application support Sm37 Status and messages See general issues of Error Handling. The background job can also be launched from transaction /SAPAPO/SNP04.0) 31 Monitoring Object APO report /SAPAPO/RM SDPDEP Output of report /SAPAPO/RM SDPDEP Monitor Monitor TA/Tool Freq.
or transaction /SAPAPO/RLCDEL.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. Monitoring Activities The following table contains a description of reports and monitoring objects for /SAPAPO/RLCDELETE.Indicator or or Error Time Status Monitoring Activity or Error Handling Procedure Check that the job is running as scheduled. and deleting older ones is necessary to either keep the liveCache from growing. and determine whether the package size needs to be tuned to improve performance.0) 32 Monitoring Object Output of report /SAPAPO/RM SNPTLB Monitor Monitor Monitor Indicator TA/Tool Freq. This is often done using report /SAPAPO/RLCDELETE. © 2004 SAP AG .0 SAP Note 660194 describes further details. are given in SAP Note 519014. or further processed in other ways. some of the order types generated during SNP planning are not converted to PP/DS. Monitoring Object /SAPAPO/RL CDELETE Monitor Monitor TA/Tool Freq. The first time the transaction is run with full data volume. along with several others for version management. The report can also be used to delete stocks. this is described in SAP Note 523250. Basic troubleshooting tips for this transaction. or as one of the steps of deleting a location-product from the system. Please be aware that using this report should be carefully evaluated with SAP Note 644676. Time or Error SM37 Depend s on busines s process Status/mes sages Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure Contact process champion Independent of the job status. the person responsible for monitoring should evaluate the data volume. Application check both the job log and support the spool file for application problems See general issues of Error Handling. Restartability and Escalation below. which summarizes the information available on the RLCDELETE report. As of SCM 4. as described in SAP Note 630751. Restartability and Escalation below. Responsibility Program scheduling management Application support Escalation Procedure Application support Log /SAPAP Depends O/RLCD on ELETE business process Status/mes sages Check the log for error messages and data volumes Contact process champion See general issues of Error Handling.x) / mySAP SCM (4. Business Process Step 17: Delete Transaction Data Under some business scenarios. SM37 Depends on business process Monit.
and the role of the Alert Monitor is to notify you of exceptions that occur during the process. A sudden switch in trends. Running Supply Network Planning in Background 5. an unexpected change in the circumstances of a supply chain partner could all lead to exception situations. An exception is any situation that needs further adjustment. and/or procurement across a supply chain with multiple locations. Most exceptions. see the Troubleshooting Guide Integration R/3 – APO. you can also prioritize alerts. Maintenance of SDP Data Storage Structures 4. if not handled immediately. so it is of special concern in this and other APO business process scenarios. the display of alerts is restricted to those which are assigned to the selected planning book. APO Alert Monitor 2. which you can find in SAPNet in the Literature Center of the R/3 Plug-In homepage.0) 33 Further Information Troubleshooting If executing this Best Practice did not produce the desired results. The Alert Monitor belongs to the suite of supply chain monitoring components in APO. The goal of Supply Network Planning is to create plans for production. The Alert Monitor is a standalone component of APO that enables you to have a unified approach to handling problem situations. can have consequences up or down the supply line. or when production plans. Alerts can also be displayed in the Supply Chain Cockpit /SAPAPO/SCC01. Monitoring of Business Warehouse Activities 3. transportation. and others. thus © 2004 SAP AG . It notifies you if a problem occurs during an ATP check or SNP run. a new fad. The Alert Monitor is an online tool designed to help you catch real-time exceptions well before they turn into problems and thus help you forecast your business needs more effectively. for example. proceed as follows: • If there are or seem to be problems in the data transfer via the Core Interface. When displaying alerts in /SAPAPO/SDP94. or vehicle schedules are being generated in one of the APO applications. together with the Supply Chain Cockpit and the Plan Monitor. Exception Based Monitoring of APO Supply Network Planning APO Alert Monitor The APO Alert Monitor allows a management-by-exception strategy. The Alert Monitor is a tool with which planners can monitor the state of a plan. It can be used by any supply chain manager or planner who practices exception-based management in the following areas: • • • • • • Demand Planning (DP) Supply Network Planning (SNP) Production Planning/Detailed Scheduling (PP/DS) Available-to-Promise (ATP) TLB/Deployment Vehicle Scheduling (VS) The Alert Monitor can be called as a standalone application via transaction code /SAPAPO/AMON1 as well as from various planning applications such as. /SAPAPO/SDP94.x) / mySAP SCM (4. The purpose of the Alert Monitor is to inform planners if the condition of a plan has been violated. Not only can you determine which types of exceptions you want to be notified of. Search for related SAP Notes Open a SAP Customer message describing your problem • • Background Information and References Related Tools and Activities This Appendix explains: 1.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. The monitoring results can be used to readjust the plan whenever necessary. demand plans. /SAPAPO/PPT1.
The three possible priority levels in the Alert Monitor are: 1. You can also have messages sent automatically to your own inbox to inform you of alerts in your area. Information The priorities should be defined in a way that . 3. you as the planner must make the ultimate decision regarding the priority of an alert. if an alert is generated. unexpected demands Orders exceed forecast Orders fall short of forecast. Generally. You have to maintain alert profiles to maintain a user-specific selection of alerts for your area of responsibility. manufacturing. Warning 3.0. In exception-based management. making it the ideal tool for tracking the quality of your alerts over a specific period of time. Alert priorities are identified by icons displayed in the profile or in the monitoring slots of the Supply Chain Cockpit control panel. Inform responsible planner. Besides forecast and SDP database alerts. you will soon be able to determine whether a 15% deviation is serious or not. Make adjustment to plan and / or profile. This knowledge would enable you to set priority variants for alerts so that you get a warning if the deviation is 10% but an error alert if it is 15%. even an information alert should reflect an exception to the planning situation and not a “success” message saying “everything ok”. alerts are now macro-dependent and thus can reflect the actual data in liveCache. However. must be deleted from the database. which may lead to excess inventory For Supply Network Planning. This alert type is NOT suitable for dealing with a large volume of planning objects because large numbers slow down performance.under normal conditions on a well run system information alerts take the biggest share and errors are generated only in rare cases. The results of the planning run show the situation as it was at the time of the run. Error 2. Unlike in the DP application where you can view only one planning book at a time. When dealing with large volumes it is best to perform a batch planning-run using the appropriate database macro. the following exception situations may arise: • • • Changes in bias. Analyze alert situation. SDP alerts can be used both in the Demand Planning and Supply Network Planning applications. There are two different types of Supply & Demand Planning alerts: • Dynamic alerts mirror the current planning situation but are not saved in the database. new trends. you can view several in the Alert Monitor. There are forecast alert profiles and SDP alert profiles. because they have been acknowledged or because they are outdated. If you regularly consider Capacity Overload alerts.0) 34 preventing an information overload. in other words. Database alerts show the planning situation as it was during the planning run. For small data volumes up to approximately 1000 alerts dynamic alert generation is usually much faster than reading alerts from the database. with database alerts you see a snapshot of the plan during run time. You also have the option of creating customer-specific dynamic or database alert types to be used with SDP macros. are not stored in the database but are dynamic only.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. Database alerts that are no longer in use. this also applies to ATP. each can be configured as either a dynamic alert (recommended for small data volumes in interactive planning only) or database alert (recommended for batch jobs and large data volumes). and distribution. PP/DS alerts. for instance.x) / mySAP SCM (4. you can send messages via e-mail to other planners to inform them of the alert situation. both supply & demand planning (SDP) alerts and Transport Load Builder (TLB) alerts are important. or last executed macro. © 2004 SAP AG • . however. For large data volumes database alerts are usually faster. 2. The SDP alert profile contains a number of alerts that are specific to the tactical planning and sourcing decisions relevant for purchasing. In the demand planning process. three activities must take place: 1. VS and TLB/Deployment alerts. As opposed to SNP alerts in APO Release 2. To support the Alert Monitor's function as a tool for exception-based management.
and 521639 and to Exception based Monitoring of APO Demand Planning. 500063. SAP BW. As there are very many applications that use this basis component and often many table entries are made. Keep alerts to a minimum. SAP recommends that in order to safeguard any business step that is based on SAP BW techniques. When adapting this concept for your company.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. You can also call the monitor from a selected Info Package or via transaction code RSMO. Monitor. You can find more information concerning this tool in the SAP Documentation under "Supply Chain Monitoring – Alert Monitor". you may have an alert profile for your own area of responsibility. The scheduler generates a background job with name prefix BI_BTCH and processes the selected Info Package. responsible teams. In Monitoring of the Administrator Workbench (select Monitoring in transaction RSA1 or call transaction RSMO) you have the option of overseeing and controlling the data loading process into the InfoCubes and you can analyze errors that may have occurred (Menu: Monitor -> Assistant). it is important to regularly delete obsolete Application Logs from the database in order to prevent these tables from © 2004 SAP AG • . Monitoring Activities Apart from safeguarding the general availability and consistency of the system components SAP APO. The log entries are subdivided into objects and sub-objects and classified by importance.0) 35 You can maintain a list of favorite Alert Monitor profiles so you can switch back and forth easily between various profiles. Too many alerts slow performance and may cause you to overlook the really important ones. For example. The monitor transaction for the Application Log is SLG1. The job has to be defined using the scheduler in the Administration Workbench (transaction RSA1) of the BW component of APO. and SAP R/3 OLTP. Monitoring of Business Warehouse Activities This section points out the concept for monitoring activities related to data transfers and the maintenance of data keeping structures in the SAP BW component of an SAP APO system. but you may also want to look at alerts in other areas. you monitor the objects listed in the following table. schedule the following job on a regular basis: Data Extraction and Load with report RSBATCH1. Relevant objects for the SAP Business Warehouse are: • • • • • • RSAR RSAU RSD RSDMD RSO_REPOSITORY RSSM BW Metadata maintenance Update rules BW data basis Master data maintenance BW Repository Scheduler. With the help of Info Package groups you can collate data requests that logically belong together and schedule them using the scheduler. 495166. and escalation paths (responsible teams) for the following monitoring activities and objects. where you should specify the (sub-) objects and the time interval you want to be displayed. Make sure that you have selected the correct time window and data to be displayed by calling the selection screen via menu Monitor -> New Selections. Tree callback Jobs for Running and Monitoring Data Transfers To or Within the Business Warehouse To ensure a timely and consistent data transfer from any data source into a SAP Business Warehouse structure. It can be browsed using transaction SLG1. The data transfer process from a source system to SAP BW InfoCube(s) as well as certain actions in RSA1 and RSMO write detail information to a central R/3 basis component called the Application Log. you must specify the times. the Application Log can be used to get more detailed information about what happened and how to resolve the problem.x) / mySAP SCM (4. Jobs for the Maintenance of the Application Log The Application Log entries are stored on tables with name prefix BAL*. Please refer also to SAP Notes 375965. In case of errors or problems. The data transfer can take place inbound or outbound the BW (APO) system to and from other SAP or third party components as well as within one APO system between different data storage units like InfoCubes and liveCache.
Responsibility Program scheduling management Escalation Procedure Contact application support RSMO After every data load Red or After selecting one request.0) overflowing as well as to keep the applications and the log retrieval performant. Software yellow read the error message and monitoring traffic lights diagnosis under tab strip team Status and the processing log under Detail. and take corrective action. For more information. please refer to SAP Note 195157. Contact application support APO: Evaluate SLG1 Application Log for BW related objects. Use the Monitor Assistant to analyze and correct the error situation. APO: Administration Workbench Monitor Monitor Monitor Monitor Indicator TA/Tool Freq.x) / mySAP SCM (4. If the job is not scheduled as provided by Application Support. Software monitoring team Contact application support APO report SBAL_DELET E. © 2004 SAP AG . schedule it accordingly. a necessary job is not scheduled. Contact the program scheduling management in order to clarify when the job will be fully defined. but the start condition has not yet been defined. The deletion can be performed using transaction SLG2 or in background by the appropriate report: • 36 Delete Obsolete Application Logs with report SBAL_DELETE. Read message long text and / or details. Time or Error RSMO Dependi or SM37 ng on your process Status Monitoring Activity or Error Handling Procedure Check if job is running as scheduled. under Background Processing. if present.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. Restartability and Escalation Error Handling Procedures Error handling for background jobs is explained in detail in the SAP R/3 documentation CD. At least daily Log class Check if there are very important logs (flagged red) or important logs (flagged yellow). If a scheduled job fails. component BC-CCM. Analyze error situation. or a scheduled job has status "finished" you may need to take action. Monitoring Object APO job BI_BTCH*. evaluate error severity and impact. Program scheduling management Contact application support Error Handling. These jobs perform the data transfer from the different data sources to APO InfoCubes. SM37 Weekly Status Check if job is running as scheduled. If the job is not scheduled as provided by Application Support. A log can only be deleted when it has reached its expiry date or if it has the "Deletion before expiry" attribute. Consider the status of the job and proceed as follows: • Status scheduled: the job steps have already been defined. This report deletes obsolete Application Logs. schedule it to run weekly.
If there are problems with the Core Interface CIF or with data missing in either R/3 or APO. Check for particular dependencies to other jobs. and updates). If the corresponding escalation path is not well defined. SAP DB or IBM DB2 UDB (DB6) database (refer to SAP Notes 16083 and 421795) Please see SAP Notes 129252 (Oracle) or © 2004 SAP AG . • • • Process Step Restartability If a background job is cancelled. forward the issue to the next support level. if a program in a job step produced an error such as issuing an "E" or "A" error message. A job scheduler has put the job in a queue to wait for an available background work process. Status cancelled: the job has terminated abnormally. consider possible succeeding jobs or dependencies on other jobs when deciding whether to restart the aborted job. you must specify the times. This can happen in two ways. message logs. search for appropriate messages in SAPNet and create a customer message if you cannot solve the problem. If the program is an SAP standard program. Maintenance of SDP Data Storage Structures If SNP time series objects are used in the planning areas of your company. and software monitoring team and / or application support must check the respective job results (such as spool output lists. contact Application Support. clarify why he or she did so and whether (and if so. when) the job must be re-run. and liveCache Time Series. If you have questions or problems that cannot be solved. the tasks associated with DP BW structures must also be executed for these time series objects. see the Troubleshooting Guide Integration R/3 – APO in the Literature Center (of the R/3 Plug-In homepage). we recommend that you search for related SAP Notes in the SAPNet R/3 front-end system for any unknown problems or errors. The aborted job may also delay the start of succeeding jobs. Status finished: all steps that make up this job have completed successfully. 37 Status active: the job is currently running and can no longer be modified or deleted. we recommend that you create a customer problem message in the SAPNet R/3 front-end system. When adapting this concept for your company. Alternatively. Check if the job is within the given timeframe. the Master Planning Object Structure. Escalation Procedures • • • In general. Status ready: the start condition of a released job has been fulfilled. Program scheduling management must check whether the job ran in the given timeframe. and escalation paths (responsible teams) for the following monitoring activities and objects. and that liveCache data structures (time series) are kept consistent. contact the software monitoring team and investigate why the error occurred. If the job exceeded the given timeframe. If none of the defined support levels can provide a solution for a particular problem. If an administrator intentionally canceled the job. This is only relevant for systems running with Oracle. All these need a certain amount of surveillance and maintenance in order to stay in a technically optimal condition and therefore to allow a fast retrieval of the data stored within. contact the software monitoring team.x) / mySAP SCM (4. either alone or together with order objects. responsible teams. schedule the following jobs to run on a regular basis: • Compute Histograms for BW InfoCubes with report SAP_ANALYZE_ALL_INFOCUBES. Monitoring Activities The data for your Demand Planning process is stored in different logical and physical structures such as InfoCubes. Jobs Necessary to Keep the APO Data Structures in Good Condition (APO) To ensure that database statistics and indices for BW specific data structures are kept up-to-date.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3.0) • • • Status released: the job has been fully defined with a start condition and will wait for that condition to be fulfilled.
showing users who have already set a change lock for the planning version. report execution is interrupted and a list of system users is displayed. in all planning areas and versions. Responsibility Program scheduling management Escalation Procedure Contact software monitoring team APO report SM37 SAP_ANALYZ E_ALL_INFO CUBES. Run this report in separate background jobs choosing options Calculate Statistics and Check Indexes for every Master Planning Object Structure and review the list of messages being displayed. 425825.. This report creates DB statistics for all InfoCubes. For further details. schedule it to run once a week with parameter percent = 100. Please also refer to SAP Note 323090. If errors are found. • 38 Check Inconsistencies in Time Series Network with report /SAPAPO/TS_LCM_CONS_CHECK_ALL. Run it with option Repair Indexes. This report checks all existing time series. Maintain Statistics and Indices for Planning Object Structures with report /SAPAPO/TS_PSTRU_TOOL. For this reason. For SAP BW releases prior to 2. 492460. Caution: When you run report /SAPAPO/TS_LCM_REORG. no other processes for a planning area (applies only to planning areas with key figures based on liveCache time series) should be allowed to run with the same planning version. For details and further information please refer to SAP Notes 358283.0) or SP 10 (APO 3. Delete Time Series and Time Bucket Profiles having no liveCache Anchors with report /SAPAPO/TS_LCM_REORG. resp. Mark the Log check box if you want to see a list of characteristic combinations having inconsistencies. If you have selected the 'Repair' option.1).x) / mySAP SCM (4. and then possibly deleted. If you cannot activate the lock.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. but simply unnecessary objects. any unnecessary time series and period patterns are deleted. Time or Error Weekly Status Monitoring Activity or Error Handling Procedure Check if job is running as scheduled. you can repair inconsistencies in a specified planning area and version using report /SAPAPO/TS_LCM_CONS_CHECK. A separate background job (job name with prefix BI_STAT) will be started to execute this request. and 520876. if problems are reported by the index check. and reports whether or not there are inconsistencies. which result in increased liveCache memory consumption.0) 328106 (DB6). In this case. © 2004 SAP AG . This report (supplied with SAP Note 542946 or Support Package 22 (APO 3. SAP DB or IBM DB2/UDB (DB6) database. and 503363. independently of planning areas. since this would result in liveCache objects that are still required by the other parallel process being recognized as unnecessary. These objects do not have any reference to the application data and are therefore not inconsistent as such.0B Support Package 17 please notice the dependency in running SAPDBA (optimizer statistics for non-BW tables) described in SAP Note 129252. • • Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. we recommend that you always run the report with the option 'Lock planning version'. If the job is not scheduled on a regular basis. refer to SAP Note 425825) determines all liveCache time series and time buckets profiles from a selected planning version that do not have any 'liveCache anchors'. please refer to SAP Notes 393655. Only for systems running with Oracle. For this reason you should only have to run the report approximately once a month. all planning areas that use the planning version to be checked are locked for the relevant version. 402046. These administrative jobs have to be run after every load of data to a planning object structure.
schedule it to run once a week.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. Traffic light Check whether the inconsistencies in the selected time series have been repaired. Software monitoring team Contact application support SM37 APO report /SAPAPO/TS_ LCM_CONS_ CHECK. Traffic light Check whether superfluous data is reported and has been deleted without errors. Output of APO SP01 report /SAPAPO/TS_ LCM_CONS_ CHECK. This report is able to repair inconsistencie s in time series. Software monitoring team Contact application support After each run. Red traffic light Check for time series with inconsistencies reported. If the job is not scheduled on a regular basis. After each run. Output of APO SP01 report /SAPAPO/TS_ LCM_REORG . This report detects inconsistencie s in time series.x) / mySAP SCM (4. Status Check if job has finished without errors. If the job is not scheduled on a regular basis. This report deletes superfluous time series and time bucket profiles. schedule it to run once a month. Time or Error Weekly Status Monitoring Activity or Error Handling Procedure Check if job is running as scheduled. Software monitoring team Contact application support Monthly Status Program scheduling management Contact application support After each run. SM37 APO report /SAPAPO/TS_ LCM_REORG with option Repair. Try to repair inconsistencies by running report /SAPAPO/TS_LCM_CONS_ CHECK for the corrupt time series setting the repair option. Responsibility Program scheduling management Escalation Procedure Contact application support SM37 APO report /SAPAPO/TS_ LCM_CONS_ CHECK_ALL. After each run. Output of APO SP01 report /SAPAPO/TS_ LCM_CONS_ CHECK_ALL.0) 39 Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. Software monitoring team Contact application support © 2004 SAP AG . Check if job is running as scheduled.
Software monitoring team Contact application support After every run. and are discussed in the pertinent chapters in earlier parts of this document. Message type (icon) Look for stop icons (cancellation). Jobs for Running and Monitoring "Supply Network Planning in Background" (APO) To ensure a proper and timely demand planning. This mass processing job is created with its necessary settings and scheduled using transactions /SAPAPO/MC8x. Status Software monitoring team Contact application support See general issues of Error Handling. The different tasks that can be performed in this way have to be customized and set up as “activities” prior to job definition. schedule the following jobs to run on a regular basis: • Run Demand Planning in the Background with report /SAPAPO/TS_BATCH_RUN. schedule it accordingly. Responsibility Program scheduling management Escalation Procedure Contact application support SM37 APO report /SAPAPO/TS_ PSTRU_TOO L with option Calculate Statistics.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. schedule it accordingly. Using transactions /SAPAPO/MC8D and /SAPAPO/MC8E you can create and change © 2004 SAP AG . Program scheduling management Contact application support After every run. This report checks and generates statistics for a POS. and red (errors) or yellow (warnings) lights.0) 40 Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. If the report is not scheduled as provided by Application Support. Job BI_STAT* SM37 started by /SAPAPO/TS_ PSTRU_TOO L with option Repair Indexes. and deployment runs) are executed using a different interface. Check if job ended correctly. optimizer. Running Supply Network Planning in Background This section outlines the monitoring concept for Supply Network Planning activities in background for processing mass data which use the same interface as Demand Planning background jobs. This report checks the indices of a POS. Mass processing allows you to run macros for large numbers of products while optimizing system resources. After every data load into the POS. and SAP R/3 OLTP. Status Monitoring Activity or Error Handling Procedure Check if job is running as scheduled. Read message long text if present. If the report is not scheduled as provided by Application Support. Output of APO SP01 report /SAPAPO/TS_ PSTRU_TOO L. Also a release of DP data to SNP is usually performed in background. in order to safeguard any business process step that performs Supply Network Planning activities in the background. Time or Error After every data load into the POS. SAP BW. APO report SM37 /SAPAPO/TS_ PSTRU_TOO L with option Check Indexes. the heuristic. Status Check if job is running as scheduled. Other Supply Network Planning background jobs (for example. Monitoring Activities Apart from safeguarding the general availability and consistency of the system components SAP APO. SAP recommends that you monitor the objects listed in the following table.x) / mySAP SCM (4. Restartability and Escalation above.
Delete DP Job Logs with report /SAPAPO/TS_BATCH_LOGFILE. With /SAPAPO/MC8G. such jobs. etc. forecast error messages if the job included a forecast. a release of DP data to SNP orders. Each selection ID should define a set of characteristic value combinations of approximately equal size and no individual characteristic combination should belong to more than one selection ID as this can cause lock issues and it is superfluous to process a combination more than once. shown Application support Contact process champion © 2004 SAP AG . To check the results of a DP mass-processing job. the execution of one or several macros.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. See also SAP Note 512184. This can be achieved by defining several jobs in /SAPAPO/MC8x running the same activity but having a different selection of characteristics. With /SAPAPO/MC8J you can copy jobs and delete them with /SAPAPO/MC8F. These jobs can then be scheduled to run at the same time. Computation of key figures with batch macros could possibly be done daily or weekly. Responsibility Program scheduling management Escalation Procedure Contact application support SM37 APO report /SAPAPO/TS_ BATCH_RUN. for example once a quarter or once a year. • Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. Standard transaction SM37 is used for a job overview and display of job logs and jump to spool lists. Status Monitoring Activity or Error Handling Procedure Check if job is running as scheduled. Old logs from planning activities must be deleted regularly to maintain high performance for the related transactions and prevent database tables from overflow. the jobs are scheduled.g. Please also refer to Exception based Monitoring of APO Demand Planning for the handling of alerts generated by a forecast run or a batch macro. You can also delete job logs with this transaction. it is often necessary to process batch runs (e. and others limit the total number of jobs that can run on a system at the same time. with warnings (yellow traffic light) or with errors (red traffic light). select Generate log when you create a job. Demand planning activities can be executed periodically with various different frequencies. whereas a release of the demand plan to production planning or R/3 is usually performed over larger intervals of time. a message for every characteristic value combination that was processed in the job. which is usually called from the customizing tree. the frequency of monitoring the jobs and deleting the DP Job Logs depends on how often you run these functions.0) 41 respectively. Time or Error Dependi ng on your process. Make sure that you delete the logs in packages. The so-called activities that are needed for these jobs have to be defined in advance via transaction /SAPAPO/MC8T. macros. An activity can be a forecast computation. “data view does not exist” or “release profile not found”. see Operational Management – Parallel and Concurrent Execution of Jobs. schedule it accordingly. Select the option 'Delete all logs with minimum age' reducing the parameter days. call transaction /SAPAPO/MC8K.x) / mySAP SCM (4.) in parallel. If the report is not scheduled as provided by Application Support. For dependencies and concurrent execution of jobs. main memory. The job log shows whether the job completed successfully (green traffic light). Red or Accordingly to the warning or yellow error reported (see message traffic lights long text). Parallel processing: Due to the large amount of data to be processed and the limited time that can usually be spent on it. use the DP Job Log. and other details. Please remember that hardware resources like number of CPUs. To view the job log. DP Job Log /SAPAP After O/MC8 each K run of /SAPAP O/TS_B ATCH_ RUN. Accordingly. /SAPAPO/MC8I allows you to check the job definition prior to execution and find errors like “no macro defined”. CPU speed. This report performs specified DP mass processing activities. To request a job log. or the transfer to R/3.
Time or Error /SAPAP At least O/AMO daily N1 SM37 Daily Alert list Monitoring Activity or Error Handling Procedure Check for forecast alerts and SDP alerts and correct the planning for the reported object appropriately.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. Jobs for an Exception Based Monitoring of Supply Network Planning To ensure a timely and efficient notification of exceptions in Supply Network Planning. The most important high-level tool for monitoring the planning situation and an exceptiondriven application management is the APO Alert Monitor. However. It deletes old alerts and is of particular importance if you use alerts stored in the database. it is not necessary for planners and / or IT staff to repeatedly call the monitor transaction actively over short intervals and then to acknowledge that nothing important has happened since the last refresh.x) / mySAP SCM (4. schedule it to run every hour to at least daily. Time or Error Dependi ng on your process. If the report is not scheduled on a regular basis. schedule the following jobs to run on a regular basis: • Send Alert Monitor mails with report /SAPAPO/AMON_MAIL_BROADCAST. see APO Alert Monitor. Status Program scheduling management © 2004 SAP AG . depending on your requirements. SAP recommends that you monitor the objects listed in the following table in order to safeguard your Supply Network Planning business process. Check if job is running as scheduled. See general issues of Error Handling. above. and SAP R/3 OLTP. Depending on user profiles. schedule it accordingly. Responsibility Application support Escalation Procedure Contact process champion Contact software monitoring team APO report /SAPAPO/AM ON_MAIL_BR OADCAST This report ensures sending of mails about existing alerts. If the report is not scheduled as provided by Application Support. Monitoring Activities Apart from safeguarding the general availability and consistency of the system components SAP APO.0) 42 Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. Status Monitoring Activity or Error Handling Procedure Check if job is running as scheduled. Delete Alert Monitor alerts with report /SAPAPO/AMON_REORG. The usage of the Alert Monitor is supported by an e-mail interface that allows notification to be sent to the responsible persons in case of new alerts. investigate the reasons for the alerts and take corrective actions in order to keep the demand plan close to the needs of your company. Responsibility Program scheduling management Escalation Procedure Contact software monitoring team SM37 APO report /SAPAPO/TS_ BATCH_LOG FILE This report deletes old DP Job Logs. the overall situation shown in the Alert Monitor should be supervised daily or adapted to the frequency of the demand planning process in your company. SAP BW. Restartability and Escalation above. The responsible persons should then call the APO Alert Monitor. • Monitoring Object APO Alert Monitor Monitor Monitor Monitor Indicator TA/Tool Freq. Exception Based Monitoring of APO Supply Network Planning This section outlines the concept for monitoring the overall planning situation in APO Supply Network Planning. Therefore. For information on database alerts and dynamic alerts in Demand Planning. mails are sent with an overview of existing alerts.
0 documentation is available on CD or in the SAP Help Portal in German or English. Therefore times for such backups must be scheduled carefully. Necessary or Useful Training Courses: ADM355 APO System Administration SCM210 Core Interface APO SCM230 Supply Network Planning Dependencies Remember that there are dependencies (date and time. This restriction applies only for liveCache 7. General APO-specific system administration: o Checkpoint writing for liveCache – You should not start a checkpoint during long running background or online planning activities because the checkpoint has to wait for the completion of the planning activity. SAP Documentation SAP APO 4. Second. SAP APO 3. We recommend that you write checkpoints before and after long running planning jobs.x. for example: • General R/3 system administration. all other users that require liveCache data have to wait for the completion of the checkpoint. Program scheduling management Contact application support See general issues of Error Handling.0 documentation is available on CD or in the SAP Help Portal in German or English. This guarantees that no checkpoint has to wait for the planning run to finish and thus causing all other transactions to wait.1 documentation is available on CD or in the SAP Help Portal in German or English. for example: o Reorganization of jobs. APO report /SAPAPO/AM ON_REORG. Restartability and Escalation above. SAP APO 3. Print files (PDF format) of several chapters in both languages are available in the Media Center of the SAP Marketplace for SCM.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. logical sequence) on business processes and process steps not mentioned in this document. Check if job is running as scheduled. at least daily. In addition.1 are also available in Release 3. Go support to APO Alert Monitor and process the alerts appropriately. Several functions that have been documented in the SAP Library for SAP APO Release 3. schedule it to run once a day. spool entries and so on o DB offline backup – During an offline database backup no online or background activity is possible. Weekly Status Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure Contact process champion Check. (this also applies to the R/3 basis of the APO system). o Archiving of DB transaction logs o Updating table statistics for the DB cost based optimizer – You should not run this activity at times when application programs are likely to be creating.0. Time or Error SO01 (or respecti ve email system) SM37 Dependi ng on your require ments. If the job is not scheduled on a regular basis. This report deletes Alert Monitor alerts. These usually comprise. Please refer to SAP Note 514971 for details.x) / mySAP SCM (4. or updating many table entries.0) 43 Monitoring Object Alert Monitor mails Monitor Monitor Monitor Indicator TA/Tool Freq. rule of thumb 4 to 6 times per day in total. it is • © 2004 SAP AG .2. deleting. if the mail lists alerts Application that are important for you.
Because of these dependencies.x) / mySAP SCM (4. overnight or over a weekend. transportation resources b) Other planning activities (for example. same resources for handling. on rare occasions. for example. Operational Management – Parallel and Concurrent Execution of Jobs The combination of liveCache and database lock issues and system resource usage makes concurrent execution of some SNP job types problematic. Recommendation: Observe the following rules for scheduling or executing SNP transactions and jobs: 1) Design SNP Planning runs to run in parallel with selection variants that avoid concurrent locks. for the completion of administration activity. because this can overload CIF and cause an undesirable communication delay. all the work necessary for the company’s core business process can be performed in the time frames determined by the business process champions. but may need to wait. or. Therefore. Especially in APO. production. b) Network Heuristic: parallel processing only if the selection variants executed in parallel specify different products AND none of the products in different variants use the same resources. online and background application system activity cannot always occur whenever desired. program scheduling management and the software monitoring group should plan and schedule system maintenance activities to run at appropriate times. certain activities – such as background jobs – should be started only after the respective preceding activity has finished. You should not transfer large packages of master data to APO when CIF is needed for the transfer of transactional data. because this can cause long waits for online users (with liveCache 7. a) Multilevel Heuristic: parallel processing only if the selection variants executed in parallel specify different products AND none of the products in different variants use the same resources.x only). Concurrent locks in SNP jobs can occur due to: a) SNP Planning Jobs that run in parallel on the same location products or objects (for example. long-running planning activities should not collide with APO checkpoint writing.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. Checking the internal (liveCache – APO DB) and external (APO – R/3) data consistency Backup for liveCache Reorganization of COM-objects and optimizer application logs with report /SAPAPO/OM_REORG_DAILY) 44 o o o • Transfer of Master Data from R/3 to APO: o Initial transfer of master data records. o Delta transfer of new master data records. o Transfer of changes made to existing master data records.2.0) warranted that the results from the planning run are safely stored away in a consistent manner with the other data in liveCache. Then. © 2004 SAP AG . Also. for example. PP/DS or SNP Optimizer) during the SNP Planning run c) Change of data by CIF during the SNP Planning run 2) The following job types may be run in parallel provided that they obey rule 1: a) SNP Batch Macros b) Deployment Heuristic c) TLB Heuristic d) Safety Stock Planning using report /SAPAPO/MSDP_SB 3) Parallel processing for the SNP heuristic may be executed for ONLY two of the three heuristic modes.
no two selection variants which contain overlapping characteristic combinations. Also run these as background jobs. separate variants should contain only products for which there is absolutely no overlap in components. some customers configure separate optimizer servers for each run. Refer to SAP Note 539348 for technical details. or ppm used by products in other variants. resulting in performance problems. a trial run of the process to be parallelized must be run: you should: a) Collect the statistical records for the run with FULL details b) Know how much total memory your system has (call this M_total) c) From the statistical records. are not. across all appropriate locations. it will create an error message in the job log.x) / mySAP SCM (4. 12) If you are using alerts in SNP. which can be separate from the application server. should be contained in the variant for that product. although the relative amount of time spent will vary with the problem structure. Optimal performance is achieved when one CPU is available for each process.depending upon how many CPU resources are needed by the particular job type. Specifically. How critical this is depends upon how much of the response time is CPU time. while others. Note that the SNP optimiser will consume CPU resources on the optimiser server. c) No product-location should belong to more than one variant. regularly delete old alerts using report /SAPAPO/AMON_REORG. The maximum number of parallel processes which should run at once is: N = (M_total)/(M_proc) 9) Execute all mass processing jobs at times of low system load due to their large data volume. find out how much memory was used by the individual process. To avoid this. Parallel processing for a complete optimiser run is possible only if the following rules are observed: a) The complete ppm for a final product. such as a batch macros which add two key figures. © 2004 SAP AG . Memory is often a bottleneck for the SNP optimizer. ppms. are heavily dependent upon the application CPU resources. Otherwise the solution will not be optimal. 10) Do not execute the daily liveCache reorganization job concurrently with ANY type of SNP planning run or CTM. 7) Parallel execution of the SNP optimiser should be designed to avoid CPU and memory bottlenecks on the optimiser server. 11) Do not execute SNP planning runs concurrently with the release from DP to SNP. For optimal performance. More jobs will run more slowly .Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. only run as many jobs as there are CPU on the system. b) To avoid a non-optimal solution. 8) Parallel execution should be designed to avoid memory bottlenecks. and products in one variant should not use resources. Some job types. A good rule of thumb is that one CPU is needed for each two optimiser jobs run in parallel. and less if there are memory limitations. transportation lanes. It unsuccessful. Typically this means these jobs should be run during the night. the Heuristic will attempt to re-plan the product for a fixed number of times. or transportation lanes.0) 45 c) Location heuristic: parallel processing if selection variants specify different locations OR if selection variants which specify the same location contain non-overlapping sets of products AND the products in the different selection variants do not use any common resources. 6) Parallel execution should be designed to avoid CPU bottlenecks on the application server. When a locking situation occurs during an SNP Heuristic Run. 5) Two users should not selection variants in SNP interactive planning which lock the same datasets. such as the SNP heuristic. resources. call this number M_proc. or else one job must wait until the other has released the lock on the data.
alias /scm >> Related Topics / Best Practices for Solution Management: mySAP SCM. SAP APO System Administration. SAP R/3 System Administration. run a time series consistency check any time you make changes to the planning object structure. and a discussion of errors caused by inconsistent time series objects can be found in Note 509479. Monitoring and Administration for SCM / APO helps you analyze the workload and performance on liveCache and the APO database. However.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3. SAP R/3 Implementation with ASAP. 1999 Other Best Practice Documents In SAP Service Marketplace. All the jobs and monitoring activities listed in the CIF document have to be considered in every business process step listed above that sends or receives data through CIF.0) 46 13) If you are executing batch macros in SNP. 2001 For background information on administrative tasks with emphasis on system planning and setup. 15) Execute model consistency checks any time the master data for SNP is changed using transaction /SAPAPO/CONSCHK with a profile appropriate for the SNP functionality you are using. see: Hartwig Brand. 14) Ensure that you are running report /SAPAPO/OM_REORG_DAILY on a regular basis. However. and are creating spool files for these runs. A description of this report exists in Note 425825. 2002 For information about how to monitor and tune general system performance. it is also recommended that you periodically run report /SAPAPO/TS_GEN_DOCTAB_CHECK to eliminate possible inconsistencies in the notes.x) / mySAP SCM (4. Manage Production Planning in mySAP SCM / SAP APO deals with Production Planning and Detailed Scheduling in APO and Production Execution in R/3. or add master data. see: • • • • Liane Will. do not run this report concurrently with any of the SNP planning runs.1 contains important information about master data consistency as well as internal consistency between APO DB and liveCache. as described in Note 139558. 16) If you are using time series objects in SNP. Manage APO Core Interface in mySAP SCM deals with the Business Process Management of the APO Core Interface CIF and is an essential enhancement to this document.0 / 3. Literature For more detailed information about how to administer an SAP R/3 System. Data Consistency Between SAP R/3 and SAP APO 3. see: Thomas Schneider. using report /SAPAPO/TS_LCM_CONS_CHECK_ALL. see: Liane Will. © 2004 SAP AG . 2000 For information about the administration of SAP APO systems. SAP R/3 Performance Optimization. please read Note 332812 carefully before using this report to automatically correct inconsistencies. 17) If you are using notes management within interactive planning. regularly delete old job logs using transaction /SAPAPO/MC8K. Manage Demand Planning in mySAP SCM / SAP APO discusses the operation of Demand Planning processes. you can find several Best Practice Documents for Solution Management like this one. or report /SAPAPO/TS_BATCH_LOGFILE.
tips & tricks 180605: Oracle database parameter settings for BW 184905: Collective note Performance BW 2.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3.sap.com/notes) The following SAP Notes contain useful information on the performance of SAP APO: • • • • • 303743: Support Packages for APO Release 3.0A 438712: Support Packages for APO Release 3.2 Please refer to the Best Practice Document dedicated to CIF for SAP Notes with information on qRFC and CIF.0: Data extraction .0 323090: Performance problems due to degenerated indexes 325839: Considerable increase of tablespace PSAPODSD 378509: Oracle DB Parametrisierung für APO 384023: Optimizing performance of ODS objects 400191: Further processing of data from the PSA 409641: Examples of packet size dependency on ROIDOCPRMS 421795: SAP_ANALYZE_ALL_INFOCUBES report 428212: Update of statistics of InfoCubes with BRCONNECT 458077: For all entries: Performance problems in APO Demand Planning 459188: Many small partitions in PSA tables under ORACLE 485878: DB2/390: BW: Partitioning the PSA tables 535986: MONITORING for BW fact tables under Oracle • 558563: How does a client copy work with Demand Planning? The following SAP Notes contain information about the APO Supply Network Planning module including CTM planning: • • • • • • • • • • • 206679: Transfer requirement not physically deleted 332812: Inconsistencies in selection/notes management 358283: Repair tool for existing time series network 359761: Demand Planning: loading performance data 360935: Demand Planning 3. The following SAP Notes contain information about the SAP Business Information Warehouse and the database underlying an SAP APO system: • • • • • • • • • • • • • • • • • • • • 124532: Performance when loading data into BW 115407: Loading large amounts of data 129252: Oracle DB Statistics for BW Tables 130253: Notes on upload of transaction data into the BW 130645: Collective note: Performance SAP BW 130691: Collective note for BW .0A 447708: Composite SAP note about APO system administration • 500843: Composite SAP note for COM and SAP liveCache >= 7.0A Demand Planning © 2004 SAP AG .0: Realignment tool – consulting 363092: Demand Planning: Performance Mass Processing 373756: Data extraction from a planning area 383906: DP 3.0 promotion: Consulting: Reporting 386735: DP: Extract data to an IC with delta update 391625: Backup and Recovery for APO 3.memory problems / COM errors 384550: APO 3.x) / mySAP SCM (4.1 420669: Collective note: General Performance Improvement APO 420594: Collective Note: Performance for DP 3.0) 47 SAP Notes (See also http://service.
0: Release from DP to SNP 412429: Definition of jobs with macros 413526: Consultation: Navigation attributes versus basic characteristics 420927: Data extraction of selected key figures 425825: Consistency checks.x) / mySAP SCM (4.0: 'No liveCache anchor found' 403050: Consulting DP 3. PP/DS planning 529663: Performance during /SAPAPO/TS_LCM_CONS_CHECK 533457: CTM: Deletion of orders without enhanced checks 538046: Checklist transfer planned independent requirement 539797: Collective consulting note on macros 539848: Collective consulting note on background processing in DP 540571: Collective consulting note on data extraction in DP 541189: Collective consulting note on selections in Demand Planning 541252: Collective consulting note for planning book maintenance 541618: Collective consulting note on BW and InfoObjects in DP 541633: Collective consulting note on interactive planning 542946: Error message time series/period pattern does not exist 546079: FAQ: Background jobs in Demand Planning 549184: FAQ: What is important for extraction 568671: Collective consulting note on versions 568669: Collective consulting note on release DP – SNP 570397: Consulting: Workaround . CTM. /sapapo/cif_deltareport 426806: Memory/performance problems during data extraction 428102: Performance: Loading planning area version 428147: Extraction of data from an SNP planning area 430688: CTM: Parallel CTM runs on a planning version 432038: Creating location product to customers and vendors 441723: CTM: Profile dependency of the default rule 443500: R/3 versus APO: Dates in sales orders and deliveries 453278: Analysis tool for export DataSources (Part 3) 482494: Loading data from liveCache: Performance optimization 485018: Info on the Performance of the Optimizer-Interface 492460: Check double entries in planning object structure 495027: Changing delivered APO InfoObjects (9A*) 505886: Performance improvement during drilldown 507810: BW Reporting with SNP RemoteCubes 509479: Elimination of inconsistencies in time series objects 512184: Background processing: Periodically delete job log 512797: Use of alerts in the deployment 514593: Performance improvement with DP background processing 520876: Inconsistencies in time series objects 528913: Lock R/3 data transfer during SNP. /sapapo/om17.Best Practice: Manage Supply Network Planning & CTM in SAP APO (3.0) • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • 393634: Release of the optimization server after 398726: DP 3.Copying Planning Object Structures 571629: How does the note management work? 572220: Avoid use of optimizer runs with the same "names" 48 © 2004 SAP AG .0: performance planning book/data view 401830: Display <=> Change in Interactive Planning 402046: DP 3.
........................24. 33 /SAPAPO/SDP_EXTR .........................19 /SAPAPO/RMSDPDEP .. /sapapo/om17........................................30 /SAPAPO/RMSNPOPT ......... 22......................... 30 /SAPAPO/SNP04.......... 26 /SAPAPO/TS_PAREA_INITIALIZE .............. You can do this at http://service......................... 30...com/message....... /sapapo/cif_deltareport 495166: Tips and Tricks for Handling Alert Monitor 500063: Overview of performance notes for the Alert Monitor 519014: Handling Planning Version Management 521639: Generation of DB Alerts in Background 572003: SCM operating concept Feedback and Questions Send any feedback by formulating an SAP customer message to component SV-GST-SMC.............. 10.................................. 38 /SAPAPO/TS_LCM_REORG............. 29 /SAPAPO/SCC01..... 12 /SAPAPO/OM_REORG_DAILY ....... 10 /SAPAPO/MSDP_SB........................ 31 /SAPAPO/SNP05.. 41 /SAPAPO/TS_BATCH_RUN ...........11................................32 /SAPAPO/RMDPLOPT.... 24 /SAPAPO/TS_GEN_DOCTAB_CHECK ............................... 33 /SAPAPO/C4 ...............................19 /SAPAPO/OPT11 ......... reorganization jobs 139558: Scheduling report /SAPAPO/OM_REORG_DAILY 195157: Application log: Deletion of logs 375965: APO Consulting: Alerts in forecast 425825: Consistency checks..................................... 26 /SAPAPO/SDP94.............................................. 21 /SAPAPO/SNP106.....................................x) / mySAP SCM (4....19 /SAPAPO/RMSNPTLB ....32 /SAPAPO/RLCDELETE...13 /SAPAPO/CIFSTOPQUEUES.................................................................25..................................25............................................... 42 /SAPAPO/AMON_REORG..... 28 /SAPAPO/CIFSTARTQUEUES......19 /SAPAPO/RDMCPPROCESS ...........................................31 /SAPAPO/RRP_NETCH........... Index /SAPAPO/AMON_MAIL_BROADCAST .................................................. 10............. 31 /SAPAPO/TS_BATCH .................. 11 /SAPAPO/RTSINPUT .9..........19 /SAPAPO/OPT12 ..13 /SAPAPO/LCOUT..................23..... 28 /SAPAPO/RLCDEL........... 19 /SAPAPO/SNP2PPDS......19 /SAPAPO/OPT03 .......Best Practice: Manage Supply Network Planning & CTM in SAP APO (3............................................................................ 25................. 33 /SAPAPO/SNP02.......................... 22 /SAPAPO/TS_LCM_CONS_CHECK................................... 21 /SAPAPO/SNPOPLOG..... 11 ............................. 38 /SAPAPO/TS_PAREA_EXTR_MGM. 25...... 40 /SAPAPO/MCPSH_GEN_SELTAB_MGM ............. 40 /SAPAPO/TS_BATCH_LOGFILE ..........sap....0) • • • 572996: Simultaneously started optimization runs 644676: Consulting note on RLCDELETE report 646738: SNP standard planning folder for safety stock planning 49 • 660194: RLCDELETE does not delete the selected orders Please also refer to the following SAP Notes: • • • • • • • • • • 016083: Standard jobs......................23.................. 38 /SAPAPO/TS_LCM_CONS_CHECK_ALL .........23........ 42 /SAPAPO/AMON1 ... 19 /SAPAPO/SNPTLB ......................29 /SAPAPO/MC8x .................................. 29 /SAPAPO/SNP94...................11 /SAPAPO/MSDP_ADMIN................................................13 © 2004 SAP AG /SAPAPO/RSDP_CALC_SAFETY_STOCK.......
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue reading from where you left off, or restart the preview.