manage supply network planning

Manage Supply Network Planning & CTM in

SAP APO (3.x) and SAP SCM (4.x / 5.x)

Best Practice for Solution Management

Version Date: November 2008This version is valid for SAP APO 3.0A, 3.1 and SAP SCM 4.0, 4.1, 5.0 and 5.1 (2007)

The newest version of this Best Practice can always beobtained through the SAP Solution Manager

ContentsApplicability, Goals, and Requirements................................................................................................2

Preliminary Information .................................................................................................................4Procedure ...................................................................................................................................10

Business Process Step 1: Initialize Planning Version ............................................................. 11Business Process Step 2: Load Data.....................................................................................13Business Process Step 3: Safety Stock Planning...................................................................14Business Process Step 4: SNP Heuristic Run........................................................................15Business Process Step 4a: CTM Planning Run......................................................................18Business Process Step 5: SNP Optimizer Run.......................................................................23Business Process Step 6: Capacity Leveling .........................................................................25Business Process Step 7: SNP Interactive Planning ..............................................................26Business Process Step 8: Shelf Life Propagation...................................................................28Business Process Step 9: Execute Batch Macros ..................................................................30Business Process Step 10: Exchange Requirements with Supplier ........................................32Business Process Step 11: Load Data into BW ......................................................................33Business Process Step 12: Create/Update Planned Orders, Transfer Orders, and PurchaseRequisitions ..........................................................................................................................34Business Process Step 13: Release SNP to DP ....................................................................35Business Process Step 15: Deployment Heuristic..................................................................37Business Process Step 16: Deployment Optimizer.................................................................38Business Process Step 17: Transport Load Builder (TLB) ......................................................38Business Process Step 18: Delete Transaction Data..............................................................39

Further Information ...........................................................................................................................40Index.....................................................................................................................................56

Best Practice: Manage Supply Network Planning & CTM in SAP APO (3.x) / SAP SCM (4.x / 5.x)

© 2008 SAP AG

2

Applicability, Goals, and RequirementsTo ensure that this Best Practice is the one you need, consider the following goals and requirements.

Goal of Using this ServiceThis Best Practice enables you to set up a business process management and monitoring concept forthe business process "Supply Network Planning", which is part of the SAP Supply ChainManagement (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 escalationmanagement for Supply Network Planning

Define the roles and responsibilities for all persons involved in the customers’ support andmonitoring organization with respect to Supply Network Planning

These procedures ensure the smooth and reliable flow of the core business process to meet yourbusiness requirements.

Alternative PracticesYou can get SAP experts to deliver this Best Practice on-site if you order a Solution ManagementOptimization (SMO) service, known as the SAP Business Process Management service.

Staff and Skills RequirementsTo implement this Best Practice, you require the following teams:

Application Management TeamThe 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 yourcompany’s:

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 SolutionSupport 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 superordinateBest Practice General Business Process Management, which you can obtain through the SAPSolution Manager.


© 2008 SAP AG

3

Necessary or Useful Training Courses:

ADM355 APO System Administration

PDEF08 LiveCache Administration

TTW060 SAP APO Technical Administration

TEWA60 SAP APO livecache Monitoring

SCM210 Core Interface APO

SCM230 Supply Network Planning (SNP)

SCM240 Production Planning (ERP)

System RequirementsThis document applies to SAP APO releases 3.0A and 3.1 and to SAP SCM releases 4.0, 4.1, 5.0 and5.1 (2007).

Duration and TimingDurationCreating 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.

TimingThe best time to apply this Best Practice is during the planning phase or during the implementationphase of your SAP solution.

How to Use this Best PracticeFirstly, 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 SAP SCMBest Practice. Record all the relevant steps in your core business process; use the example businessprocess 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 owntemplate. Complete the information according to your specific requirements, for example, frequencyand time of monitoring activity. If the process step includes CIF data transfer, add the information fromthe 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 businessprocess 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 sectionSystem 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 tomonitor.


© 2008 SAP AG

4

Preliminary Information

The SCM System LandscapeThe substantial components of an SAP SCM system landscape are summarized in the following tableand shown schematically in the subsequent figure.

SAP APO System The SAP Advanced Planning and Optimization system facilitates thestrategic, tactical, and operational planning processes.

APO consists of several software components: a relational databasesystem (RDBMS) just as there is in any R/3 system, known as the APODB; an SAP Web Application Server (or for releases up to APO 3.1 anR/3 Basis); the APO application programs; a separate, very fast object-oriented SAP DB database called liveCache; application programsrunning in liveCache – the COM routines; and a number of programs thatexecute elaborated optimization algorithms, called the optimizationengines. These components can run on the same or on different servers.

OLTP System The Online Transaction Processing system covers functionality for salesand distribution, material and inventory management, controlling, shopfloor control, logistic execution, and so on.

OLAP System An Online Analysis Processing system, such as SAP BusinessInformation Warehouse (BW), provides cumulated historical data as abasis for future extrapolation purposes in APO Demand Planning.

SAP R/3 Plug-In

OLTPSystem

RDBMS

SAP R/3 Plug-In

OLTPSystem

RDBMS

RDBMS

SAP APOSystem

liveCachelive

Cache

OLAPSystem

RDBMS

The various strategies for using SAP APO, SAP R/3, SAP Business Information Warehouse(BW), and possibly other data processing systems in combination are called integration scenarios.

Data for planned independent demand can enter the Supply Network Planning (SNP) moduleeither through the Demand Planning (DP) module, or from external systems. Since SNP can have


© 2008 SAP AG

5

some or all of its Key Figures in the time series liveCache, data can enter it in the same manner asthey enter Demand Planning. Usually, an APO system is connected to one or several systems thatprovide historical and actual data, for example, sales figures, for your Supply Network Planningbusiness process. These systems can be SAP R/3, SAP BW, and / or third party and legacy systemsor a combination of these. As APO comprises a complete SAP BW, the tools for extracting data fromother systems and transferring them to APO for demand planning purposes are the same as thoseused by SAP BW. The APO BW reads the data using remote function call (RFC) techniques, IDocs, orOS file access. In addition, data such as sales orders, stock, production orders or purchase orders canbe sent from R/3 to SNP as order objects through the Core Interface Function (CIF), which isdescribed in the corresponding Best Practice Manage APO Core Interface in SAP SCM.

On the other hand, the planning results of the supply network planning process are fed intoother applications for further planning or execution purposes. The system types that can be used hereare APO itself - in particular its modules DP and / or PP/DS, SAP R/3, or again third party, or legacy,systems. The latter is not considered in this Best Practice document.

This Best Practice is therefore based on a general and common integration scenario for settingup an SAP Supply Chain Management solution using SAP APO. As data sources, SAP BW, SAP R/3,and flat files can be connected to the SAP APO system.


© 2008 SAP AG

6

SAP Advanced Planning and Optimization (APO) is the planning component of SAP SCM, theSupply Chain Management solution provided by SAP. SAP APO is used to make strategic, tactical,and operational decisions and supports you in performing the following planning activities:

Demand Planning (DP) Supply Network Planning (SNP) Production Planning (PP) Detailed Scheduling (DS) Deployment Transport Load Builder (TLB) Transport Planning and Vehicle Scheduling (TP/VS) Global Available-to-Promise (gATP)

SAP APO is most of all a planning tool, although some industry specific execution functions areavailable, for example, production backflush for repetitive manufacturing.In standard business scenarios, execution functions, such as confirmations, goods receipt,purchasing, and so on are performed in the SAP R/3 OLTP system, which contains all functionality for,among other things, Material Management MM, Sales and Distribution SD, Production OrderProcessing PP-SFC, Logistics Execution LES, and Controlling CO.


© 2008 SAP AG

7

Supply Network PlanningThe individual core business process and its modeling in SNP for planning your supply network maydiffer more or less from the canonical process described and illustrated as follows.

Description: The process flow above describes a typical SNP process flow. Before data can beloaded into Supply Network Planning, a planning area and planning version must be created andinitialized. The planning version can consist of order key figures, time series key figures, or both.

After initialization, data can be loaded into SNP in several ways: by releasing a forecast from DemandPlanning, by CIF transfer from R/3, or from a flat file using a BAPI (Data from BW can only come toSNP either via BAPI or by transferring it through the APO data mart into a DP planning area, fromwhere later a release to SNP can be done).


© 2008 SAP AG

8

Many customers then execute a batch job to calculate safety stock: in some cases this is doneseparately from the main planning run using report /SAPAPO/MSDP_SB. In other cases, it iscalculated by a macro during the heuristic or optimizer run, depending on which safety stock planningmethod used.

Most customers then run either the SNP Optimizer or the SNP Heuristic, depending on the size of theproblem and whether they can meet their needs with the infinite planning considered by the Heuristic.After the run is complete, planners usually check the results in interactive planning, possibly usingalerts. If the SNP Heuristic has been run, Capacity Leveling is often performed on bottleneckresources to ensure that a feasible plan is created.

Often customers perform a variety of tasks via batch macros: these can be used to generate alertsand perform further calculations on the data either before or after the planning run. Many SNP processflows then exchange requirements with suppliers – often using collaborative planning.

At some point in the planning flow, some SNP customers use remote InfocCubes in a BW system forreporting on the SNP plan. The SNP planning results can also be sent to R/3 using the CIF interface,where the planned orders and purchase requisitions produced by SNP planning are then furtherprocessed using MRP. In other cases, the constrained forecast calculated by SNP can be releasedback to DP, and used in evaluating the feasibility of a forecast. Another use for the SNP data is totransfer it to PP/DS, where a more detailed, single-location planning is performed. After the PP/DS runoccurs, the deployment algorithms - either heuristic or optimizer based approaches are available - canbe used to plan transfers of single location products from one location to another, and to implementfair share rules. Although deployment is a short-term planning, it uses algorithms similar to the SNPheuristic or optimizer, so it is classed within SNP. In some cases, a detailed transport load is needed toconsider transport load building constraints (min-max load) and to ensure that loading of thetransportation resources for multiple products is feasible. Some comment is also needed about theuse of /SAPAPO/RLCDELETE: since SNP alone is not an execution system, many customers alsouse this report to clean the order objects from the planning version used for SNP Planning after theresults of the planning run have been sent to their respective destinations.

The system can automatically split the data set and automate the parallel scheduling of batch jobs.This is already possible in SAP SCM 4.0 for most Demand Planning and Supply Network Planningprocesses. With SAP SCM 5.0 and SAP SCM 4.1 (SP 4 – note 779850) this is also available for:

Deployment Heuristic

Transport Load Builder

Master Data Initialization

Consistency check

Time Series consistency check

Saving of optimizer results to liveCache

Capable to Match (CTM) (only SAP SCM 5.0)

For all functions, it is possible to specify a parallel processing profile to control the parallelization. Itcontains:

Maximal number of parallel work processes

Maximum block size

Server group (optional)

Capable to MatchIf you are using CTM as a planning tool within your Supply Network Planning network – also consultthe above figure and paragraph – there are usually some differences to the SNP standard process.For this purpose, we also provide here a typical business process involving CTM. The numbering ofthe process is oriented on the SNP process to make finding related sections in this document easier.Of course, your specific process might differ more or less from this canonical process:


© 2008 SAP AG

9

Description: The process flow is quite similar to the process flow of SNP above and therefore notdescribed in detail again. Of course, you have to keep in mind that CTM can also be used with PP/DSorders and PP/DS PPMs. This then implies differences in the processes, for example, that ininteractive planning, transaction /SAPAPO/RRP3 is used more often than /SAPAPO/SNP94. Pleaseconsider the following overview for a better understanding.

Overview: Multilevel Supply and Demand Matching (SDM) is the umbrella for the SAP APO solutionfor matching prioritized customer demands and forecasts to a set of supplies, while taking the currentproduction capacities and transport capabilities into consideration.

SDM's approach is production flow-centric, not production resource-centric, as is the case withtraditional planning approaches. SDM does not consider the individual distribution and productionlevels of the supply chain one after the other, but considers all possible paths through the distributionand production levels together. For each demand element, the search is performed through the supplychain and the first possible way to fulfill the demand element is determined.

Multilevel Supply and Demand Matching (SDM) is the umbrella for the SAP APO solution for matchingprioritized customer demands and forecasts to a set of supplies, while taking the current productioncapacities and transport capabilities into consideration.

SDM aims at a medium to long-term planning horizon and guarantees a timely multilevel synchronousproduction flow, triggering the flow only when necessary. Because SDM is order-based, it requires atool that also supports a multilevel dynamic order split.

Capable-to-Match (CTM) is the central planning tool of SDM. In addition, an order-based method ofSupply Distribution and a tool that provides a graphical, flow-oriented view of the supply chain,complement this application.

SDM complements the cross-plant supply chain planning strategies of the SAP APO applicationsSupply Network Planning (SNP) and Production Planning and Detailed Scheduling (PP/DS).


© 2008 SAP AG

10

Therefore, it is also necessary to read especially the SNP Feasibility Check Assessment Guide tounderstand the entire business process.

The business area Multilevel Supply and Demand Matching – similarly to SNP – covers the followingactivities:

Supply Chain Planning

Creating feasible plans for purchasing, manufacturing, distribution and transportation

Integrating purchasing, manufacturing, distribution, and transportation planning for themidterm

Making sourcing decisions through the Supply Network

Categorizing supply to meet prioritized demands

Synchronizing activities and plan material flow throughout the supply chain

Capable-to-Match (CTM) planning is the planning tool in SDM. It uses constraint-based heuristics toconduct cross-plant checks of production capacities and transportation capabilities based onpredefined supply categories and demand priorities. At the same time, existing supplies are clearedwhen matching them with demands. The aim of the CTM planning run is to propose a feasible solutionfor fulfilling demands.

CTM first prioritizes the demands then schedules them one after the other in the prioritizationsequence. CTM then matches the supplies and demands on a first come, first served basis whiletaking the production capacities, transport options and existing supplies into consideration.

Customers often use CTM as an alternative to the SNP heuristic or SNP optimizer. However, there arealso customers using CTM in the PP/DS environment. For such cases, also refer to the Best Practicedocument Manage Production Planning in SCM / APO.

The CTM engine runs on an extra optimizer server, which must be based on Windows NT/2000/XP.This will connect to an APO application server using Remote Function Calls (RFC). During installation,or after configuration changes, make sure that the connection to the optimizer server maintained inSM59 still works correctly.

ProcedureIn applying this Best Practice procedure, you create a company-specific process-oriented monitoringconcept. This concept consists of monitoring activities to be performed for each business-processstep and its respective monitoring objects.When adapting this concept for your company, you must specify the times, responsible teams, andescalation paths (teams) for the monitoring activities associated with each business-process step andits monitoring objects.In each of the business process steps described below, you will find the following information:

A detailed functional description of the process step Monitoring activities for the process step Error handling, restartability, and escalation A monitoring object table, listing each relevant monitoring object, showing the:

o Monitoring objecto Monitoring transaction or toolo Monitoring frequencyo Monitoring time (intentionally left blank, to be filled in according to your schedule)o Indicator or erroro Monitoring activity or error handling procedureo Responsible teamo Escalation procedure

https://service.sap.com/~sapidb/011000358700007382512002E


© 2008 SAP AG

11

As the frequency of SNP planning processes varies from daily activities at certain companies to onlymonthly or quarterly at others, the monitoring frequency in these monitoring object tables is partly onlya rough estimate and has to be adapted to your particular business process. During the Going Liveand stabilization phase of your APO implementation project, all items listed in this document should bemonitored tightly. After becoming more experienced with system behavior, error occurrences, andapplication operations, the monitoring frequency can be decreased, but should never be reduced tozero unless you do not use the respective function. Important planning jobs usually have to bemonitored after each run. Regular jobs of minor priority, for example, certain clean-up jobs, can bechecked less frequently than the actual scheduled run times. For example, daily jobs can be checkedweekly.The following seems obvious but should nevertheless be mentioned: Besides the monitoring of jobsdescribed in the business process steps below, it is essential that you check all jobs that are running inyour system at least several times per day for abnormal terminations. For status “cancelled”, see ErrorHandling, Restartability and Escalation. You should investigate and correct these terminationsappropriately. This check can be done easily, for instance, with transaction SM37 by entering the timeinterval since the latest check and selecting all jobs with status “cancelled”. If you have no automaticnotification in place that informs the people responsible for Program Scheduling Management in yourSupport Organization of abnormally terminated jobs, you need to take measures to ensure that this isdone manually in a reliable and timely manner.A number of jobs must run periodically in a live R/3 installation, for example, the jobs for deletingoutdated jobs or spool objects. For details and comments, see SAP Note 16083.

Business Process Step 1: Initialize PlanningVersionBefore a new planning version can be used in SNP, the planning version must be initialized for an SNPplanning area. How the planning area is initialized depends on whether it contains only order objects,or whether some or all key figures are time series key figures. For order objects only, initializing theplanning area is straightforward: execute transaction /SAPAPO/MSDP_ADMIN and find the planningarea of interest; in most cases, the standard 9ASNP02 is used for order objects. Right click on theplanning area, choose “initialize planning version”. Type in the name of the planning version, andexecute. For planning versions with significant amounts of master data, select the “execute inbackground” option. General information on handling problems with version management is availablein SAP Note 519014.When you need to change the validity period on a planning area with time series objects, simply entertransaction /SAPAPO/MSDP_ADMIN, right click on the planning area, and choose “Create TimeSeries”. Then, enter the existing planning version and the new start and end dates for the time seriesthat are desired. For large data volumes, it is preferable to use the option “Execute in Background”, sothat the program will not time out and so that the monitoring tools of SM37 are available.In SCM 5.0 it is possible to compare the results of the planning based on different master data sets.For that purpose, the standard SNP planning book contains additional key figures that can be linked toa second planning version.

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 forinconsistent time series objects using report /SAPAPO/TS_LCM_CONS_CHECK_ALL or/SAPAPO/TS_LCM_CONS_CHECK. 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,while /SAPAPO/TS_LCM_CONS_CHECK has a parameter screen that allows the user to choose aplanning area and to decide whether to correct the inconsistencies. SAP Note 358283 gives adescription of the report.


© 2008 SAP AG

12

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error

Monitoring Activity orError Handling Procedure

Respon-sibility

EscalationProcedure

Initializeplanningversion

Report/SAPAPO/TS_LCM_CONS_CHECK

As oftenas youchangemasterdata

Status Run the job periodically toensure that processes suchas delta initialization of theplanning area have notcreated extraneous objects inthe liveCache

Programschedulingmanagement

Contactapplicationsupport


SM37 Depend-ing onbusinessprocess

Status Ensure that job completessuccessfully




SM37 Depend-ing onbusinessprocess

Status/messages

Whether or not the jobcompletes successfully,monitor the messages in thejob log to ensure that noerrors occurred

Applicationsupport

Contactprocesschampion

See general issues of Error Handling, Restartability and Escalation below.


© 2008 SAP AG

13

Business Process Step 2: Load DataDepending upon your business process, it may be that you periodically load either only transactionaldata or both master data changes and transactional data into SNP. Transactional data is usuallyloaded into SNP by a release from Demand Planning to SNP, which is described in the Best PracticeManage Demand Planning in SAP SCM / SAP APO.

Master data changes cover the master data objects like location, product, resource, PPM andtransportation lane which are assigned to the model as the characteristic combinations. If new masterdata are loaded into a model, 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 andcheck the output in SM37 afterwards. The profile used should be restricted to the functionality anddata which you are actually using. After loading new master data, the data must be initialized for SNPplanning. When the planning area contains time series key figures, this has to be done by reinitializingthe SNP planning area in /SAPAPO/MSDP_ADMIN or alternatively, by running report/SAPAPO/TS_PAREA_INITIALIZE. When the planning area does not contain any time series keyfigures, this can either be done by reinitializing the SNP planning area or automatically by startingSNP interactive planning or SNP mass processing.

Additionally, the consistency check report can be used in repair mode. The consistency check shouldalso be executed if the master data are changed in APO but not visible or accessible via SNP. Foradditional information see SAP Note 577038.Usually, master data changes are sent by CIF from R/3 to SNP. If this is the case, you need toregularly check and update the selection data tables for the Planning Area(s) used for SNP. To do this,execute report /SAPAPO/MCPSH_GEN_SELTAB_MGM. There exists a consistency check forselections, in addition to functions for adding and deleting the functions. However, please read Note332812 carefully before using this report to automatically correct inconsistencies. All CIF datainterchanges should also be monitored as described in the Manage APO Core Interface in SAP SCM.Some customers also load data using a BAPI. If large amounts of data are loaded by BAPI, it ispossible that tables /SAPAPO/TSQ* can become very large and cause performance problems. Ensurethat only delta records are loaded by the BAPI, and reinitialize the planning area using report/SAPAPO/TS_PAREA_INITIALIZE to prevent this problem.

Monitoring ActivitiesApart from safeguarding the general availability and consistency of the system components SAP APO,SAP BW, and SAP R/3 OLTP, to safeguard this business step SAP recommends that you monitor theobjects listed in the following table.

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

Master data /SAPAPO/CONSCHK

Whendata aremodified

Messages Check log of consistencycheck for master data objectsthat display inconsistencies.

Applicationsupport team


Master Data /SAPAPO/CONSSHOW

Whendata aremodified

Messages Check log of consistencycheck



See general issues ofError Handling, Restartability and Escalation below.


© 2008 SAP AG

14

Business Process Step 3: Safety StockPlanningThere are two types of safety stock methods in SNP: standard methods (SB, SZ, SM, MB, MZ, andMM) and advanced methods (AT, AS, BT, BS). Standard methods are performed in macroSAFETY_CALC, see note 504253 for an introduction. Advanced methods are performed in report/SAPAPO/RSDP_CALC_SAFETY_STOCK (transaction: /SAPAPO/MSDP_SB). In the remainder ofthis section, only advanced methods are considered.The advanced safety stock methods used in SNP are based on the following assumptions (see alsonote 617567):

Demand is regular, that is, there is demand in almost every planning period, the demandquantities are significantly greater than zero and do not fluctuate too much between planningperiods. “Spare parts” is a business area that usually does not meet this assumption.

In case of shortage, the missing parts can always be delivered belatedly, that is, no demandgets lost (backorder case).

If neither regular stock nor safety stock suffice to cover the whole demand, the remainder ismade available using alternative arrangements, for example, rush shipments (no delayapproach).

All uncertainties in the supply chain are statistically independent of each other.

Please be aware that the safety stock values calculated may differ significantly from the correct ones ifone or more of these assumptions are violated. In extreme cases, the methods will not calculate anyreasonable values.

Also, make sure that the supply chain does not contain "cycles" for the location products to beplanned. In this context, a cycle is a sequence of PPMs and/or transportation lanes that transform alocation product on to its self. If such cycles exist Safety Stock Planning will be caught in an endlessloop unless SAP Note 547049 has been applied.Safety stock calculations for different location products are independent of each other. Therefore, theorder of calculations is arbitrary. If you need to improve performance, you can execute parallelprocessing by creating separate variants for transaction /SAPAPO/MSDP_SB and running them at thesame time. In general, to avoid lock issues, it is advisable not to make changes to the SNP planningversion in which safety stock is run. Please also consider notes 599871 and 600766.Be aware that with release SCM 4.0, the results of extended safety stock planning can no longer besaved in auxiliary key figures, but in time series key figures only. In addition, the previous SNPstandard planning folders (9ASNP94, for example) only support the methods SB, SZ and SM forsafety stock planning.As of Release SCM 4.0 Support Package 08, a new 9ASNP_SSP SNP standard planning book existsfor the safety stock planning, which contains two specific time series key figures for safety stockplanning (9ASAFETY, 9ASVTTY). The 9ASNP_SSP folder supports all methods of the safety stockplanning in SNP (SB, SZ, SM, MB, MZ, MM, AS, AT, BS, BT). Please consult SAP Note 646738 fordetails.As of Release SCM 5.0, the Safety Stock for sporadic demand can be calculated with a standardplanning profile. This makes Safety Stock Planning also suitable for industries such as spare parts.New fields in the product-location master data also enable a Replenishment lead time determinationand the consideration of maximum and minimum Safety Stock LevelsAs of Release SCM 5.0, it is possible to aggregate the method parameter values, demand, andreplenishment lead time on a detailed level and use the results instead of the values from headerlevel.

Monitoring ActivitiesThe monitoring activities needed to ensure that safety stock planning runs are executed correctly areindicated in the table below.


© 2008 SAP AG

15

Jobs for Running and Monitoring "Safety Stock Planning"To ensure consistency and good performance of safety stock calculations, schedule the following jobsto run on a regular basis:

Calculate safety stocks with advanced methods with report/SAPAPO/RSDP_CALC_SAFETY_STOCK. This report calculates the safety stock associatedwith reorder point methods (either alpha or beta service level; reorder cycle or reorder point).

When checking the spool file, look especially for messages in the form of:"Product &1 in location &2 cannot be procured.”This indicates an error in the procurement type for the location product, which should be corrected bythe application support team. Most commonly, the error is caused by a location product withprocurement type E (in-house production) for which there is no valid PPM. For such location products,no safety stock can be planned since there is no way to procure it.When checking the job in SM37, in addition to looking for jobs which cancelled, also look for largevalues in the field Delay(sec), which might indicate that the job had to wait for another process torelease locked data, and make a note of which other processes were running concurrently.

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO Report/SAPAPO/RSDP_CALC_SAFETY_STOCK

SM37 Eachtime thereport isrun

Check spool file for errors.Look for large values ofDelay (sec) in SM37.


Contactapplicationsupport team.


Business Process Step 4: SNP Heuristic RunIn Release 3.x, the SNP heuristic performs infinite planning for the supply chain. It can be run in one ofthree modes: Multilevel (all products at all locations), Network (all locations, but BOM is only explodedto one level) or Location (all products at one location, but a full BOM explosion takes place).In Release SCM 4.x, the handling of heuristic has been enhanced (not for interactive planning). Fortransaction /../snp01, the following changes have been made:

The heuristic can be executed in two modes. Network (selected products in all locations) orLocation (selected products in selected locations).

In addition to both modes, you can set a flag to perform a full BOM explosion. This enables toplan a part of the network but on all levels.

o For this, the report /sapapo/rsnpllcset has to be performed to determine the low-level-code of all products of a version. This should be done on a regular basis but has to bedone after relevant master data changes (for example, transportation lanes or PPMs)

Use of the Net Change planning flag is not recommended, unless the number of location products ishigh and the number of changing demands is comparatively small. Net change planning is onlyavailable in the active version (000). The entries of objects flagged for net change planning can beviewed from transaction /SAPAPO/RRP_NETCH.

When there is enough demand, it can be cheaper to distribute directly from the plant to the customer.The Planning algorithms are up to SCM 4.x not able (except partly the optimization) to take this intoconsideration, especially because this is typically a multi-product decision. In SCM 5.0 the SNPHeuristic is enabled to decide for a direct ship, instead of considering the quotations. For this aTransport Load Builder check is carried out to comply to load limits on multiple products.

SCM 5.0 allows users to perform an SNP run on an aggregated level, by defining hierarchies forproducts and locations to be taken into account by the SNP heuristic, A disaggregating logic isavailable to ensure that plans are consistent at all levels of aggregation and the Interactive Planningoffers extended drilldown options for displaying the planning results. Larger supply chain models canbe planned, performance improvements by calculation on aggregation levels can be achieved and theplanning process is simplified.


© 2008 SAP AG

16

To set up the aggregated planning in SNP:1. Define the aggregated planning objects (MD aggregates: location aggregates, product aggregates,BOM/Routing aggregates, resource aggregates)

2. Define the relations between aggregated objects and detailed objects (define location-product-hierarchies, BOM/Routing hierarchies, resource hierarchies)

3. Generate aggregated transactional data based on the definition of aggregated master data

4. Perform Supply Network Planning based on aggregated master data and transactional data

5. Disaggregate planning result to detailed level (optional)

To set up interchangeability in SNP Heuristic:

In Supply Network Planning (SNP), both heuristic-based and optimization-based planning take intoaccount the interchangeability of products. You can use product interchangeability in the SupplyNetwork Planning run to transfer demands for a product that is to be discontinued onto a successorproduct for instance, or to use existing stock of a current product to fulfill demand for the successorproduct.

SNP supports the following product interchangeability methods:

Supersession chain

FFF classesYou have to use the standard SNP planning book called 9ASNP_PS with data view PROD_SUBST tobe able to take product interchangeability into account in Supply Network Planning. This planningbook contains the required key figures Substitution Demand and Substitution Receipt and an adaptedmacro (that takes these key figures into account) for calculating the stock balance. However, you canalso create your own planning book based on this standard planning book.

To set up an interchangeability scenario, you need to define the necessary interchangeability masterdata, that is, either a supersession chain or an FFF class. You can do this via transaction /INCMD/UI.

For interchangeability, only location heuristic run is allowed; you perform this either in Interactiveplanning (using planning book/data view 9ASNP_PS/ PROD_SUBST) or in transaction/SAPAPO/SNP01.

If you run interchangeability scenario via transaction /SAPAPO/SNP01, make sure you have the flag“Add products from supersession chains” set.

After running the SNP heuristic with interchangeability scenario, in the application log you will seeinformation about the number of substitution orders created, also you have the possibility to accessthe details of the substitution orders.

Some special features as of SCM 2007:

You have the possibility to control how existing stock is used up with BADI/SAPAPO/SNP_INC_STFW

You have the possibility to control the handling of horizons with BADI/SAPAPO/SNP_INC_HRCH

Stock is forwarded over the whole supersession chain

Validity of interchangeability rules are considered at target locations as well

Stock forwarding algorithm with FFF classes is also enhanced, a member product can forwardstock directly to another member products.

If the heuristic run is executed in Version 000, the inbound or outbound queues in the R/3 systemshould be locked during the time of the heuristic run:


© 2008 SAP AG

17

If you cannot rule out that, during the heuristic run, data will be transferred from an SAP R/3system to the SAP APO system (or from APO to R/3) over the core interface (CIF), you canlock inbound or outbound queues in the SAP R/3 system from the SAP APO system. Thisshould prevent inconsistencies occurring in the planning if, during the heuristic run, transactiondata is transferred from SAP R/3 to SAP APO that is ignored by the heuristic.

To lock outbound queues, you can use the /SAPAPO/CIFSTOPQUEUES and/SAPAPO/CIFSTARTQUEUES reports in SAP APO. Reports RSTRFCI1 and RSTRFCI3 areavailable for locking inbound queues. See also SAP note 487261 / 528913.

Occasionally, with the import of a support package, the length of data fields in report variants canchange, which can cause inconsistencies if not corrected. Fortunately, this problem can be alleviatedby running report RSVCHECK after implementation of a new support package.

Monitoring ActivitiesRegarding SM37: when several heuristics identify large values of “Delay (sec)”, it is recommended thatyou investigate the possibility that another process (or several parallel jobs) is locking one another.While the processes are running, locks on the APO database can be seen with transaction SM12.

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO report/SAPAPO/RSNPDRP1

This reportperforms theSNP heuristicrun.

SM37 Dependsonbusinessprocess

Status Check if job is running asscheduled. Also check thecolumn “Delay(sec)- largevalues may indicate thatanother process was lockingthe job, and it waited for theother process to finish.

If the report is not scheduledas provided by ApplicationSupport, schedule itaccordingly.



Spool file ofreport/SAPAPO/RSNPDRP1

SM37 As oftenasheuristicisexecuted

Log file Check whether the spool filehas any error messages, orstrange results (e.g. manyorders, each with a quantityof 1 for the same location-product on the same date)

ApplicationSupport


Application logof report/SAPAPO/RSNPDRP1

Slg1 As oftenasheuristicisexecuted

Log file Check whether the spool filehas any error messages.

ApplicationSupport


SCM report/sapapo/rsnpllcset

Sm37 On aregularbase butafterrelevantmasterdatachanges

Status Look for error messages likecycles. They are not allowedfor SNP.



Reportvariants

RSVCHECK

Once amonth, orafterimportingnewsupportpackages

List ofvariantswithproblems

Check if any variants haveproblems





© 2008 SAP AG

18

Business Process Step 4a: CTM Planning RunCritical steps in CTMThe three critical areas for performance during CTM run are loading and preprocessing of data,runtime of CTM engine and the writing of the results to liveCache. In case of performance problems, itis crucial to determine which of the areas is critical -> Please see section “Monitoring Activities” fordetails.

The most common reasons for poor performance are:

1) Slow reading and preprocessing of data:a) Order selection is slow:

- due to deletion of orders taking too long

- due to many orders being selected

- due to pegging being analysedPossible solutions:

- Filter demands and supplies considered by date

- Reduce the planning horizon considered

– for example, try to consider planning runs with shorter horizon during theweek and with long horizon on weekends

- Optimize the parameter package size for orders selection in /n/SAPAPO/CTMCUST

- Verify whether you really need all the selected location-products to be planned for

b) Reading further data (products, PPMs, resources, transports) is slowPossible solutions:

- Filter master data using only actively planned (by CTM) objects;

- Verify whether, for example, all the activities of a PPM need to be planned as wellby CTM

c) Slow prioritization of demandsPossible solutions:

- Of course the time for prioritization is depending on the amount of selected orders,so primary goal should be to only select the ones necessary for the CTM run

- In the time for prioritization of demands, rule determination and evaluation are alsoincluded. Best for performance here is of course to use setting “Do Not ApplyRules”. However, if rules are necessary try to use “Apply Default Rule” instead of“Apply Rules!” and evaluate whether planning parameter “DEFAULT_RULE” isapplicable (see SAP Note 441723).

2) CTM engine is slow:

Possible solutions:

- Use Aggregation

- Reduce horizons for late and early demand fulfillment as much as possible

- Filter demands by order category and date

3) Writing to liveCache is slow:

Possible solutions:


© 2008 SAP AG

19

- Use asynchronous liveCache update

- Optimize package size for creating orders

- Optimize package size for creating pegging relationships

- Optimize package size for asynchronous liveCache update

Important additional performance settingsSome specific performance relevant settings and referral notes are briefly discussed in the followingparagraphs:

Set the indicator “Do not Evaluate Pegging Relationships” in the technical settings of the CTMprofile, to delete all non-firm orders without any further checks. (In APO 3.0A and 3.10 this settingmust still be carried out via the planning parameter “FAST_DEL”.) The system then does notcheck, for example, whether a pegging relationship exists between an order and a demand thatlies outside the planning horizon. This means that the system will certainly delete the order. If youdo not require these checks, you can set the indicator to shorten the runtime of the orderselection. If all orders lie within the planning horizon, checks are not required as the result of theorder selection is the same with or without the checks. Note that this indicator must not be used inconnection with subcontracting, as the system must evaluate pegging relationships for deletingsubcontracting orders. Also, only use this indicator with planning mode “Replan all Orders” anddeletion mode “Delete all Non-Firm Orders”. If this functionality is used in combination with amaster data selection, all orders which contain at least one location product of the master dataselection will be deleted. For more information about this setting, refer to note: 533457.

During the demand prioritisation and supply categorisation, the demands and supplies are storedin database tables /SAPAPO/CTMDEM, /SAPAPO/CTMSUP, /SAPAPO/CTMMAP). Thesedatabase tables can grow with every new CTM profile, new planning version in a CTM profile.During a CTM planning run for the current CTM profile and planning version entries for demandsand supplies are deleted form the database tables, entries are created and entries are read to behanded on to the CTM engine. If there are many entries in the database tables, thedelete/read/write accesses can be time consuming. If these tables contain many entries, they canbe deleted by using program /SAPAPO/CTM_DEMSUP_DELETE Also see note 375174 forfurther details. The table entries are automatically deleted if the planning version is deleted or theCTM profile is deleted. With release SCM4.1, it is possible to decide (customizing setting) if thesetables should be updated for a CTM planning run or if the data is directly transferred.

Asynchronous liveCache update: The default setting of the CTM engine is synchronous liveCachewriting. This means that after the CTM engine has finished, the system starts writing the wholeresult to the liveCache. When changed to asynchronous update, writing is carried out in parallel toplanning. After finishing a certain planning package (a planning package is finished after aspecified number of demands were planned by CTM) the result is written to the liveCache whilethe CTM engine continues planning. In cases where liveCache time and engine runtime areapproximately the same, this setting can save up to 50% of the time, as those steps will then runin parallel.

The runtimes of “order selection” and “writing to liveCache” also strongly vary according to thechosen package sizes. The relevant parameters are maintained in /SAPAPO/CTMCUST.However, the package size parameter for asynchronous liveCache updates can also bemaintained via the variable planning parameter “PackageSize” for each CTM profile. Pleaseconsider the following points for optimal settings for these parameters:

1. The setting for Order Selection is based on location-products rather than on number orders. If,for example, the parameter is set to 5000, CTM reads the orders for the first 5000 locationproducts in one package from liveCache. If the average amount of orders per location productcombination is

a. 0.2 (each fifth loc-prod. has an order), the result is 1000 orders per package

b. 10 (each loc-prod. has on average 10 orders), the result is 50000 orders per package

As you can see, this setting strongly depends on the orders (including fixed orders, PP/DSorders) existing per location-product. Therefore, it is important to try different settings to clarifyperformance issues. As a guideline, SAP expects values of 10000-50000 orders per packagefor optimal performance


© 2008 SAP AG

20

2. The setting for the package size for asynchronous liveCache Update considers the existingrequirements and creates orders for them. The PackageSize parameter determines here thenumber of requirements considered before sending the resulting orders to liveCache. Thepossibility exists that several orders have been created per requirement or just one. Therefore,the parameter does not imply that the package includes 500 orders, if this is the currentsetting; it only means that 500 requirements are considered and the respective orders sent inone package.

It is only necessary to change this parameter if the CTM engine is waiting for the liveCache(the queue for packages to be transferred to liveCache increases as liveCache is not dealingwith the necessary updates fast enough). One can then look into the CTM Application log andfind the number of orders transferred per package depending on the most relevant categories:

a. planned orders / production orders

b. purchase requisitions

c. transport orders

d. substitution orders

The amount of orders per package coming from these categories together should result in atleast 5000 orders per package to have optimal performance.

Note that using CTM in parallel is not usual and often not practical. Before using CTM in parallel itis crucial to verify that the two (or more) subproblems to be run in parallel are truly and completelyindependent / non-overlapping! Refer to SAP Note 430688 for more information.

Monitoring ActivitiesCTM Run

Monitoring the CTM run includes understanding how long each of those three steps takesapproximately to see where possible problems may be situated. For this information to be recorded,you need to have the “Save CTM messages”-Box on the “Settings”-tab in the CTM profile activated,which results in a brief application log being written. To find the information written in th log go to:

- /SAPAPO/OPT11, then select the appropriate CTM run and click and press on the “Log”-icon, or

- /SAPAPO/CTM -> result analysis -> display logs and choose the appropriate log from the list; fromhere the times and the warning messages should be regularly analyzed after CTM runs.

1) Estimate for loading data and preproccesing:end time of reading transports - start time of selecting orders;

2) Rough estimate for CTM engine runtime (This might be wrong with asynchronous liveCacheupdate, if the writing is so slow that the CTM engine stops. In case of doubts about theruntime estimate for the CTM engine, the CTM trace file has to be looked at and the timestamps for “Engine Start” and “Engine Finished” have to be considered; this time estimate ismore exact, but also more time consuming;):end time of entry for CTM Planning run in SM37->Job log - end time of reading transports;

3) Rough estimate for writing data to liveCache:Sum of the differences between End and Start times of each package to be written toliveCache.

4) In case there is safety stock being build up, there will be a second CTM run after the end ofthe first one. Determining times here works accordingly.

CIF Queues

In addition to those steps, please notice that the CIF Queues should be locked during the execution ofthe planning run to prevent inconsistencies. Please see SAP Note 528913 for a full discussion. Notethat this does not apply if the CTM run is executed on an inactive planning version. Also note that you


© 2008 SAP AG

21

should upgrade your CTM engine in parallel with support package upgrades to ensure optimalfunctionality and performance. In general it is always good to take the newest available CTM engine.

Deleting locks after short dump during CTM run

In the event of a short dump during the CTM run, there are two options to delete locks which prevent anew start of the CTM engine:

1) Delete CTM engine run manually in transaction /SAPAPO/OPT03 before another run can bestarted. See Note 393634 for details. They are also deleted by the job/SAPAPO/OM_REORG_DAILY, which should be run once a day, but NEVER concurrently withany optimizer or CTM runs.

2) Enter the planning profile via /SAPAPO/CTM.

Jobs and Tools for Running and Monitoring "CTM Planning Run"To safeguard the functionality of the CTM planning run, refer to the monitoring jobs in the table below.For an additional list of transactions used to set up the engine during installation or changes to theoptimizer server, refer to the section Monitoring APO Optimizers in the Best Practice: Monitoring andAdministration for SCM/APO.

1. To run CTM in the background, use the CTM report /SAPAPO/CTMPLRUN. There are twooptions for deleting locks which prevent a new start of the CTM run in the event of a shortdump during the CTM run:

a. Delete the run manually in transaction /SAPAPO/OPT03 before another run can bestarted. See Note 393634 for details. Locks are also deleted by the job/SAPAPO/OM_REORG_DAILY, which should be run once a day, but NEVERconcurrently with any optimizer or CTM runs.

b. Enter the planning profile via /SAPAPO/CTM. This will automatically delete the locktable entries

2. To verify that the optimizer server is running correctly during the run:

a. Lists of users and processes running on the optimizer server can be seen fromtransactions /SAPAPO/OPT03 and /SAPAPO/OPT12 respectively. With thesetransactions, you can check whether processes are still active on the optimizer server.These transactions are usually only used for problem analysis beyond the CTMengine, for example, in case of hardware or operating system problems on theoptimizer server.


© 2008 SAP AG

22

MonitoringObject

MonitorTA/Tool

MonitorFreq.

Moni-torTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO reportCTM:/SAPAPO/CTMPLRUN

This reportruns theCTM in thebackground

SM37 Depending onyourprocess.

Status Check if job is running asscheduled.

If the report is notscheduled as provided byApplication Support,schedule it accordingly.



CTMapplicationlog

/SAPAPO/CTM ->resultanalysis ->displaylogsor/SAPAPO/CTMAPLOG

Aftereveryrun

MessageType

Review messages in logwith stop, red or yellowindicator

Applicationsupport


Spool file SM37 Aftereveryrun

Messagesin spoolfile

Check for applicationerrors after the CTM run,too.

Applicationsupport

ContactProcessChampion

OptimizerLogs

/SAPAPO/OPT11

In caseofcancellation ofengineor forperformanceanalysis

Check forerrors andtimestamps

Display and analyze logsin this section, if there isno result delivered fromthe optimizer.

Applicationsupport


/SAPAPO/OM_REORG_DAILY

Among itsotheractivities,this job willdeletedatabaseentries andfiles on theoptimizerserver whichare no longerneeded.

SM37 Daily Check if job is running asscheduled.

If the report is notscheduled as provided bysoftware monitoring team,schedule it accordingly.


Contactsoftwaremonitoringteamsupport


© 2008 SAP AG

23

MonitoringObject

MonitorTA/Tool

MonitorFreq.

Moni-torTime

Indicatoror Error


Respon-sibility

EscalationProcedure

Master Dataconsistencycheck

/SAPAPO/CTM ->Edit ->Checkyourdata

Aftermasterdatachanges

Check forinconsistencies

This job will identify anyinconsistent data prior torunning the CTM run

Applicationsupport


User list forOptimizers

/SAPAPO/OPT03

Seeabove

Displays a user list ofoptimization runs

Softwaremonitoringteam


Runningoptimizerprocesses

/SAPAPO/OPT12

Seeabove

Displays a list of optimizerprocesses on theoptimization server




Business Process Step 5: SNP Optimizer RunThe CIF Queues should be locked during the execution of the planning run to prevent inconsistencies.Please see SAP Note 528913 for a full discussion. Note that this does not apply if the optimizer isexecuted on an inactive planning version. Also note that you should upgrade your optimizer in parallelwith support package upgrades to ensure optimal functionality and performance.To get an overview of the optimization system steps, refer to note 587407.

To improve the performance of an optimization run, refer to note 485018; in addition, simply set thefield “Number of Processes” in the background transactions for the optimizers. It will spawn parallelprocesses during some portions of the data read and model creation of the optimization run. Note thata single optimization-based planning run can use only one CPU on the optimizer server. Care shouldbe taken that the number of processes does not exceed the number of available batch processes forthis user on the system. Due to the runtime and memory requirements of the optimization engine, wemust also think about the model size and complexity. For an optimal performance of the optimizationengine, see note 454433.In the event of a short dump during the optimizer run, the optimizer run must be manually deleted intransaction /SAPAPO/OPT03 before another run can be started. See Note 393634 for details. Theyare also deleted by the job /SAPAPO/OM_REORG_DAILY, which should be run once a day, butNEVER concurrently with optimizer runs.If several optimization runs are carried out in parallel, they should never have the same names. Alsoensure that you have applied Note 572220 (APO 3.0A, SP23; APO 3.1A SP13) to prevent loss ofoptimizer result logs. In addition, if you ever run two optimizer runs simultaneously, be sure to set theparameter enque/delay_max in transaction RZ11 as described in consulting note 572996 to avoid lockproblems.

SCM 5.0 allows users to perform an SNP run on an aggregated level, by defining hierarchies forproducts and locations to be taken into account by the SNP heuristic, A disaggregating logic isavailable to ensure that plans are consistent at all levels of aggregation and the Interactive Planningoffers extended drilldown options for displaying the planning results. Larger supply chain models canbe planned, performance improvements by calculation on aggregation levels can be achieved and theplanning process is simplified.

To set up the aggregated planning in SNP:

1. Define the aggregated planning objects (MD aggregates: location aggregates, product aggregates,BOM/Routing aggregates, resource aggregates)


© 2008 SAP AG

24

2. Define the relations between aggregated objects and detailed objects (define location-product-hierarchies, BOM/Routing hierarchies, resource hierarchies)

3. Generate aggregated transactional data based on the definition of aggregated master data

4. Perform Supply Network Planning based on aggregated master data and transactional data

5. Disaggregate planning result to detailed level (optional)

It is sometimes difficult to understand the results of the optimization, and to easily answer questionssuch as “what is the reason for shortfall quantities of a specific product?”, "where are resource ormaterial constraints?”, and "what are the reasons for specific sourcing decisions?”. In SCM 5.0, anexplanation tool is introduced delivering additional information in the optimizer log for more detailedexplanation of the planning result. The user can choose the explanation goal, the level of detail wheremore information is required, and the precision of the explanation.

In SCM 5.0, costs can be generated automatically based on few initial settings for storage, PPMs,transport, procurement, safety stock penalty, non-delivery penalty and late-delivery penalty. BusinessLogic can be expressed in a simple way that enables an economical interpretation.

Monitoring ActivitiesThe following table describes how to monitor and ensure the correct functionality of the optimizer run.

Jobs for Running and Monitoring "SNP Optimizer" and “Deployment Optimizer” (APO)To safeguard the continued functionality of the optimizer, refer to the monitoring jobs in the tablebelow. For an additional list of transactions used to help set up the optimizer during installation orchanges to the optimizer server, refer to the section Monitoring APO Optimizers in the Best Practice:Monitoring and Administration for SCM/APO.

To run the optimizer in the background: Use for SNP report /SAPAPO/RMSNPOPT andDeployment report /SAPAPO/RMDPLOPT.To verify that the optimizer is running correctly during the run: Lists of users andprocesses running on the optimizer server can be seen from transactions /SAPAPO/OPT03and /SAPAPO/OPT12 respectively. It is recommended that these be checked periodically toensure that everything is functioning as expected.After the planning run is finished: Use transactions sm37, and the optimizer logs in/SAPAPO/SNPOPLOG and /SAPAPO/OPT11, and the resulting costs from the optimizationrun /SAPAPO/SNP106 to verify that the run was executed without problems, and that theresults are as expected.

MonitoringObject

MonitorTA/Tool

MonitorFreq.

Moni-torTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO reportSNP:/SAPAPO/RMSNPOPT

Deployment:/SAPAPO/RMDPLOPT

This reportruns the opti-mizer in thebackground






Optimizer log /SAPAPO/SNPOPLOG

Afterevery run

Status Review messages in log withred or yellow status

Applicationsupport



© 2008 SAP AG

25

MonitoringObject

MonitorTA/Tool

MonitorFreq.

Moni-torTime

Indicatoror Error


Respon-sibility

EscalationProcedure

Verify andmaintain RFCconnections

SM59 Duringinstallation or afterconfigchanges

Status Check that the TCP/IPconnection to the optimizerserver is open andfunctioning correctly.

Programschedulingmanagement.

Contactsoftwaremonitoringteam

Spool file ofoptimizer run

SM37 Afterevery run

Messagesin spool file

Also check for applicationerrors after the optimizer run.

Applicationsupport


SNPOptimizerResultingCosts, also forDeployment

Transaction/SAPAPO/SNP106

Afterevery run

Resultssummaryof the SNPOptimizer

Check for reasonability of theresults: for example, whetherthe optimizer run has decidednot to produce anything.

Applicationsupport




Duringinstallation or afterconfigchanges

Among its other activities,this job will delete databaseentries and files on theoptimizer server which are nolonger needed.



Consistencycheck

/SAPAPO/CONSCHK

Aftereachchangeto masterdata

This job will identify anyinconsistent data prior torunning the optimizer run

Applicationsupport


OptimizerLogs

/SAPAPO/OPT11

Asrequired

Check forerrors

Display and analyze logs inthis section, if there is noresult delivered from theoptimizer.

System andapplicationmonitoringteams

Dependingon error type:system orapplicationmonitoringteam

User list forOptimizers

/SAPAPO/OPT03

Asrequired

Displays a user list ofoptimization runs

Basis support Contactapplicationteam

Runningoptimizerprocesses

/SAPAPO/OPT12

Asrequired

Displays a list of optimizerprocesses on theoptimization server

Basis support Contactapplicationteam


Business Process Step 6: Capacity LevelingThe SNP heuristic performs only infinite planning: that is, without considering the available capacitiesof resources. To create a feasible plan, it will sometimes be necessary to adjust the results of the SNPheuristic to change the production times of quantities to ensure that no resource is overloaded.SNP Capacity Leveling underwent a complete redesign in SCM 4.0. The new version is also availablein APO 3.0 as of SP 22 and in APO 3.1 as of SP15 as an alternative to the original version. Amongother features, the new version offers three different leveling methods - heuristic, optimizer, and BADI.It is activated by creating a user parameter /SAPAPO/SNPCAP with value 'X'. Both versions can beexecuted interactively from transaction /SAPAPO/SNP94. Click on the icon "Capacity Leveling" inCapacity View. The new version can also be executed as a background job using transaction/SAPAPO/SNP05. Further information on the new version, including full documentation, can be foundin release note 564702.Due to the improvements made in Capacity Leveling regarding result quality,performance, and stability we would like to encourage customers to test the new version for theirbusiness scenario and to use it instead of the original if it works well.As of SCM 5.0, a resource can be also leveled with alternative resources in the same location,depending on the existing alternative PPM/PDS


© 2008 SAP AG

26

For performance, consider the recommendations in Note 493258. Use an auxiliary table rather thanthe macro function for getting the date, and use macro function ACT_VERSION instead of macrofunction KEYFS_VERSION.

Monitoring Activities for Capacity Leveling

Jobs for Running and Monitoring "Capacity Leveling" (APO)The following table describes how to monitor the capacity run.

Capacity Leveling: Execute transaction /SAPAPO/SNP94 and change to data viewSNP94(2). If the Capacity View shows any resource overloads click on the Capacity Levelingicon in change mode. If necessary, you can select those planning periods and/or products thatshould be processed. In addition, the three alert macros may be run either within interactiveplanning or in the background to identify exceptional situations such as resource overload orunder load.Capacity Leveling in Background (new version only): in addition to launching the job, youshould monitor the job using SM37.

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

Capacityleveling ininteractiveplanning

Alerts Dependsonbusinessprocess

Alerts Look for fields which arecolored red due toexceptional resourcesituations. Run directlyexecutable macros tomeasure capacity under loadand overload situations.



Capacity runin background(new version)


Status Ensure that job is scheduledand runs without error.


Contactapplicationsupport team


Business Process Step 7: SNP InteractivePlanning

In the following section, we discuss transaction /SAPAPO/SNP94, as most customers usingCTM use this transaction for interactive planning. However, it is also possible to use PP/DStransactions like /SAPAPO/RRP3, depending on the customer scenario, for example, in some caseswhen using CTM. In such a case, please refer to the Best Practice document Manage ProductionPlanning in SCM / APO.

Within transaction /SAPAPO/SNP94, you can do almost everything that SAP APO SupplyNetwork Planning offers. In particular, you can evaluate planning results, compare different scenarios,enter management overwrites, correct key figures manually, run macros, aggregate data, and createor view alerts. Supply Network Planning supports online simulation in multiple planning scenarios,consistent planning throughout your enterprise, drilling up and down, and aggregation. As of SCM 5.0,planning can be performed within aggregated data; this is displayed accordingly in Interactive Planning

For performance reasons, any interactive processing of data should be restricted to very smalldata volumes by specifying the selection criteria as far as possible. This is independent of when thisplanning step takes place, for instance before or after a planning run. Tasks that can be performedwithout direct user interaction, for example, because they take place at a certain point in the businesscycle where real-time feedback to online users is not required, should be performed as batch jobsrather than interactively.

While tables of selection variants are usually not a problem in release 3.0A and higher, adescription of monitoring and managing them is given in Note 376383. For systems with largenumbers of interactive users, periodically deleting unused selections may become necessary.




© 2008 SAP AG

27

If you are using notes management within interactive planning, we also recommendperiodically executing report /SAPAPO/TS_GEN_DOCTAB_CHECK to eliminate possibleinconsistencies in the notes. However, please read Note 332812 carefully before using this report toautomatically correct inconsistencies.

Please note that, for performance reasons, SNP interactive planning defaults to “display” modewhen a user enters. This can be changed by altering user parameter /SAPAPO/SDP94_D_MODE, asdescribed in Note 401830. Also in this note it is stated that it is possible to write a BADI to override thedefault display. You might want to do one of the two for a number of reasons; for instance, when a userswitches from display to change mode, the data must be reread to set the appropriate locks.In some cases, you may wish to define one or more separate planning books for use with SNPinteractive planning. Some hints on the design and usage of planning books and macros for interactiveplanning 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, macros, keyfigures, and any other views that are used by that individual user. In addition, users whoperform more than one task type should consider creating more than one planning book toaccommodate each task type.

Minimize the number of default macros used for SDP interactive planning; see if any of thesecan be executed less frequently as start, end, or drill-down macros. In addition, each onlineuser should verify that the macros in her/his planning book are all used regularly as part of thestandard business practice and remove any which are not.

Implement composite time bucket profiles with coarser time buckets in the long-term past andfuture, and fine time buckets only near the present time. For example, showing a year as 9weeks and 10 months will dramatically improve the performance without decreasing the timeperiod shown. Also, any users who do not actively view and use historical data shouldconsider the “history not shown” flag as this allows macros to use the data without loading thedata onto the screen.

Each online user should create several selection variants to restrict the number ofcharacteristic combinations considered to those which s/he needs for a specific task.

Monitoring ActivitiesApart from safeguarding the general availability and consistency of the system components SAP APO,SAP BW, and SAP R/3 OLTP, SAP recommends that you monitor the objects listed in the followingtable in order to safeguard this business step.

Jobs for Running and Monitoring "SNP Interactive Planning (APO)"To ensure a timely and efficient notification of exceptions in Supply Network Planning, schedule thefollowing jobs to run on a regular basis:

Send Alert Monitor mails with report /SAPAPO/AMON_MAIL_BROADCAST. Depending onuser profiles, mails are sent with an overview of existing alerts. The responsible persons thenshould call up the APO Alert Monitor, investigate the reasons for the alerts and take correctiveactions in order to keep the production plan close to the needs of your company.Delete Alert Monitor alerts with report /SAPAPO/AMON_REORG. It deletes old alerts and isof particular importance if you use alerts stored in the database. Information on databasealerts and dynamic alerts in Demand Planning can be seen in the APO Alert Monitor andbelow.

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO AlertMonitor

/SAPAPO/AMON1

At leastdaily

Check for forecast alerts andSDP alerts and correct theplanning for the reportedobject appropriately.

Applicationsupport



© 2008 SAP AG

28

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO report/SAPAPO/AMON_MAIL_BROADCAST

This reportensuressending ofmails aboutexisting alerts.

SM37 Daily Status Check if job is running asscheduled.

If the report is not scheduledon a regular basis, scheduleit to run from between everyhour to at least daily,depending on yourrequirements.



Alert Monitormails

SO01(orrespective e-mailsystem)

Depending onyourrequirements,at leastdaily.

Check if the mail lists alertsthat are important for you. Goto APO Alert Monitor andprocess the alertsappropriately.

Applicationsupport


APO report/SAPAPO/AMON_REORG.

This reportdeletes AlertMonitor alerts.

SM37 Weekly Status Check if job is running asscheduled.

If the job is not scheduled ona regular basis, schedule it torun once a day.




Business Process Step 8: Shelf LifePropagationAs of release SCM 2007, SNP is able to monitor shelf life (maturation and expiration of perishableproducts) along the supply chain. See note 1072022 for a detailed description of the newfunctionalities.

Shelf life is only considered for products where the planning with shelf life flag is set at the “Properties”tab page of the product master. Here, you can set default shelf life values that are assigned to allorders created by SNP Planning applications.

Sales orders can be enabled to be transferred from R/3 with shelf life requirements (see notes 391018and 483576). The shelf life values of forecasts released from DP can be set by the implementation ofmethod CHANGE_RELDATA of BAdI /SAPAPO/SDP_RELDATA. Shelf life of batches assigned tostocks can be also integrated (see note 751392). Shelf life of purchase requisitions is integrated as ofrelease SCM 2007.

SNP planning applications do not consider shelf life (except for the SNP Optimizer - see Note 579556)and they create orders with default shelf life values. The role of shelf life propagation (transaction/SAPAPO/SNP10) is to propagate valid shelf life values to orders created by planning applications.The propagation is done in a top down direction, starting from initial demands and ending with plannedorders or purchase requisitions. It is important to note that Shelf Life Propagation is not a planningtool, so it does not change any other attribute of the orders than the shelf life values (except if run inorder split mode).

Shelf life propagation has to be run after planning applications have changed the orders, because theyreset the shelf life values. Therefore, it can be considered to re-run shelf life propagation as BusinessProcess Step 17, after the Deployment run.

The connection between demands and receipts in the propagation network is determined using thedynamic pegging functionality of liveCache, so in order that propagation works correctly, the settingson the “Pegging” tab page of the “Demand” tab page of Product master have to be considered.Especially, it is advised to extend the “Maximum Lateness of the Receipt” from the default 0 hoursvalue because SNP Planning applications usually create late receipts due to the bucket orientednature of the planning.


© 2008 SAP AG

29

In addition to shelf life propagation, the shelf life attributes of orders can be manually modified inInteractive Planning Detailed View, in planning book 9ASNP_SHLF, data view SHELF_LIFE.

Monitoring ActivitiesThe results of shelf life propagation can be monitored in SNP Interactive Planning using planning book9ASNP_SHLF, data view SHELF_LIFE. The data view contains shelf life specific keyfigures and alerts.The keyfigures are:

Stock on hand (shelf life) and Supply shortage (shelf life) can be used to monitorprojected stock situation considering shelf life, like for example the expiry of stockelements Projected wastage and Expiring quantity can be used to monitor the wastage ofstocks due to expiration.

Shelf life specific macros are available to generate shelf life alerts based on the values of the shelf lifekeyfigures, for example when there is a projected wastage or when the demands cannot be satisfiedwith available stock, due to shelf life restrictions.

Shelf life attributes of orders can be visualized in the Shelf Life View. The Shelf Life View, (if available– the planning book needs at least one shelf life related key figure) can be started from interactiveplanning with the Shelf Life View button, or from the context menu of the grid’s top-left corner.

For displaying Shelf Life View, a Shelf Life Profile is needed. The Shelf Life Profile can be set up in thetransaction /SAPAPO/SNP_SHLFPROF.

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

InteractivePlanning orAPO AlertMonitor

/SAPAPO/SDP94 or

/SAPAPO/AMON1

At leastdaily

Check for shelf life alerts andcorrect the planning for thereported object appropriately.

Applicationsupport


APO report/SAPAPO/RSNP_SHLF_PROP

(shelf lifepropagation).

SM37 As oftenasplanningruns areexecuted


If the report is not scheduledon a regular basis, scheduleit to run after the SNPplanning applications,depending on yourrequirements.



Application logof report/SAPAPO/RSNPDRP1

Slg1 As oftenaspropagation isexecuted

Log file Check whether the spool filehas any error messages.

ApplicationSupport



© 2008 SAP AG

30

Business Process Step 9: Execute BatchMacrosIn SNP, the usual reasons for creating batch macros are either to perform calculations and evaluationsof alert situations, or to calculate additional quantities and save them to time series key figures.After the planning run and manual adjustment, it is often desirable to monitor alert situations orcalculate quantities in time series key figures using batch macros run in SNP Planning Areas.For manual corrections, see Business Process Step 7: SNP Interactive Planning.

Some hints on the design and usage of macros for batch processing: Create a separate planning book for each macro background job. The planning book should

contain only key figures used by the macro itself, and only macros executed as activities bythe mass processing job. The planning book should only contain one planning view. Adifferent planning book should be used whenever different key figures are needed by twomacros, and a different data view whenever the time periods are different.

Remove all unused macros from planning books associated with mass processing jobs, asthey can be very performance-intensive and are not helpful to your business process.

The planning book used for batch macros should have only the functionality it uses: in thecase of SNP macros, the planning book should have no macros selected.

All macros in mass processing should be defined as manually executable, and only in theplanning book for the mass processing job in which they are used. In general, you do not needautomatic macro execution for mass processing jobs. Furthermore, defining macros as defaultmacros and to be executed at another time is redundant and extremely performance-intensive, since default macros are executed upon entry, loading a selection, changing data,and exit.

Create several background jobs with roughly equal numbers of location products and run themin parallel. Make sure that no individual location product belongs to more than one selectionvariant, as this can cause lock issues.

If you need to run two macros on the same key figures with the same level of aggregation, putboth into one planning book and execute them as two actions within the same backgroundactivity (defined with transaction /SAPAPO/MC8T, see below). You thus save the time neededfor loading the data again.

For the high data volumes usually considered in background processing, use database alertsrather than dynamic alerts.

When reading and writing alerts from the alert table in the APO database (table/SAPAPO/AM_ALERT), minimize the number of steps which manipulate alerts. Also, try touse “Delete” rather than “Delete in Context”, and “Add” rather than “Update in Context”whenever possible. For general advice on creating alerts in background jobs, please refer toconsulting Note 521639.

Monitoring ActivitiesApart from safeguarding the general availability and consistency of the system components SAP APO,SAP BW, and SAP R/3 OLTP, to safeguard this business step, SAP recommends that you monitor theobjects listed in the following table.The frequency of executing these Supply Network Planning batch jobs can vary significantlydepending on the business process for which the scenario is built. Macros that check for alertsituations - particularly those related to Deployment and TLB - may be executed as often as daily,while other jobs, such as adjusting data released from DP to SNP, may only be executed once amonth. Accordingly, the frequency of monitoring the jobs and deleting the SDP Job Logs depends onhow often you run these functions.For dependencies and concurrent execution of jobs, see Operational Management – Parallel andConcurrent Execution of Jobs. Please also refer to Exception based Monitoring of APO SupplyNetwork Planning for the handling of alerts generated by a batch macro.


© 2008 SAP AG

31

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO report/SAPAPO/TS_BATCH_RUN.

This reportperformsspecified SDPmassprocessingactivities.






SDP Job Log /SAPAPO/MC8K

Aftereachrun of/SAPAPO/TS_BATCH_RUN.

Red oryellowtraffic lightsshown

According to the warning orerror reported (see messagelong text).

Applicationsupport


APO report/SAPAPO/TS_BATCH_LOGFILE

This reportdeletes oldSDP JobLogs.






APO report/SAPAPO/AMON_REORG

This reportdeletes olddatabasealerts ofvarious types.

SM37 Depending onyourprocess




Contactsoftwaremonitoringteam.



© 2008 SAP AG

32

Business Process Step 10: ExchangeRequirements with SupplierIn some cases, it is desirable to exchange requirements with suppliers. In SNP, it is usual to transferthe data periodically, rather than immediately after planning is complete, as is the default setting inPP/DS. These settings are maintained in transactions /SAPAPO/SDP110 and /SAPAPO/C4 (the latteris user-specific). Note that, while the information is user specific, you cannot use wild cards here, butmust either specify the full user ID or user entry ‘*’ for all users not explicitly specified. In addition,please refer to the corresponding documentation on CIF functionality regarding transactional datatransfers between R/3 and APO. A number of consulting notes exist regarding the transfer of APOorders to and from R/3 in the context of exchanging information with suppliers; for example, Notes443500, 206679, and 432038.

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 bothsystems, certain jobs must be scheduled on a regular basis. These jobs are:

Publish Planning Results with report /SAPAPO/RDMCPPROCESS. This report evaluatesthe APO change pointers (not the same as ALE change pointers!) that are written duringplanning activities. The corresponding objects, such as planned orders, are sent to R/3.Check Processing of APO Change Pointers with report /SAPAPO/RDMCPPROCESS. Thisreport verifies that all change pointers are processed by checking that the list displayed in thereport /SAPAPO/RDMCPPROCESS is empty. If change pointers remain unprocessed, contactthe application support team to clarify whether these change pointers are needed and whythey are not processed. Note: Deleting change pointers may cause inconsistencies, as thecorresponding order changes are not transferred to R/3.

The jobs mentioned in the Manage APO Core Interface in SAP SCM, section Operation andMonitoring of the APO Core Interface.

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO Report/SAPAPO/RDMCPPROCESS

This reportpublishes theresults ofautomatic andinteractiveplanning toR/3.

SM37 Depending onyourneeds,or atleastonce aweek




ContactApplicationSupport.

APO Report/SAPAPO/RDMCPPROCESS to displaychangepointers


If job is not scheduled on aregular basis and periodicpublishing of data to R/3 isperformed on the system,schedule the job daily.


ContactApplicationSupport



© 2008 SAP AG

33

Business Process Step 11: Load Data into BWAs mentioned above, every SAP APO system comprises a complete SAP Business InformationWarehouse System (BW), which should be used exclusively for APO purposes. Though in thisbusiness process step data is extracted from a separate BW system, all periodic monitoring taskshave to be performed in the APO system as well as job definition and most of the configuration tasks.In order to load the data into BW, the data must first be extracted from the SNP planning area. Pleaserefer to Note 428147, which discusses limitations of this functionality in detail.

Note 507810 describes the complete procedure for performing BW reporting on SNP remote cubes.The function of creating, checking and testing the data source in the APO system can now beperformed with report /SAPAPO/TS_PAREA_EXTR_MGM (transaction /SAPAPO/SDP_EXTR). Thisreport is described in Note 453278. From this report, a background job for the extraction can begenerated, which will run report /SAPAPO/TS_PAREA_TO_ICUBE. In addition, a consistency checkand test for the remote cube are available through this functionality.


Apart from safeguarding the general availability and consistency of the system components SAP APO,SAP BW, and SAP R/3 OLTP, to safeguard this business step SAP recommends that you monitor theobjects listed under Monitoring of Business Warehouse Activities.

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, andthat liveCache data structures (time series) are kept consistent, schedule the following jobs to run on aregular basis:

Compute Histograms for BW InfoCubes with report SAP_ANALYZE_ALL_INFOCUBES.This is only relevant for systems running with Oracle, SAP DB or IBM DB2 UDB (DB6)database (refer to SAP Notes 16083 and 421795). Please see SAP Notes 129252 (Oracle) or328106 (DB6). For SAP BW releases prior to 2.0B Support Package 17 please notice thedependency to running SAPDBA (optimizer statistics for non-BW tables) described in SAPNote 129252. Please also refer to SAP Note 323090.For SAP BW releases 3.0A and onwards (affects SAP APO 4.0) the InfoCube statistics can becomputed using the BRCONNECT tool as well as the ‘normal’ database statistics. For SAPBW releases 2.x (affects APO 3.0A and 3.10) this is not recommended. Please refer to SAPNotes 428212 and 535986 for details.

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO reportSAP_ANALYZE_ALL_INFOCUBES.

This reportcreates DBstatistics for allInfoCubes.

Only forsystemsrunning withOracle, SAPDB or IBMDB2/UDB(DB6)database.


If the job is not scheduled ona regular basis, schedule it torun once a week withparameter percent = 100.




© 2008 SAP AG

34

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

Indices ofAPOInfoCubes.

RSA1 orRSRV

Weekly Red oryellowtraffic light

Select Check (Aggregate)Indexes. If the traffic lightgets yellow or red, selectRepair Indexes (now) orDelete Index (batch) andCreate Index (batch).




Business Process Step 12: Create/UpdatePlanned Orders, Transfer Orders, and PurchaseRequisitionsAfter the planning runs are complete, and, if necessary, capacity leveling has been performed, manycustomers update the results of SNP, that is, the planned orders, transfer orders, and purchaserequisitions. In SNP, it is usual to transfer the data periodically, rather than immediately after planningis complete, as is the default setting in PP/DS. These settings are maintained in transactions/SAPAPO/SDP110 and /SAPAPO/C4 (the latter is user specific). Note that, while the information isuser specific, you cannot use wild cards here, but must either specify the full user ID or user entry ‘*’for all users not explicitly specified. In addition; please refer to the corresponding documentation onCIF functionality regarding transactional data transfers between R/3 and APO.Please note that not all order types may be transferred from R/3 to SNP. In particular, plannedindependent requirements may only be transferred from APO to R/3, and not in the other direction(compare Note 538046). For SNP planned orders only some manual changes are transferred from R/3to APO: changes to output quantity, availability date and order fixing.

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 bothsystems, certain jobs must be scheduled on a regular basis. These jobs are:

Publish Planning Results with report /SAPAPO/RDMCPPROCESS. This report evaluatesthe APO change pointers (not the same as ALE change pointers!) that are written duringplanning activities. The corresponding objects, such as planned orders, are sent to R/3.Check Processing of APO Change Pointers with report /SAPAPO/RDMCPPROCESS. Thisreport verifies that all change pointers are processed by checking that the list displayed in thereport /SAPAPO/RDMCPPROCESS is empty. If change pointers remain unprocessed, contactthe application support team to clarify whether these change pointers are needed and whythey are not processed. Note: Deleting change pointers may cause inconsistencies, as thecorresponding order changes are not transferred to R/3.

The jobs mentioned in the Manage APO Core Interface in SAP SCM, section Operation andMonitoring of the APO Core Interface.


© 2008 SAP AG

35

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO Report/SAPAPO/RDMCPPROCESS

This reportpublishes theresults ofautomatic andinteractiveplanning toR/3.

SM37 Depending onyourneeds,or atleastonce aweek




ContactApplicationSupport.

APO Report/SAPAPO/RDMCPPROCESS to displaychangepointers


If job is not scheduled on aregular basis and periodicpublishing of data to R/3 isperformed on the system,schedule the job daily.


ContactApplicationSupport


Business Process Step 13: Release SNP to DPMany customers who also use Demand Planning release the results of the SNP run (often called theconstrained demand plan) back to DP to compare with the original forecast.This process can be run in parallel, for example, by selecting properly disjoint data sets for therelease. No reverse location or product split is possible.

Monitoring ActivitiesApart from safeguarding the general availability and consistency of the system components SAP APO,SAP BW, and SAP R/3 OLTP, SAP recommends that you monitor the objects listed in the followingtable in order to safeguard this business step.

Jobs for Running and Monitoring "Release SNP to DP (APO)"To release the constrained Demand Plan back to DP, do the following:

Release SNP Orders to DP time series with transaction /SAPAPO/LCOUT or report/SAPAPO/RTSINPUT. With this report, you can release the quantities stored in SNP orderobjects into DP time series key figures.

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO report/SAPAPO/RTSINPUT.

This reportcopies thequantity storedin an SNPOrder KeyFigure into aDP time serieskey figure



If the job is not scheduled asprovided by ApplicationSupport, schedule itaccordingly.




© 2008 SAP AG

36

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

Output of APOreport/SAPAPO/RTSINPUT.

SP01 Aftereachrun

Messagesin spoollist.

Check the spool file to ensurethat all records passed havea green status light. If red oryellow traffic lights occur, itindicates an error.

Applicationsupport



Business Process Step 14: Release SNP to PP/DSMany customers using SNP or CTM also use the PP/DS planning functionality. There are severalpossibilities for how to integrate SNP with PP/DS. Some of these possibilities are described in note481906.To convert planned orders within the production horizon from SNP into PP/DS, an explicit orderconversion needs to be executed. The conversion can be done in one of two ways: either using amass conversion report launched from transaction /SAPAPO/SNP2PPDS, or for individual product-locations, using the online transaction /SAPAPO/RRP_SNP2PPDS. Note that at this point in time,releases from SNP to PP/DS may only be executed within the same planning version.

Monitoring ActivitiesTo safeguard the functionality of releasing SNP to PP/DS, we recommend the reports listed below.

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. This converts theSNP orders for the specified location product(s) within the production horizon into PP/DSorders. When this report is run, it should be run with logging set to normal, that is, by followingthe path Settings-> Planning Log. For individual product-locations you can also use onlinetransaction /SAPAPO/RRP_SNP2PPDS.

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO report/SAPAPO/RRP_SNP2PPDS

This reportconverts anSNP or CTMorder to aPP/DS order






Output of APOreport/SAPAPO/RRP_SNP2PPDS


Status,messages

Whether or not the jobfinishes without error,application support shouldcheck the job log for errormessages such as“Component 100-100 of PPMP-1021000000100000000N5000000401031 not valid on orderdates”

Applicationsupport




© 2008 SAP AG

37

Business Process Step 15: DeploymentHeuristicThe purpose of deployment is to calculate replenishment for one product at one location at a time,which creates deployment stock transfers. The deployment heuristic does this based on any of severaldistribution methods and fair share rules, which govern how the orders will be distributed across thenetwork in cases of surplus or shortage. The distribution methods and fair share rules are described indetail in the deployment section of the APO documentation. Deployment determines whichrequirements can be fulfilled by the existing supply. If the available quantities match required quantitiesas planned in SNP planning, the result of deployment is a confirmation of the supply network plan.As of SCM 4.1 automatic parallelization can be used for the Deployment Heuristic, this improvesperformance and optimizes system resources utilization.

Fair-share alerts for deployment are automatically generated during the deployment run. If you are notmonitoring this alert type as part of your business process, turn off the alerts as described in Note512797. If you are using these alerts, be sure to delete the old ones regularly using report/SAPAPO/AMON_REORG with appropriate filters.The Deployment heuristic only considers demands at destination locations, which are propagated tothe source location as planned distribution demand (using SNP Heuristic, Optimization or CTM). As ofSCM 5.0 the demand from Sales Orders and Forecast is shared among the source and distributiondemands

As of release SCM 2007, the Deployment algorithm supports product interchangeability, that is to sayit is capable of confirming the Planned Substitution Orders created by the previous planningprocesses. For setting up a scenario check Business Process Step 4: SNP Heuristic Run. The resultsof the confirmation of the planned substitutions at the source location are Confirmed SubstitutionOrders at the destination location, and can be found in the new keyfigures Substitution Receipts(Confirmed) and Substitution Demands (Confirmed) in Interactive Planning. The new process can beapplied for both Supersession Chains and FFF classes.If you run interchangeability scenario via transaction /SAPAPO/SNP02; make sure you have the flag“Add products from supersession chains” set.


Jobs for Running and Monitoring "Deployment Heuristic”To execute the deployment heuristic

Execute the deployment heuristic in the background with report /SAPAPO/RMSDPDEP;you should save one or more variants and execute them in the background. Note that parallelprocessing is possible for variants which contain no overlap in location-product or resourcesused. Use transaction /SAPAPO/SNP02 for small data volume only.

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error

Monitoring Activity orError HandlingProcedure

Respon-sibility

EscalationProcedure

APO report/SAPAPO/RMSDPDEP

Sm37 Dependingonbusinessprocess

Status Check if job is running asscheduled




© 2008 SAP AG

38

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error

Monitoring Activity orError HandlingProcedure

Respon-sibility

EscalationProcedure

Output ofreport/SAPAPO/RMSDPDEP

Sm37 Dependingonbusinessprocess

Status andmessages

Whether or not the jobfinishes without error,application supportshould check the job logand spool file for errormessages

Applicationsupport

Contactprocessmanagement


Business Process Step 16: DeploymentOptimizerLike the deployment heuristic, the purpose of the deployment optimizer is to create deploymentconfirmed stock transfers. The difference is that the optimizer takes the current demand situation inthe network into account rather than just the stock transfer demands of the individual location. Thismeans rather than using one of the available fair-share techniques, the deployment optimizer insteadtries to compute the lowest-cost manner in which to distribute the orders. Another difference is thatDeployment Optimizer deletes all from SNP planned transport orders, both firmed and non-firmed andcreates deployment confirmed stock transfers independently.

See Business Process Step 5: SNP Planning Run Optimizer. It is identical.

Business Process Step 17: Transport LoadBuilder (TLB)The deployment run generates deployment confirmed stock transfers. The Transport Load Builder(TLB) then uses these stock transfers to generate TLB confirmed stock transfers and build transportloads comprised of multiple products, and which consider the minimum and maximum constraints ofthe means of transport, that is, number of pallets, weight and volume. TLB can be executed eitherusing interactive planning, via transaction /SAPAPO/SNPTLB, or as a background job by running anappropriately designed variant for report /SAPAPO/RMSNPTLB. The background job can also belaunched from transaction /SAPAPO/SNP04. Neither method of executing TLB will automaticallycreate alerts; if they are desired, create a batch macro to create them.As of SCM 4.1 automatic parallelization can be used for TLB, this improves performance andoptimizes system resources utilization.

Monitoring ActivitiesThe following table contains a description of reports and monitoring objects for TLB. The monitoringobject indicates whether the information refers to TLB run in batch or foreground.

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO report/SAPAPO/RMSNPTLB

SM37 Depends onbusinessprocess

Status Check that the job is runningas scheduled.


Applicationsupport


© 2008 SAP AG

39

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

Output ofreport/SAPAPO/RMSNPTLB

SM37 Depends onbusinessprocess

Status/messages

Independent of the job status,check both the job log andthe spool file for applicationproblems

Applicationsupport



Business Process Step 18: Delete TransactionDataUnder some business scenarios, some of the order types generated during SNP planning are notconverted to PP/DS, or further processed in other ways, and deleting older ones is necessary to eitherkeep the liveCache from growing, or as one of the steps of deleting a location-product from thesystem. This is often done using report /SAPAPO/RLCDELETE, or transaction /SAPAPO/RLCDEL.Basic troubleshooting tips for this transaction, along with several others for version management, aregiven in SAP Note 519014. The first time the transaction is run with full data volume, the personresponsible for monitoring should evaluate the data volume, and determine whether the package sizeneeds to be tuned to improve performance; this is described in SAP Note 523250. The report can alsobe used to delete stocks, as described in SAP Note 630751.Please be aware that using this report should be carefully evaluated with SAP Note 644676, whichsummarizes the information available on the RLCDELETE report. As of SCM 4.0, SAP Note 660194describes further details.

Monitoring ActivitiesThe following table contains a description of reports and monitoring objects for/SAPAPO/RLCDELETE.

MonitoringObject

MonitorTA/Tool

MonitorFreq.

Monit-orTime

Indicatoror Error


Respon-sibility

EscalationProcedure

/SAPAPO/RLCDELETE


Status Check that the job is runningas scheduled.


Applicationsupport

Log /SAPAPO/RLCDELETE

Dependsonbusinessprocess

Status/messages

Check the log for errormessages and data volumes

Applicationsupport




© 2008 SAP AG

40

Further Information

TroubleshootingIf executing this Best Practice did not produce the desired results, proceed as follows:

If there are or seem to be problems in the data transfer via the Core Interface, see theTroubleshooting Guide Integration R/3 – APO, which you can find in SAPNet in theLiterature Center of the R/3 Plug-In homepage.

Search for related SAP Notes Open a SAP Customer message describing your problem

Background Information and References

Related Tools and ActivitiesThis Appendix explains:

1. APO Alert Monitor2. Monitoring of Business Warehouse Activities3. Maintenance of SDP Data Storage Structures4. Running Supply Network Planning in Background5. Exception Based Monitoring of APO Supply Network Planning

APO Alert MonitorThe APO Alert Monitor allows a management-by-exception strategy, so it is of special concern in thisand other APO business process scenarios. The Alert Monitor is a standalone component of APO thatenables you to have a unified approach to handling problem situations. It notifies you if a problemoccurs during an ATP check or SNP run, or when production plans, demand plans, or vehicleschedules are being generated in one of the APO applications.The Alert Monitor is a tool with which planners can monitor the state of a plan. The monitoring resultscan be used to readjust the plan whenever necessary. The purpose of the Alert Monitor is to informplanners if the condition of a plan has been violated. The Alert Monitor belongs to the suite of supplychain monitoring components in APO, together with the Supply Chain Cockpit and the Plan Monitor. Itcan be used by any supply chain manager or planner who practices exception-based management inthe 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 aswell as from various planning applications such as, /SAPAPO/SDP94, /SAPAPO/PPT1, and others.Alerts can also be displayed in the Supply Chain Cockpit /SAPAPO/SCC01. When displaying alerts in/SAPAPO/SDP94, for example, the display of alerts is restricted to those which are assigned to theselected planning book.The goal of Supply Network Planning is to create plans for production, transportation, and/orprocurement across a supply chain with multiple locations, and the role of the Alert Monitor is to notifyyou of exceptions that occur during the process. An exception is any situation that needs furtheradjustment. A sudden switch in trends, a new fad, or an unexpected change in the circumstances of asupply chain partner could all lead to exception situations. Most exceptions, if not handledimmediately, can have consequences up or down the supply line.The Alert Monitor is an online tool designed to help you catch real-time exceptions well before theyturn into problems and thus help you forecast your business needs more effectively. Not only can youdetermine which types of exceptions you want to be notified of, you can also prioritize alerts, thus

http://service.sap.com/~form/sapnet?_FRAME=OBJECT&_HIER_KEY=501100035870000009376&_HIER_KEY=601100035870000050275&_HIER_KEY=701100035871000068587&#HOME

http://service.sap.com/R3-Plug-In

http://service.sap.com/notes


© 2008 SAP AG

41

preventing an information overload. In exception-based management, you as the planner must makethe ultimate decision regarding the priority of an alert. If you regularly consider Capacity Overloadalerts, you will soon be able to determine whether a 15% deviation is serious or not. This knowledgewould enable you to set priority variants for alerts so that you get a warning if the deviation is 10% butan error alert if it is 15%.Alert priorities are identified by icons displayed in the profile or in the monitoring slots of the SupplyChain Cockpit control panel. The three possible priority levels in the Alert Monitor are:

1. Error2. Warning3. Information

The priorities should be defined in a way that - under normal conditions on a well run system -information alerts take the biggest share and errors are generated only in rare cases. However, evenan information alert should reflect an exception to the planning situation and not a “success” messagesaying “everything ok”.Unlike in the DP application where you can view only one planning book at a time, you can viewseveral in the Alert Monitor, making it the ideal tool for tracking the quality of your alerts over a specificperiod of time.In the demand planning process, the following exception situations may arise:

Changes in bias, new trends, unexpected demands Orders exceed forecast Orders fall short of forecast, which may lead to excess inventory

For Supply Network Planning, both supply & demand planning (SDP) alerts and Transport LoadBuilder (TLB) alerts are important; each can be configured as either a dynamic alert (recommendedfor small data volumes in interactive planning only) or database alert (recommended for batch jobsand large data volumes). SDP alerts can be used both in the Demand Planning and Supply NetworkPlanning applications.You have to maintain alert profiles to maintain a user-specific selection of alerts for your area ofresponsibility. There are forecast alert profiles and SDP alert profiles.The SDP alert profile contains a number of alerts that are specific to the tactical planning and sourcingdecisions relevant for purchasing, manufacturing, and distribution. There are two different types ofSupply & Demand Planning alerts:

Dynamic alerts mirror the current planning situation but are not saved in the database. Asopposed to SNP alerts in APO Release 2.0, alerts are now macro-dependent and thus canreflect the actual data in liveCache. This alert type is NOT suitable for dealing with a largevolume of planning objects because large numbers slow down performance. For small datavolumes, up to approximately 1000 alerts, dynamic alert generation is usually much fasterthan reading alerts from the database. For large data volumes, database alerts are usuallyfaster.Database alerts show the planning situation as it was during the planning run, or lastexecuted macro. When dealing with large volumes it is best to perform a batch planning-runusing the appropriate database macro. The results of the planning run show the situation as itwas at the time of the run, in other words, with database alerts you see a snapshot of the planduring run time.

You also have the option of creating customer-specific dynamic or database alert types to be usedwith SDP macros.Database alerts that are no longer in use, for instance, because they have been acknowledged orbecause they are outdated, must be deleted from the database. Besides forecast and SDP databasealerts, this also applies to ATP, VS and TLB/Deployment alerts. PP/DS alerts, however, are not storedin the database but are dynamic only.Generally, if an alert is generated, three activities must take place:

1. Analyze alert situation.2. Inform responsible planner.3. Make adjustment to plan and / or profile.


© 2008 SAP AG

42

To support the Alert Monitor's function as a tool for exception-based management, you can sendmessages via e-mail to other planners to inform them of the alert situation. You can also havemessages sent automatically to your own inbox to inform you of alerts in your area.You can maintain a list of favorite Alert Monitor profiles so you can switch back and forth easilybetween various profiles. For example, you may have an alert profile for your own area ofresponsibility, but you may also want to look at alerts in other areas.Keep alerts to a minimum. Too many alerts slow performance and may cause you to overlook thereally important ones.You can find more information concerning this tool in the SAP Documentation under "Supply ChainMonitoring – Alert Monitor". Please refer also to SAP Notes 375965, 495166, 500063, and 521639 andto Exception based Monitoring of APO Demand Planning.

Monitoring of Business Warehouse ActivitiesThis section points out the concept for monitoring activities related to data transfers and themaintenance of data keeping structures in the SAP BW component of an SAP APO system. The datatransfer can take place inbound or outbound the BW (APO) system to and from other SAP or thirdparty components as well as within one APO system between different data storage units likeInfoCubes and liveCache. When adapting this concept for your company, you must specify the times,responsible teams, and escalation paths (responsible teams) for the following monitoring activities andobjects.

Monitoring ActivitiesApart from safeguarding the general availability and consistency of the system components SAP APO,SAP BW, and SAP R/3 OLTP, SAP recommends that in order to safeguard any business step that isbased on SAP BW techniques, you monitor the objects listed in the following table.The data transfer process from a source system to SAP BW InfoCube(s) as well as certain actions inRSA1 and RSMO write detail information to a central R/3 basis component called the Application Log.It can be browsed using transaction SLG1. The log entries are subdivided into objects and sub-objectsand classified by importance. In case of errors or problems, the Application Log can be used to getmore detailed information about what happened and how to resolve the problem. The monitortransaction for the Application Log is SLG1, where you should specify the (sub-) objects and the timeinterval you want to be displayed. 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; Monitor; Tree callback

Jobs for Running and Monitoring Data Transfers To or Within the Business WarehouseTo ensure a timely and consistent data transfer from any data source into an SAP BusinessWarehouse structure, schedule the following job on a regular basis:

Data Extraction and Load with report RSBATCH1. The job has to be defined using thescheduler in the Administration Workbench (transaction RSA1) of the BW component of APO.The scheduler generates a background job with name prefix BI_BTCH and processes theselected Info Package. With the help of Info Package groups you can collate data requeststhat logically belong together and schedule them using the scheduler.

In Monitoring of the Administrator Workbench (select Monitoring in transaction RSA1 or calltransaction RSMO) you have the option of overseeing and controlling the data loading process into theInfoCubes and you can analyze errors that may have occurred (Menu: Monitor -> Assistant). You canalso call the monitor from a selected Info Package or via transaction code RSMO. Make sure that youhave selected the correct time window and data to be displayed by calling the selection screen viamenu Monitor -> New Selections.


© 2008 SAP AG

43

Jobs for the Maintenance of the Application LogThe Application Log entries are stored on tables with name prefix BAL*. As there are very manyapplications that use this basis component and often many table entries are made, it is important toregularly delete obsolete Application Logs from the database in order to prevent these tables fromoverflowing as well as to keep the applications and the log retrieval running optimally. The deletion canbe performed using transaction SLG2 or in background by the appropriate report:

Delete Obsolete Application Logs with report SBAL_DELETE. A log can only be deletedwhen it has reached its expiry date or if it has the "Deletion before expiry" attribute. For moreinformation, please refer to SAP Note 195157.

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO jobBI_BTCH*.

These jobsperform thedata transferfrom thedifferent datasources toAPOInfoCubes.

RSMOor SM37

Depending onyourprocess





APO:AdministrationWorkbench -Monitor

RSMO Aftereverydataload

Red oryellowtraffic lights

After selecting one request,read the error message anddiagnosis under tab stripStatus and the processing logunder Detail.

Use the Monitor Assistant toanalyze and correct the errorsituation.



APO: EvaluateApplicationLog for BWrelatedobjects.

SLG1 At leastdaily

Log class Check if there are veryimportant logs (flagged red)or important logs (flaggedyellow).

Read message long text and/ or details, if present.Analyze error situation,evaluate error severity andimpact, and take correctiveaction.



APO reportSBAL_DELETE.

This reportdeletesobsoleteApplicationLogs.


If the job is not scheduled asprovided by ApplicationSupport, schedule it to runweekly.



Error Handling, Restartability and Escalation

Error Handling ProceduresError handling for background jobs is explained in detail in the SAP R/3 documentation CD,component BC-CCM, under Background Processing.If a scheduled job fails, a necessary job is not scheduled, or a scheduled job has status "finished" youmay need to take action. Consider the status of the job and proceed as follows:


© 2008 SAP AG

44

Status scheduled: the job steps have already been defined, but the start condition has not yetbeen defined. Contact the program scheduling management in order to clarify when the jobwill be fully defined.

Status released: the job has been fully defined with a start condition and will wait for thatcondition to be fulfilled.

Status ready: the start condition of a released job has been fulfilled. A job scheduler has putthe job in a queue to wait for an available background work process.

Status active: the job is currently running and can no longer be modified or deleted. Check ifthe job is within the given timeframe. Check for particular dependencies to other jobs. If thejob exceeded the given timeframe, contact the software monitoring team.

Status finished: all steps that make up this job have completed successfully. Programscheduling management must check whether the job ran in the given timeframe, and softwaremonitoring team and / or application support must check the respective job results (such asspool output lists, message logs, and updates).

Status cancelled: the job has terminated abnormally. This can happen in two ways. If anadministrator intentionally canceled the job, clarify why he or she did so and whether (and ifso, when) the job must be re-run. Alternatively, if a program in a job step produced an errorsuch as issuing an "E" or "A" error message, contact the software monitoring team andinvestigate why the error occurred. If the program is an SAP standard program, search forappropriate messages in SAPNet and create a customer message if you cannot solve theproblem.

If there are problems with the Core Interface CIF or with data missing in either R/3 or APO,see the Troubleshooting Guide Integration R/3 – APO in the Literature Center (of the R/3Plug-In homepage).

Process Step RestartabilityIf a background job is cancelled, consider possible succeeding jobs or dependencies on other jobswhen deciding whether to restart the aborted job. The aborted job may also delay the start ofsucceeding jobs.

Escalation Procedures In general, we recommend that you search for related SAP Notes in the SAPNet R/3 front-end

system for any unknown problems or errors. If you have questions or problems that cannot be solved, forward the issue to the next support

level. If the corresponding escalation path is not well defined, contact Application Support. If none of the defined support levels can provide a solution for a particular problem, we

recommend that you create a customer problem message in the SAPNet R/3 front-endsystem.

Maintenance of SDP Data Storage StructuresIf SNP time series objects are used in the planning areas of your company, either alone or togetherwith order objects, the tasks associated with DP BW structures must also be executed for these timeseries objects.When adapting this concept for your company, you must specify the times, responsible teams, andescalation paths (responsible teams) for the following monitoring activities and objects.

Monitoring ActivitiesThe data for your Demand Planning process is stored in different logical and physical structures suchas InfoCubes, the Master Planning Object Structure, and liveCache Time Series. All these need acertain amount of surveillance and maintenance in order to stay in a technically optimal condition andtherefore to allow a fast retrieval of the data stored within.

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, andthat liveCache data structures (time series) are kept consistent, schedule the following jobs to run on aregular basis:

http://service.sap.com/~form/sapnet?_FRAME=OBJECT&_HIER_KEY=501100035870000009376&_HIER_KEY=601100035870000050275&_HIER_KEY=701100035871000068587&#HOME


© 2008 SAP AG

45

Compute Histograms for BW InfoCubes with report SAP_ANALYZE_ALL_INFOCUBES.This is only relevant for systems running with Oracle, SAP DB or IBM DB2 UDB (DB6)database (refer to SAP Notes 16083 and 421795) Please see SAP Notes 129252 (Oracle) or328106 (DB6). For SAP BW releases prior to 2.0B Support Package 17 please notice thedependency in running SAPDBA (optimizer statistics for non-BW tables) described in SAPNote 129252. Please also refer to SAP Note 323090.Check Inconsistencies in Time Series Network with report/SAPAPO/TS_LCM_CONS_CHECK_ALL. This report checks all existing time series, in allplanning areas and versions, and reports whether or not there are inconsistencies. If errorsare found, you can repair inconsistencies in a specified planning area and version usingreport /SAPAPO/TS_LCM_CONS_CHECK. Mark the Log check box if you want to see a list ofcharacteristic combinations having inconsistencies. For details and further information pleaserefer to SAP Notes 358283, 425825, 402046, and 520876.Delete Time Series and Time Bucket Profiles having no liveCache Anchors with report/SAPAPO/TS_LCM_REORG. This report (supplied with SAP Note 542946 or Support Package22 (APO 3.0) or SP 10 (APO 3.1), resp.; refer to SAP Note 425825) determines all liveCachetime series and time buckets profiles from a selected planning version that do not have any'liveCache anchors', independently of planning areas. These objects do not have anyreference to the application data and are therefore not inconsistent as such, but simplyunnecessary objects, which result in increased liveCache memory consumption. For thisreason you should only have to run the report approximately once a month.If you have selected the 'Repair' option, any unnecessary time series and period patterns aredeleted. Caution: When you run report /SAPAPO/TS_LCM_REORG, no other processes for aplanning area (applies only to planning areas with key figures based on liveCache time series)should be allowed to run with the same planning version, since this would result in liveCacheobjects that are still required by the other parallel process being recognized as unnecessary,and then possibly deleted. For this reason, we recommend that you always run the report withthe option 'Lock planning version'. In this case, all planning areas that use the planningversion to be checked are locked for the relevant version. If you cannot activate the lock,report execution is interrupted and a list of system users is displayed, showing users whohave already set a change lock for the planning version.Maintain Statistics and Indices for Planning Object Structures with report/SAPAPO/TS_PSTRU_TOOL.Run this report in separate background jobs choosing options Calculate Statistics and CheckIndexes for every Master Planning Object Structure and review the list of messages beingdisplayed. Run it with option Repair Indexes, if problems are reported by the index check. Aseparate background job (job name with prefix BI_STAT) will be started to execute thisrequest. These administrative jobs have to be run after every load of data to a planning objectstructure. For further details, please refer to SAP Notes 393655, 492460, and 503363.

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO reportSAP_ANALYZE_ALL_INFOCUBES.

This reportcreates DBstatistics for allInfoCubes.

Only forsystemsrunning withOracle, SAPDB or IBMDB2/UDB(DB6)database.


If the job is not scheduled ona regular basis, schedule it torun once a week withparameter percent = 100.



http://service.sap.com/~iron/fm/011000358700000431401997/0421795E















© 2008 SAP AG

46

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO report/SAPAPO/TS_LCM_CONS_CHECK_ALL.

This reportdetectsinconsistencies in timeseries.


If the job is not scheduled ona regular basis, schedule it torun once a week.



Output of APOreport/SAPAPO/TS_LCM_CONS_CHECK_ALL.

SP01 Aftereachrun.

Red trafficlight

Check for time series withinconsistencies reported.

Try to repair inconsistenciesby running report/SAPAPO/TS_LCM_CONS_CHECK for the corrupt timeseries setting the repairoption.



APO report/SAPAPO/TS_LCM_CONS_CHECK.

This report isable to repairinconsistencies in timeseries.

SM37 Aftereachrun.

Status Check if job has finishedwithout errors.



Output of APOreport/SAPAPO/TS_LCM_CONS_CHECK.

SP01 Aftereachrun.

Traffic light Check whether theinconsistencies in theselected time series havebeen repaired.



APO report/SAPAPO/TS_LCM_REORGwith optionRepair.

This reportdeletessuperfluoustime seriesand timebucketprofiles.

SM37 Monthly Status Check if job is running asscheduled.

If the job is not scheduled ona regular basis, schedule it torun once a month.



Output of APOreport/SAPAPO/TS_LCM_REORG.

SP01 Aftereachrun.

Traffic light Check whether superfluousdata is reported and hasbeen deleted without errors.




© 2008 SAP AG

47

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO report/SAPAPO/TS_PSTRU_TOOL with optionCalculateStatistics.

This reportchecks andgeneratesstatistics for aPOS.

SM37 Aftereverydataload intothePOS.





APO report/SAPAPO/TS_PSTRU_TOOL with optionCheckIndexes.

This reportchecks theindices of aPOS.

SM37 Aftereverydataload intothePOS.





Output of APOreport/SAPAPO/TS_PSTRU_TOOL.

SP01 Aftereveryrun.

Messagetype (icon)

Look for stop icons(cancellation), and red(errors) or yellow (warnings)lights. Read message longtext if present.



Job BI_STAT*started by/SAPAPO/TS_PSTRU_TOOL with optionRepairIndexes.

SM37 Aftereveryrun.

Status Check if job ended correctly. Softwaremonitoringteam


See general issues of Error Handling, Restartability and Escalation above.

Running Supply Network Planning in BackgroundThis section outlines the monitoring concept for Supply Network Planning activities in background forprocessing mass data which use the same interface as Demand Planning background jobs. Massprocessing allows you to run macros for large numbers of products while optimizing system resources.Also a release of DP data to SNP is usually performed in background. The different tasks that can beperformed in this way have to be customized and set up as “activities” prior to job definition. OtherSupply Network Planning background jobs (for example, the heuristic, optimizer, and deploymentruns) are executed using a different interface, and are discussed in the pertinent chapters in earlierparts of this document.

Monitoring ActivitiesApart from safeguarding the general availability and consistency of the system components SAP APO,SAP BW, and SAP R/3 OLTP, SAP recommends that you monitor the objects listed in the followingtable, in order to safeguard any business process step that performs Supply Network Planningactivities in the background.

Jobs for Running and Monitoring "Supply Network Planning in Background" (APO)To ensure a proper and timely demand planning, schedule the following jobs to run on a regular basis:

Run Demand Planning in the Background with report /SAPAPO/TS_BATCH_RUN. Thismass 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


© 2008 SAP AG

48

respectively, such jobs. The so-called activities that are needed for these jobs have to bedefined in advance via transaction /SAPAPO/MC8T, which is usually called from thecustomizing tree. An activity can be a forecast computation, the execution of one or severalmacros, a release of DP data to SNP orders, or the transfer to R/3. /SAPAPO/MC8I allows youto check the job definition prior to execution and find errors like “no macro defined”, “data viewdoes not exist” or “release profile not found”. With /SAPAPO/MC8G, the jobs are scheduled.Standard transaction SM37 is used for a job overview and display of job logs and jump tospool lists.To check the results of a DP mass-processing job, use the DP Job Log. To request a job log,select Generate log when you create a job. To view the job log, call transaction/SAPAPO/MC8K. The job log shows whether the job completed successfully (green trafficlight), with warnings (yellow traffic light) or with errors (red traffic light), a message for everycharacteristic value combination that was processed in the job, forecast error messages if thejob included a forecast, and other details. You can also delete job logs with this transaction.With /SAPAPO/MC8J you can copy jobs and delete them with /SAPAPO/MC8F.Parallel processing: Due to the large amount of data to be processed and the limited timethat can usually be spent on it, it is often necessary to process batch runs (for example,macros, and so on) in parallel. This can be achieved by defining several jobs in/SAPAPO/MC8x running the same activity but having a different selection of characteristics.Each selection ID should define a set of characteristic value combinations of approximatelyequal size and no individual characteristic combination should belong to more than oneselection ID as this can cause lock issues and it is superfluous to process a combination morethan once. These jobs can then be scheduled to run at the same time. Please remember thathardware resources like number of CPUs, CPU speed, main memory, and others limit the totalnumber of jobs that can run on a system at the same time.Delete DP Job Logs with report /SAPAPO/TS_BATCH_LOGFILE. Old logs from planningactivities must be deleted regularly to maintain high performance for the related transactionsand prevent database tables from overflow. Make sure that you delete the logs in packages.Select the option 'Delete all logs with minimum age' reducing the parameter days. See alsoSAP Note 512184.

Demand planning activities can be executed periodically with various frequencies. Computation of keyfigures with batch macros could possibly be done daily or weekly, whereas a release of the demandplan to production planning or R/3 is usually performed over larger intervals of time, for example, oncea quarter or once a year. Accordingly, the frequency of monitoring the jobs and deleting the DP JobLogs depends on how often you run these functions.For dependencies and concurrent execution of jobs, see Operational Management – Parallel andConcurrent Execution of Jobs. Please also refer to Exception based Monitoring of APO DemandPlanning for the handling of alerts generated by a forecast run or a batch macro.

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO report/SAPAPO/TS_BATCH_RUN.

This reportperformsspecified DPmassprocessingactivities.






DP Job Log /SAPAPO/MC8K

Aftereachrun of/SAPAPO/TS_BATCH_RUN.

Red oryellowtraffic lightsshown

Accordingly to the warning orerror reported (see messagelong text).

Applicationsupport




© 2008 SAP AG

49

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO report/SAPAPO/TS_BATCH_LOGFILE

This reportdeletes old DPJob Logs.







Exception Based Monitoring of APO Supply Network PlanningThis section outlines the concept for monitoring the overall planning situation in APO Supply NetworkPlanning. The most important high-level tool for monitoring the planning situation and an exception-driven application management is the APO Alert Monitor. The usage of the Alert Monitor is supportedby an e-mail interface that allows notification to be sent to the responsible persons in case of newalerts. Therefore, it is not necessary for planners and / or IT staff to repeatedly call the monitortransaction actively over short intervals and then to acknowledge that nothing important has happenedsince the last refresh. However, the overall situation shown in the Alert Monitor should be superviseddaily or adapted to the frequency of the demand planning process in your company.

Monitoring ActivitiesApart from safeguarding the general availability and consistency of the system components SAP APO,SAP BW, and SAP R/3 OLTP, SAP recommends that you monitor the objects listed in the followingtable in order to safeguard your Supply Network Planning business process.

Jobs for an Exception Based Monitoring of Supply Network PlanningTo ensure a timely and efficient notification of exceptions in Supply Network Planning, schedule thefollowing jobs to run on a regular basis:

Send Alert Monitor mails with report /SAPAPO/AMON_MAIL_BROADCAST. Depending onuser profiles, mails are sent with an overview of existing alerts. The responsible personsshould then call the APO Alert Monitor, investigate the reasons for the alerts and takecorrective actions in order to keep the demand plan close to the needs of your company.Delete Alert Monitor alerts with report /SAPAPO/AMON_REORG. It deletes old alerts and isof particular importance if you use alerts stored in the database. For information on databasealerts and dynamic alerts in Demand Planning, see APO Alert Monitor, above.

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO AlertMonitor

/SAPAPO/AMON1

At leastdaily

Alert list Check for forecast alerts andSDP alerts and correct theplanning for the reportedobject appropriately.

Applicationsupport


APO report/SAPAPO/AMON_MAIL_BROADCAST

This reportensuressending ofmails aboutexisting alerts.

SM37 Daily Status Check if job is running asscheduled.

If the report is not scheduledon a regular basis, scheduleit to run every hour to at leastdaily, depending on yourrequirements.




© 2008 SAP AG

50

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

Alert Monitormails

SO01(orrespective e-mailsystem)

Depending onyourrequirements,at leastdaily.

Check, if the mail lists alertsthat are important for you. Goto APO Alert Monitor andprocess the alertsappropriately.

Applicationsupport


APO report/SAPAPO/AMON_REORG.

This reportdeletes AlertMonitor alerts.


If the job is not scheduled ona regular basis, schedule it torun once a day.




SAP DocumentationSAP APO 5.1 (2007) documentation is available on CD or in the SAP Help Portal in German orEnglish.SAP APO 5.0 documentation is available on CD or in the SAP Help Portal in German or English.SAP APO 4.1 documentation is available on CD or in the SAP Help Portal in German or English.SAP APO 4.0 documentation is available on CD or in the SAP Help Portal in German or English.SAP APO 3.1 documentation is available on CD or in the SAP Help Portal in German or English.SAP APO 3.0 documentation is available on CD or in the SAP Help Portal in German or English.Print files (PDF format) of several chapters in both languages are available in the Media Center of theSAP Marketplace for SCM.Several functions that have been documented in the SAP Library for SAP APO Release 3.1 are alsoavailable in Release 3.0. Please refer to SAP Note 514971 for details.

DependenciesRemember that there are dependencies (date and time, logical sequence) on business processes andprocess steps not mentioned in this document. These usually comprise, for example:

General R/3 system administration, (this also applies to the R/3 basis of the APO system),for example:

o Reorganization of jobs, spool entries and so ono DB offline backup – During an offline database backup no online or background

activity is possible. Therefore times for such backups must be scheduled carefully.o Archiving of DB transaction logso 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, deleting, orupdating many table entries.

http://help.sap.com/

http://help.sap.com/saphelp_scm2007/helpdata/de/e1/8e51341a06084de10000009b38f83b/frameset.htm

http://help.sap.com/saphelp_scm2007/helpdata/en/e1/8e51341a06084de10000009b38f83b/frameset.htm


http://help.sap.com/saphelp_scm50/helpdata/de/12/3dfd81126e1c448c870f335f11d016/frameset.htm

http://help.sap.com/saphelp_scm50/helpdata/en/12/3dfd81126e1c448c870f335f11d016/frameset.htm








http://help.sap.com/saphelp_apo31ca/helpdata/de/92/dd013872af2946e10000009b38f8cf/frameset.htm

http://help.sap.com/saphelp_apo31ca/helpdata/en/92/dd013872af2946e10000009b38f8cf/frameset.htm


http://help.sap.com/saphelp_apo/helpdata/de/e1/8e51341a06084de10000009b38f83b/frameset.htm

http://help.sap.com/saphelp_apo/helpdata/en/e1/8e51341a06084de10000009b38f83b/frameset.htm

http://service.sap.com/scm



© 2008 SAP AG

51

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 towait for the completion of the planning activity. In addition, all other users thatrequire liveCache data have to wait for the completion of the checkpoint. Thisrestriction applies only for liveCache 7.2.x. We recommend that you writecheckpoints before and after long running planning jobs, rule of thumb 4 to 6times per day in total. This guarantees that no checkpoint has to wait for theplanning run to finish and thus causing all other transactions to wait. Second, it iswarranted that the results from the planning run are safely stored away in aconsistent manner with the other data in liveCache.

o Checking the internal (liveCache – APO DB) and external (APO – R/3) dataconsistency

o Backup for liveCacheo 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,o Delta transfer of new master data records,o Transfer of changes made to existing master data records. You should not transfer

large packages of master data to APO when CIF is needed for the transfer oftransactional data, because this can overload CIF and cause an undesirablecommunication delay.

Because of these dependencies, online and background application system activity cannot alwaysoccur whenever desired, but may need to wait, for example, for the completion of administrationactivity. Especially in APO, long-running planning activities should not collide with APO checkpointwriting, because this can cause long waits for online users (with liveCache 7.2.x only).

Therefore, program scheduling management and the software monitoring group should plan andschedule system maintenance activities to run at appropriate times, for example, overnight or over aweekend. Then, all the work necessary for the company’s core business process can be performed inthe time frames determined by the business process champions. Also, certain activities – such asbackground jobs – should be started only after the respective preceding activity has finished.

Operational Management – Parallel and Concurrent Execution of JobsThe combination of liveCache and database lock issues and system resource usage makesconcurrent execution of some SNP job types problematic.Recommendation: Observe the following rules for scheduling or executing SNP transactions and jobs:

1) Design SNP Planning runs to run in parallel with selection variants that avoid concurrent locks.Concurrent locks in SNP jobs can occur due to:

a) SNP Planning Jobs that run in parallel on the same location products or objects (forexample, same resources for handling, production, or, on rare occasions,transportation resources

b) Other planning activities (for example, PP/DS or SNP Optimizer) during the SNPPlanning 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 heuristicmodes.


© 2008 SAP AG

52

a) Multilevel Heuristic: parallel processing only if the selection variants executed inparallel specify different products AND none of the products in different variants usethe same resources.

b) Network Heuristic: parallel processing only if the selection variants executed inparallel specify different products AND none of the products in different variants usethe same resources.

c) Location heuristic: parallel processing if selection variants specify different locationsOR if selection variants which specify the same location contain non-overlapping setsof products AND the products in the different selection variants do not use anycommon resources. When a locking situation occurs during an SNP Heuristic Run, theHeuristic will attempt to re-plan the product for a fixed number of times. Itunsuccessful, it will create an error message in the job log. Refer to SAP Note 539348for technical details. Parallel processing for a complete optimiser run is possible only if

the following rules are observed:

a) The complete ppm for a final product, across all appropriate locations, should becontained in the variant for that product.

b) To avoid a non-optimal solution, separate variants should contain only products forwhich there is absolutely no overlap in components, resources, ppms, ortransportation lanes. Otherwise the solution will not be optimal.

c) No product-location should belong to more than one variant, and products in onevariant should not use resources, transportation lanes, or ppm used by products inother variants.

5) Two users should not selection variants in SNP interactive planning which lock the samedatasets. Specifically, no two selection variants which contain overlapping characteristiccombinations, or else one job must wait until the other has released the lock on the data,resulting in performance problems.

6) Parallel execution should be designed to avoid CPU bottlenecks on the application server.Optimal performance is achieved when one CPU is available for each process. How criticalthis is depends upon how much of the response time is CPU time. For optimal performance,only run as many jobs as there are CPU on the system, and less if there are memorylimitations. More jobs will run more slowly - depending upon how many CPU resources areneeded by the particular job type. Some job types, such as the SNP heuristic, are heavilydependent upon the application CPU resources, while others, such as a batch macros whichadd two key figures, are not. Note that the SNP optimiser will consume CPU resources on theoptimiser server, which can be separate from the application server.

7) Parallel execution of the SNP optimiser should be designed to avoid CPU and memorybottlenecks on the optimiser server. A good rule of thumb is that one CPU is needed for eachtwo optimiser jobs run in parallel, although the relative amount of time spent will vary with theproblem structure. Memory is often a bottleneck for the SNP optimizer; some customersconfigure separate optimizer servers for each run.

8) Parallel execution should be designed to avoid memory bottlenecks. To avoid this, a trial runof 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, find out how much memory was used by the individualprocess; call this number M_proc. The maximum number of parallel processes whichshould 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.Typically this means these jobs should be run during the night. Also run these as backgroundjobs.

10) Do not execute the daily liveCache reorganization job concurrently with ANY type of SNPplanning run or CTM.


© 2008 SAP AG

53

11) Do not execute SNP planning runs concurrently with the release from DP to SNP.

12) If you are using alerts in SNP, regularly delete old alerts using report/SAPAPO/AMON_REORG.

13) If you are executing batch macros in SNP, and are creating spool files for these runs, regularlydelete old job logs using transaction /SAPAPO/MC8K, or report/SAPAPO/TS_BATCH_LOGFILE.

14) Ensure that you are running report /SAPAPO/OM_REORG_DAILY on a regular basis, asdescribed in Note 139558. However, do not run this report concurrently with any of the SNPplanning runs.

15) Execute model consistency checks any time the master data for SNP is changed usingtransaction /SAPAPO/CONSCHK with a profile appropriate for the SNP functionality you areusing.

16) If you are using time series objects in SNP, run a time series consistency check any time youmake changes to the planning object structure, or add master data, using report/SAPAPO/TS_LCM_CONS_CHECK_ALL. A description of this report exists in Note 425825,and a discussion of errors caused by inconsistent time series objects can be found in Note509479.

17) If you are using notes management within interactive planning, it is also recommended thatyou periodically run report /SAPAPO/TS_GEN_DOCTAB_CHECK to eliminate possibleinconsistencies in the notes. However, please read Note 332812 carefully before using thisreport to automatically correct inconsistencies.

LiteratureFor more detailed information about how to administer an SAP Netweaver System, see:

Frank Föse, Sigrid Hagemann, Liane Will, SAP NetWeaver AS ABAP – System Administration,2008

For information about the administration of SAP APO systems, see: Liane Will, SAP APO System Administration, 2002

For information about how to monitor and tune general system performance, see: Thomas Schneider, SAP Performance Optimization Guide, 2008

For background information on administrative tasks with emphasis on system planning and setup, see: Hartwig Brand, SAP R/3 Implementation with ASAP, 1999

Other Best Practice DocumentsIn SAP Service Marketplace, alias /scm >> Related Topics / Best Practices for Solution Management:SAP SCM, you can find several Best Practice Documents for Solution Management like this one.

Monitoring and Administration for SCM / APO helps you analyze the workload and performance onliveCache and the APO database.Manage APO Core Interface in SAP SCM deals with the Business Process Management of the APOCore Interface CIF and is an essential enhancement to this document. All the jobs and monitoringactivities listed in the CIF document have to be considered in every business process step listedabove that sends or receives data through CIF.Manage Production Planning in SAP SCM / SAP APO deals with Production Planning and DetailedScheduling in APO and Production Execution in R/3.

Manage Demand Planning in SAP SCM / SAP APO discusses the operation of Demand Planningprocesses.

Data Consistency For SAP APO (3.x) / SAP SCM (4.x, 5.x) contains important information aboutmaster data consistency as well as internal consistency between APO DB and liveCache.

http://service.sap.com/scm


© 2008 SAP AG

54

SAP Notes(See also http://service.sap.com/notes)The following SAP Notes contain useful information on the performance of SAP APO:

303743: Support Packages for APO Release 3.0A438712: Support Packages for APO Release 3.1420669: Collective note: General Performance Improvement APO420594: Collective Note: Performance for DP 3.0A447708: Composite SAP note about APO system administration500843: Composite SAP note for COM and SAP liveCache >= 7.2

Please refer to the Best Practice Document dedicated to CIF for SAP Notes with information on qRFCand CIF.The following SAP Notes contain information about the SAP Business Information Warehouse and thedatabase underlying an SAP APO system:

124532: Performance when loading data into BW115407: Loading large amounts of data129252: Oracle DB Statistics for BW Tables130253: Notes on upload of transaction data into the BW130645: Collective note: Performance SAP BW130691: Collective note for BW - tips & tricks180605: Oracle database parameter settings for BW184905: Collective note Performance BW 2.0323090: Performance problems due to degenerated indexes325839: Considerable increase of tablespace PSAPODSD378509: Oracle DB Parametrisierung für APO384023: Optimizing performance of ODS objects400191: Further processing of data from the PSA409641: Examples of packet size dependency on ROIDOCPRMS421795: SAP_ANALYZE_ALL_INFOCUBES report428212: Update of statistics of InfoCubes with BRCONNECT458077: For all entries: Performance problems in APO Demand Planning459188: Many small partitions in PSA tables under ORACLE485878: DB2/390: BW: Partitioning the PSA tables535986: MONITORING for BW fact tables under Oracle558563: How does a client copy work with Demand Planning?

The following SAP Notes contain information about the APO Supply Network Planning moduleincluding CTM planning:

206679: Transfer requirement not physically deleted332812: Inconsistencies in selection/notes management358283: Repair tool for existing time series network359761: Demand Planning: loading performance data360935: Demand Planning 3.0: Realignment tool – consulting363092: Demand Planning: Performance Mass Processing373756: Data extraction from a planning area383906: DP 3.0: Data extraction - memory problems / COM errors384550: APO 3.0 promotion: Consulting: Reporting386735: DP: Extract data to an IC with delta update391625: Backup and Recovery for APO 3.0A Demand Planning

http://service.sap.com/notes








































© 2008 SAP AG

55

393634: Release of the optimization server after398726: DP 3.0: performance planning book/data view401830: Display <=> Change in Interactive Planning402046: DP 3.0: 'No liveCache anchor found'403050: Consulting DP 3.0: Release from DP to SNP412429: Definition of jobs with macros413526: Consultation: Navigation attributes versus basic characteristics420927: Data extraction of selected key figures425825: Consistency checks, /sapapo/om17, /sapapo/cif_deltareport426806: Memory/performance problems during data extraction428102: Performance: Loading planning area version428147: Extraction of data from an SNP planning area430688: CTM: Parallel CTM runs on a planning version432038: Creating location product to customers and vendors441723: CTM: Profile dependency of the default rule443500: R/3 versus APO: Dates in sales orders and deliveries453278: Analysis tool for export DataSources (Part 3)482494: Loading data from liveCache: Performance optimization485018: Info on the Performance of the Optimizer-Interface492460: Check double entries in planning object structure495027: Changing delivered APO InfoObjects (9A*)505886: Performance improvement during drilldown507810: BW Reporting with SNP RemoteCubes509479: Elimination of inconsistencies in time series objects512184: Background processing: Periodically delete job log512797: Use of alerts in the deployment514593: Performance improvement with DP background processing520876: Inconsistencies in time series objects528913: Lock R/3 data transfer during SNP, CTM, PP/DS planning529663: Performance during /SAPAPO/TS_LCM_CONS_CHECK533457: CTM: Deletion of orders without enhanced checks538046: Checklist transfer planned independent requirement539797: Collective consulting note on macros539848: Collective consulting note on background processing in DP540571: Collective consulting note on data extraction in DP541189: Collective consulting note on selections in Demand Planning541252: Collective consulting note for planning book maintenance541618: Collective consulting note on BW and InfoObjects in DP541633: Collective consulting note on interactive planning542946: Error message time series/period pattern does not exist546079: FAQ: Background jobs in Demand Planning549184: FAQ: What is important for extraction568671: Collective consulting note on versions568669: Collective consulting note on release DP – SNP570397: Consulting: Workaround - Copying Planning Object Structures571629: How does the note management work?572220: Avoid use of optimizer runs with the same "names"

















































© 2008 SAP AG

56

572996: Simultaneously started optimization runs644676: Consulting note on RLCDELETE report646738: SNP standard planning folder for safety stock planning660194: RLCDELETE does not delete the selected orders

Please also refer to the following SAP Notes:016083: Standard jobs, reorganization jobs139558: Scheduling report /SAPAPO/OM_REORG_DAILY195157: Application log: Deletion of logs375965: APO Consulting: Alerts in forecast425825: Consistency checks, /sapapo/om17, /sapapo/cif_deltareport495166: Tips and Tricks for Handling Alert Monitor500063: Overview of performance notes for the Alert Monitor519014: Handling Planning Version Management521639: Generation of DB Alerts in Background572003: SCM operating concept

Feedback and QuestionsSend any feedback by formulating an SAP customer message to component SV-SMG-SER. You cando this at http://service.sap.com/message.

Index/SAPAPO/AMON_MAIL_BROADCAST..27, 49

/SAPAPO/AMON_REORG......... 27, 31, 37, 49

/SAPAPO/AMON1 ...........................27, 29, 40

/SAPAPO/C4 .........................................32, 34

/SAPAPO/CIFSTARTQUEUES....................17

/SAPAPO/CIFSTOPQUEUES......................17

/SAPAPO/CTM ............................................20

/SAPAPO/CTM_DEMSUP_DELETE............19

/SAPAPO/CTMPLRUN ................................21

/SAPAPO/LCOUT........................................35

/SAPAPO/MC8x...............................30, 31, 47

/SAPAPO/MCPSH_GEN_SELTAB_MGM ....13

/SAPAPO/MSDP_ADMIN.......................11, 13

/SAPAPO/MSDP_SB...................................14

/SAPAPO/OM_REORG_DAILY..............21, 23

/SAPAPO/OPT03...................................21, 23

/SAPAPO/OPT11 ...................................20, 24

/SAPAPO/OPT12...................................21, 24

/SAPAPO/RDMCPPROCESS................32, 34

/SAPAPO/RLCDEL......................................39

/SAPAPO/RLCDELETE ...............................39

/SAPAPO/RMDPLOPT ................................24

/SAPAPO/RMSDPDEP................................37

/SAPAPO/RMSNPOPT................................24

/SAPAPO/RMSNPTLB.................................38

/SAPAPO/RRP_NETCH...............................15

/SAPAPO/RRP3...........................................26

/SAPAPO/RSDP_CALC_SAFETY_STOCK..14

/SAPAPO/RSNPDRP1.................................17

/sapapo/rsnpllcset ........................................15

/SAPAPO/RTSINPUT ..................................35

/SAPAPO/SCC01.........................................40

/SAPAPO/SDP_EXTR .................................33

/SAPAPO/SDP110.................................32, 34

/SAPAPO/SDP94...................................26, 40

/SAPAPO/SNP02.........................................37

/SAPAPO/SNP04.........................................38

/SAPAPO/SNP05.........................................25

/SAPAPO/SNP106.......................................24

/SAPAPO/SNP2PPDS .................................36

/SAPAPO/SNP94.........................................25

/SAPAPO/SNPOPLOG ................................24

/SAPAPO/SNPTLB ......................................38

/SAPAPO/TS_BATCH_LOGFILE...........31, 48

http://www.service.sap.com/~iron/fm/011000358700000431401997/0572996E














http://service.sap.com/message


© 2008 SAP AG

57

/SAPAPO/TS_BATCH_RUN ..................31, 47

/SAPAPO/TS_GEN_DOCTAB_CHECK........27

/SAPAPO/TS_LCM_CONS_CHECK............45

/SAPAPO/TS_LCM_CONS_CHECK_ALL...11,45

/SAPAPO/TS_LCM_REORG .......................45

/SAPAPO/TS_PAREA_EXTR_MGM............33

/SAPAPO/TS_PAREA_INITIALIZE...............13

/SAPAPO/TS_PAREA_TO_ICUBE ..............33

/SAPAPO/TS_PSTRU_TOOL ......................45

BRCONNECT..............................................33

RSA1.....................................................34, 42

RSBATCH1 .................................................42

RSMO..........................................................42

RSTRFCI1...................................................17

RSTRFCI3...................................................17

RSVCHECK.................................................17

SAP_ANALYZE_ALL_INFOCUBES.......33, 45

SBAL_DELETE............................................43

SLG1...........................................................42

SO01 ...........................................................28

© Copyright 2008 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission ofSAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other softwarevendors.Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner,WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks orregistered trademarks of IBM Corporation.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarksof Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented byNetscape.MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, and other SAP products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in severalother countries all over the world. All other product and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAPGroup") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable forerrors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are setforth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed asconstituting an additional warranty.Disclaimer: SAP AG assumes no responsibility for errors or omissions in these materials. These materials are provided “as is”without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability,fitness for a particular purpose, or non-infringement.SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages thatmay result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics,links or other items contained within these materials. SAP has no control over the information that you may access through the useof hot links contained in these materials and does not endorse your use of third party Web pages nor provide any warrantywhatsoever relating to third party Web pages.

manage supply network planning

Documents

business process step

planning version

ctm planning run

snp interactive planning

load data

snp heuristic run

snp optimizer run

sap scm