manage demand planning in apo 3.x & mysap scm 4.x

Manage Demand Planning in

SAP APO (3.x) / mySAP SCM (4.x) Best Practice for Solution Management

Version Date: September, 2004 This version is valid for SAP APO (3.0, 3.1) and mySAP SCM (4.0, 4.1)

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

Contents

Applicability, Goals, and Requirements....................................................................................................2 Best Practice Procedure and Verification .................................................................................................3

Preliminary Information ......................................................................................................................3 Monitoring Procedure...................................................................................................................7 Business Process Step 1: Extract Data from InfoCube (BW) ......................................................8 Business Process Step 2: Generate Flat File (Legacy System) ................................................10 Business Process Step 3: Extract Data from Logistic Information System (R/3).......................10 Business Process Step 4: Load Data into APO Data Mart (APO) .............................................10 Business Process Step 5: Set up Master Data (APO) ...............................................................12 Business Process Step 6: Load Data into Planning Area (APO) ...............................................17 Business Process Step 7: Calculate Proportional Factors (APO)..............................................18 Business Process Step 8: Adjust Historical Data (APO)............................................................19 Business Process Step 9: Create Demand Plan (APO) ............................................................22 Business Process Step 10: Determine Forecast Accuracy (APO).............................................22 Business Process Step 11: Perform Interactive Planning (APO)...............................................23 Business Process Step 12: Plan Promotions and Product Life Cycle (APO) ............................25 Business Process Step 13: Copy liveCache Data to InfoCube (APO).......................................26 Business Process Step 14: Transfer DP to R/3 (APO) ..............................................................27 Business Process Step 15: Perform Material Requirements Planning MRP (R/3) ....................27 Business Process Step 16: Release DP to SNP (APO).............................................................28 Business Process Step 17: Compute Constrained Plan (APO).................................................28 Business Process Step 18: Release SNP Plan to DP (APO) ....................................................29 Related Tools and Activities .......................................................................................................30

Further Information .................................................................................................................................39

Best Practice: Manage Demand Planning in mySAP SCM / SAP APO

© 2004 SAP AG

2

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

Goal of Using this Service This Best Practice enables you to set up a business-process management and monitoring concept for the business process Demand Planning which is part of the mySAP Supply Chain Management (SCM) solution using the SAP Advanced Planner and Optimizer (APO). It is valid for SAP APO releases 3.0A and 3.10. This business-process management and monitoring concept aims to:

• Define procedures for business-process oriented monitoring, error handling, and escalation management for Demand Planning

• Define the roles and responsibilities for all persons involved in the customer’s support and monitoring organization with respect to Demand Planning

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

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

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

Application Management Team The Application Management Team should create the SCM / APO business process management concept specified in this Best Practice. This team combines experts from several areas of your company:

Business department

Solution support organization (for example, the IT department and the Help Desk)

Implementation project team

Execution Teams

The execution teams are the following groups, which are taken together from your Solution Support Organization:

The Business Process Champion for each business process

Application Support

Development Support

Program Scheduling Management

Software Monitoring Team

System Monitoring Team

More information about roles and responsibilities of these teams can be found in the superordinate Best Practice General Business Process Management, which you can obtain through the SAP Solution Manager.


© 2004 SAP AG

3

Necessary or Useful Training Courses:

BC355 APO System Administration

SCM210 Basic Data Integration (previous AP205)

SCM220 Demand Planning (previous AP210)

System Requirements None.

Duration and Timing Duration

Creating a business-process management concept may take around one week per business process.

Implementing the business-process management concept may take around one additional week.

Timing

The best time to apply this Best Practice is during the planning phase or during the implementation phase of your mySAP solution.

Best Practice Procedure and Verification

Preliminary Information

The SCM System Landscape The substantial components of an SAP SCM system landscape are summarized in the following table and shown schematically in the subsequent illustration.

SAP APO System The SAP Advanced Planner and Optimizer system facilitates the strategic, tactical, and operational planning processes.

APO consists of several software components: a relational database system (RDBMS) as in any SAP R/3 System, known as the APO DB; an SAP R/3 Basis; the APO application programs; a separate, very fast object-oriented SAP DB database called liveCache; and a number of programs that execute elaborate optimization algorithms, called optimizers. These components can run on the same or on different servers.

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

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


© 2004 SAP AG

4

SAP R/3 Plug-In

OLTP System

RDBMS

SAP R/3 Plug-In

OLTP System

RDBMS

RDBMS

SAP APO System

liveCache

liveCache

OLAP System

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.

Usually, an APO system is connected to one or several systems that provide historical and actual data, such as sales figures, for your demand planning business process. These systems can be SAP R/3, SAP BW, and / or third party and legacy systems or a combination of these. As SAP APO comprises a complete SAP BW, the tools for extracting data from other systems and transferring them to APO for demand planning purposes are the same as SAP BW uses. The APO BW reads the data using remote function call (RFC) techniques, IDocs, or OS file access.

The planning results that come out of the demand planning process are fed into other data processing systems for further planning or execution purposes. The system types that can be used here are SAP APO itself (in particular its modules SNP and / or PP/DS), SAP R/3, or again third-party (legacy) systems. Third-party systems are not considered in this Best Practice document.

This Best Practice is therefore based on a general and common integration scenario for setting up a mySAP Supply Chain Management solution using SAP APO. As data sources, SAP BW, SAP R/3, and flat files from any other system type can be connected to the SAP APO system. The results from the demand planning process are processed by another module of the APO system itself, or are transferred to an SAP R/3 OLTP system via the Core Interface (CIF).


© 2004 SAP AG

5

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

• 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 primarily a planning tool, although some industry specific execution functions are available (such as production backflush for repetitive manufacturing). In standard business scenarios, execution functions such as confirmations, goods receipt, purchasing, and so on are performed in the SAP R/3 OLTP system, which contains all functionality for (among many others) Material Management MM, Sales and Distribution SD, Production Order Processing PP-SFC, Logistics Execution LES, and Controlling CO.

Demand Planning The core business process you run in your company for planning your demand and supply, though it is also based on the mySAP SCM solution, may differ more or less from the canonical process described as follows and illustrated on the next page. The past and actual data your Demand Planning is based on is obtained from the source systems such as R/3, BW, or others and loaded into BW InfoCube(s) located in the APO system, the APO Data Mart(s). New characteristic value combinations need to be generated, for example if new products are planned or if a planning-relevant customer purchases a product for the first time. The master data need to undergo a realignment step, for example if sales organization structure or product hierarchy is changed. Normally, some historical data is copied from InfoCubes to key figures stored in liveCache, in the Planning Area(s). For disaggregation purposes, proportional factors have to be (re)calculated. Historical data has to be adjusted and cleared from exceptional influences (such as promotions, outliers, or unique occurrences like the introduction of a new currency) in order to serve as a reliable basis for the forecast. In the batch forecast run, the demand plan is created. Afterwards, the accuracy of the forecast can be determined by comparing the differences between the actual values and the ex-post values. In Interactive Planning, the results of a forecast created in the background are verified, manual corrections and less quantifiable processes and trends derived from experience are applied to the Demand Plan, and computations of key figures are performed using macros. (However, Interactive Planning should be restricted to the processing of small data volumes. Larger amounts of data should be processed in the background wherever possible.) Using dedicated tools, the influence of promotions can be estimated and evaluated, and the different phases of the life cycle of products can be modeled. Many APO installations save the data kept in liveCache into an InfoCube from time to time and use this InfoCube, for example, for reporting purposes involving the Business Explorer. The final and confirmed demand plan can be either transferred to R/3 creating planned independent requirements and serving as basis for the Material Requirement Planning run (MRP). You can take production or distribution restrictions into consideration by releasing the demand plan to the SNP module of APO. You can then transfer the resulting supply network plan back to DP for comparison with the unconstrained demand plan. Any major discrepancies between these two plans can trigger re-forecasting, and ultimately, re-planning. For example, you may determine that the capacity situation demands a change in the promotion strategy.


© 2004 SAP AG

6

The following diagram shows all the business process steps whose monitoring is defined by this Best Practice:

Extract Data from InfoCube

SAP BW System

Generate Flat File

Legacy or Third Party System

SAP APO System

Load Data into APO Data Mart

Update Master Data

Load Data into Planning Area

Calculate Proportional Factors

Adjust Historical Data

Create Demand Plan

Determine Forecast Accuracy

Perform Interactive Planning

Plan Promotions and Product Life Cycle

Copy liveCache Data to InfoCube

Transfer DP to R/3

Release DP to SNP

Demand Planning

Supply Network Planning

Extract Data from LIS

SAP R/3 OLTP system

Perform Material Requirements Planning

(MRP)

Compute Constrained Plan

Release SNP-Plan to DP

INTERFACES

tRFC / IDoc

OS FileSystem

tRFC / IDoc

CIF


© 2004 SAP AG

7

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

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

o Monitoring object o Monitoring transaction or tool o Monitoring frequency o Monitoring time (intentionally left blank, to be filled in according to your schedule) o Indicator or error o Monitoring activity or error handling procedure o Responsible team o Escalation procedure

As the frequency of demand planning processes vary from daily activities at certain companies to only monthly or quarterly at others, the monitoring frequency in these monitoring object tables is partly only a rough estimate and has to be adapted to your particular business process. During the going-live and stabilization phase of your APO implementation project, you should closely monitor all items listed in this document. Once you have some experience with system behavior, error occurrences, and application operations, you can decrease the monitoring frequency, but you should never reduce it to zero (except for functions you do not use). Normally, you need to monitor important planning jobs after each run. You can check whether regular jobs with lower priority (such as certain clean-up jobs) run as scheduled less frequently; for example, you can check daily jobs weekly. The following seems obvious but should nevertheless be mentioned: Besides the monitoring of jobs described in the business process steps below, it is essential that you check all jobs that are running in your system at least several times per day for abnormal terminations (status “cancelled”, see Error Handling, Restartability and Escalation) and that you investigate and correct these terminations appropriately. This check can be done easily, for instance, with transaction SM37 by entering the time interval since the latest check and selecting all jobs with status “cancelled”. If you have no automatic notification in place that informs the people responsible for Program Scheduling Management in your Support Organization of abnormally terminated jobs, you need to take measures to ensure that this is done 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 deleting outdated jobs or spool objects. For details and comments, see SAP Note 16083.

Depending on the types of data processing systems you use in your solution landscape and which of these contribute data for your demand planning process, you will possibly not execute all of the business process steps 1, 2, and 3 described below, but only one or two of this type.


© 2004 SAP AG

8

Business Process Step 1: Extract Data from InfoCube (BW) All SAP APO systems include a complete SAP Business Information Warehouse System (BW), which should be used exclusively for APO purposes. In this business process step, data is extracted from a separate BW system. All periodic monitoring tasks must still be performed in the APO system as well as job definition and most of the configuration tasks. The Administrator Workbench (transaction code RSA1) is the tool for loading data into the InfoCubes from a source system. Using the Administrator Workbench Scheduler, you create an InfoPackage specifying source, target, time, background parameters, and selection criteria for the data transfer to the InfoCube. You can see a log for the request that is generated for the transfer job in the Manager, which you can access from the Administrator Workbench by selecting the InfoCube and choosing it in the context menu.

Usually, a single job is set up in the BW of the APO system with different processing steps to extract the required data from the source system, transfer it to APO, and write it into the InfoCube(s). For the data transfer method, you can select either of two options in the respective InfoSource:

• Transfer into PSA (Persistent Staging Area): The data is sent directly from the source system to the Business Information Warehouse and is stored in the Operational Data Store (ODS). From there your data can either be updated manually or automatically in the InfoCubes. The transfer type for this is transactional remote function call (tRFC). In customizing transaction RSCUSTV6, you can set threshold values for the data load, such as packet size and partition size. For details, see SAP Notes 325839 and 459188 (for Oracle databases), and 485878 (for DB2 on OS/390). These notes also provide guidelines for default sizes of these parameters.

• Data transfer with IDocs (Intermediate Documents): The data is packed into IDocs by the source system and sent to the Business Information Warehouse. In BW your data is saved persistently and non-transparently in the IDoc store. From there the InfoCubes can be updated manually or automatically.

SAP recommends using tRFC, as it has a performance advantage. If IDocs are used, you can easily find the required monitoring screens (IDoc list, status and data records as in transaction BD87) in transactions RSA1 or RSMO. For details and performance hints, see SAP Notes 124532, 130253, 400191, and 409641. SAP Notes 124532 and 115407 apply to SAP APO 3.0A and higher. SAP Note 115407 is restricted to SAP BW up to 1.2B. For all types of databases, dropping the indexes of the fact table before loading a huge amount of data is a viable option. However, it depends on the ratio of the data volume in the cube and the data volume to be loaded whether it is faster to update the indexes with the data or drop and rebuild them. There is no general rule, so do a test and choose the faster method. With Oracle, indexes are rebuilt in parallel if the database has the correct parameters, so it is often faster with dropped indexes. See also the Best Practice Documents dealing with the data transfer to an SAP BW system.

Monitoring Activities Apart 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 following table in order to safeguard this business step. The data transfer process as well as certain actions in RSA1 and RSMO write detail information to a central R/3 basis component called the application log. The log entries are subdivided into objects and sub-objects and classified by importance. In case of errors or problems, the application log can be used to get more detailed information about what happened and how to resolve the problem. The monitoring transaction for the application log is SLG1, where you should specify the (sub-) objects and the time interval you want to be displayed. Relevant objects for the SAP Business Information Warehouse are:

• RSAR BW Metadata maintenance • RSAU Update rules • RSD BW data basis


© 2004 SAP AG

9

• RSDMD Master data maintenance • RSO_REPOSITORY BW Repository • RSSM Scheduler; Monitor; Tree callback

Jobs for Running and Monitoring "Extract Data from InfoCube" (APO) To ensure a timely and consistent data transfer from your BW into your APO system, schedule the following job on a regular basis:

• Data Extraction and Load with report RSBATCH1. Define this job using the scheduler 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 the selected Info Package. With the help of Info Package Groups, you can collate data requests that logically belong together and schedule them using the scheduler.

In Administrator Workbench Monitoring (select Monitoring in transaction RSA1 or call transaction RSMO) you can oversee and control the data loading process into the InfoCubes and you can analyze errors that may have occurred (choose Monitor >> Assistant). You can also call the monitor from a selected Info Package. To be sure to select the correct time window and data to be displayed, call the selection screen by choosing Monitor >> New Selections.

Jobs for the Maintenance of the Application Log The application log entries are stored on tables with name prefix BAL*. As there are very many applications that use this basis component and often many table entries are made, it is important to delete obsolete application logs from the database regularly in order to prevent these tables from overflowing and to help ensure that the applications and log retrieval run smoothly. You can delete them using transaction SLG2 or in background by the appropriate report:

• Delete Obsolete Application Logs with report SBAL_DELETE. A log can only be deleted when it has reached its expiry date or if it has the "Deletion before expiry" attribute. For more information, see SAP Note 195157.

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error

Monitoring Activity or Error Handling Procedure

Respon-sibility

Escalation Procedure

APO job BI_BTCH*

These jobs perform the data transfer from the different data sources to APO InfoCubes

RSMO or SM37

Depending on your process

Status Check if job is running as scheduled.

If the job is not scheduled as provided by Application Support, schedule it accordingly.

Program scheduling management

Contact Application Support

APO: Administration Workbench Monitor

RSMO After every data load

Red or yellow traffic lights

After selecting one request, read the error message and diagnosis under tab strip Status and the processing log under Detail.

Use the Monitor Assistant to analyze and correct the error situation.

Software monitoring team


APO: Evaluate Application Log for BW related objects

SLG1 At least daily

Log class Check if there are very important logs (flagged red) or important logs (flagged yellow).

Read message long text and / or details, if present. Analyze error situation, evaluate error severity and impact, and take corrective action.




© 2004 SAP AG

10

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


APO report SBAL_DELETE

This report deletes obsolete Application Logs.

SM37 Weekly Status Check if job is running as scheduled.

If the job is not scheduled as provided by Application Support, schedule it to run weekly.



See general issues of Error Handling, Restartability and Escalation.

Business Process Step 2: Generate Flat File (Legacy System) This business process step is similar to Business Process Step 1: Extract Data from InfoCube (BW), except that the Info Source is defined differently. The data from the legacy or third party system must be provided by methods and programs of that system in flat file form with format *.csv (comma separated values) or *.asc (ASCII). The file should be sorted by key sequence and be uploaded from the application server rather than a presentation server, if possible. For performance issues, see SAP Notes 124532 and 359761. It is also valid for SAP APO 3.0 and onwards, except that report /SAPAPO/RMDP_ICUBE_PERFORM has been replaced by /SAPAPO/TS_PSTRU_TOOL ; see SAP Note 393655. For details, see Maintenance of DP Data Storage Structures.

Monitoring Activities Apart 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 under Monitoring of Business Warehouse Activities in order to safeguard this business step.

Business Process Step 3: Extract Data from Logistic Information System (R/3) Like Business Process Step 2: Generate Flat File (Legacy System), this business process step resembles Business Process Step 1: Extract Data from InfoCube (BW). In this case, the data is automatically updated from selected info structures in the Logistic Information System (LIS) of an SAP R/3 OLTP to the BW component of APO. As the extractor used to get the data from LIS is generic, you can use any SAP-delivered or custom-defined info structure (table Snnn with 3 digit number nnn) as data source. APO Demand Planning can use information from all parts of logistics, such as sales, inventory, purchasing, shop floor control, and quality management.


Business Process Step 4: Load Data into APO Data Mart (APO) As described under Business Process Step 1: Extract Data from InfoCube (BW), you use the BW Administration Workbench Scheduler of your APO system to set up jobs for the data transfer from the different data sources to APO. Such a job extracts the required data in the source system, transfers it to APO, and updates the specified InfoCube(s) in different processing steps. You can control and monitor these steps from the BW monitor transaction RSMO. If the data update from ODS or PSA to


© 2004 SAP AG

11

the InfoCube is not performed automatically but triggered manually, you will need to monitor this step again using RSMO. For the data load step, it is important that statistics and indexes of the InfoCube(s) the data is loaded into are current. To check this: in transaction RSA1 right-click on the respective InfoCube and choose Manage. In the next screen, choose tab strip Performance and select Check Statistics (available only for certain databases. see below), Check Indexes and Check Aggregate Indexes, resp. InfoCube statistics should be created regularly in background using report SAP_ANALYZE_ALL_INFOCUBES. You can also use transaction RSRV for the analysis of BW objects. For information about data transfer to an SAP BW system, see also the Best Practice Documents.

Monitoring Activities Apart 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 following table and under Monitoring of Business Warehouse Activities in order to safeguard this business step.

Jobs Necessary to Keep the APO Data Structures in Good Condition (APO) To ensure that database statistics and indexes for BW specific data structures are kept up to date, and that liveCache data structures (time series) are kept consistent, schedule the following jobs to run on a regular basis:

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

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


APO report SAP_ANALYZE_ALL_INFOCUBES

This report creates DB statistics for all InfoCubes.

Only for systems running with Oracle, SAP DB or IBM DB2/UDB (DB6) database


If the job is not scheduled on a regular basis, schedule it to run once a week with parameter percent = 100.


Contact software monitoring team

Indexes of APO InfoCubes

RSA1 or RSRV

Weekly Red or yellow traffic light

Select Check (Aggregate) Indexes. If the traffic light gets yellow or red, select Repair Indexes (now) or Delete Index (batch) and Create Index (batch).





© 2004 SAP AG

12

Business Process Step 5: Set up Master Data (APO) During operation, new characteristic value combinations occur. For instance, your company introduces new products or existing products are additionally manufactured at another location. There are six ways of creating characteristic value combinations:

• Individually and manually, by completely defining characteristic values in transaction /SAPAPO/MC62 (this creates one data record). You also can delete characteristic value combinations with /SAPAPO/MC62 (single values or generic by using the * wildcard).

• Automatically, by generating the combinations based on existing data from an InfoCube. With this option, the system generates all the new combinations that it finds in the horizon specified. You can plan automatic generation periodically so that new characteristic value combinations are added each time but old ones are never deleted. This function can also be called from transaction /SAPAPO/MC62 or is executed in background using report /SAPAPO/TS_PLOBS_GENERATE.

From release mySAP SCM 4.1 you have four additional ways for creating characteristic value combinations:

• You can create them by referring to a different Planning Object Structure (POS) in your system.

• New characteristic combinations can be based on an Infoprovider (like e.g. an Infocube, but other Infoproviders are also possible).

• They can be based on a flat file upload (now without using an Infocube as workaround solution for releases 3.0, 3.1 and 4.0).

• Characteristic value combinations can be automatically created using a new BadI. Transaction /sapapo/mc62 has been extended for release mySAP SCM 4.1 and offers these four new ways as additional options. Releases 3.0, 3.1 and 4.0 do not offer an option to create characteristic combinations from flat file. The workaround solution for this is to use an Infocube: You can edit the combinations in a flat file, such as a Microsoft Excel file, upload this file to an InfoCube, and then use this InfoCube to generate the characteristic value combinations. You may wish to realign your data because of structural changes in the characteristics. For example, one of your existing products will in future belong to a new product group, so you want to assign the product to the new product group, and realign the planning data to the new characteristic value combination(s). You can create the new characteristic value combinations automatically using an SAP realignment tool. You create a table that contains the changes, then new characteristic value combinations are created from this table and you decide whether you want to copy existing combinations or to replace them. The data stored in the key figures is copied correspondingly. For details, see SAP Notes 360935 and 492399 (depending on your release and support package). Please note that these two notes are only valid for SAP APO releases 3.0 and 3.1! Remember that you cannot modify standard characteristics 9ALOCNO (location) and 9AMATNR (product). Concerning the usage of basic characteristics and / or navigation attributes in your planning object structure, see SAP Note 413526. For the generation of characteristic combinations and the corresponding time series, it is important to update statistics and indexes of the planning object using report /SAPAPO/TS_PSTRU_TOOL.

Monitoring Activities Apart 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 following table and under Maintenance of DP Data Storage Structures in order to safeguard this business step.


© 2004 SAP AG

13

Jobs for Running and Monitoring "Set up Master Data" (APO) To ensure a complete and correct setup of master data needed for your Demand Planning process, schedule the following jobs to run on a regular basis:

• Generate new Characteristic Value Combinations with report /SAPAPO/TS_PLOBS_GENERATE. It generates the same characteristics and characteristic value combinations (that is, the corresponding time series) in the selected planning object structure as it finds in the source version of the InfoCube specified. Run it after every data load into the InfoCube that contains the relevant characteristic combinations.

• Adapt Time Series for New Characteristic Combinations with report /SAPAPO/TS_LCM_PLOB_DELTA_SYNC. For example, if you create a new characteristic combination without the option 'Create time series objects' (see transaction /SAPAPO/MC62), you get the error “No liveCache anchor found” when selecting this characteristic combination. In this case, execute report /SAPAPO/TS_LCM_PLOB_DELTA_SYNC for the basis planning object structure of the planning area. This creates the corresponding liveCache anchors and liveCache time series for all planning areas that use this basis planning object structure and for all versions of these planning areas for which time series objects already exist. /SAPAPO/TS_REALIGNMENT cannot work without the liveCache anchors. So before executing realignment (or if missing liveCache anchors are reported), run report /SAPAPO/TS_LCM_PLOB_DELTA_SYNC. Mark the option display error log to get a log in case of unsuccessful execution. See also SAP Notes 492399 and 573127. If necessary, you can determine and repair inconsistencies for the planning area by executing report /SAPAPO/TS_LCM_CONS_CHECK and choosing the Repair option (see Maintenance of DP Data Storage Structures). For details, see SAP Note 402046.

• There are different transactions and reports for the realignment of Characteristic Value Combinations in the releases SAP APO 3.0 and 3.1 in comparison with newer releases. In SAP APO 3.0 and 3.1 you can do this with report /SAPAPO/TS_REALIGNMENT as far as you have the need to consider structural changes in your characteristic combinations. From release mySAP SCM 4.0 you can use transaction /SAPAPO/RLGCOPY or, if you want to do the realignment as an automated task, use directly report /SAPAPO/TS_REALIGN_COPY for this activity.

• Re-Initialize Your Planning Area with report /SAPAPO/TS_PAREA_INITIALIZE. The creation of time series objects for the planning area is known as initializing the planning area. The system creates a network of characteristics and key figures in liveCache, time series objects are created for a version and a period of time. You can extend the time series into the future and delete the oldest periods from liveCache by re-initializing the time series periodically. In this way you can maintain a "rolling horizon". The system recognizes where new characteristic value combinations or new time series exist, and creates time series objects only for the new master data. From release mySAP SCM 4.0 you can define key-figure specific initialization horizons and save a lot of memory in your liveCache. E.g. for historical key figures you can initialize only time buckets in the past and for forecast figures only buckets in the future. This can be defined in a Pop-Up window during the start of the report or in the transaction for key figure administration. The report /SAPAPO/TS_PAREA_INITIALIZE locks the complete version of the planning area. If the lock cannot be set, the report terminates. From release SAP SCM 4.0 you have the additional possibility to perform the initialization with parallel processes. For this you have to define a block size and a maximum number of parallel processes for the planning area. After starting the initialization job, it creates automatically the desired number of parallel processes. If the report terminates abnormally for any reason other than lock problems (you can see this in the job log), run report /SAPAPO/TS_LCM_CONS_CHECK with option Repair (see Maintenance of DP Data Storage Structures) before restarting /SAPAPO/TS_PAREA_INITIALIZE. For example, if you no longer need a certain planning version, you can remove its data from liveCache by deleting the time series objects with report /SAPAPO/TS_PAREA_DE_INITIALIZE.

Jobs for the Maintenance of the Planning Object Structure • Maintain Statistics and Indexes for Planning Object Structures with report

/SAPAPO/TS_PSTRU_TOOL. Run this report in separate background jobs choosing options Calculate Statistics and Check Indexes for every Master Planning Object Structure and review the list of messages being


© 2004 SAP AG

14

displayed. If problems are reported by the index check, run it with option Repair Indexes. A separate background job (job name with prefix BI_STAT) is started to execute this request. These administrative jobs must be run after every load of data to a planning object structure. For further details, see SAP Notes 393655, 492460, 503363, and 510639.

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


APO report /SAPAPO/TS_PLOBS_GENERATE

This report generates new characteristic combinations.

SM37 Depending on your process


If the report is not scheduled as provided by Application Support, schedule it accordingly.



Output of APO report /SAPAPO/TS_PLOBS_GENERATE

SP01 After every run

Messages in spool list.

Review the messages listed like “Number of incorrect combinations”.

Application support

Contact process champion

APO report /SAPAPO/TS_LCM_PLOB_DELTA_SYNC

This report creates liveCache anchors and new time series






Output of APO report /SAPAPO/TS_LCM_PLOB_DELTA_SYNC

This report creates liveCache anchors and new time series

SM37 After every run

Status If status is “cancelled”, check job log for error messages.



APO report /SAPAPO/TS_REALIGNMENT

This report is available in the releases 3.0 and 3.1 and realigns characteristic combinations







© 2004 SAP AG

15

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


Output of APO report /SAPAPO/TS_REALIGNMENT


Messages in spool list

Review the list for problems reported like “Error: Realignment job cancelled”, “No connection to liveCache”, “Aggregate, indexes and statistics must be checked” (and more).

Take corrective action if necessary.

Application support

Contact Process Champion

APO report /SAPAPO/TS_REALIGN_COPY

This report is available in the releases 4.0 and 4.1 and realigns characteristic combinations






Output of APO report /SAPAPO/TS_REALIGN_COPY

Special log file, view and administrate with /SAPAPO/RLGCOPY

After every run

Messages in log file. If report was run in background, an additional spool file exists

Review the list for problems reported like “Error: Realignment job cancelled”, “No connection to liveCache”, “Aggregate, indexes and statistics must be checked” (and more).


Application Support


APO report /SAPAPO/TS_PAREA_INITIALIZE

This report re-initializes time-series objects






Output of APO report /SAPAPO/TS_PAREA_INITIALIZE



Review the list for problems reported like “Time stream (XXX) for year (YYYY) not generated”.


Application support


For releases 3.0, 3.1 and 4.0:

APO report /SAPAPO/TS_PSTRU_TOOL with option Calculate Statistics

This report checks and generates statistics for a POS

SM37

After every data load into the POS






© 2004 SAP AG

16

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility



APO report /SAPAPO/TS_PSTRU_TOOL with option Check Indexes

This report checks the indices of a POS

SM37 After every data load into the POS






Output of APO report /SAPAPO/TS_PSTRU_TOOL


Message type (icon)

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




Job BI_STAT* started by /SAPAPO/TS_PSTRU_TOOL with option Repair Indexes


Status Check if job ended correctly. Program scheduling management


For release 4.1:

APO report /SAPAPO/TS_PSTRU_CONS_CHECK for checking and repairing inconsistencies (if repairing is possible)






© 2004 SAP AG

17

Business Process Step 6: Load Data into Planning Area (APO) You store permanent data in InfoCubes. In general this is either historical actual data or forecasts that you want to keep for future comparison. Actual data for planning is kept in liveCache in planning areas. Demand Planning itself is conducted in liveCache. For example, to use historical data as the basis for forecasting, you either access data directly from the InfoCube or transfer data between it and liveCache. Both methods have advantages and disadvantages. Placing a lot of a data in liveCache improves performance, but it also requires more memory, and you need to consider this when sizing your APO system and when designing your planning area. SAP strongly recommends storing all key figures that are used in background or interactive Demand Planning in liveCache even if not enough memory is available. It is faster to read data from liveCache even if it is swapping than from an InfoCube. As it is not possible to change key figures interactively that are stored in an InfoCube, you need to copy key figures to the liveCache if you want to change them. However, you should not change historical actuals; instead, copy them to a separate key figure “corrected history” that you can afterwards maintain manually. For this business process step, use transaction /SAPAPO/TSCUBE for an online copy, (do this only in exceptional cases and for a very small amount of data), or report /SAPAPO/RTSINPUT_CUBE for background mass data processing. From release mySAP SCM 4.1 it is possible to set up parallel jobs using individual selections for shorter processing times. Two new options help reduce the upload data quantity and can help with the creation of parallel selections: The flag “Ignore data sets with 0 forecast quantity” directly reduces the data quantity for processing. The flag “Ignore values which are not within the selected horizon“ reduces the data quantity as well and offers an option for setting up parallel jobs. From release mySAP SCM 4.1 you can navigate directly to the report log by clicking on a button. Other data you want to use in a specific Demand Planning business process may already be present in liveCache, but stored in a different planning area and / or version. In this case, you can use a similar function called Copy/Version Management (TA /SAPAPO/TSCOPY, report /SAPAPO/RTSCOPY), which allows you to copy data between planning areas and versions. As of release mySAP SCM 4.1, it is possible to set up parallel jobs using individual selections for shorter processing times. One new option helps reduce the upload data quantity and can help with the creation of parallel selections: The flag “Ignore values which are not within the selected horizon“ reduces the data quantity and offers an option for setting up parallel jobs. From release mySAP SCM 4.1 you can navigate directly to the report log by clicking on a button.

Jobs for Running and Monitoring "Load Data into Planning Area" (APO) To ensure a complete and correct copy of key figures, schedule the following jobs to run on a regular basis:

• Load Planning Area Version with report /SAPAPO/RTSINPUT_CUBE. To get a list of success and error messages from this report, mark the check box Log in the selection variant you use for this job. The list looks like the application log (transaction SLG1), but is not stored separately from the job. For performance hints, see SAP Note 428102.

• Copy Data Between Planning Areas and Versions with report /SAPAPO/RTSCOPY. To get a list of success and error messages from this report, mark the check box Log in the selection variant you use for this job. The list looks like the application log (transaction SLG1), but is not stored separately from the job.


© 2004 SAP AG

18

Monitoring Activities Apart 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 following table in order to safeguard this business step.

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


APO report /SAPAPO/RTSINPUT_CUBE

This report copies key figures from an InfoCube to a Planning Area






Output of APO report /SAPAPO/RTSINPUT_CUBE


Message type (icon)


Application support


APO report /SAPAPO/RTSCOPY

This report copies key figures between Planning Areas and versions






Output of APO report /SAPAPO/RTSCOPY


Message type (icon)


Application support



Business Process Step 7: Calculate Proportional Factors (APO) One way to perform disaggregation is to use constant proportional factors. The constant proportional factors are derived from historical data or, occasionally, from past planning data. You can carry out disaggregation differently for different key figures. Generate constant proportional factors if you wish to disaggregate planning data based on the constant proportional factors either always or if no planning data exists. The proportional factors are stored in key figure APODPDANT. Using transaction /SAPAPO/MC8V, the computation of the proportional factors for a selected planning area can be started to run online or in the background, or by using report /SAPAPO/RMDP_SHARE_MANAGER as a scheduled background job. For details, see also SAP Notes 363221 (only for APO 2.0A; as of release 3.0, the proportional factor is always stored in liveCache) and 488020. As of release mySAP SCM 4.1 you can use parallel processing for the calculation of proportional factors. You can navigate from transaction /SAPAPO/MC8V directly to the maintenance of parallel processing profiles or use /SAPAPO/SDP_PAR for direct access. After defining block size and the number of maximum parallel processes you have to assign the parallel processing profile to the


© 2004 SAP AG

19

selection variant. The next time you run this selection as a background job it will automatically run with parallel processing.


Jobs for Running and Monitoring "Calculate Proportional Factors (APO)" To allow a correct disaggregation, schedule the following job to run on a regular basis:

• Calculate Proportional Factors with report /SAPAPO/RMDP_SHARE_MANAGER. If you wish to view the results, mark the check box Log for Proportion calculation. Caution: This is intended for use in the test phase only. As all characteristic value combinations and the calculated factors are listed (and for all periods, if Calculate detailed proportions for all periods has been selected), this list can become very large.

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


APO report /SAPAPO/RMDP_SHARE_MANAGER

This report calculates the proportional factors







Business Process Step 8: Adjust Historical Data (APO) The original actuals can be adjusted for different circumstances: phase-in/out profile, workday adjustment, past promotions, outlier corrections, and manual adjustments. Various automatic procedures that are activated in the forecast profile can be used to adjust the actuals. Workday adjustment ensures that higher values are forecasted for periods that have many workdays. Historical data must be adjusted to take this into account. To generate more exact forecasts, remove the impact of one-time promotions or delivery problems from the actuals. It is usual to not make these adjustments in the original key figure but in the corrected history key figure. Usually, these corrections are carried out by macros run in the background for mass data processing. You can also adjust the actuals manually. By making manual modifications, you can fine-tune the demand plan. Management overrides are one example of this. To document a modification, write a note in the Demand Planning table and attach it to the cell and the level in which you made the modification. You can also check for any errors in the demand forecast and run some macros to correct it or select a suitable forecast model. For manual corrections, see Business Process Step 11: Perform Interactive Planning (APO). For more information and details on background macro processing, see SAP Notes 412429 and 546079. Some hints on the design and usage of macros for background processing:

• Create a separate planning book for each macro background job. The planning book should contain only the key figures used by the macro itself, and only macros executed as activities by the mass-processing job. Use a different planning book whenever different key figures are needed by two macros, and a different data view whenever the time periods are different.

• Remove all unused macros from planning books associated with mass processing jobs, as they are loaded in an unorganized manner, which can be performance-intensive, and they are not helpful to your business process.


© 2004 SAP AG

20

• Only those macros that are called by an activity are executed in the background; start, end, level change. Default macros are not executed automatically, as they are in dialog. When defining a job, you must therefore first establish which start and default macros have to be executed and in which sequence, so that your own self-defined macro can work correctly. Macros which run in the background need not involve actions such as setting colors, hiding fields, display icons, or sending popup windows that are frequently included in default macros for online use.

• The planning book used for background macros should have only the functionality it uses; i.e. application demand planning and no other functionality.

• For performance reasons, run macros for a delta period rather than the entire horizon wherever possible. Under most circumstances, historical data is not changed, other than adding new periods, one time bucket profile at a time. Rather than performing the full calculation over a long historical period, run a macro to do this once, and then design a new macro that only performs the calculation for the “delta” period, or the period that has just entered the historical horizon.

• Create several background jobs with roughly equal numbers of characteristic combinations and run them in parallel. Make sure that no individual characteristic combination belongs to more than one selection variant, as this can cause lock issues.

• From release mySAP SCM 4.1 you can use parallel processing for running macros, e.g. for the adjustment of historical data. You can navigate from transaction /SAPAPO/MC8T directly to the maintenance of parallel processing profiles or use /SAPAPO/SDP_PAR for direct access. After defining block size and number of maximum parallel processes you have to assign the parallel processing profile to the selection variant. The next time you run this selection as background job it will automatically run with parallel processing.

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


Jobs for Running and Monitoring "Adjust Historical Data" (APO) To ensure correct 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. This mass processing job is created with the necessary settings and scheduled using transactions /SAPAPO/MC8x. You can create and change such jobs using the respective transactions /SAPAPO/MC8D and /SAPAPO/MC8E. Define the activities needed for these jobs in advance via transaction /SAPAPO/MC8T (usually called from the customizing tree). An activity can be a forecast computation, the execution of one or several macros, a release of DP data to SNP orders, or the transfer to R/3. /SAPAPO/MC8I enables you to check the job definition prior to execution and find errors like “no macro defined”, “data view does not exist” or “release profile not found”. With /SAPAPO/MC8G, the jobs are scheduled. To overview the jobs, display the job logs, and jump to spool lists, use transaction SM37. 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 traffic light), with warnings (yellow traffic light), or with errors (red traffic light), a message for every characteristic value combination that was processed in the job, forecast error messages if the job included a forecast, and other details. You can also delete job logs with this transaction. You can copy jobs with /SAPAPO/MC8J and delete them with /SAPAPO/MC8F. Parallel processing: Due to the large amount of data to be processed and the limited time available for it, it is often necessary to process background runs (of macros or whatever) in parallel. You can do this 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 approximately equal size, and no individual characteristic combination should belong to more than one selection ID, as this can cause lock issues and it is superfluous to process a combination more than once. These jobs can then be scheduled to


© 2004 SAP AG

21

run at the same time. Remember that hardware resources such as the number of CPUs, CPU speed, main memory, and others limit the total number of jobs that can run on a system at the same time. From release mySAP SCM 4.1 you can use parallel processing for running macros or any other planning activity like performing a statistical forecast. You can navigate from transaction /SAPAPO/MC8T directly to the maintenance of parallel processing profiles or use /SAPAPO/SDP_PAR for direct access. After defining block size and number of maximum parallel processes you have to assign the parallel processing profile to the selection variant. The next time you run this selection as background job it will automatically run with parallel processing.

• Delete DP Job Logs with report /SAPAPO/TS_BATCH_LOGFILE (or transaction /SAPAPO/MC8K). Old logs from planning activities must be deleted regularly to maintain high performance for the related transactions and prevent database tables from overflowing. Make sure that you delete the logs in packages. Select the option 'Delete all logs with minimum age' reducing the parameter days. See also SAP Note 512184.

Demand planning activities can be executed periodically with very different frequencies. Key figures can be computed with batch macros daily or weekly, whereas a release of the demand plan to production planning or R/3 is usually performed at larger intervals, for example once a month or once a year. How often you monitor the jobs and delete the DP job logs depends on how often you run these functions. For dependencies and concurrent execution of jobs, see Operational Management – Parallel and Concurrent Execution of Jobs. For the handling of alerts generated by a forecast run or a batch macro, see also Exception based Monitoring of APO Demand Planning.

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


APO report /SAPAPO/TS_BATCH_RUN

This report performs specified DP mass processing activities






DP Job Log /SAPAPO/MC8K

After each run of /SAPAPO/TS_BATCH_RUN

Red or yellow traffic lights shown

According to the warning or error reported (see message long text).

Application support


APO report /SAPAPO/TS_BATCH_LOGFILE

This report deletes old DP job logs








© 2004 SAP AG

22

Business Process Step 9: Create Demand Plan (APO) The historic data is used from the InfoCube for forecasting. In this process step, you create or modify demand forecast applying the most suitable forecast model such as Univariate Forecasting, Multiple Linear Regression (MLR) and/or Composite Forecasting. Typically, you do a planning run for multiple products in the background with mass processing, and then adjust the figures interactively. See Business Process Step 11: Perform Interactive Planning (APO). The planner interactively defines various master forecast profiles to forecast typical historical time series showing the constant, trend, or seasonal patterns. If different key figures are to be forecast, you must have master profiles for each key figure to be forecast. You can assign a master forecast profile with a univariate forecast profile and/or an MLR profile and/or a composite profile. The forecast results depend greatly on which forecast model you use and how you set it up. For a detailed overview on the strategies delivered by SAP, see the SAP Documentation, chapter Forecast Strategies. You can store multiple demand planning scenarios to evaluate different forecast models and settings in Demand Planning before deciding what data to use onward. A demand plan is stored in a planning version within a planning area. It is a good idea to have (one or more) additional key figures containing different forecast scenarios based on the same primary (historical) data rather than creating a separate planning version for each scenario: This reduces the space required in liveCache because the primary data is stored only once instead of n times for every version. Moreover, the different scenarios can be compared easily in a single planning book. If your business process allows it, you can run your forecast at an aggregated level, which is selected in transaction /SAPAPO/MC8E when defining your background job. The fewer characteristics you select, the coarser and faster your forecast run will be. The forecast at the more detailed levels will result from disaggregation according to the calculation type for this key figure (see transaction /SAPAPO/MSDP_ADMIN). It may be even an advantage and not just a loss of information if you consider the trends and seasonal variation of your historical data not on all the characteristic combinations but only on a selected subset. Statistical variation at a very detailed level can conceal correlations, trends, and so on that are apparent at a more aggregated, coarser level. If you use MLR, see the SAP Documentation, chapter Measures of Fit. It is recommended that uncorrelated parameters be removed from the profile once they are measured to be non-correlated, since the runtime of the MLR depends on the number of variables used. See also the SAP Documentation, chapters Forecast Strategies and Automatic model selection. There are six forecast errors you can select when defining a univariate forecast profile in transaction /SAPAPO/MC96B, for example MAD (Mean Absolute Deviation) or MSE (Mean Square Error). For performance reasons, it is advisable to configure as few errors as possible. See also SAP Notes 388216 and 372939.

Monitoring Activities Apart 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 Running Demand Planning in Background in order to safeguard this business step.

Business Process Step 10: Determine Forecast Accuracy (APO) APO offers the following ways to monitor forecast accuracy:

• Statistical error analysis • Univariate forecast error measurements • Multiple linear regression model measures of fit • Planned/actual comparison • Viewing purpose-designed KPI’s with a BW frontend (Business Explorer, BEX)


© 2004 SAP AG

23

Executing this business process step, you will most probably run one or several macros in background mode in order to calculate the forecast errors and evaluate the results in transaction /SAPAPO/SDP94 (see Business Process Step 11: Perform Interactive Planning (APO)) or the APO Alert Monitor. SAP BW reporting tools such as the Business Explorer are also widely used.

Once you have gained some experience with production data, it is advisable to restrict the number of forecast accuracy checks. This prevents you from carrying out activities such as calculating huge numbers of errors or goodness of fit data for large numbers of different models that do not fit the data.

Monitoring Activities Apart 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 Running Demand Planning in Background and Exception based Monitoring of APO Demand Planning in order to safeguard this business step.

Business Process Step 11: Perform Interactive Planning (APO) Within transaction /SAPAPO/SDP94, you can carry out almost every option that SAP APO Demand Planning offers. In particular, you can evaluate planning results, compare different scenarios, enter management overwrites, correct key figures manually, run macros, aggregate and disaggregate data, maintain proportional factors manually, fix values and therewith prevent them from changes by macros or batch jobs, create promotions, run forecasts, and create or view alerts. Demand Planning supports online simulation in multiple planning scenarios, consistent planning throughout your enterprise (top down, middle out, or bottom up), drilling up and down, aggregation and disaggregation, and slice-and-dice techniques. Top-down planning is at a high level, such as for a whole region. Middle-out planning is at a medium level, such as for each division within the region. Bottom-up planning is at a detailed level, such as for each of the products in each division within the region. For performance reasons, any interactive processing of data should be restricted to very small data volumes by specifying the selection criteria as far as possible. This is independent of when this planning step takes place, for instance before or after a planning run. Tasks that can easily be automated, for example because they always take place at a certain point in time and consist of a fixed sequence of calculations as it applies to macros in most cases, should be performed as background jobs rather than interactively. In some cases, it is a good idea to define fixed aggregates, according to SAP Note 503363, item 5. In these cases, choose one or two aggregates that will significantly decrease the data volume used by your interactive planning and background jobs. Be aware that the consequences of creating an aggregate are that it will help the performance of reading data from the liveCache, but generally hurts performance of writing data to the liveCache. You can use transaction /SAPAPO/MC62 to determine which sets of characteristics reduce the number of characteristic combinations significantly. See also SAP Note 413526 on the usage of navigation attributes. Some hints on the design and usage of planning books and macros for interactive planning (see also SAP Note 398726):

• Create a separate planning book for each user that contains only the views, macros, key figures, and any other views that are used by that individual user. Users who perform more than one task type should also consider creating more than one planning book to accommodate each task type.

• The planning book used for SDP interactive planning should contain only the functionality that an individual user actively uses while performing a specific task. For example, a user who performs promotion adjustments should have a planning book specific to this task, which has the functionality for promotions, any forecasts used, interactive planning, and nothing else.

• Minimize the number of default macros used for SDP interactive planning; see if any of these can be executed less frequently as start, end, or drill-down macros. Each online user should verify that the macros in her/his planning book are all used regularly as part of the standard business practice and remove any which are not.


© 2004 SAP AG

24

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

• Each online user should create several selection variants to restrict the number of characteristic combinations considered to that which s/he needs for a specific task. For example, a planner who looks at corrected forecasts for location ABC all day on Monday can create 4 selection variants, each containing different products, for which the forecast is to be corrected.

Monitoring Activities Apart 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 following table in order to safeguard this business step. 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 supported by an e-mail interface for notifying the responsible persons in case of new alerts. Therefore, planners and / or IT staff do not need to call the monitor transaction frequently just to confirm that nothing important has happened since the last refresh. However, the overall situation shown in the Alert Monitor should be supervised daily or adapted to the frequency of the demand planning process in your company.

Jobs for Monitoring “Perform Interactive Planning (APO)” To ensure a timely and efficient notification regarding exceptions in Demand Planning, schedule the following jobs to run on a regular basis:

• Send Alert Monitor mails with report /SAPAPO/AMON_MAIL_BROADCAST. Depending on user profiles, mails are sent with an overview of existing alerts. The responsible persons then should call the APO Alert Monitor, investigate the reasons for the alerts and take corrective actions 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 is of particular importance if you use alerts stored in the database. On database alerts and dynamic alerts in Demand Planning, see APO Alert Monitor, below.

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


APO Alert Monitor

/SAPAPO/AMON1

At least daily

Check for forecast alerts and SDP alerts and correct the planning for the reported object appropriately.

Application Support


APO report /SAPAPO/AMON_MAIL_BROADCAST

This report ensures sending of mails about existing alerts

SM37 Daily Status Check if job is running as scheduled.

If the report is not scheduled on a regular basis, schedule it to run every hour to at least daily, depending on your requirements.



Alert Monitor mails

SO01 (or respective e-mail system)

Depending on your requirements, at least daily

Check if the mail lists alerts that are important for you. Go to APO Alert Monitor and process the alerts appropriately.

Application Support



© 2004 SAP AG

25

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


APO report /SAPAPO/AMON_REORG

This report deletes Alert Monitor alerts


If the job is not scheduled on a regular basis, schedule it to run once a day.




Business Process Step 12: Plan Promotions and Product Life Cycle (APO) Promotion Planning – With promotion planning, you can extract past actions (such as special offers) from the actuals so that they are not included in the forecast. Promotions can have a major impact on consumer behavior. In APO Demand Planning, you can plan promotions or other special events separately from the rest of your forecast. Use Promotion Planning to record either one-time events, such as the millennium, or repeated events such as quarterly advertising campaigns. Other examples of promotions are trade fairs, coupons, freestanding inserts, competitors' activities, market intelligence, upward/downward economic trends, hurricanes, and tornadoes. Promotional uplifts can be defined in units or percentages by promotion patterns. A promotion pattern that occurred in the past can be automatically detected using historical sales or estimated by the planner. A promotion pattern can be archived in a promotion catalog; it can therefore be reused if a promotion of the same type is repeated. A copy function in the promotion catalog also supports "like" modeling of similar products, regions, and so on. Several techniques are available for estimating the impact of a historical promotion such as multiple linear regressions with or without a trend or seasonality. See also SAP Note 540282. Lifecycle Planning – A product's lifecycle consists of different phases: launch, growth, maturity, and discontinuation. In this business process step, you model the launch, growth and discontinuation phases. For any characteristic values combination, you can use either a phase-in profile, or a phase-out profile, or a "like" profile, or any combination of these. A phase-in profile, as well as a phase-out profile, changes the demand history or demand forecast of a product by given percentages during a specified period or periods. See also SAP Note 354660 for releases SAP APO 3.0 and 3.1, for releases mySAP SCM 4.0 and 4.1 see note 642593. These planning tasks are usually executed interactively using transaction /SAPAPO/MP34, which can also be called from the Supply and Demand Planner /SAPAPO/SDP94 using the promotion button. Promotion evaluations can be started via transaction /SAPAPO/MP39 (see SAP Notes 384550 and 484334). With this transaction, you can also see the attributes of the selected promotions, whereas the BW Business Explorer shows you key figures only.


Jobs for Running and Monitoring "Plan Promotions and Product Life Cycle (APO)" To keep the promotion key figure(s) in liveCache consistent with the promotion data, schedule the following job to run on a regular basis:

• Reconcile Inconsistencies between the Promotion Key Figure and Activated Promotions with report /SAPAPO/PROMOTION_UPDATE_30. With this report, you can activate, initialize, and deactivate promotions, and you can write activated promotions into the planning area again. Here, the available data in the promotion key figure will not be checked. By setting indicator Update for Consistency, data will be initialized (deleted) in the promotion key figure first and the data of the promotions are written in the key figure again. This report can also be called interactively with transaction code /SAPAPO/MP38. For details, see SAP Notes 367031, 350381, 366650, and 454644. Note that this report locks the entire planning version, so it can only run if no other – background or interactive – action is implemented concurrently on the same planning area and version.


© 2004 SAP AG

26

As of release mySAP SCM 4.1 there are the new transactions /SAPAPO/MP46 (Activate and Deactivate Promotions) and /SAPAPO/MP47 (Update for Promotion Consistency) available which provide the functionality for mass operations on promotions. The group of new transactions in this area can be centrally accessed by running transaction /SAPAPO/MP42 (Promotion Management). Here you can reset the promotion key figures, deactivate and respectively activate all promotions again. Use /SAPAPO/MP47 for the update of the promotion key figures in liveCache. If you want to run one of these transactions as scheduled background job, you can run report /SAPAPO/PROMOTION_ACTIVATION which provides the functionality of transaction /SAPAPO/MP46, or report /SAPAPO/PROMOTION_UPDATE which provides the functionality of transaction /SAPAPO/MP47.

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


APO report /SAPAPO/PROMOTION_UPDATE_30.

This report reconciles inconsistencies between promotions and planning areas.






Output of APO report /SAPAPO/PROMOTION_UPDATE_30.

SP01 After each run


Look for warning and error messages like “Error saving the promotion data” or “No promotion level is assigned”.

Application Support



Business Process Step 13: Copy liveCache Data to InfoCube (APO) In SAP APO 3.0A with liveCache 7.2.x, results from Demand Planning (key figure values) are not automatically logged: that is, they are not written from liveCache memory to disc space synchronously with the change of data. However, you do not need to save the results of your Demand Planning activities to a database (such as an InfoCube in APO or a separate SAP BW system) in order to prevent data loss in case of a liveCache crash. For this purpose, we recommend that you schedule a checkpoint (report /SAPAPO/OM_CHECKPOINT_WRITE) to run every four to six hours. As there is no logging of DP data with liveCache 7.2.x, it cannot be avoided that data between the last checkpoint and the time of a crash is lost. Therefore it is advisable to run the checkpoints depending on the schedule of the planning runs and have one checkpoint before and one after a long planning run. As it is strongly recommended that these checkpoints be run, there is no advantage in additionally saving DP data to an InfoCube, unless you wish to report on this data using the Business Explorer. This also applies to liveCache 7.4.x and onward, where backups and automatic logging ensure data integrity independently of checkpoints. For more information on checkpoints, see the Best Practice document Monitoring and Administration for SCM / APO. Most important, copying data this way can never replace or enhance a thorough backup and recovery concept for your SAP APO solution. Copying all data in a planning area to an InfoCube using the methods described below is very memory and resource intensive and takes a long time. For this reason, we recommend that you run no other processes concurrently with this. Do not run such a process step more frequently than required for your business process purposes. There are two methods to export data from Planning Areas to InfoCubes:

• Directly in move mode (“Extract Data from a Planning Area”) • Indirectly in delta mode using ODS objects (“Update InfoCubes from Planning Areas”)


© 2004 SAP AG

27

For details, see the SAP Documentation and the Best Practice documents dealing with the data transfer to an SAP BW system. Extracting data directly has the disadvantage that the complete data set is copied to the InfoCube at each update, so the same data is written again and again. With the second method using ODS objects, it is easier to update InfoCubes, as this procedure only updates the new and changed data. But the delta mode is relatively slow. Depending on your absolute data volume and the relative amount of changes, decide for yourself which method to use. For performance improvement, see SAP Notes 482494, 384023, and 386735. For other information, see SAP Notes 373756, 391625, and 426806.


Business Process Step 14: Transfer DP to R/3 (APO) You can transfer the results of your Demand Planning activities (that is, your demand plan) to your SAP R/3 OLTP system for further planning steps, in particular for Material Requirements Planning (MRP). This transfer has to be performed as a mass-processing job in the background. The information is taken from the time series of the appropriate Final Forecast key figure and transferred to R/3 via the APO Core Interface (CIF). In R/3 Demand Management, planned independent requirements are created in the same buckets as those of the data view on which the transfer job is based. The CIF queue entries are written by the transfer job and processed according to the CIF settings.

The transfer job uses report /SAPAPO/TS_BATCH_RUN with a planning activity using an appropriate transfer profile. You can make these activity and profile settings in APO customizing and define the background jobs needed in the transactions /SAPAPO/MC8x. For details, see Run Demand Planning in the Background and SAP Note 546079. As the CIF is an essential component of SAP APO and its business processes, it’s monitoring and administration is of critical importance for the performance and reliability of any business process that exchanges data between APO and the R/3 Systems connected to it. Therefore, it is extremely important that you follow the business process management procedure described in the Best Practice document dedicated to CIF.

Monitoring Activities Apart 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 Running Demand Planning in Background as well as those listed in the Best Practice document mentioned above concerning CIF in order to safeguard this business step.

Business Process Step 15: Perform Material Requirements Planning MRP (R/3) The planned independent requirements created in R/3 by business process step 14 can be used to determine the quantities and requirement dates of raw materials and components needed for the manufacturing of the products planned in APO Demand Planning. The monitoring procedure for this business process step is described in the Best Practice document Manage Production Planning in SCM / APO.

Monitoring Activities Apart 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 Best


© 2004 SAP AG

28

Practice document mentioned above concerning Production Planning in order to safeguard this business step.

Business Process Step 16: Release DP to SNP (APO) This business process step makes the demand plan available to the supply chain planner if the supply chain planner performs SNP using liveCache orders. The supply chain planner can then use the demand plan as a basis for making sourcing, deployment, and transportation decisions. The simulation process in Demand Planning can be done in conjunction with the simulation of planning scenarios to drive Sales and Operations Planning. For example, you may release two demand planning scenarios to SNP for simulation purposes: one based on the assumption of a sales increase of 5% in the next six months, and one based on a sales increase of 10% in this timeframe. From a technical point of view, you are copying data from liveCache time series objects to a forecast ATP category (for instance “FA” = independent requirements) in the liveCache orders. This release function can be performed online with transaction /SAPAPO/MC90 or report /SAPAPO/RTSOUTPUT_FCST (only for a small amount of data, see SAP Notes 403050 and 546079) or in the background by report /SAPAPO/TS_BATCH_RUN with a planning activity using an appropriate release profile. These activity and profile settings are made in APO customizing and the background jobs needed are defined in the transactions /SAPAPO/MC8x. For details, see Run Demand Planning in the Background. Parallel processing of this function is possible: see also Operational Management – Parallel and Concurrent Execution of Jobs. There is a flag “Create new orders” in the release profile, which is called “Add data” in report /SAPAPO/RTSOUTPUT_FCST. If you set this indicator, new order quantities are created in SNP when you release the demand plan to SNP. The system ignores existing orders in the same SNP version for the same product, location, and periods, so if you release to SNP twenty times, twenty separate orders are created in SNP. If you do not set this indicator, existing order quantities in the same SNP version for the same product, location and periods are overwritten. Set this indicator only under exceptional circumstances. Remarks: In contrast to DP, where data is stored either in time series or an InfoCube, in interactive SNP and in Distribution Resource Planning (DRP) data is stored in liveCache orders. However, if you are using interactive Sales and Operations Planning (SOP), for example to execute Supply & Demand Propagation, the data you wish to use must be stored in liveCache time series as in DP. This also applies for the usage of other SNP functionality; for details, see the SAP Documentation, chapter Data Storage in SNP and DP. In SOP, you release the results back to SNP with transaction /SAPAPO/MC90 as well, but with button Release: Extended; or in background with report /SAPAPO/RTSOUTPUT “Data Transfer Time Series to Order Network”. You may also have mixed planning areas with some order key figures and some time series key figures. To copy selected time series key figures from your DP planning area to your SNP planning area, use report /SAPAPO/RTSCOPY, This is described in Business Process Step 6: Load Data into Planning Area (APO).

Monitoring Activities Apart 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 Running Demand Planning in Background in order to safeguard this business step.

Business Process Step 17: Compute Constrained Plan (APO) Supply Network Planning with liveCache order objects and / or time series is used to gain a rough-cut plan taking limited resources into consideration, such as production or distribution capacities. The supply chain planner can use this to plan resources based on a full and reliable picture of demand. The demand planner can use it to monitor where adjustments to the demand plan were required due to production capacities, distribution limitations and other constraints.

As the computation of an SNP plan can comprise almost the full functionality of the APO SNP module such as the use of background planning runs, interactive planning, macros, optimizers, heuristics, and


© 2004 SAP AG

29

others, no details of this business process step are discussed in this Best Practice document. They are planned for a future document dedicated to SNP. For an overview of available documents, see the Best Practice documents in SAP Service Marketplace.

Business Process Step 18: Release SNP Plan to DP (APO) In Supply Network Planning, releasing the plan entails the following concepts:

• Releasing the SNP-confirmed forecast (that is, the results from an optimization run) to DP using transaction /SAPAPO/SNPFCST (report /SAPAPO/RELEASE_SNP_FORECAST).

• Releasing the SNP plan to DP to compare the constrained plan with the unconstrained plan, or to use the data from SNP in Sales & Operations Planning using transaction /SAPAPO/LCOUT (report /SAPAPO/RTSINPUT, data transfer Order Network to Time Series)

The only relevant case for the business process in this document is the second one: In this “traditional” release of the supply network plan, you release the final supply network plan back to the demand planner to compare the unconstrained demand plan to the constrained supply network plan. Major discrepancies between these two plans could trigger re-forecasting, and ultimately, re-planning. For example, you may determine that the capacity situation demands a change in the promotion strategy. Technically, you must transfer the data from the relevant order categories to the appropriate time series key figures.


Jobs for Running and Monitoring "Release SNP-Plan to DP (APO)" To ensure the availability of SNP data for the DP process, schedule the following job to run on a regular basis:

• Release Order Objects to Time Series with report /SAPAPO/RTSINPUT. To obtain a result log, mark the appropriate check box in the selection screen of the report. Caution: As all characteristic value combinations being updated are listed, this list can become very large.

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


APO report /SAPAPO/RTSINPUT

This report releases SNP orders to DP key figures






Output of APO report /SAPAPO/RTSINPUT

SP01 After each run

Message type (icon)

Look for stop icons (cancelation), and red (errors) or yellow (warnings) lights. Read message long text if present.

Application Support




© 2004 SAP AG

30

Related Tools and Activities

APO Alert Monitor The APO Alert Monitor allows a management-by-exception strategy, so it is of special concern in this and other APO business process scenarios. The Alert Monitor is a standalone component of APO that enables you to have a unified approach to handling problem situations. It notifies you if a problem occurs during an ATP check or SNP run, or when production plans, demand plans, or vehicle schedules 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 results can be used to readjust the plan whenever necessary. The purpose of the Alert Monitor is to inform planners if a condition of a plan has been violated. The Alert Monitor belongs to the suite of supply chain monitoring components in APO, together with the Supply Chain Cockpit and the Plan Monitor. It can be used by any supply chain manager or planner who practices exception-based management in the following areas:

• Demand Planning (DP) • Supply Network Planning (SNP) • Production Planning/Detailed Scheduling (PP/DS) • Available-to-Promise (ATP) • TLB/Deployment • Vehicle Scheduling (VS)

The Alert Monitor can be called as a standalone application via transaction code /SAPAPO/AMON1 as well as from various planning applications like /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 the selected planning book. The goal of Demand Planning is to create accurate forecasts and demand plans, and the role of the Alert Monitor is to notify you of exceptions that occur during the process. An exception is any situation that needs further adjustment. A sudden switch in trends, a new fad, or an unexpected change in the circumstances of a supply chain partner could all lead to exception situations. Most exceptions, if not handled immediately, 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 they turn into problems and thus help you forecast your business needs more effectively. Not only can you determine which types of exceptions you want to be notified of, you can also prioritize alerts, thus preventing an information overload. In exception-based management, you as the planner must make the ultimate decision regarding the priority of an alert. If you regularly compare your forecast figures with your actual figures, you will soon be able to determine whether a 15% deviation is serious or not. This knowledge would enable you to set priority variants for alerts so that you get a warning if the deviation is 10% but an error alert if it is 15%. Alert priorities are identified by icons displayed in the profile or in the monitoring slots of the Supply Chain Cockpit control panel. The three possible priority levels in the Alert Monitor are:

1. Error 2. Warning 3. 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, even an information alert should reflect an exception to the planning situation and not a “success” message saying “everything ok”. Whereas in the DP application you can view only one planning book at a time, you can view several in the Alert Monitor, making it the ideal tool for tracking the quality of your alerts over a specific period 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


© 2004 SAP AG

31

For Demand Planning, forecast alerts and Supply and Demand Planning (SDP) alerts are important. Alert types of both these areas can be used in the DP and SNP applications. The Alert Monitor comes equipped with two forecast alert types that correspond to the exception situations that can arise in forecasting and demand planning, namely Univariate forecasting alerts (based on the six forecast errors like Mean Absolute Deviation and Mean Square Error) and Multiple Linear Regression alerts (based on the five MLR measures of fit). You need to maintain alert profiles to maintain a user-specific selection of alerts for your area of responsibility. 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 sourcing decisions relevant for purchasing, manufacturing, and distribution. There are two different types of SDP alerts:

• Dynamic alerts mirror the current planning situation but are not saved in the database. As opposed to SNP alerts in APO Release 2.0, alerts are now macro-dependent and thus can reflect the actual data in liveCache. Because large numbers slow down performance, this alert type is not suitable for dealing with a large volume of planning objects. For small data volumes up to approximately 1000 alerts, dynamic alert generation is usually faster than reading alerts from the database. For large data volumes, database alerts are usually faster.

• Database alerts show the planning situation as it was during the planning run, or last executed macro. When dealing with large volumes, it is best to perform a background planning run using the appropriate database macro. The results of the planning run show the situation as it was at the time of the run, so with database alerts you see a snapshot of the plan during run time.

You also have the option of creating customer-specific dynamic or database alert types to be used with SDP macros. Database alerts that are no longer in use (for example, because they have been acknowledged or because they are outdated) must be deleted from the database. Among forecast and SDP database alerts, this applies to ATP, VS and TLB/Deployment alerts. However, PP/DS alerts are dynamic only and are not stored in the database. 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.

To support the Alert Monitor's function as a tool for exception-based management, you can send messages via e-mail to other planners to inform them of the alert situation. You can also have messages 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 easily between various profiles. For example, you may have an alert profile for your own area of responsibility, 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 the really important ones. You can find more information concerning this tool in the SAP Documentation under "Supply Chain Monitoring – Alert Monitor". See also SAP Notes 375965, 495166, 500063, and 521639, and Exception based Monitoring of APO Demand Planning.

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


© 2004 SAP AG

32

Monitoring Activities Apart from safeguarding the general availability and consistency of the system components SAP APO, SAP BW, and SAP R/3 OLTP, to safeguard any business step that is based on SAP BW techniques SAP recommends that you monitor the objects listed in the following table. See also the Best Practice documents dealing with the data transfer to an SAP BW system. The data transfer process from a source system to SAP BW InfoCube(s) as well as certain actions in RSA1 and RSMO write detail information to a central R/3 basis component called Application Log. It can be browsed using transaction SLG1. The log entries are subdivided into objects and sub-objects and classified by importance. In case of errors or problems, the Application Log can be used to get more detailed information about what happened and how to resolve the problem. The monitor transaction for the Application Log is SLG1, where you should specify the (sub-) objects and the time interval you want to be displayed. Relevant objects for the SAP Business Information 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 SAP Business Warehouse To ensure a timely and consistent data transfer from any data source into a SAP Business Information Warehouse structure, schedule the following job on a regular basis:

• Data Extraction and Load with report RSBATCH1. Define the job using the scheduler 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 the selected Info Package. With the help of Info Package groups you can collate data requests that logically belong together and schedule them using the scheduler.

In Monitoring of the Administrator Workbench (select Monitoring in transaction RSA1 or call transaction RSMO) you have the option of overseeing and controlling the data loading process into the InfoCubes. To analyze any rrors that may have occurred, choose Monitor >> Assistant. You can also call the monitor from a selected Info Package or via transaction code RSMO. To make sure that you have selected the correct time window and data to be displayed, call the selection screen: choose Monitor >> New Selections.

Jobs for the Maintenance of the Application Log The Application Log entries are stored on tables with name prefix BAL*. As there are many applications that use this basis component and often many table entries are made, it is important to delete obsolete application logs from the database regularly to prevent these tables from overflowing or impacting the performance of the applications and the log retrieval. The deletion can be performed using transaction SLG2 or in background by the appropriate report:

• Delete Obsolete Application Logs with report SBAL_DELETE. A log can only be deleted when it has reached its expiry date or if it has the attribute "Deletion before expiry". For more information, see SAP Note 195157.

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


APO job BI_BTCH*

These jobs perform the data transfer from the different data sources to APO InfoCubes

RSMO or SM37

Depending on your process






© 2004 SAP AG

33

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


APO: Administration Workbench – Monitor

RSMO After every data load

Red or yellow traffic lights

After selecting one request, read the error message and diagnosis under tab strip Status and the processing log under Detail.

Use the Monitor Assistant to analyze and correct the error situation.



APO: Evaluate Application Log for BW related objects

SLG1 At least daily

Log class Check if there are very important logs (flagged red) or important logs (flagged yellow).

Read message long text and / or details, if present. Analyze error situation, evaluate error severity and impact, and take corrective action.



APO report SBAL_DELETE

This report deletes obsolete Application Logs


If the job is not scheduled as provided by Application Support, schedule it to run weekly.



Error Handling, Restartability and Escalation Error Handling Procedures Error 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" you may need to take action. Consider the status of the job and proceed as follows:

• In case of status scheduled, the job steps have already been defined, but the start condition has not yet been defined. Contact the program scheduling management and clarify when the job will be fully defined.

• In case of status released, the job has been fully defined with a start condition and will wait for that condition to be fulfilled.

• In case of status ready, the start condition of a released job has been fulfilled. A job scheduler has put the job in a queue to wait for an available background work process.

• In case of status active, the job is currently running and can no longer be modified or deleted. Check if the job is within the given timeframe. Check for particular dependencies to other jobs. If the job exceeded the given timeframe, contact the software monitoring team.

• In case of status finished, all steps that make up this job have completed successfully. Program scheduling management must check whether the job ran in the given timeframe, and software monitoring team and / or application support must check the respective job results (such as spool output lists, message logs, and updates).

• In case of status canceled, the job has terminated abnormally. This can happen in two ways. If an administrator intentionally canceled the job, clarify why he or she did so and whether (and if so, when) the job must be re-run. Alternatively, if a program in a job step produced an error such as issuing an "E" or "A" error message, contact the software monitoring team and investigate why the error occurred. If the program is an SAP standard program, search for appropriate SAP Notes in the SAPNet R/3 Frontend or on the SAP Notes Home Page. If you cannot solve the problem, create a support notification.


© 2004 SAP AG

34

• If there are problems with the Core Interface 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/3 Plug-In homepage).

Process Step Restartability If a background job is canceled and you are deciding whether to restart it, consider possible following jobs or dependencies on other jobs. Restarting the job may also delay the start of following jobs.

Escalation Procedures • In general, we recommend that you search for SAP Notes related to any unknown problems or

errors through SAPNet R/3 Frontend or SAP Notes Home Page. • 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 support notification in SAPNet R/3 Frontend.

Maintenance of DP Data Storage Structures When adapting this concept for your company, you must specify the times, responsible teams, and escalation paths (responsible teams) for the following monitoring activities and objects.

Monitoring Activities The data for your DP process is stored in different logical and physical structures such as InfoCubes, the Master Planning Object Structure, and liveCache time series. All these need monitoring and maintenance to keep them in a technically optimal condition and allow fast retrieval of the data stored in them.

Jobs Necessary to Keep the APO Data Structures in Good Condition (APO) To ensure that database statistics and indexes for BW-specific data structures are kept up to date, and that liveCache data structures (time series) are kept consistent, schedule the following jobs to run on a regular basis:

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

• Check Inconsistencies in Time Series Network with report /SAPAPO/TS_LCM_CONS_CHECK_ALL. This report checks all existing time series (in all planning areas and versions) and reports whether or not there are inconsistencies. If errors are found, you can repair inconsistencies in a specified planning area and version using report /SAPAPO/TS_LCM_CONS_CHECK afterwards. Mark the Log check box if you want to see a list of characteristic combinations that have inconsistencies. For more information, see 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 is supplied with SAP Note 542946, SP 22 (for APO 3.0), and SP 10 (for APO 3.1) – see SAP Note 425825. The report determines all liveCache time 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 refer to the application data so they are not inconsistent, but they are unnecessary and consume liveCache memory. It may be sufficient to run the report approximately once a month. If you have selected the 'Repair' option, any such unnecessary objects are deleted. Caution: When you run report /SAPAPO/TS_LCM_REORG, no other processes for a


© 2004 SAP AG

35

planning area with key figures based on liveCache time series should be allowed to run with the same planning version. Otherwise, liveCache objects that are still required by the other parallel process may be recognized as unnecessary and even deleted. For this reason, we recommend that you always run the report with the option 'Lock planning version'. In this case, all planning areas that use the planning version 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 who have already set a change lock for the planning version.

• Maintain Statistics and Indexes for Planning Object Structures with report /SAPAPO/TS_PSTRU_TOOL. Run this report in separate background jobs choosing options Calculate Statistics and Check Indexes for every Master Planning Object Structure and review the list of messages being displayed. If problems are reported by the index check, run it with option Repair Indexes. A separate background job (job name with prefix BI_STAT) is started to execute this request. These administrative jobs must be run after every load of data to a planning object structure. For further details, see SAP Notes 393655, 492460, and 503363.

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


APO report SAP_ANALYZE_ALL_INFOCUBES

This report creates DB statistics for all InfoCubes.

Only for systems running with Oracle, SAP DB or IBM DB2/UDB (DB6) database


If the job is not scheduled on a regular basis, schedule it to run once a week with parameter percent = 100.


Contact Software Monitoring Team

Indexes of APO InfoCubes

RSA1 or RSRV

Weekly Red or yellow traffic light

Select Check (Aggregate) Indexes. If the traffic light gets yellow or red, select Repair Indexes (now) or Delete Index (batch) and Create Index (batch).



APO report /SAPAPO/TS_LCM_CONS_CHECK_ALL

This report detects inconsistencies in time series


If the job is not scheduled on a regular basis, schedule it to run once a week.



Output of APO report /SAPAPO/TS_LCM_CONS_CHECK_ALL

SP01 After each run

Red traffic light

Check for time series with inconsistencies reported.

Repair inconsistencies by running report /SAPAPO/TS_LCM_CONS_CHECK for the corrupt time series setting the repair option.




© 2004 SAP AG

36

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


APO report /SAPAPO/TS_LCM_CONS_CHECK

This report can repair inconsistencies in time series

SM37 After each run

Status Check if job has finished without errors.



Output of APO report /SAPAPO/TS_LCM_CONS_CHECK

SP01 After each run

Traffic light Check whether the inconsistencies in the selected time series have been repaired.



APO report /SAPAPO/TS_LCM_REORG with option Repair.

This report deletes superfluous time series and time bucket profiles.

SM37 Monthly Status Check if job is running as scheduled.

If the job is not scheduled on a regular basis, schedule it to run once a month.



Output of APO report /SAPAPO/TS_LCM_REORG.

SP01 After each run

Traffic light Check whether superfluous data is reported and has been deleted without errors.



APO report /SAPAPO/TS_PSTRU_TOOL with option Calculate Statistics

This report checks and generates statistics for a POS






APO report /SAPAPO/TS_PSTRU_TOOL with option Check Indexes

This report checks the indices of a POS






Output of APO report /SAPAPO/TS_PSTRU_TOOL


Message type (icon)

Look for stop icons (cancelation), and red (errors) or yellow (warnings) lights. Read message long text if present.




© 2004 SAP AG

37

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


Job BI_STAT* started by /SAPAPO/TS_PSTRU_TOOL with option Repair Indexes





Running Demand Planning in Background This section outlines the monitoring concept for DP activities in background for processing mass data. Mass processing allows you to create demand forecasts or run macros for large numbers of products while optimizing system resources. Also a release of DP data to SNP or a transfer to R/3 is usually performed in background. The different tasks that can be performed in this way need to be customized and set up as “activities” prior to job definition.

Monitoring Activities Apart from safeguarding the general availability and consistency of the system components SAP APO, SAP BW, and SAP R/3 OLTP, to safeguard any business process step that performs DP activities in background SAP recommends that you monitor the objects listed in the following table.

Jobs for Running and Monitoring "Demand Planning in Background" (APO) To ensure correct 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. This mass processing job is created with its necessary settings and scheduled using transactions /SAPAPO/MC8x. To create a job, call /SAPAPO/MC8D. To change a job, call /SAPAPO/MC8E. To define in advance the activities that are needed for these jobs, call /SAPAPO/MC8T (you can do this from the customizing tree). An activity can be a forecast computation, execution of one or several macros, a release of DP data to SNP orders, or the transfer to R/3. To check the job definition prior to execution and find errors like “no macro defined”, “data view does not exist” or “release profile not found”, call /SAPAPO/MC8I. To schedule the job, call /SAPAPO/MC8G. To see a job overview, display job logs, and jump to spool lists, call standard transaction SM37. 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 /SAPAPO/MC8K. The job log shows whether the job completed successfully (green traffic light), with warnings (yellow light), or with errors (red light), together with a message for every characteristic value combination that was processed in the job, forecast error messages if the job included a forecast, and other details. You can also delete job logs with this transaction. To copy jobs, call /SAPAPO/MC8J. To delete jobs, you can call /SAPAPO/MC8F. Parallel processing: Given the large amount of data to be processed and the limited time available, you may need to process background runs (of macros or what else) in parallel. You can do this 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 approximately equal size and no individual characteristic combination should belong to more than one selection ID, as this can cause lock issues and anyway you do not need to process a combination more than once. These jobs can then be scheduled to run at the same time. Remember that hardware resources like the number of CPUs and their speed, the amount of main memory, and so on limit the total number of jobs that can run on a system at the same time. From release mySAP SCM 4.1 you can use parallel processing for running macros or any other planning activity like performing a statistical forecast. You can navigate from transaction /SAPAPO/MC8T directly to the maintenance of parallel processing profiles or use /SAPAPO/SDP_PAR for direct access. After defining block size and number of maximum parallel processes you have to assign the parallel processing profile to the selection variant. The next time you run this selection as background job it will automatically run with parallel processing.


© 2004 SAP AG

38

• Delete DP Job Logs with report /SAPAPO/TS_BATCH_LOGFILE. Old logs from planning activities must be deleted regularly to maintain high performance for the related transactions and prevent database tables from overflowing. Make sure that you delete the logs in packages. Select the option 'Delete all logs with minimum age' reducing the parameter days. See also SAP Note 512184.

Demand planning activities can be executed periodically with very different frequencies. For example, key figures can be computed with background macros daily or weekly, whereas a release of the demand plan to Production Planning or R/3 is usually performed at longer intervals, for example once a quarter or once a year. Accordingly, the frequency of monitoring the jobs and deleting the DP Job Logs depends on how often you run these functions. For dependencies and concurrent execution of jobs, see Operational Management – Parallel and Concurrent Execution of Jobs. See also Exception based Monitoring of APO Demand Planning for the handling of alerts generated by a forecast run or a batch macro.

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


APO report /SAPAPO/TS_BATCH_RUN

This report performs specified DP mass processing activities






DP Job Log /SAPAPO/MC8K

After each run of /SAPAPO/TS_BATCH_RUN

Red or yellow traffic lights shown

Accordingly to the warning or error reported (see message long text).

Application Support


APO report /SAPAPO/TS_BATCH_LOGFILE

This report deletes old DP Job Logs







Exception Based Monitoring of APO Demand Planning This section outlines the concept for monitoring the overall planning situation in APO Demand Planning. 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 supported by an e-mail interface that allows notifying the responsible persons in case of new alerts. So it is not necessary for planners and / or IT staff to call the monitor transaction frequently just to confirm that nothing important has happened since the last refresh. However, the overall situation shown in the Alert Monitor should be supervised daily or adapted to the frequency of the demand planning process in your company.

Monitoring Activities Apart 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 following table in order to safeguard your DP business process.


© 2004 SAP AG

39

Jobs for an Exception Based Monitoring of Demand Planning To ensure a timely and efficient notification about exceptions in DP, schedule the following jobs to run on a regular basis:

• Send Alert Monitor mails with report /SAPAPO/AMON_MAIL_BROADCAST. Depending on user profiles, mails are sent with an overview of existing alerts. The responsible persons then should call the APO Alert Monitor, investigate the reasons for any alerts and take corrective actions to keep the demand plan close to the needs of your company.

• Delete Alert Monitor alerts with report /SAPAPO/AMON_REORG. This report is of particular importance if you use alerts stored in the database. On database alerts and dynamic alerts in Demand Planning, see APO Alert Monitor.

Monitoring Object

Monitor TA/Tool

Monitor Freq.

Monitor Time

Indicator or Error


Respon-sibility


APO Alert Monitor

/SAPAPO/AMON1

At least daily

Alert list Check for forecast alerts and SDP alerts and correct the planning for the reported object appropriately.

Application Support


APO report /SAPAPO/AMON_MAIL_BROADCAST

This report ensures sending of mails about existing alerts

SM37 Daily Status Check if job is running as scheduled.

If the report is not scheduled on a regular basis, schedule it to run every hour to at least daily, depending on your requirements.



Alert Monitor mails

SO01 (or respective e-mail system)

Depending on your requirements, at least daily.

Check if the mail lists alerts that are important for you. Go to APO Alert Monitor and process the alerts appropriately.

Application support


APO report /SAPAPO/AMON_REORG

This report deletes Alert Monitor alerts.


If the job is not scheduled on a regular basis, schedule it to run once a day.




Further Information

Dependencies Remember that there are dependencies (date and time, logical sequence) to business processes and process steps not mentioned in this document. These usually comprise for example:

• General SAP 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 on o 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 logs


© 2004 SAP AG

40

o Updating table statistics for the DB cost based optimizer – You should not run this activity at times when application programs are likely to be creating, deleting, or updating many table entries.

• 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 must wait for the completion of the planning activity and all other users that require liveCache data must wait for the completion of the checkpoint. This restriction applies only for liveCache 7.2.x. We recommend that you write checkpoints before and after long running planning jobs, as a rule 4 to 6 times per day in total. This ensures, first, that no checkpoint has to wait for the planning run to finish and thus cause all other transactions to wait and second, that the results from the planning run are safely stored away in a consistent manner with the other data in liveCache.

o Checking the internal (liveCache – APO DB) and external (APO – R/3) data consistency o Backup for liveCache o 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 of transactional data, because this can overload CIF and cause an undesirable communication delay.

Because of these dependencies, online and background application system activity cannot always occur whenever desired, but may need to wait, for example, for the completion of administration activity. Especially in APO, long-running planning activities should not collide with APO checkpoint writing. In liveCache 7.2.x, this can cause long waits for online users.

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

Operational Management – Parallel and Concurrent Execution of Jobs The combination of InfoCube lock issues and system resource usage makes concurrent execution of some DP job types problematic. Recommendation: Observe the following rules for scheduling or executing DP transactions and jobs:

1) Calculate new statistics for all InfoCubes and Planning Object Structures defined on the system regularly (at least once a week) using report SAP_ANALYZE_ALL_INFOCUBES with 100% of the available data.

2) Do not run batch jobs in DP that lock the same data concurrently. Specifically, do not run two jobs in parallel if they use selection variants that contain overlapping characteristic combinations, or else one job must wait until the other has released the lock on the data, resulting in performance problem. For further explanation of how lock logic works, see SAP Note 397292 for APO 3.0A.

3) Mass processing background jobs performing forecasts, macros, release from DP to SNP, and transfer to R/3 may be run in parallel, or concurrently with one another, provided that they obey rule 2. Ideally, these jobs should be of approximately the same size, so that each job takes the same amount of time to run. This is most easily accomplished by designing selection variants with the same number of characteristic combinations.


© 2004 SAP AG

41

4) Loading data from an InfoCube into the liveCache may be executed in parallel by defining several different variants that obey rule 2 and running them at the same time. Ideally, these jobs should be of approximately the same size, so that each job takes the same amount of time to run. This is most easily accomplished by designing selection variants with the same number of characteristic combinations.

5) Two users should not run selection variants in DP interactive planning that lock the same datasets, or specifically that contain overlapping characteristic combinations, or else one job must wait until the other has released the lock on the data, impacting performance.

6) Execute initial data load jobs, calculation of proportional factors, copying planning versions or key figures, and all mass processing jobs at times of low system load; that is, during the night, due to their large data volume. Also run these as background jobs.

7) Plan parallel execution to avoid CPU bottlenecks on the application server. Optimal performance is achieved when one CPU is available for each process. How critical this is depends upon how much of the response time is CPU time. For optimal performance, only run as many jobs as there are CPUs in the system, and less if there are memory limitations. More jobs will run more slowly – depending upon the CPU resources needed by the job type. Some job types, such as forecasts, are heavily dependent upon the application CPU resources, while others, such as the release from DP to SNP, require less.

8) Plan parallel execution to avoid memory bottlenecks. To avoid this, perform a trial run of the process to be parallelized and collect the statistical records for the run with full details.

Find out how much total memory your system has and call this M_total. From the statistical records, find out how much memory was used by the individual process and call this M_proc. The maximum number of parallel processes that should run at once is: N = (M_total)/(M_proc)

9) Execute checkpoint writes on average 4 times a day.

10) When executing batch jobs that run longer than 6 hours, consider executing a checkpoint write before and after the batch job to ensure data consistency.

11) Do not perform initial data load concurrently with any of the following jobs: a) Copy key figures b) Calculate proportional factors c) Release from DP to SNP d) Any macro or forecast

12) Do not execute the release from DP to SNP concurrently with any of the following job types: a) Data import into DP, in the same Planning Area b) SNP heuristic planning run c) Daily liveCache reorganization d) Any DP transaction or mass processing job which locks (uses) the same data as the

release

13) Some extract jobs that read data from liveCache (such as copy data from liveCache to an InfoCube for backup) may require a different setting for the number of periods per block to avoid memory problems. If this is the case, execute the following sequence:

a) Execute job /SAPAPO/TS_PAREA_EXTR_SETTING for planning area of interest, and set the number of periods necessary for the data extract job.

b) Run the data extract job. c) Execute report /SAPAPO/TS_PAREA_EXTR_SETTING for the appropriate planning

area again, and reset the number of periods necessary for the data extract job to 0.

14) If background jobs that generate macros are run at high volume, delete old job logs regularly (once a week if possible) using transaction /SAPAPO/MC8K.

15) If alerts are generated as part of the business process, regularly delete alerts (once a week if possible) using transaction /SAPAPO/AMON1 or report /SAPAPO/AMON_REORG.


© 2004 SAP AG

42

Troubleshooting If 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 the Troubleshooting Guide Integration R/3 – APO, which you can find in the SAP Service Marketplace, in the Literature Center of the R/3 Plug-In homepage.

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

Literature For more detailed information about how to administer an SAP R/3 System, see:

• Liane Will, SAP R/3 System Administration, 2000

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 R/3 Performance Optimization, 2001

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

For more information about these and other books, visit http://service.sap.com/books.

Best Practice Documents In the SAP Service Marketplace, under alias solutionmanagerbp >> mySAP.com Solution >> mySAP Supply Chain Management (SCM), you can find several relevant Best Practices for Solution Management, including:

Monitoring and Administration for SCM / APO helps you analyzing the workload and performance on liveCache and the APO database.

Manage APO Core Interface in SCM deals with the Business Process Management of the APO CIF and is an essential enhancement to this document. All the jobs and monitoring activities listed in the CIF document have to be considered in every business process step listed above that sends or receives data through CIF.

Manage Production Planning in SCM / APO deals with Production Planning and Detailed Scheduling in APO and Production Execution in R/3, including the MRP run mentioned in Business Process Step 15: Perform Material Requirements Planning MRP (R/3).

Under alias solutionmanagerbp >> mySAP.com Solution >> mySAP Business Intelligence, you can find the Best Practice documents SAP BW Master Data Upload and SAP BW Data Target Upload. These can help you in setting up and monitoring the data transfer to an SAP BW system, which also underlies SAP APO.

Background Information and References SAP Documentation 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 the SAP Service Marketplace for SCM. Several functions that have been documented in the SAP Library for SAP APO 3.1 are also available in APO 3.0. For details, see SAP Note 514971.

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

• 370601: Collective note: Performance APO 30


© 2004 SAP AG

43

• 303743: Support Packages for APO Release 3.0A • 438712: Support Packages for APO Release 3.1 • 420669: Collective note: General Performance Improvement APO • 420594: Collective Note: Performance for DP 3.0A • 447708: Composite SAP note about APO system administration • 500843: Composite SAP note for COM and SAP liveCache >= 7.2

See the Best Practice document dedicated to CIF for SAP Notes with information on qRFC and CIF. The following SAP Notes contain information about the SAP Business Information Warehouse and the database underlying an SAP APO system:

• 124532: Performance when loading data into BW • 115407: Loading large amounts of data • 129252: Oracle DB Statistics for BW Tables • 130253: Notes on upload of transaction data into the BW • 130645: Collective note: Performance SAP BW • 130691: Collective note for BW - tips & tricks • 180605: Oracle database parameter settings for BW • 184905: Collective note Performance BW 2.0 • 323090: Performance problems due to degenerated indexes • 325839: Considerable increase of tablespace PSAPODSD • 378509: Oracle DB parameter setting for APO • 384023: Optimizing performance of ODS objects • 400191: Further processing of data from the PSA • 409641: Examples of packet size dependency on ROIDOCPRMS • 421795: SAP_ANALYZE_ALL_INFOCUBES report • 428212: Update of statistics of InfoCubes with BRCONNECT • 458077: For all entries: Performance problems in APO Demand Planning • 459188: Many small partitions in PSA tables under ORACLE • 485878: DB2/390: BW: Partitioning the PSA tables • 535986: MONITORING for BW fact tables under Oracle • 558563: How does a client copy work with Demand Planning?

The following SAP Notes contain information about the APO Demand Planning module: • 200347: Demand Planning: How does the lock logic work? (2.0A) • 301488: Demand Planning: Actions after 3.0A upgrade • 333243: Analysis of faulty definition and execution of macros • 350381: Promotion: Report for updating active promotions • 354660: Advice APO 3.0 / 3.1 life cycle planning • 358283: Repair tool for existing time series network • 359761: Demand Planning: loading performance data • 360935: Demand Planning 3.0: Realignment tool – consulting • 363092: Demand Planning: Performance Mass Processing • 363221: Consulting: Proportional factors / version copy • 366650: APO 3.0 promotion: update promotions w/ check of consistency • 367031: Update advise promotion: /SAPAPO/PROMOTION_UPDATE_30 • 372939: APO consulting: Compare forecast in interactive &…. • 373756: Data extraction from a planning area • 383906: DP 3.0: Data extraction - memory problems / COM errors • 384550: APO 3.0 promotion: Consulting: Reporting


© 2004 SAP AG

44

• 386735: DP: Extract data to an IC with delta update • 388216: Collective note consulting forecast • 388260: APO Consulting forecast: Automatic model selection • 391625: Backup and Recovery for APO 3.0A Demand Planning • 393655: DP 3.0: Administer performance • 397292: DP 3.0: How does the lock logic work? • 398726: DP 3.0: performance planning book/data view • 402046: DP 3.0: 'No liveCache anchor found' • 403050: Consulting DP 3.0: Release from DP to SNP • 412429: Definition of jobs with macros • 413526: Consultation: Navigation attributes versus basic characteristics • 420927: Data extraction of selected key figures • 425825: Consistency checks, /sapapo/om17, /sapapo/cif_deltareport • 426806: Memory/performance problems during data extraction • 428102: Performance: Loading planning area version • 454644: Consultancy: Lock logic in promotion planning • 482494: Loading data from liveCache: Performance optimization • 488020: Performance improvement of the detailed proportion calculation • 492399: Realignment tool – consulting • 492460: Check double entries in planning object structure • 495027: Changing delivered APO InfoObjects (9A*) • 503363: Use & management of fixed aggregates in Demand Planning • 505886: Performance improvement during drilldown • 506393: Conversion exits when creating characteristics combinations • 509479: Elimination of inconsistencies in time series objects • 510639: Assignment of aggregates of planning object structure • 512184: Background processing: Periodically delete job log • 514593: Performance improvement with DP background processing • 514971: SAP Library Documentation Release 3.0 and 3.1 for DP • 515120: Performance of extraction of InfoCube-based key figures • 515523: Unexpected numerical results in demand planning • 520876: Inconsistencies in time series objects • 529663: Performance during /SAPAPO/TS_LCM_CONS_CHECK • 539797: Collective consulting note on macros • 539848: Collective consulting note on background processing in DP • 540241: Collective consulting note on CBF • 540282: Collective consulting note on promotion planning • 540571: Collective consulting note on data extraction in DP • 540926: Collective consulting note on planning object structures • 541189: Collective consulting note on selections in Demand Planning • 541252: Collective consulting note for planning book maintenance • 541618: Collective consulting note on BW and InfoObjects in DP • 541633: Collective consulting note on interactive planning • 541703: Collective consulting note on technical subjects in DP • 542946: Error message time series/period pattern does not exist • 546079: FAQ: Background jobs in Demand Planning • 549184: FAQ: What is important for extraction


© 2004 SAP AG

45

• 558563: How does a client copy work with Demand Planning? • 558995: Advice on consistency report for forecast profiles • 566527: Composite SAP Note for DP performance in APO 3.1 • 568506: Collective consulting note on consumption of forecasts • 568671: Collective consulting note on versions • 568669: Collective consulting note on release DP – SNP • 570397: Consulting: Workaround - Copying Planning Object Structures • 571629: How does the note management work? • 573127: Creating several char. combinations: /SAPAPO/MC62 • 576015: Collective Consulting Note for Demand Planning

See also the following SAP Notes: • 016083: Standard jobs, reorganization jobs • 195157: Application log: Deletion of logs • 375965: APO Consulting: Alerts in forecast • 425825: Consistency checks, /sapapo/om17, /sapapo/cif_deltareport • 495166: Tips and Tricks for Handling Alert Monitor • 500063: Overview of performance notes for the Alert Monitor • 519014: Handling Planning Version Management • 521639: Generation of DB Alerts in Background • 572003: SCM operating concept

Feedback and Questions Send any feedback by formulating an SAP customer message to component SV-GST-SMC. You can do this at http://service.sap.com/message.

Index /SAPAPO/AMON_MAIL_BROADCAST..24, 39

/SAPAPO/AMON_REORG................24, 39, 41

/SAPAPO/AMON1.......................24, 30, 39, 41

/SAPAPO/LCOUT..........................................29

/SAPAPO/MC62 ......................................12, 23

/SAPAPO/MC8V............................................18

/SAPAPO/MC8x ..........................20, 28, 37, 41

/SAPAPO/MC90 ............................................28

/SAPAPO/MP34 ............................................25

/SAPAPO/MP39 ............................................25

/SAPAPO/MSDP_ADMIN..............................22

/SAPAPO/OM_CHECKPOINT_WRITE.........26

/SAPAPO/OM_REORG_DAILY ....................40

/SAPAPO/PROMOTION_UPDATE_30.........25

/SAPAPO/RELEASE_SNP_FORECAST......29

/SAPAPO/RMDP_ICUBE_PERFORM..........10

/SAPAPO/RMDP_SHARE_MANAGER ........19

/SAPAPO/RTSCOPY ..............................17, 28

/SAPAPO/RTSINPUT ................................... 29

/SAPAPO/RTSINPUT_CUBE ....................... 17

/SAPAPO/RTSOUTPUT ............................... 28

/SAPAPO/RTSOUTPUT_FCST.................... 28

/SAPAPO/SCC01.......................................... 30

/SAPAPO/SDP94.................................... 23, 25

/SAPAPO/SNPFCST .................................... 29

/SAPAPO/TS_BATCH_LOGFILE........... 21, 38

/SAPAPO/TS_BATCH_RUN ...... 20, 27, 28, 37

/SAPAPO/TS_LCM_CONS_CHECK...... 13, 34

/SAPAPO/TS_LCM_CONS_CHECK_ALL ... 34

/SAPAPO/TS_LCM_PLOB_DELTA_SYNC . 13

/SAPAPO/TS_LCM_REORG........................ 34

/SAPAPO/TS_PAREA_DE_INITIALIZE ....... 13

/SAPAPO/TS_PAREA_EXTR_SETTING ..... 41

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

/SAPAPO/TS_PLOBS_GENERATE............. 13

/SAPAPO/TS_PSTRU_TOOL .......... 10, 13, 35


© 2004 SAP AG

46

/SAPAPO/TS_REALIGNMENT .....................13

/SAPAPO/TSCOPY.......................................17

/SAPAPO/TSCUBE .......................................17

BD87................................................................8

BRCONNECT..........................................11, 34

RSA1 ...................................................8, 11, 32

RSBATCH1 ...............................................9, 32

RSCUSTV6 .....................................................8

RSMO ................................................. 8, 10, 32

RSRV ............................................................ 11

SAP_ANALYZE_ALL_INFOCUBES. 11, 34, 40

SBAL_DELETE......................................... 9, 32

SLG1........................................................... 8, 9

SLG2............................................................... 9

SO01....................................................... 24, 39

© Copyright 2003 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 of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation. ORACLE® is a registered trademark of ORACLE Corporation. INFORMIX®-OnLine for SAP and Informix® Dynamic Server

TM are registered trademarks of Informix Software

Incorporated. UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute 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 by Netscape. SAP, SAP Logo, R/2, RIVA, R/3, ABAP, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies. 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 that may 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 use of hot links contained in these materials and does not endorse your use of third party Web pages nor provide any warranty whatsoever relating to third party Web pages.