Manage Supply Network Planning in MySAP SCM SAP APO (PDF)

Manage Supply Network Planning inmySAP SCM / SAP APO Best Practice for Solution Management Version Date: September 2003 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 ...........................................................................................................................................7 Business Process Step 1: Initialize Planning Version ..................................................................8 Business Process Step 2: Load Data...........................................................................................9 Business Process Step 3: Safety Stock Planning ......................................................................10 Business Process Step 4: SNP Planning Run Heuristic ............................................................11 Business Process Step 5: SNP Planning Run Optimizer...........................................................12 Business Process Step 6: Capacity Leveling.............................................................................14 Business Process Step 7: SNP Interactive Planning .................................................................15 Business Process Step 8: Execute Batch Macros .....................................................................16 Business Process Step 9: Exchange Requirements with Supplier ............................................18 Business Process Step 10: Load Data into BW .........................................................................19 Business Process Step 11: Create/Update Planned Orders, Transfer Orders, and Purchase Requisitions................................................................................................................................21 Business Process Step 12: Release SNP to DP........................................................................22 Business Process Step 14: Deployment Heuristic .....................................................................23 Business Process Step 15: Deployment Optimizer....................................................................24 Business Process Step 16: Transport Load Builder (TLB).........................................................24 Business Process Step 17: Delete Transaction Data.................................................................25 Further Information .................................................................................................................................26 Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 2 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. Alternative Practices 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. © 2003 SAP AG Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 3 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. Preliminary Information 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. OLAP System 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. © 2003 SAP AG Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 4 OLTP System SAP R/3 Plug-In RDBMS SAP APO System live Cache OLTP System OLAP System RDBMS RDBMS 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 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 can be sent into 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 that come out of the supply network planning process are fed into other data processing systems 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 one 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 from any other system type can be connected to the SAP APO system. The results from the demand planning process are processed by another module of the APO system itself, or are transferred to an SAP R/3 OLTP system via the Core Interface CIF. © 2003 SAP AG Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 5 SAP Advanced Planning and Optimization (APO) is the planning component of mySAP SCM. Logistics Execution LES. which contains all functionality for. and operational decisions and supports you in performing the following planning activities: • 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. and so on are performed in the SAP R/3 OLTP system. execution functions. Production Order Processing PP-SFC. for example. purchasing. In standard business scenarios. Material Management MM. production backflush for repetitive manufacturing. SAP APO is used to make strategic. goods receipt. such as confirmations. the Supply Chain Management solution provided by SAP. and Controlling CO. Sales and Distribution SD. among many others. tactical. © 2003 SAP AG . although some industry specific execution functions are available. a planning area and planning version must be created and initialized. and the result rechecked in interactive planning. depending on which safety stock planning method used. though it is also based on the mySAP SCM solution. After the run is complete. The planning version can consist of order key figures. At this point. Before data can be loaded into Supply Network Planning. by transferring data from BW through the APO data mart into an SNP planning area.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 6 Supply Network Planning The core business process you run in your company for planning your supply network. time series key figures. or from a flat file using a BAPI. depending on the size of the problem and whether they can meet their needs with the finite planning considered by the Heuristic. it is calculated by a macro during the heuristic or optimizer run. In other cases. customers perform a variety of tasks with © 2003 SAP AG . data can be loaded into SNP in several ways: by releasing a forecast from Demand Planning. Description: The process flow above describes a typical SNP process flow. Capacity Leveling is often performed on bottleneck resources to ensure that a feasible plan is created. Most customers then run either the SNP Optimizer or the SNP Heuristic. After initialization. If the SNP Heuristic has been run. may differ more or less from the canonical process described as follows and illustrated on the next page. 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. possibly using alerts. planners usually check the results in interactive planning. or both. by CIF transfer from R/3. and escalation • A monitoring object table. the monitoring frequency can be decreased. listing each relevant monitoring object. Regular jobs of minor priority.either a heuristic or an optimizer are available . it uses algorithms similar to the SNP heuristic or optimizer. Restartability and Escalation. you will find the following information: • A detailed functional description of the process step • Monitoring activities for the process step • Error handling. For status “cancelled”. and used in evaluating the feasibility of a forecast. After the PP/DS run occurs. the constrained forecast calculated by SNP can be released back to DP. 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 other cases. single-location planning is performed. and escalation paths (teams) for the monitoring activities associated with each business-process step and its monitoring objects. From there it can either be saved on the APO system or transferred to a BW system for reporting.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 7 batch macros: these can be used to generate alerts and perform further calculations on the data. error occurrences. and application operations. This concept consists of monitoring activities to be performed for each business-process step and its respective monitoring objects. Many SNP process flows then exchange requirements with suppliers.can be used to plan transfers of single location-products from one location to another. with transaction SM37 by entering the time interval since the latest check and selecting all jobs with status “cancelled”. responsible teams. where a more detailed. During the Going Live and stabilization phase of your APO implementation project. can be checked less frequently than the actual scheduled run times. you must specify the times. you create a company-specific process-oriented monitoring concept. and to implement fair share rules. At some point in the planning flow. In some cases. certain clean-up jobs. You should investigate and correct these terminations appropriately. restartability. a detailed transport load is needed to account for lot sizing and to ensure that loading of the transportation resources for multiple products is feasible. For example. showing the: o Monitoring object o Monitoring transaction or tool o Monitoring frequency o Monitoring time (intentionally left blank. the monitoring frequency in these monitoring object tables is partly only a rough estimate and has to be adapted to your particular business process. This check can be done easily. Some comment is also needed about the use of /SAPAPO/RLCDELETE: since SNP alone is not an execution system. all items listed in this document should be monitored tightly. daily jobs can be checked weekly. When adapting this concept for your company. If you have no automatic notification in place that informs the people responsible for Program Scheduling Management in your © 2003 SAP AG . Planning results can also be sent to R/3 using the CIF interface. see Error Handling. where the planned orders and purchase order produced by SNP planning are then further processed using MRP. After becoming more experienced with system behavior. many SNP users back up some of the key figures into an InfoCube in the APO data mart. but should never be reduced to zero unless you do not use the respective function. Still another use for the SNP data is to transfer it to PP/DS.often using collaborative planning. it is essential that you check all jobs that are running in your system at least several times per day for abnormal terminations. for instance. 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. While deployment is a short-term planning. The following seems obvious but should nevertheless be mentioned: Besides the monitoring of jobs described in the business process steps below. Important planning jobs usually have to be monitored after each run. so it is classed within SNP. In each of the business process steps described below. for example. Procedure In applying this Best Practice procedure. the deployment algorithms . the planning version must be initialized for an SNP planning area. When you need to change the validity period on a planning area with time series objects. the jobs for deleting outdated jobs or spool objects. and choose “Create Time Series”. it is preferable to use the option “Execute in Background”. 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. in most cases. For order objects only. or whether some or all key figures are time series key figures. right click on the planning area. Then enter the existing planning version and the new start and end dates for the time series that are desired. Monitoring Object Monitor Monitor TA/Tool Freq. A number of jobs must run periodically in a live R/3 installation. monitor the messages in the job log to ensure that no errors occurred Application support Contact process champion See general issues of Error Handling. Initialize planning version Report /SAPAP O/TS_L CM_CO NS_CH ECK Initialize planning version Initialize planning version Monit or Time Indicator or Error Monitoring Activity or Error Handling Procedure As often as you change master data Status 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 Contact application support SM37 Depending on business process Status Ensure that job completes successfully Program scheduling management Contact application support SM37 Depending on business process Status/mes sages Whether or not the job completes successfully. you need to take measures to ensure that this is done manually in a reliable and timely manner. For planning versions with significant amounts of master data.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 8 Support Organization of abnormally terminated jobs. Right click on the planning area. © 2003 SAP AG Responsibility Escalation Procedure . for example. both so that the program will not time out and so that the monitoring tools of SM37 are available. see SAP Note 16083. Business Process Step 1: Initialize Planning Version Before a new planning version can be used in SNP. choose “initialize planning version”. 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. initializing the planning area is straightforward: execute transaction /SAPAPO/MSDP_ADMIN and find the planning area of interest. Restartability and Escalation below. the standard 9ASNP02 is used for order objects. For details and comments. Monitoring Activities Jobs for Running and Monitoring "Initialize Planning Version" (APO) If the planning area used for SNP contains time series key figures. you should periodically check for inconsistent time series objects using report /SAPAPO/TS_LCM_CONS_CHECK_ALL or /SAPAPO/TS_LCM_CONS_CHECK. select the “execute in background” option. How the planning area is initialized depends on whether it contains only order objects. simply enter transaction /SAPAPO/MSDP_ADMIN. General information on handling problems with version management is available in SAP Note 519014. For large data volumes. Type in the name of the planning version. and execute. SAP Note 358283 gives a description of the report. please read Note 332812 carefully before using this report to automatically correct inconsistencies. All CIF data interchanges should also be monitored as described in the Manage APO Core Interface in mySAP SCM. Restartability and Escalation below. and SAP R/3 OLTP. The consistency check should also be executed if the master data are changed in APO but not visible or accessible via SNP. When the planning area contains time series key figures. 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. If large amounts of data are loaded by BAPI. 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. SAP BW. When the planning area does not contain any time series key figures. the consistency check report can be used in repair mode.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 9 Business Process Step 2: Load Data Depending upon your business process. Monitoring Activities Apart from safeguarding the general availability and consistency of the system components SAP APO. you need to regularly check and update the selection data tables for the Planning Area(s) used for SNP. Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. After loading new master data. by running report /SAPAPO/TS_PAREA_INITIALIZE. it may be that you periodically load either only transactional data or both master data changes and transactional data into SNP. If this is the case. In some cases. If new master data are loaded into a model. Transactional data is usually loaded into SNP by a release from Demand Planning to SNP. To do this. Time or Error Monitoring Activity or Error Handling Procedure Master data /SAPAP When O/CON data are SCHK modified Messages Check log of consistency Application check for master data objects support team that display inconsistencies. Contact process champion Master Data /SAPAP When O/CON data are SSHOW modified Messages Check log of consistency check Contact process champion See general issues ofError Handling. Ensure that only delta records are loaded by the BAPI. master data changes are sent by CIF from R/3 to SNP. execute report /SAPAPO/MCPSH_GEN_SELTAB_MGM. © 2003 SAP AG Responsibility Application support team Escalation Procedure . However. The profile used should be restricted to the functionality and data which you are actually using. to safeguard this business step SAP recommends that you monitor the objects listed in the following table. the data must be initialized for SNP planning. this has to be done by reinitializing the SNP planning area in /SAPAPO/MSDP_ADMIN or alternatively. which is described in the Best Practice Manage Demand Planning in mySAP SCM / SAP APO. in addition to functions for adding and deleting the functions. Additionally. For additional information see SAP Note 577038. Some customers also load data using a BAPI. this can either be done by reinitializing the SNP planning area or automatically by starting SNP interactive planning or SNP mass processing. Safety stock calculations for different location products are independent of each other. the methods will not calculate any reasonable values. When checking the job in SM37. MB. © 2003 SAP AG . no demand gets lost (backorder case). MZ. If you need to improve performance. to avoid lock issues. for example. which should be corrected by the application support team.e. In this context. Spare parts is a business area that usually does not meet this assumption. also look for large values in the field Delay(sec). the missing parts can always be delivered belatedly. Advanced methods are performed in report /SAPAPO/RSDP_CALC_SAFETY_STOCK (transaction: /SAPAPO/MSDP_SB). ƒ If neither regular stock nor safety stock suffice to cover the whole demand. you can execute parallel processing by creating separate variants for transaction /SAPAPO/MSDP_SB and run them at the same time. Monitoring Activities The monitoring activities needed to ensure that safety stock planning runs are executed correctly are indicated in the table below. For such location products no safety stock can be planned since there is no way to procure it. a cycle is a sequence of PPMs and/or transportation lanes that transform a location product on to its self. Jobs for Running and Monitoring "Safety Stock Planning" To ensure consistency and good performance of safety stock calculations. Also make sure that the supply chain does not contain "cycles" for the location products to be planned. in addition to looking for jobs which cancelled. rush shipments (no delay approach). and make a note of which other processes were running concurrently. AS. This report calculates the safety stock associated with reorder point methods (either alpha or beta service level. the demand quantities are significantly greater than zero and do not fluctuate too much between planning periods. which might indicate that the job had to wait for another process to release locked data. When checking the spool file. In general. the remainder is made available using alternative arrangements. there is demand in almost every planning period. the error is caused by a location product with procurement type E (in-house production) for which there is no valid PPM. and MM) and advanced methods (AT. The advanced safety stock methods used in SNP are based on the following assumptions (see also note 617567): ƒ Demand is regular. Therefore. SZ. In extreme cases.” This indicates an error in the procurement type for the location product. SM. Most commonly. i.. 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. In the remainder of this section. look especially for messages in the form of: "Product &1 in location &2 cannot be procured. ƒ In case of shortage. Please also consider notes 599871 and 600766. schedule the following jobs to run on a regular basis: • Calculate safety stocks with advanced methods with report /SAPAPO/RSDP_CALC_SAFETY_STOCK. BT. Standard methods are performed in macro SAFETY_CALC.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 10 Business Process Step 3: Safety Stock Planning There are two types of safety stock methods in SNP: standard methods (SB. If such cycles exist Safety Stock Planning will be caught in an endless loop unless note 547049 has been applied. it is advisable not to make changes to the SNP planning version in which safety stock is run.. see note 504253 for an introduction. ƒ All uncertainties in the supply chain are statistically independent of each other. the order of calculations is arbitrary.e. only advanced methods are considered. i. reorder cycle or reorder point). BS). during the heuristic run. This should prevent inconsistencies occurring in the planning if. locks on the APO database can be seen with transaction SM12. and it waited for the other process to finish. unless the number of location products is high and the number of changing demands is comparatively small. Look for large values of Delay (sec) in SM37. The entries of objects flagged for net change planning can be viewed from transaction /SAPAPO/RRP_NETCH. Program scheduling management Contact application support If the report is not scheduled as provided by Application Support. it is recommended that you investigate the possibility that another process (or several parallel jobs) are locking one another. • To lock outbound queues. during the heuristic run. you can lock inbound or outbound queues in the SAP R/3 system from the SAP APO system. Time or Error APO Report SM37 /SAPAPO/RS DP_CALC_SA FETY_STOCK Each time the report is run 11 Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure Check spool file for errors. © 2003 SAP AG . Program scheduling management Contact application support team. Network (all locations. which can cause inconsistencies if not corrected. Reports RSTRFCI1 and RSTRFCI3 are available for locking inbound queues. Business Process Step 4: SNP Planning Run Heuristic The SNP heuristic performs infinite planning for the supply chain. Fortunately. schedule it accordingly. Monitoring Object Monitor Monitor TA/Tool Freq. the length of data fields in report variants can change.large values may indicate that another process was locking the job. APO report /SAPAPO/RS NPDRP1 SM37 This report performs the SNP heuristic run. See also SAP note 487261 / 528913. Monitoring Activities Regarding SM37: when several heuristics identify large values of “Delay(sec)”. 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. If the heuristic run is executed in Version 000. Also check the column “Delay(sec). It can be run in one of three modes: Multilevel (all products at all locations). transaction data is transferred from SAP R/3 to SAP APO that is ignored by the heuristic. 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). but a full BOM explosion takes place). but BOM is only exploded to one level) or Location (all products at one location. While the processes are running. Restartability and Escalation below. Depends on business process Monit or Time Indicator or Error Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure Status Check if job is running as scheduled. See general issues of Error Handling. this problem can be alleviated by running report RSVCHECK after implementation of a new support package.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. with the import of a support package. Net change planning is only available in the active version (000). Occasionally. Use of the Net Change planning flag is not recommended. you can use the /SAPAPO/CIFSTOPQUEUES and /SAPAPO/CIFSTARTQUEUES reports in SAP APO. Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO Monitoring Object Monitor Monitor TA/Tool Freq. Monitoring Activities The following table describes how to monitor and ensure the correct functionality of the optimizer run. simply set the field “Number of Processes” in the background transactions for the optimizers. Also ensure that you have applied Note 572220 (APO 3. be sure to set the parameter enque/delay_max in transaction RZ11 as described in consulting note 572996 to avoid lock problems. © 2003 SAP AG . each with a quantity of 1 for the same locationproduct on the same date) Application Support Contact process champion Once a month. many orders. refer to the monitoring jobs in the table below. the optimizer run must be manually deleted in transaction /SAPAPO/OPT03 before another run can be started. 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. Jobs for Running and Monitoring "SNP Optimizer" and “Deployment Optimizer” (APO) To safeguard the continued functionality of the optimizer. Business Process Step 5: SNP Planning Run Optimizer The CIF Queues should be locked during the execution of the planning run to prevent inconsistencies. refer to the section Monitoring APO Optimizers in the Best Practice: Monitoring and Administration for SCM/APO. but NEVER concurrently with optimizer runs. If several optimization runs are made in parallel. Please see SAP Note 528913 for a full discussion. It will spawn parallel processes during some portions of the data read and model creation of the optimization run. To get an overview of the optimization system steps.g. Note that this does not apply if the optimizer is executed on an inactive planning version. refer to note 485018. we must also think about the model size and complexity. or strange results (e. For an optimal performance of the optimization engine. They are also deleted by the job /SAPAPO/OM_REORG_DAILY.1A SP13) to prevent loss of optimizer result logs. or after importing new support packages List of variants with problems Check if any variants have problems Program scheduling management Contact application support See general issues of Error Handling.0A. which should be run once a day. APO 3. • To run the optimizer in the background: use for SNP report /SAPAPO/RMSNPOPT and Deployment report /SAPAPO/RMDPLOPT. see note 454433. refer to note 587407. Also note that you should upgrade your optimizer in parallel with support package upgrades to ensure optimal functionality and performance. Spool file of report /SAPAPO/RS NPDRP1 SM37 Report variants RSVCH ECK Monit or Time 12 Indicator or Error Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure As often as heuristic is executed Log file Check whether the spool file has any error messages. In the event of a short dump during the optimizer run. SP23. To improve the performance of an optimization run. See Note 393634 for details. if you ever run two optimizer runs simultaneously. in addition. For an additional list of transactions used to help set up the optimizer during installation or changes to the optimizer server. Restartability and Escalation below. In addition. they should never have the same names. Due to the runtime and memory requirements of the optimization engine. also for Deployment Transac After tion every run /SAPAP O/SNP1 06 Results summary of the SNP Optimizer Check for reasonability of the Application results: e. and the optimizer logs in /SAPAPO/SNPOPLOG and /SAPAPO/OPT11. schedule it accordingly. and the resulting costs from the optimization run /SAPAPO/SNP106 to verify that the run was executed without problems..g. Contact Process Champion /SAPAPO/OM /SAPAP _REORG_DAI O/OM_ LY REORG _DAILY During installatio n or after config changes Among its other activities. if there is no result delivered from the optimizer. monitoring team Spool file of optimizer run SM37 After every run Messages in spool file Also check for application errors after the optimizer run. • After the planning run is finished: use transactions sm37. Program scheduling management Contact application support Contact process champion If the report is not scheduled as provided by Application Support.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 13 • 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. Application support Contact Process Champion SNP Optimizer Resulting Costs. Deployment: /SAPAPO/RM DPLOPT This report runs the optimizer in the background Optimizer log /SAPAP O/SNP OPLOG After every run Status Review messages in log with red or yellow status Application support Verify and maintain RFC connections SM59 During installatio n or after config changes Status Check that the TCP/IP connection to the optimizer server is open and functioning correctly. Program Contact scheduling software management. It is recommended that these be checked periodically to ensure that everything is functioning as expected. and that the results are as expected. Program this job will delete database scheduling entries and files on the management optimizer server which are no longer needed. Monitoring Object Monitor Monitor TA/Tool Freq. Status Check if job is running as scheduled. System and application monitoring teams Depending on error type: system or application monitoring team User list for Optimizers /SAPAP As O/OPT0 required 3 Displays a user list of optimization runs Basis support Contact application team © 2003 SAP AG Check for errors . APO report SNP: /SAPAPO/RM SNPOPT SM37 Monitor Time Indicator or Error Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure Dependi ng on your process. whether the support optimizer run has decided not to produce anything. Contact software monitoring team Consistency check /SAPAP O/CON SCHK After each change to master data This job will identify any inconsistent data prior to running the optimizer run Application support Contact process champion Optimizer Logs /SAPAP As O/OPT1 required 1 Display and analyze logs in this section. including full documentation. Click on the icon "Capacity Leveling" in Capacity View. Run directly executable macros to measure capacity under load and overload situations. optimizer.1 as of SP15 as an alternative to the original version. Capacity leveling in interactive planning Alerts Capacity run in background (new version) SM37 Monit or Time Indicator or Error Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure Depends on business process Alerts Look for fields which are colored red due to exceptional resource situations. Business Process Step 6: Capacity Leveling The SNP heuristic performs only infinite planning: that is. 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. without considering the available capacities of resources. The new version can also be executed as a background job using transaction /SAPAPO/SNP05. Among other features. Restartability and Escalation below. 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. If the Capacity View shows any resource overloads click on the Capacity Leveling icon in change mode. • Capacity Leveling in Background (new version only): in addition to launching the job. performance. you can select those planning periods and/or products that should be processed. Program scheduling management Contact application support team See general issues of Error Handling. can be found in release note 564702. • Capacity Leveling: execute transaction /SAPAPO/SNP94 and change to data view SNP94(2). © 2003 SAP AG . the new version offers three different leveling methods . In addition. If necessary. you should monitor the job using SM37. Application support team Contact process champion Depends on business process Status Ensure that job is scheduled and runs without error. The new version is also available in APO 3. For performance.Due to the improvements made in Capacity Leveling regarding result quality. Monitoring Activities for Capacity Leveling Jobs for Running and Monitoring "Capacity Leveling" (APO) The following table describes how to monitor the capacity run.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO Monitoring Object Monitor Monitor TA/Tool Freq. It is activated by creating a user parameter /SAPAPO/SNPCAP with value 'X'. consider the recommendations in Note 493258. and use macro function ACT_VERSION instead of macro function KEYFS_VERSION.0. Running optimizer processes /SAPAP As O/OPT1 required 2 Monitor Time Indicator or Error 14 Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure Displays a list of optimizer processes on the optimization server Basis support Contact application team See general issues of Error Handling. and BADI. Both versions can be executed interactively from transaction /SAPAPO/SNP94.heuristic. Further information on the new version. Use an auxiliary table rather than the macro function for getting the date. In order to create a feasible plan. Monitoring Object Monitor Monitor TA/Tool Freq.0 as of SP 22 and in APO 3. Restartability and Escalation below. SNP Capacity Leveling underwent a complete redesign in SCM 4. 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. and aggregation. you can do almost everything that SAP APO Supply Network Planning offers. • Implement composite time bucket profiles with coarser time buckets in the long-term past and future. SNP interactive planning defaults to “display” mode when a user enters. mails are sent with an overview of existing alerts. and SAP R/3 OLTP. As described in Note 401830. In addition. macros. Also. Jobs for Running and Monitoring "SNP Interactive Planning (APO)" To ensure a timely and efficient notification of exceptions in Supply Network Planning. In particular. However. investigate the reasons for the alerts and take corrective actions in order to keep the production plan close to the needs of your company. showing a year as 9 weeks and 10 months will dramatically improve the performance without decreasing the time period shown. for instance. SAP BW. While tables of selection variants are usually not a problem in release 3. users who perform more than one task type should consider creating more than one planning book to accommodate each task type. please read Note 332812 carefully before using this report to automatically correct inconsistencies. Supply Network Planning supports online simulation in multiple planning scenarios. • Minimize the number of default macros used for SDP interactive planning. because they take place at a certain point in the business cycle where real-time feedback to online users is not required. The responsible persons then should call up the APO Alert Monitor. If you are using notes management within interactive planning. 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. you can evaluate planning results. when a user switches from display to change mode. run macros. it is possible to write a BADI to override the default display.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 15 Business Process Step 7: SNP Interactive Planning Within transaction /SAPAPO/SNP94. This is independent of when this planning step takes place. 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. end. You might want to do this for a number of reasons. any interactive processing of data should be restricted to very small data volumes by specifying the selection criteria as far as possible. SAP recommends that you monitor the objects listed in the following table in order to safeguard this business step. consistent planning throughout your enterprise. Monitoring Activities Apart from safeguarding the general availability and consistency of the system components SAP APO. For performance reasons. © 2003 SAP AG . and any other views that are used by that individual user. In addition. you may wish to define one or more separate planning books for use with SNP interactive planning. should be performed as batch jobs rather than interactively.0A and higher. aggregate data. Tasks that can be performed without direct user interaction. 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. Depending on user profiles. drilling up and down. we also recommend periodically executing report /SAPAPO/TS_GEN_DOCTAB_CHECK to eliminate possible inconsistencies in the notes. periodically deleting unused selections may become necessary. and fine time buckets only near the present time. Please note that. In some cases. For systems with large numbers of interactive users. enter management overwrites. a description of monitoring and managing them is given in Note 376383. for instance before or after a planning run. compare different scenarios. or drill-down macros. schedule the following jobs to run on a regular basis: • Send Alert Monitor mails with report /SAPAPO/AMON_MAIL_BROADCAST. for example. for performance reasons. correct key figures manually. see if any of these can be executed less frequently as start. and create or view alerts. For example. • 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. the data must be reread to set the appropriate locks. key figures. or to calculate additional quantities and save them to time series key figures. and a different data view whenever the time periods are different. • Remove all unused macros from planning books associated with mass processing jobs. Program scheduling management Contact software monitoring team Daily Status If the report is not scheduled on a regular basis. as they can be very performance-intensive and are not helpful to your business process. Contact application support If the job is not scheduled on a regular basis. The planning book should only contain one planning view. • The planning book used for batch macros should have only the functionality it uses: in the case of SNP macros. it is often desirable to monitor alert situations or calculate quantities in time series key figures using batch macros run in SNP Planning Areas. the usual reasons for creating batch macros are either to perform calculations and evaluations of alert situations. Restartability and Escalation below. Program scheduling management See general issues of Error Handling. Information on database alerts and dynamic alerts in Demand Planning can be seen in the APO Alert Monitor and below. the planning book should have no macros selected. at least daily. It deletes old alerts and is of particular importance if you use alerts stored in the database. and only macros executed as activities by the mass processing job.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO • 16 Delete Alert Monitor alerts with report /SAPAPO/AMON_REORG. Time or Error Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure APO Alert Monitor /SAPAP At least O/AMO daily N1 Check for forecast alerts and SDP alerts and correct the planning for the reported object appropriately. Application support Contact process champion APO report /SAPAPO/AM ON_MAIL_BR OADCAST SM37 Check if job is running as scheduled. This report ensures sending of mails about existing alerts. Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. depending on your requirements. The planning book should contain only key figures used by the macro itself. After the planning run and manual adjustment. © 2003 SAP AG . Some hints on the design and usage of macros for batch processing: • Create a separate planning book for each macro background job. A different planning book should be used whenever different key figures are needed by two macros. Contact process champion Check if job is running as scheduled. Status Check if the mail lists alerts Application that are important for you. Business Process Step 8: Execute Batch Macros In SNP. For manual corrections see Business Process Step 7: SNP Interactive Planning. schedule it to run from between every hour to at least daily. SM37 Weekly This report deletes Alert Monitor alerts. Go support to APO Alert Monitor and process the alerts appropriately. Alert Monitor mails SO01 (or respecti ve email system) Dependi ng on your require ments. schedule it to run once a day. APO report /SAPAPO/AM ON_REORG. please refer to consulting Note 521639. you do not need automatic macro execution for mass processing jobs.particularly those related to Deployment and TLB . see below). and “Add” rather than “Update in Context” whenever possible. You thus save the time needed for loading the data again. schedule it accordingly. and only in the planning book for the mass processing job in which they are used. as this can cause lock issues. /SAPAP After O/MC8 each K run of /SAPAP O/TS_B ATCH_ RUN. SAP BW. For dependencies and concurrent execution of jobs. such as adjusting data released from DP to SNP. Accordingly. In general. Furthermore. SDP Job Log Dependi ng on your process. © 2003 SAP AG Status Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure Check if job is running as scheduled. and SAP R/3 OLTP.may be executed as often as daily. see Operational Management – Parallel and Concurrent Execution of Jobs. Red or According to the warning or yellow error reported (see message traffic lights long text). try to use “Delete” rather than “Delete in Context”. and exit. Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. Monitoring Activities Apart from safeguarding the general availability and consistency of the system components SAP APO. Program scheduling management Contact application support Application support Contact process champion If the report is not scheduled as provided by Application Support. This report performs specified SDP mass processing activities.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO • • • • • 17 All macros in mass processing should be defined as manually executable. Please also refer to Exception based Monitoring of APO Supply Network Planning for the handling of alerts generated by a batch macro. Time or Error SM37 APO report /SAPAPO/TS_ BATCH_RUN. The frequency of executing these Supply Network Planning batch jobs can vary significantly depending upon the business process for which the scenario is built. loading a selection. use database alerts rather than dynamic alerts. minimize the number of steps which manipulate alerts. When reading and writing alerts from the alert table in the APO database (table /SAPAPO/AM_ALERT). may only be executed once a month. Make sure that no individual location product belongs to more than one selection variant. to safeguard this business step SAP recommends that you monitor the objects listed in the following table. Create several background jobs with roughly equal numbers of location products and run them in parallel. the frequency of monitoring the jobs and deleting the SDP Job Logs depends on how often you run these functions. For general advice on creating alerts in background jobs. If you need to run two macros on the same key figures with the same level of aggregation. changing data. Macros that check for alert situations . since default macros are executed upon entry. Also. put both into one planning book and execute them as two actions within the same background activity (defined with transaction /SAPAPO/MC8T. shown . For the high data volumes usually considered in background processing. defining macros as default macros and to be executed at another time is redundant and extremely performanceintensive. while other jobs. Program scheduling management Contact software monitoring team Program scheduling management Contact software monitoring team. such as planned orders. schedule it accordingly. If the report is not scheduled as provided by Application Support. 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. rather than immediately after planning is complete. Notes 443500. • Check Processing of APO Change Pointers with report /SAPAPO/RDMCPPROCESS. 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. please refer to the corresponding documentation on CIF functionality regarding transactional data transfers between R/3 and APO. If the report is not scheduled as provided by Application Support. are sent to R/3. 18 Check if job is running as scheduled. These jobs are: • Publish Planning Results with report /SAPAPO/RDMCPPROCESS. section Operation and Monitoring of the APO Core Interface. certain jobs must be scheduled on a regular basis. Business Process Step 9: Exchange Requirements with Supplier In some cases. as is the default setting in PP/DS.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. Status APO report /SAPAPO/AM ON_REORG SM37 Dependi ng on your process Status This report deletes old database alerts of various types. contact the application support team to clarify whether these change pointers are needed and why they are not processed. This report evaluates the APO change pointers (not the same as ALE change pointers!) that are written during planning activities. for example. and are user specific. If change pointers remain unprocessed. but must either specify the full user ID or user entry ‘*’ for all users not explicitly specified. This report deletes old SDP Job Logs. See general issues of Error Handling. while the information is user specific. Restartability and Escalation below. Note that. as the corresponding order changes are not transferred to R/3. you cannot use wild cards here. schedule it accordingly. The corresponding objects. 206679. it is usual to transfer the data periodically. In addition. and 432038. © 2003 SAP AG . Note: Deleting change pointers may cause inconsistencies. In SNP. These settings are maintained in transaction /SAPAPO/C4. This report verifies that all change pointers are processed by checking that the list displayed in the report /SAPAPO/RDMCPPROCESS is empty. Time or Error SM37 APO report /SAPAPO/TS_ BATCH_LOG FILE Dependi ng on your process. • The jobs mentioned in the Manage APO Core Interface in mySAP SCM. it is desirable to exchange requirements with suppliers. Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure Check if job is running as scheduled. Monitoring Activities Apart from safeguarding the general availability and consistency of the system components SAP APO.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. Check if job is running as scheduled. which should be used exclusively for APO purposes. 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. which discusses limitations of this functionality in detail. Please also refer to SAP Note 323090. For SAP © 2003 SAP AG . every SAP APO system comprises a complete SAP Business Information Warehouse System (BW).0A and onwards (affects SAP APO 4. In order to load the data into BW. SAP DB or IBM DB2 UDB (DB6) database (refer to SAP Notes 16083 and 421795). Please see SAP Notes 129252 (Oracle) or 328106 (DB6). schedule it accordingly. The function of creating. and that liveCache data structures (time series) are kept consistent.0B Support Package 17 please notice the dependency to running SAPDBA (optimizer statistics for non-BW tables) described in SAP Note 129252. to safeguard this business step SAP recommends that you monitor the objects listed under Monitoring of Business Warehouse Activities. Business Process Step 10: Load Data into BW As mentioned above. Note 507810 describes the complete procedure for performing BW reporting on SNP remote cubes. From this report. all periodic monitoring tasks have to be performed in the APO system as well as job definition and most of the configuration tasks. For SAP BW releases prior to 2. For SAP BW releases 3. Program scheduling management Contact Application Support. a background job for the extraction can be generated. In addition.0) the InfoCube statistics can be computed using the BRCONNECT tool as well as the ‘normal’ database statistics. 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). which will run report /SAPAPO/TS_PAREA_TO_ICUBE. and SAP R/3 OLTP. or at least once a week Status Weekly Status 19 Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure Check if job is running as scheduled. APO Report SM37 /SAPAPO/RD MCPPROCES S to display change pointers Dependi ng on your needs. Restartability and Escalation below. This is only relevant for systems running with Oracle. See general issues of Error Handling. schedule the following jobs to run on a regular basis: • Compute Histograms for BW InfoCubes with report SAP_ANALYZE_ALL_INFOCUBES. a consistency check and test for the remote cube are available through this functionality. This report is described in Note 453278. 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. schedule the job daily. SAP BW. Program scheduling management Contact Application Support If the report is not scheduled as provided by Application Support. Time or Error SM37 APO Report /SAPAPO/RD MCPPROCES S This report publishes the results of automatic and interactive planning to R/3. Please refer to Note 428147. This report creates DB statistics for all InfoCubes. Program scheduling management Contact software monitoring team Software monitoring team Contact application support If the job is not scheduled on a regular basis.10) this is not recommended.x (affects APO 3. © 2003 SAP AG . If the traffic light gets yellow or red. See general issues of Error Handling. Only for systems running with Oracle. Weekly Status Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure Check if job is running as scheduled. Indices of APO InfoCubes. Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. RSA1 or Weekly RSRV Red or yellow traffic light Select Check (Aggregate) Indexes. schedule it to run once a week with parameter percent = 100. Restartability and Escalation below. SAP DB or IBM DB2/UDB (DB6) database. select Repair Indexes (now) or Delete Index (batch) and Create Index (batch).Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 20 BW releases 2. Time or Error APO report SM37 SAP_ANALYZ E_ALL_INFO CUBES.0A and 3. Please refer to SAP Notes 428212 and 535986 for details. © 2003 SAP AG . while the information is user specific. Please note that not all order types may be transferred from R/3 to SNP. planned independent requirements may only be transferred from APO to R/3. schedule it accordingly. This report evaluates the APO change pointers (not the same as ALE change pointers!) that are written during planning activities. capacity leveling has been performed. This report verifies that all change pointers are processed by checking that the list displayed in the report /SAPAPO/RDMCPPROCESS is empty. In addition. APO Report SM37 /SAPAPO/RD MCPPROCES S to display change pointers Dependi ng on your needs. or at least once a week Status Weekly Status Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure Check if job is running as scheduled. Program scheduling management Contact Application Support If the report is not scheduled as provided by Application Support. contact the application support team to clarify whether these change pointers are needed and why they are not processed. Note 538046). and not in the other direction (cf. 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. For SNP planned orders only some manual changes are transferred from R/3 to APO: changes to output quantity. schedule the job daily. and Purchase Requisitions After the planning runs are complete. These jobs are: • Publish Planning Results with report /SAPAPO/RDMCPPROCESS. Restartability and Escalation below. the planned orders. See general issues of Error Handling. you cannot use wild cards here. if necessary. and.e. as the corresponding order changes are not transferred to R/3. section Operation and Monitoring of the APO Core Interface.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 21 Business Process Step 11: Create/Update Planned Orders. • The jobs mentioned in the Manage APO Core Interface in mySAP SCM. please refer to the corresponding documentation on CIF functionality regarding transactional data transfers between R/3 and APO. These settings are maintained in transaction /SAPAPO/C4. If change pointers remain unprocessed. are sent to R/3. If job is not scheduled on a regular basis and periodic publishing of data to R/3 is performed on the system. availability date and order fixing. Program scheduling management Contact Application Support. Note: Deleting change pointers may cause inconsistencies. • Check Processing of APO Change Pointers with report /SAPAPO/RDMCPPROCESS. The corresponding objects. In particular. rather than immediately after planning is complete. and purchase requisitions. such as planned orders. it is usual to transfer the data periodically. many customers update the results of SNP i. Transfer Orders. but must either specify the full user ID or user entry ‘*’ for all users not explicitly specified. Note that. In SNP. Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. certain jobs must be scheduled on a regular basis. as is the default setting in PP/DS. Check if job is running as scheduled. Time or Error SM37 APO Report /SAPAPO/RD MCPPROCES S This report publishes the results of automatic and interactive planning to R/3. and are user specific. transfer orders. it should be run with logging set to normal. SAP recommends that you monitor the objects listed in the following table in order to safeguard this business step. SM37 Check if job is running as scheduled. and SAP R/3 OLTP. If the job is not scheduled as provided by Application Support. Program scheduling management Contact application support This report copies the quantity stored in an SNP Order Key Figure into a DP time series key figure Output of APO SP01 report /SAPAPO/RT SINPUT.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 22 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. Check the spool file to ensure Application that all records passed have support a green status light. Contact Process Champion See general issues of Error Handling. i. we recommend the reports listed below. In order to transfer orders within the production horizon from SNP into PP/DS. by following the © 2003 SAP AG . Business Process Step 13: Release SNP to PP/DS Many customers using SNP or CTM also use the PP/DS planning functionality. With this report. 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. it indicates an error. you can release the quantities stored in SNP order objects into DP time series key figures. If red or yellow traffic lights occur. schedule it accordingly. SAP BW. or for individual product-locations. Dependi ng on your process Status After each run Messages in spool list. Jobs for Running and Monitoring "Release SNP to DP (APO)" To release the constrained Demand Plan back to DP. This converts the SNP orders for the specified location product(s) within the production horizon into PP/DS orders. Note that at this point in time. Jobs for Running and Monitoring "Release SNP to PP/DS (APO)" To convert SNP/CTM orders into PP/DS orders: • Release SNP Orders to PP/DS with report /SAPAPO/RRP_SNP2PPDS. releases from SNP to PP/DS may only be executed within the same planning version. Monitoring Activities Apart from safeguarding the general availability and consistency of the system components SAP APO. Time or Error Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure APO report /SAPAPO/RT SINPUT. The conversion can be done in one of two ways: either using a mass conversion report launched from transaction /SAPAPO/SNP2PPDS. When this report is run. Monitoring Activities In order to safeguard the functionality of releasing SNP to PP/DS. No reverse location or product split is possible. using the online transaction /SAPAPO/RRP_SNP2PPDS. Restartability and Escalation below. Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq.e. an explicit order conversion needs to be executed. Restartability and Escalation below. which govern how the orders will be distributed across the network in cases of over.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 23 path Settings-> Planning Log. 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. be sure to delete the old ones regularly using report /SAPAPO/AMON_REORG with appropriate filters. 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. Whether or not the job Application finishes without error. The distribution methods and fair share rules are described in detail in the deployment section of the APO documentation. Note that parallel processing is possible for variants which contain no overlap in location-product or resources used. deployment determines which requirements can be fulfilled by the existing supply. which creates deployment stock transfers. Program scheduling management Contact application support If the job is not scheduled as provided by Application Support. you should save one or more variants and execute them in the background. If you are not monitoring this alert type as part of your business process. If you are using these alerts. After production is complete. Business Process Step 14: Deployment Heuristic The purpose of deployment is to calculate replenishment for one product at one location at a time. turn off the alerts as described in Note 512797. Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. messages Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure Check if job is running as scheduled. © 2003 SAP AG . If the produced quantities match actual quantities planned in SNP planning. Use transaction /SAPAPO/SNP02 for small data volume only. schedule it accordingly. the result of deployment is a confirmation of the supply network plan. The deployment heuristic does this based on any of several distribution methods and fair share rules. For individual product-locations you can also use online transaction /SAPAPO/RRP_SNP2PPDS. Fair-share alerts for deployment are automatically generated during the deployment run. Time or Error 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 Dependi ng on your process Status.or undersupply. the deployment optimizer instead tries to compute the lowest-cost manner in which to distribute the orders. Time or Error Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure APO report /SAPAPO/RM SNPTLB SM37 Check that the job is running as scheduled. The Transport Load Builder (TLB) then uses these stock transfers to generate transportation plans and build transport loads comprised of multiple products. Monitoring Activities The following table contains a description of reports and monitoring objects for TLB. Business Process Step 16: Transport Load Builder (TLB) The deployment run generates deployment stock transfers. or as a background job by running an appropriately designed variant for report /SAPAPO/RMSNPTLB. The monitoring object indicates whether the information refers to TLB run in batch or foreground. via transaction /SAPAPO/SNPTLB. if they are desired. the purpose of the deployment optimizer is to create deployment stock transfers. both firmed and non-firmed and creates deployment stock transfer independently.e. It is identical. Program scheduling management Application support © 2003 SAP AG Depend s on busines s process Status . The difference is that. APO report /SAPAPO/RM SDPDEP Sm37 Output of report /SAPAPO/RM SDPDEP Sm37 Monitor Time 24 Indicator or Error Monitoring Activity or Error Handling Procedure Responsibility Depending on business process Status Check if job is running as Program scheduled scheduling management Contact application support Depending on business process Status and messages Whether or not the job finishes without error. application support should check the job log and spool file for error messages Contact process management Application support Escalation Procedure See general issues of Error Handling. create a batch macro to produce them.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO Monitoring Object Monitor Monitor TA/Tool Freq. Restartability and Escalation below. i. number of pallets. Business Process Step 15: Deployment Optimizer Like the deployment heuristic. See Business Process Step 5: SNP Planning Run Optimizer. weight and volume. and which consider the minimum and maximum constraints of the means of transport. The background job can also be launched from transaction /SAPAPO/SNP04. rather than using one of the available fair-share techniques. Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. TLB can be executed either using interactive planning. Neither method of executing TLB will automatically produce alerts. Another difference is that Deployment Optimizer deletes all from SNP planned transport orders. or transaction /SAPAPO/RLCDEL. Monitoring Activities The following table contains a description of reports and monitoring objects for /SAPAPO/RLCDELETE. some of the order types generated during SNP planning are not converted to PP/DS. Monitoring Object Monitor Monitor TA/Tool Freq. Basic troubleshooting tips for this transaction. or further processed in other ways. Application check both the job log and support the spool file for application problems Depend s on busines s process Status/mes sages Responsibility Escalation Procedure Contact process champion See general issues of Error Handling. Business Process Step 17: Delete Transaction Data Under some business scenarios. /SAPAPO/RL CDELETE SM37 Log /SAPAP Depends O/RLCD on ELETE business process Depends on business process Monit. and determine whether the package size needs to be tuned to improve performance.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 25 Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. this is described in SAP Note 523250. along with several others for version management. the person responsible for monitoring should evaluate the data volume. The report can also be used to delete stocks. The first time the transaction is run with full data volume. Time or Error Monitoring Activity or Error Handling Procedure Output of report /SAPAPO/RM SNPTLB SM37 Independent of the job status. © 2003 SAP AG . are given in SAP Note 519014. Restartability and Escalation below.Indicator or or Error Time Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure Status Check that the job is running as scheduled. This is often done using report /SAPAPO/RLCDELETE. and deleting older ones is necessary to either keep the liveCache from growing. Restartability and Escalation below. Program scheduling management Application support Status/mes sages Check the log for error messages and data volumes Application support Contact process champion See general issues of Error Handling. or as one of the steps of deleting a location-product from the system. as described in SAP Note 630751. you can also prioritize alerts. Exception Based Monitoring of APO Supply Network Planning APO Alert Monitor The APO Alert Monitor allows a management-by-exception strategy. can have consequences up or down the supply line. proceed as follows: • If there are or seem to be problems in the data transfer via the Core Interface. The Alert Monitor is a tool with which planners can monitor the state of a plan. or when production plans. see the Troubleshooting Guide Integration R/3 – APO. /SAPAPO/PPT1. Maintenance of SDP Data Storage Structures 4. The Alert Monitor is a standalone component of APO that enables you to have a unified approach to handling problem situations. APO Alert Monitor 2. It notifies you if a problem occurs during an ATP check or SNP run. An exception is any situation that needs further adjustment. The Alert Monitor belongs to the suite of supply chain monitoring components in APO. The monitoring results can be used to readjust the plan whenever necessary. if not handled immediately. The purpose of the Alert Monitor is to inform planners if the condition of a plan has been violated.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 26 Further Information Troubleshooting If executing this Best Practice did not produce the desired results. a new fad. The goal of Supply Network Planning is to create plans for production. Not only can you determine which types of exceptions you want to be notified of. for example. and others. transportation. Running Supply Network Planning in Background 5. 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. demand plans. so it is of special concern in this and other APO business process scenarios. which you can find in SAPNet in the Literature Center of the R/3 Plug-In homepage. together with the Supply Chain Cockpit and the Plan Monitor. 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. and/or procurement across a supply chain with multiple locations. Alerts can also be displayed in the Supply Chain Cockpit /SAPAPO/SCC01. A sudden switch in trends. an unexpected change in the circumstances of a supply chain partner could all lead to exception situations. the display of alerts is restricted to those which are assigned to the selected planning book. /SAPAPO/SDP94. • 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. thus © 2003 SAP AG . When displaying alerts in /SAPAPO/SDP94. Monitoring of Business Warehouse Activities 3. and the role of the Alert Monitor is to notify you of exceptions that occur during the process. Most exceptions. or vehicle schedules are being generated in one of the APO applications. however. this also applies to ATP. Unlike in the DP application where you can view only one planning book at a time. For large data volumes database alerts are usually faster. You can also have messages sent automatically to your own inbox to inform you of alerts in your area. In exception-based management. When dealing with large volumes it is best to perform a batch planning-run using the appropriate database macro. If you regularly consider Capacity Overload alerts. 2. making it the ideal tool for tracking the quality of your alerts over a specific period of time. even an information alert should reflect an exception to the planning situation and not a “success” message saying “everything ok”. the following exception situations may arise: • Changes in bias. you can send messages via e-mail to other planners to inform them of the alert situation. Besides forecast and SDP database alerts.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 27 preventing an information overload. manufacturing. PP/DS alerts. with database alerts you see a snapshot of the plan during run time. © 2003 SAP AG . You also have the option of creating customer-specific dynamic or database alert types to be used with SDP macros. Generally. or last executed macro. and distribution. which may lead to excess inventory For Supply Network Planning. The SDP alert profile contains a number of alerts that are specific to the tactical planning and sourcing decisions relevant for purchasing. The results of the planning run show the situation as it was at the time of the run. As opposed to SNP alerts in APO Release 2. In the demand planning process.0. you as the planner must make the ultimate decision regarding the priority of an alert. you can view several in the Alert Monitor. 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%. Analyze alert situation. Information The priorities should be defined in a way that . There are forecast alert profiles and SDP alert profiles. To support the Alert Monitor's function as a tool for exception-based management. for instance. if an alert is generated. Make adjustment to plan and / or profile. 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). The three possible priority levels in the Alert Monitor are: 1. SDP alerts can be used both in the Demand Planning and Supply Network Planning applications. Database alerts that are no longer in use. Alert priorities are identified by icons displayed in the profile or in the monitoring slots of the Supply Chain Cockpit control panel. Warning 3. There are two different types of Supply & Demand Planning alerts: • Dynamic alerts mirror the current planning situation but are not saved in the database. Inform responsible planner. This alert type is NOT suitable for dealing with a large volume of planning objects because large numbers slow down performance. VS and TLB/Deployment alerts. in other words. must be deleted from the database. because they have been acknowledged or because they are outdated. However. three activities must take place: 1. unexpected demands • Orders exceed forecast • Orders fall short of forecast. alerts are now macro-dependent and thus can reflect the actual data in liveCache. new trends. Error 2. 3. both supply & demand planning (SDP) alerts and Transport Load Builder (TLB) alerts are important. For small data volumes up to approximately 1000 alerts dynamic alert generation is usually much faster than reading alerts from the database.under normal conditions on a well run system information alerts take the biggest share and errors are generated only in rare cases. • Database alerts show the planning situation as it was during the planning run. You have to maintain alert profiles to maintain a user-specific selection of alerts for your area of responsibility. you will soon be able to determine whether a 15% deviation is serious or not. are not stored in the database but are dynamic only. Monitoring Activities Apart from safeguarding the general availability and consistency of the system components SAP APO. Please refer also to SAP Notes 375965. and 521639 and to Exception based Monitoring of APO Demand Planning. 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. you may have an alert profile for your own area of responsibility. As there are very many applications that use this basis component and often many table entries are made. It can be browsed using transaction SLG1. the Application Log can be used to get more detailed information about what happened and how to resolve the problem. 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). 500063. You can find more information concerning this tool in the SAP Documentation under "Supply Chain Monitoring – Alert Monitor". The monitor transaction for the Application Log is SLG1. 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.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 28 You can maintain a list of favorite Alert Monitor profiles so you can switch back and forth easily between various profiles. and SAP R/3 OLTP. and escalation paths (responsible teams) for the following monitoring activities and objects. With the help of Info Package groups you can collate data requests that logically belong together and schedule them using the scheduler. you must specify the times. 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. responsible teams. In case of errors or problems. but you may also want to look at alerts in other areas. 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. schedule the following job on a regular basis: • Data Extraction and Load with report RSBATCH1. The log entries are subdivided into objects and sub-objects and classified by importance. it is important to regularly delete obsolete Application Logs from the database in order to prevent these tables from © 2003 SAP AG . SAP recommends that in order to safeguard any business step that is based on SAP BW techniques. When adapting this concept for your company. Too many alerts slow performance and may cause you to overlook the really important ones. 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 monitor the objects listed in the following table. The job has to be defined using the scheduler in the Administration Workbench (transaction RSA1) of the BW component of APO. Keep alerts to a minimum. For example. where you should specify the (sub-) objects and the time interval you want to be displayed. Monitor. Relevant objects for the SAP Business Warehouse are: • RSAR BW Metadata maintenance • RSAU Update rules • RSD BW data basis • RSDMD Master data maintenance • RSO_REPOSITORY BW Repository • RSSM Scheduler. Jobs for the Maintenance of the Application Log The Application Log entries are stored on tables with name prefix BAL*. 495166. The scheduler generates a background job with name prefix BI_BTCH and processes the selected Info Package. SAP BW. You can also call the monitor from a selected Info Package or via transaction code RSMO. RSMO Dependi or SM37 ng on your process Status Check if job is running as scheduled. If a scheduled job fails. These jobs perform the data transfer from the different data sources to APO InfoCubes. Time or Error Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure APO job BI_BTCH*. under Background Processing. schedule it accordingly. Contact application support Use the Monitor Assistant to analyze and correct the error situation. © 2003 SAP AG . evaluate error severity and impact. The deletion can be performed using transaction SLG2 or in background by the appropriate report: • Delete Obsolete Application Logs with report SBAL_DELETE. Software monitoring team Contact application support Program scheduling management Contact application support Read message long text and / or details. Error Handling. Software yellow read the error message and monitoring traffic lights diagnosis under tab strip team Status and the processing log under Detail. component BC-CCM. or a scheduled job has status "finished" you may need to take action. Consider the status of the job and proceed as follows: • Status scheduled: the job steps have already been defined. For more information. Restartability and Escalation Error Handling Procedures Error handling for background jobs is explained in detail in the SAP R/3 documentation CD. APO: Evaluate SLG1 Application Log for BW related objects. Log class Check if there are very important logs (flagged red) or important logs (flagged yellow). Contact the program scheduling management in order to clarify when the job will be fully defined. A log can only be deleted when it has reached its expiry date or if it has the "Deletion before expiry" attribute. if present. At least daily APO report SBAL_DELET E. Weekly SM37 This report deletes obsolete Application Logs. Program scheduling management Contact application support RSMO Red or After selecting one request. Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. Analyze error situation. APO: Administration Workbench Monitor After every data load If the job is not scheduled as provided by Application Support. and take corrective action. If the job is not scheduled as provided by Application Support. Status Check if job is running as scheduled. schedule it to run weekly. please refer to SAP Note 195157.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 29 overflowing as well as to keep the applications and the log retrieval performant. a necessary job is not scheduled. but the start condition has not yet been defined. and that liveCache data structures (time series) are kept consistent. schedule the following jobs to run on a regular basis: • Compute Histograms for BW InfoCubes with report SAP_ANALYZE_ALL_INFOCUBES. message logs. • Status ready: the start condition of a released job has been fulfilled. The aborted job may also delay the start of succeeding jobs. SAP DB or IBM DB2 UDB (DB6) database (refer to SAP Notes 16083 and 421795) Please see SAP Notes 129252 (Oracle) or © 2003 SAP AG . contact Application Support. forward the issue to the next support level. This is only relevant for systems running with Oracle. if a program in a job step produced an error such as issuing an "E" or "A" error message. and software monitoring team and / or application support must check the respective job results (such as spool output lists. • If you have questions or problems that cannot be solved. we recommend that you create a customer problem message in the SAPNet R/3 front-end system. the tasks associated with DP BW structures must also be executed for these time series objects. If an administrator intentionally canceled the job. If the program is an SAP standard program. contact the software monitoring team and investigate why the error occurred. you must specify the times. 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. Monitoring Activities The data for your Demand Planning process is stored in different logical and physical structures such as InfoCubes. Check if the job is within the given timeframe. responsible teams. • If there are problems with the Core Interface CIF or with data missing in either R/3 or APO. If the corresponding escalation path is not well defined. clarify why he or she did so and whether (and if so. and escalation paths (responsible teams) for the following monitoring activities and objects. A job scheduler has put the job in a queue to wait for an available background work process. Program scheduling management must check whether the job ran in the given timeframe. This can happen in two ways. If the job exceeded the given timeframe. consider possible succeeding jobs or dependencies on other jobs when deciding whether to restart the aborted job. • Status finished: all steps that make up this job have completed successfully. Process Step Restartability If a background job is cancelled. • Status cancelled: the job has terminated abnormally. Check for particular dependencies to other jobs. either alone or together with order objects. • Status active: the job is currently running and can no longer be modified or deleted. Maintenance of SDP Data Storage Structures If SNP time series objects are used in the planning areas of your company. the Master Planning Object Structure. when) the job must be re-run. and updates). When adapting this concept for your company. search for appropriate messages in SAPNet and create a customer message if you cannot solve the problem. Alternatively. contact the software monitoring team. • If none of the defined support levels can provide a solution for a particular problem. Escalation Procedures • In general. see the Troubleshooting Guide Integration R/3 – APO in the Literature Center (of the R/3 Plug-In homepage). 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.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 30 • Status released: the job has been fully defined with a start condition and will wait for that condition to be fulfilled. we recommend that you search for related SAP Notes in the SAPNet R/3 front-end system for any unknown problems or errors. and liveCache Time Series. 402046. For further details. and then possibly deleted. but simply unnecessary objects. These administrative jobs have to be run after every load of data to a planning object structure. Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. If errors are found.0B Support Package 17 please notice the dependency in running SAPDBA (optimizer statistics for non-BW tables) described in SAP Note 129252. and 503363. 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. Please also refer to SAP Note 323090. SAP DB or IBM DB2/UDB (DB6) database. independently of planning areas. since this would result in liveCache objects that are still required by the other parallel process being recognized as unnecessary. • Delete Time Series and Time Bucket Profiles having no liveCache Anchors with report /SAPAPO/TS_LCM_REORG. Only for systems running with Oracle. and 520876. Time or Error APO report SM37 SAP_ANALYZ E_ALL_INFO CUBES.0) or SP 10 (APO 3. any unnecessary time series and period patterns are deleted. Mark the Log check box if you want to see a list of characteristic combinations having inconsistencies. all planning areas that use the planning version to be checked are locked for the relevant version. please refer to SAP Notes 393655. This report (supplied with SAP Note 542946 or Support Package 22 (APO 3. A separate background job (job name with prefix BI_STAT) will be started to execute this request. showing users who have already set a change lock for the planning version. Program scheduling management Contact software monitoring team If the job is not scheduled on a regular basis. which result in increased liveCache memory consumption. For details and further information please refer to SAP Notes 358283.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 31 328106 (DB6). schedule it to run once a week with parameter percent = 100. © 2003 SAP AG Weekly Status Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure Check if job is running as scheduled. 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'. This report checks all existing time series. 492460. In this case. . These objects do not have any reference to the application data and are therefore not inconsistent as such. 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. If you cannot activate the lock. Caution: When you run report /SAPAPO/TS_LCM_REORG. if problems are reported by the index check.1).. we recommend that you always run the report with the option 'Lock planning version'. For this reason you should only have to run the report approximately once a month. • Maintain Statistics and Indices for Planning Object Structures with report /SAPAPO/TS_PSTRU_TOOL. For this reason. in all planning areas and versions. resp. Run it with option Repair Indexes. • Check Inconsistencies in Time Series Network with report /SAPAPO/TS_LCM_CONS_CHECK_ALL. 425825. If you have selected the 'Repair' option. For SAP BW releases prior to 2. and reports whether or not there are inconsistencies. This report creates DB statistics for all InfoCubes. you can repair inconsistencies in a specified planning area and version using report /SAPAPO/TS_LCM_CONS_CHECK. report execution is interrupted and a list of system users is displayed. Traffic light Check whether superfluous data is reported and has been deleted without errors. Traffic light Check whether the inconsistencies in the selected time series have been repaired. Program scheduling management Contact application support Software monitoring team Contact application support Try to repair inconsistencies by running report /SAPAPO/TS_LCM_CONS_ CHECK for the corrupt time series setting the repair option. © 2003 SAP AG After each run. Red traffic light Check for time series with inconsistencies reported. Output of APO SP01 report /SAPAPO/TS_ LCM_REORG . . After each run. After each run. 32 Output of APO SP01 report /SAPAPO/TS_ LCM_CONS_ CHECK_ALL.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. This report is able to repair inconsistencie s in time series. SM37 APO report /SAPAPO/TS_ LCM_CONS_ CHECK. Time or Error SM37 APO report /SAPAPO/TS_ LCM_CONS_ CHECK_ALL. Status Check if job has finished without errors. If the job is not scheduled on a regular basis. Weekly Status Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure Check if job is running as scheduled. Monthly Status Check if job is running as scheduled. schedule it to run once a month. After each run. This report detects inconsistencie s in time series. schedule it to run once a week. Software monitoring team Contact application support SM37 APO report /SAPAPO/TS_ LCM_REORG with option Repair. Software monitoring team Contact application support Output of APO SP01 report /SAPAPO/TS_ LCM_CONS_ CHECK. This report deletes superfluous time series and time bucket profiles. Program scheduling management Contact application support Software monitoring team Contact application support If the job is not scheduled on a regular basis. 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. and red (errors) or yellow (warnings) lights. Status Output of APO SP01 report /SAPAPO/TS_ PSTRU_TOO L. APO report SM37 /SAPAPO/TS_ PSTRU_TOO L with option Check Indexes. SAP recommends that you monitor the objects listed in the following table. Software monitoring team Contact 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. Also a release of DP data to SNP is usually performed in background. optimizer. Status After every data load into the POS. and SAP R/3 OLTP. Read message long text if present. If the report is not scheduled as provided by Application Support. and are discussed in the pertinent chapters in earlier parts of this document. the heuristic.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. After every run. Monitoring Activities Apart from safeguarding the general availability and consistency of the system components SAP APO. This report checks and generates statistics for a POS. Other Supply Network Planning background jobs (for example. schedule it accordingly. The different tasks that can be performed in this way have to be customized and set up as “activities” prior to job definition. 33 Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure Check if job is running as scheduled. Status Check if job ended correctly. Restartability and Escalation above. Message type (icon) Look for stop icons (cancellation). Program scheduling management Contact application support Program scheduling management Contact application support After every data load into the POS. This report checks the indices of a POS. Mass processing allows you to run macros for large numbers of products while optimizing system resources. Check if job is running as scheduled. SAP BW. After every run. See general issues of Error Handling. Jobs for Running and Monitoring "Supply Network Planning in Background" (APO) To ensure a proper and timely demand planning. Time or Error SM37 APO report /SAPAPO/TS_ PSTRU_TOO L with option Calculate Statistics. 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. in order to safeguard any business process step that performs Supply Network Planning activities in the background. Software monitoring team Contact application support If the report is not scheduled as provided by Application Support. This mass processing job is created with its necessary settings and scheduled using transactions /SAPAPO/MC8x. Using transactions /SAPAPO/MC8D and /SAPAPO/MC8E you can create and change © 2003 SAP AG . a message for every characteristic value combination that was processed in the job. Old logs from planning activities must be deleted regularly to maintain high performance for the related transactions and prevent database tables from overflow.g. or the transfer to R/3. “data view does not exist” or “release profile not found”. use the DP Job Log. schedule it accordingly. © 2003 SAP AG Status Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure Check if job is running as scheduled. Demand planning activities can be executed periodically with various different frequencies. see Operational Management – Parallel and Concurrent Execution of Jobs. This can be achieved by defining several jobs in /SAPAPO/MC8x running the same activity but having a different selection of characteristics. You can also delete job logs with this transaction. Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq.) in parallel. for example once a quarter or once a year. Select the option 'Delete all logs with minimum age' reducing the parameter days. 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. Standard transaction SM37 is used for a job overview and display of job logs and jump to spool lists. etc. Make sure that you delete the logs in packages. the frequency of monitoring the jobs and deleting the DP Job Logs depends on how often you run these functions. To view the job log. select Generate log when you create a job. main memory. /SAPAPO/MC8I allows you to check the job definition prior to execution and find errors like “no macro defined”. Red or Accordingly to the warning or yellow error reported (see message traffic lights long text). the jobs are scheduled. whereas a release of the demand plan to production planning or R/3 is usually performed over larger intervals of time.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 34 respectively. such jobs. See also SAP Note 512184. With /SAPAPO/MC8J you can copy jobs and delete them with /SAPAPO/MC8F. • Delete DP Job Logs with report /SAPAPO/TS_BATCH_LOGFILE. a release of DP data to SNP orders. To request a job log. Parallel processing: Due to the large amount of data to be processed and the limited time that can usually be spent on it. /SAPAP After O/MC8 each K run of /SAPAP O/TS_B ATCH_ RUN. and others limit the total number of jobs that can run on a system at the same time. Time or Error SM37 APO report /SAPAPO/TS_ BATCH_RUN. it is often necessary to process batch runs (e. call transaction /SAPAPO/MC8K. This report performs specified DP mass processing activities. CPU speed. the execution of one or several macros. Computation of key figures with batch macros could possibly be done daily or weekly. and other details. 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. which is usually called from the customizing tree. For dependencies and concurrent execution of jobs. To check the results of a DP mass-processing job. These jobs can then be scheduled to run at the same time. macros. DP Job Log Dependi ng on your process. The job log shows whether the job completed successfully (green traffic light). forecast error messages if the job included a forecast. An activity can be a forecast computation. The so-called activities that are needed for these jobs have to be defined in advance via transaction /SAPAPO/MC8T. Program scheduling management Contact application support Application support Contact process champion If the report is not scheduled as provided by Application Support. With /SAPAPO/MC8G. Accordingly. shown . Please remember that hardware resources like number of CPUs. with warnings (yellow traffic light) or with errors (red traffic light). However. mails are sent with an overview of existing alerts. schedule the following jobs to run on a regular basis: • Send Alert Monitor mails with report /SAPAPO/AMON_MAIL_BROADCAST. SAP BW. 35 See general issues of Error Handling. Program scheduling management Contact software monitoring team If the report is not scheduled as provided by Application Support. 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. Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. For information on database alerts and dynamic alerts in Demand Planning. The most important high-level tool for monitoring the planning situation and an exceptiondriven application management is the APO Alert Monitor. Exception Based Monitoring of APO Supply Network Planning This section outlines the concept for monitoring the overall planning situation in APO Supply Network Planning. depending on your requirements. Time or Error Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure APO Alert Monitor /SAPAP At least O/AMO daily N1 Alert list Check for forecast alerts and SDP alerts and correct the planning for the reported object appropriately. investigate the reasons for the alerts and take corrective actions in order to keep the demand plan close to the needs of your company. schedule it accordingly. 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.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. see APO Alert Monitor. Restartability and Escalation above. © 2003 SAP AG Daily If the report is not scheduled on a regular basis. It deletes old alerts and is of particular importance if you use alerts stored in the database. Monitoring Activities Apart from safeguarding the general availability and consistency of the system components SAP APO. and SAP R/3 OLTP. Program scheduling management Contact software monitoring team This report ensures sending of mails about existing alerts. Time or Error SM37 APO report /SAPAPO/TS_ BATCH_LOG FILE Dependi ng on your process. Status Monitoring Activity or Error Handling Procedure Responsibility Escalation Procedure Check if job is running as scheduled. . 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. • Delete Alert Monitor alerts with report /SAPAPO/AMON_REORG. Therefore. above. The responsible persons should then call the APO Alert Monitor. SAP recommends that you monitor the objects listed in the following table in order to safeguard your Supply Network Planning business process. Depending on user profiles. Jobs for an Exception Based Monitoring of Supply Network Planning To ensure a timely and efficient notification of exceptions in Supply Network Planning. schedule it to run every hour to at least daily. This report deletes old DP Job Logs. Application support Contact process champion APO report /SAPAPO/AM ON_MAIL_BR OADCAST SM37 Status Check if job is running as scheduled. Go support to APO Alert Monitor and process the alerts appropriately. schedule it to run once a day. Therefore times for such backups must be scheduled carefully. SAP APO 3. if the mail lists alerts Application that are important for you. deleting. This guarantees that no checkpoint has to wait for the planning run to finish and thus causing all other transactions to wait. (this also applies to the R/3 basis of the APO system). Check.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 36 Monitoring Object Monitor Monitor Monitor Indicator TA/Tool Freq. for example: • General R/3 system administration.2. logical sequence) on business processes and process steps not mentioned in this document. it is © 2003 SAP AG . for example: o Reorganization of jobs. SAP APO 3. all other users that require liveCache data have to wait for the completion of the checkpoint. Please refer to SAP Note 514971 for details. This restriction applies only for liveCache 7. In addition.1 documentation is available on CD or in the SAP Help Portal in German or English. This report deletes Alert Monitor alerts. SAP Documentation SAP APO 4. SM37 Weekly Status Check if job is running as scheduled. Several functions that have been documented in the SAP Library for SAP APO Release 3. Responsibility Program scheduling management Escalation Procedure Contact process champion Contact application support See general issues of Error Handling. or updating many table entries.0 documentation is available on CD or in the SAP Help Portal in German or English. rule of thumb 4 to 6 times per day in total. spool entries and so on o DB offline backup – During an offline database backup no online or background activity is possible.0 documentation is available on CD or in the SAP Help Portal in German or English. 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.0. APO report /SAPAPO/AM ON_REORG. We recommend that you write checkpoints before and after long running planning jobs.x. at least daily.1 are also available in Release 3. These usually comprise. • 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. 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. Print files (PDF format) of several chapters in both languages are available in the Media Center of the SAP Marketplace for SCM. Second. If the job is not scheduled on a regular basis. Time or Error Monitoring Activity or Error Handling Procedure Alert Monitor mails SO01 (or respecti ve email system) Dependi ng on your require ments. Restartability and Escalation above. program scheduling management and the software monitoring group should plan and schedule system maintenance activities to run at appropriate times. production. o Transfer of changes made to existing master data records. all the work necessary for the company’s core business process can be performed in the time frames determined by the business process champions. or. 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. online and background application system activity cannot always occur whenever desired. Also. same resources for handling. for the completion of administration activity. overnight or over a weekend.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO o o o • 37 warranted that the results from the planning run are safely stored away in a consistent manner with the other data in liveCache.x only). Especially in APO. for example. certain activities – such as background jobs – should be started only after the respective preceding activity has finished. for example. Therefore. but may need to wait. 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. 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. © 2003 SAP AG .2. on rare occasions. 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. long-running planning activities should not collide with APO checkpoint writing. 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. transportation resources b) Other planning activities (for example. Then. o Delta transfer of new master data records. 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. 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) Transfer of Master Data from R/3 to APO: o Initial transfer of master data records. because this can overload CIF and cause an undesirable communication delay. Because of these dependencies. 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. separate variants should contain only products for which there is absolutely no overlap in components. regularly delete old alerts using report /SAPAPO/AMON_REORG. transportation lanes. More jobs will run more slowly . Parallel processing for a complete optimiser run is possible only if the following rules are observed: a) The complete ppm for a final product. 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. which can be separate from the application server. or else one job must wait until the other has released the lock on the data. Refer to SAP Note 539348 for technical details. Memory is often a bottleneck for the SNP optimizer. it will create an error message in the job log. find out how much memory was used by the individual process. or transportation lanes. c) No product-location should belong to more than one variant. although the relative amount of time spent will vary with the problem structure. regularly delete old job logs using transaction /SAPAPO/MC8K. Otherwise the solution will not be optimal. some customers configure separate optimizer servers for each run. are heavily dependent upon the application CPU resources. Optimal performance is achieved when one CPU is available for each process. How critical this is depends upon how much of the response time is CPU time. resources. 13) If you are executing batch macros in SNP. 12) If you are using alerts in SNP. When a locking situation occurs during an SNP Heuristic Run. and less if there are memory limitations. © 2003 SAP AG . It unsuccessful. resulting in performance problems. 7) Parallel execution of the SNP optimiser should be designed to avoid CPU and memory bottlenecks on the optimiser server. should be contained in the variant for that product. ppms. b) To avoid a non-optimal solution. Some job types.depending upon how many CPU resources are needed by the particular job type. no two selection variants which contain overlapping characteristic combinations. such as a batch macros which add two key figures. only run as many jobs as there are CPU on the system. Note that the SNP optimiser will consume CPU resources on the optimiser server. such as the SNP heuristic. are not. and products in one variant should not use resources. or report /SAPAPO/TS_BATCH_LOGFILE. Also run these as background jobs. while others. For optimal performance. Specifically. and are creating spool files for these runs. 8) Parallel execution should be designed to avoid memory bottlenecks. the Heuristic will attempt to re-plan the product for a fixed number of times. To avoid this. call this number M_proc.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 38 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. 11) Do not execute SNP planning runs concurrently with the release from DP to SNP. across all appropriate locations. 5) Two users should not selection variants in SNP interactive planning which lock the same datasets. A good rule of thumb is that one CPU is needed for each two optimiser jobs run in parallel. 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. Typically this means these jobs should be run during the night. 6) Parallel execution should be designed to avoid CPU bottlenecks on the application server. 10) Do not execute the daily liveCache reorganization job concurrently with ANY type of SNP planning run or CTM. or ppm used by products in other variants. it is also recommended that you periodically run report /SAPAPO/TS_GEN_DOCTAB_CHECK to eliminate possible inconsistencies in the notes. run a time series consistency check any time you make changes to the planning object structure. 1999 Other Best Practice Documents In SAP Service Marketplace. and a discussion of errors caused by inconsistent time series objects can be found in Note 509479. you can find several Best Practice Documents for Solution Management like this one. Manage Production Planning in mySAP SCM / SAP APO deals with Production Planning and Detailed Scheduling in APO and Production Execution in R/3. 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. 16) If you are using time series objects in SNP. Monitoring and Administration for SCM / APO helps you analyze the workload and performance on liveCache and the APO database. do not run this report concurrently with any of the SNP planning runs. A description of this report exists in Note 425825. Manage Demand Planning in mySAP SCM / SAP APO discusses the operation of Demand Planning processes. However. 2000 For information about the administration of SAP APO systems. © 2003 SAP AG . see: • Hartwig Brand. see: • Liane Will. 17) If you are using notes management within interactive planning. SAP R/3 Performance Optimization. SAP APO System Administration. alias /scm >> Related Topics / Best Practices for Solution Management: mySAP SCM.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 39 14) Ensure that you are running report /SAPAPO/OM_REORG_DAILY on a regular basis. SAP R/3 System Administration. see: • Thomas Schneider. as described in Note 139558.1 contains important information about master data consistency as well as internal consistency between APO DB and liveCache. using report /SAPAPO/TS_LCM_CONS_CHECK_ALL. 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. please read Note 332812 carefully before using this report to automatically correct inconsistencies. 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. or add master data. see: • Liane Will. Data Consistency Between SAP R/3 and SAP APO 3. 2002 For information about how to monitor and tune general system performance. Literature For more detailed information about how to administer an SAP R/3 System.0 / 3. 2001 For background information on administrative tasks with emphasis on system planning and setup. SAP R/3 Implementation with ASAP. However. 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: • 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.tips & tricks • 180605: Oracle database parameter settings for BW • 184905: Collective note Performance BW 2.0A • 447708: Composite SAP note about APO system administration • 500843: Composite SAP note for COM and SAP liveCache >= 7.sap.0A • 438712: Support Packages for APO Release 3.0 promotion: Consulting: Reporting • 386735: DP: Extract data to an IC with delta update • 391625: Backup and Recovery for APO 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 .2 Please refer to the Best Practice Document dedicated to CIF for SAP Notes with information on qRFC and CIF.memory problems / COM errors • 384550: APO 3.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 40 SAP Notes (See also http://service.com/notes) The following SAP Notes contain useful information on the performance of SAP APO: • 303743: Support Packages for APO Release 3.0: Data extraction .0A Demand Planning • 393634: Release of the optimization server after © 2003 SAP AG .0: Realignment tool – consulting • 363092: Demand Planning: Performance Mass Processing • 373756: Data extraction from a planning area • 383906: DP 3.1 • 420669: Collective note: General Performance Improvement APO • 420594: Collective Note: Performance for DP 3. 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.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO • 398726: DP 3.0: 'No liveCache anchor found' • 403050: Consulting DP 3. /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 • 432038: Creating location product to customers and vendors • 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 • 529663: Performance during /SAPAPO/TS_LCM_CONS_CHECK • 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 .0: performance planning book/data view • 401830: Display <=> Change in Interactive Planning • 402046: DP 3. reorganization jobs • 139558: Scheduling report /SAPAPO/OM_REORG_DAILY • 195157: Application log: Deletion of logs © 2003 SAP AG 41 .Copying Planning Object Structures • 571629: How does the note management work? • 572220: Avoid use of optimizer runs with the same "names" • 572996: Simultaneously started optimization runs Please also refer to the following SAP Notes: • 016083: Standard jobs. /sapapo/om17. ........................... 28 /SAPAPO/RMSNPOPT . 33 /SAPAPO/MCPSH_GEN_SELTAB_MGM .. 18..................................................................15. 21 /SAPAPO/SNP2PPDS... 19 /SAPAPO/RMSDPDEP ...............17... 20..............................................................sap...............10 /SAPAPO/TS_GEN_DOCTAB_CHECK ................ 9 /SAPAPO/RLCDEL.............................................. 11 /SAPAPO/SCC01 .................................... 22 /SAPAPO/CIFSTARTQUEUES..................................................... 26 /SAPAPO/SNP106................12 /SAPAPO/TS_LCM_CONS_CHECK................................. 35 /SAPAPO/SNP05............................25 /SAPAPO/TS_PSTRU_TOOL .................................. 30 /SAPAPO/SDP_EXTR...............................13 /SAPAPO/TS_PAREA_EXTR_MGM......11 /SAPAPO/SNP94.... 17 /SAPAPO/MSDP_SB...............................................22 RSVCHECK ................................................................ 14 /SAPAPO/AMON1 ................................ /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 42 Feedback and Questions Send any feedback by formulating an SAP customer message to component SV-GST-SMC........................................ 34 /SAPAPO/MSDP_ADMIN................ 31 /SAPAPO/RMDPLOPT.....................24 RSMO .23 SO01.......25 /SAPAPO/TS_PAREA_TO_ICUBE .................................12 RSBATCH1...................... 24 /SAPAPO/MC8x ...................................................................................................Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO • 375965: APO Consulting: Alerts in forecast • 425825: Consistency checks..... 31 /SAPAPO/OPT03 ...........19 SBAL_DELETE........................... 21 /SAPAPO/TS_PAREA_INITIALIZE ..... 19 /SAPAPO/RDMCPPROCESS .............................15.................................. 35 /SAPAPO/SNP04..11 RSTRFCI1 .................... 9 /SAPAPO/TS_BATCH_RUN ........................... 28 /SAPAPO/RMSNPTLB .............................................12 /SAPAPO/TS_LCM_CONS_CHECK_ALL 8..16.............. 18.............................................18.............. 29 /SAPAPO/SDP94 .... 13 /SAPAPO/C4 ........ Index /SAPAPO/AMON_MAIL_BROADCAST ... 28 /SAPAPO/RRP_NETCH...................23 RSA1.........11 /SAPAPO/SNPOPLOG.......................................... 24 /SAPAPO/AMON_REORG.... 19..................................................... 15 /SAPAPO/OM_REORG_DAILY ...................... 33 /SAPAPO/TS_BATCH ... 19 /SAPAPO/RLCDELETE.............. 14 /SAPAPO/CIFSTOPQUEUES............................................. 28 /SAPAPO/SNP02 ............................................................. 16 © 2003 SAP AG ................................................................... You can do this at http://service...............com/message.............................13 /SAPAPO/TS_LCM_REORG................9 /SAPAPO/TS_BATCH_LOGFILE .......... 13 /SAPAPO/LCOUT................................ 31 /SAPAPO/OPT11 ..........22 /SAPAPO/SNPTLB .......... 11 /SAPAPO/RTSINPUT.......... /sapapo/om17.........18..................16........................................ 11 /SAPAPO/RSDP_CALC_SAFETY_STOCK................. 26 SLG1...9 RSTRFCI3 ........................................................12 BRCONNECT ..................................26 SAP_ANALYZE_ALL_INFOCUBES...............8.......... 23...................... 31 /SAPAPO/OPT12 ..................... R/3. PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. SAP ArchiveLink. either express or implied. SAP. links or other items contained within these materials. RS/6000®. World Wide Web Consortium. NT®. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party Web pages nor provide any warranty whatsoever relating to third party Web pages. Microsoft®. Massachusetts Institute of Technology. Disclaimer: SAP AG assumes no responsibility for errors or omissions in these materials.com Logo and mySAP. Inc. AS/400®. special. All other products mentioned are trademarks or registered trademarks of their respective companies. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. R/2. DHTML. or consequential damages that may result from the use of these materials. SAP EarlyWatch. OSF/1®. WebFlow. HTML. RIVA. EXCEL®. and Motif® are registered trademarks of the Open Group. ORACLE® is a registered trademark of ORACLE Corporation. Inc. indirect. All rights reserved. DB2/6000®. Management Cockpit. AIX®. SAP Business Workflow. UNIX®. These materials are provided “as is” without a warranty of any kind. XHTML are trademarks or registered trademarks of W3C®. and OS/400® are registered trademarks of IBM Corporation. MVS/ESA®. The information contained herein may be changed without prior notice. or non-infringement.Best Practice: Manage Supply Network Planning in mySAP SCM / SAP APO 43 © Copyright 2003 SAP AG. DB2®. the implied warranties of merchantability. SAP does not warrant the accuracy or completeness of the information. S/390®. including but not limited to. JAVA® is a registered trademark of Sun Microsystems. ABAP. TM INFORMIX®-OnLine for SAP and Informix® Dynamic Server are registered trademarks of Informix Software Incorporated. graphics. IBM®. © 2003 SAP AG . fitness for a particular purpose.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. text. JAVASCRIPT® is a registered trademark of Sun Microsystems. OS/390®. Word®. BAPI. OS/2®. XML. X/Open®. SAPPHIRE. SAP shall not be liable for damages of any kind including without limitation direct. Parallel Sysplex®. WINDOWS®. SAP Logo. used under license for technology invented and implemented by Netscape.. mySAP. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.