Manage Production Planning in SAP SCM 7.0

8/10/2019 Manage Production Planning in SAP SCM 7.0

http://slidepdf.com/reader/full/manage-production-planning-in-sap-scm-70 1/47

© 2010 SAP AG

Best Practice

Manage Production Planning inSAP SCM (4.1, 5.x, and 7.0)

Dietmar-Hopp-Allee 16D-69190 Walldorf

DATE09.2010

SOLUTION MANAGEMENT PHASE SAP SOLUTION

Operations & Continuous Improvement SAP Supply Chain Management (SCM)

TOPIC AREA SOLUTION MANAGER AREA

Application & Integration Management Business Process Operations



Best PracticeManage Production Planning in SAP SCM (4.1, 5.x, 7.0)

© 2010 SAP AG page 2/47

Table of Contents

1 Management Summary 3

1.1

Goal of Using This Service 3

1.2 Alternative Practices 3

1.3 Staff and Skills Requirements 3

1.4 System Requirements 4

1.5 Duration and Timing 4

1.6 How to Use this Best Practice 4

2 Best Practice 5

2.1

Preliminary Tasks 5

2.2

Monitoring Procedure 8

2.3

Procedure 11

2.3.1

Business Process Step 1: Release DP to SNP (APO) 11

2.3.2

Business Process Step 2: Perform Demand Management (ERP) 13

2.3.3

Business Process Step 3: Create Sales Orders (ERP) 13

2.3.4

Business Process Step 4: Perform Planning Run (APO) 13

2.3.5

Business Process Step 5: Create/Change Planned Orders (APO) 20

2.3.6

Business Process Step 6: Create/Update Planned Orders (ERP) 22

2.3.7

Business Process Step 7: Run MRP for Non-APO Components (ERP) 22

2.3.8

Business Process Step 8: Perform Interactive Planning (APO) 24

2.3.9 Business Process Step 9: Convert Planned Orders into Production Orders (APO) 25

2.3.10 Business Process Step 10: Automatic Order Conversion (ERP) 26

2.3.11

Business Process Step 11: Release Production Orders (ERP) 27

2.3.12 Business Process Step 12: Update Production Orders (APO) 27

2.3.13 Business Process Step 13: Post Goods Issue for Components (ERP) 27

2.3.14 Business Process Step 14: Confirm Order Processing (ERP) 28

2.3.15 Business Process Step 15: Post Goods Receipt for Products (ERP) 28

2.3.16 Business Process Step 16: Settle Production Orders (ERP) 28

2.3.17 Business Process Step 17: Close Production Orders (ERP) 28

2.3.18 Business Process Step 18: Post Goods Issue in Delivery (ERP) 29

2.4 Alternative Processes 30

2.5 Related Tools and Activities 32

3

Further Information 41

3.1 Troubleshooting 41

3.2 Background Information and References 41

3.3 Index 46




© 2010 SAP AG page 3/47

1 Management Summary

This Best Practice enables you to set up a business process management and monitoring concept forbusiness processes using Production Planning and Detailed Scheduling (PP/DS), which is part of the SAPSupply Chain Management (SCM) solution.

It contains a template business process and, for each process step, the most important specific monitoringitems. Important housekeeping reports that delete technical data like logs are also included. Furthermore, youwill find information on how to monitor your business process using SAP Solution Manager. It providesapplication-specific details concerning the generic procedures described in the SAP Standard for ExceptionHandling and Business Process and Interface Monitoring.

When adapting this concept for your company, you must adapt the template business process to your actuallyused process, including non-standard programs and the more generic monitoring items like “average runtime”for a business transaction or “batch job ended before deadline,” if applicable and relevant. Furthermore, youmust specify the times, monitoring frequencies, responsible teams, and escalation paths (teams) for themonitoring activities associated with each business process step and its monitoring objects.

1.1 Goal of Using This Service

This Best Practice enables you to set up a business process management and monitoring concept for thebusiness process Production Planning and Detailed Scheduling (PP/DS), which is part of the SAP SupplyChain Management (SCM) solution using SAP R/3 or SAP ERP and SAP Advanced Planning andOptimization (APO).

This business process management and monitoring concept aims to:

Define procedures for business-process-oriented monitoring, error handling, and escalationmanagement for Production Planning and Detailed Scheduling .

Define the roles and responsibilities for all persons involved in the customer‟s support and

monitoring organization with respect to Production Planning and Detailed Scheduling .These procedures ensure the smooth and reliable flow of the core business process to meet your businessrequirements.

1.2 Alternative Practices

You can get SAP experts to deliver this Best Practice onsite if you order the Solution ManagementOptimization (SMO) service SAP Business Process Management.

1.3 Staff and Skills Requirements

To implement this Best Practice, you require the following teams:

Application Management Team

The SCM / APO business process management concept (which this Best Practice aims to produce)should be created by the application management team. This team combines experts from yourcompany‟s…

Business department

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

Implementation project team

Execution Teams

The execution teams, which are all taken from the customer‟s Solution Support Organization, comprise thefollowing groups:

The business process champion for each business process

Application support

Development support




© 2010 SAP AG page 4/47

Program scheduling management

Software monitoring team

System monitoring teamMore information about the roles and responsibilities of these teams can be found in the Best PracticeGeneral Business Process Management , which you can obtain through SAP Solution Manager.

Necessary or Useful Training Courses:

PDEF08 liveCache Administration

TTW060 SAP APO Technical Administration

TEWA60 SAP APO liveCache Monitoring

SCM210 Core Interface APO

SCM240 Production Planning (ERP)

SCM250 Production Planning (APO-PP/DS)

1.4 System Requirements

This document applies to SAP SCM 4.1, 5.0, 5.1 (2007), and 7.0.

1.5 Duration and Timing

Duration

Creating a business process management concept can take approximately one week per businessprocess.

Implementing the business process management concept can take one additional week.

Timing

The best time to apply this Best Practice is during the planning phase or during the implementation phase

for your SAP solution.

1.6 How to Use this Best PracticeIn advance, read the entire document to get an overview of its structure, content, and details.

Determine your APO PP/DS core business process to be monitored. If you use the APO Core Interface (CIF)within this process, also get the respective Best Practice document dedicated to CIF. Record all relevantsteps of your core business process; use the example business process as a template. Exclude templateprocess steps that you do not perform.

For every process step, take the monitoring elements from the tables and insert them into your own template.Complete the information according to your specific requirements, for example, frequency and time ofmonitoring activity. If the process step includes CIF data transfer, add the information from the CIF document,section Operation and Monitoring of the APO CIF .

Do not forget to include the respective information for interfaces other than CIF and for business processsteps performed with your own (Y-, Z-) programs. Determine the related monitoring activities, tools, andresponsible teams and fill in the table accordingly.

For activities that are not directly related to a business process step, like those mentioned in section System Administration Related to the APO CIF in the CIF Best Practice, create a separate table.

Proceed in the same way with all your other core business processes and other activities you want to monitor.




© 2010 SAP AG page 5/47

2 Best Practice

2.1 Preliminary Tasks

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

SAP APO System SAP Advanced Planning and Optimization within the SAP SCM systemfacilitates the strategic, tactical, and operational planning processes.

APO consists of several software components: a relational databasesystem (RDBMS) as in any ERP system, known as the APO DB; an SAPNetWeaver; the APO application programs; a separate, very fast, object-oriented SAP DB database called liveCache; application programs

running in liveCache – the COM routines; and a number of programs thatexecute elaborated optimization algorithms, called the optimizationengines. These components can run on the same or on different servers.

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

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




© 2010 SAP AG page 6/47

The following figure shows the relationship between APO application software components and thedatabases.

The various strategies for using SAP ERP and APO in combination are called integration scenarios.

This Best Practice is based on the most common integration scenario for setting up an SAP Supply ChainManagement solution using SAP APO. The SAP APO system is connected to one or more SAP ERP OLTPsystems via the APO Core Interface (CIF), which transfers all relevant data between them. The CIF usesqueued remote function calls (qRFCs) to ensure the desired sequence and transactional security of datatransmissions. For information about solution management for APO CIF, refer to the respective Best Practicedocument.

You may also use OLTP systems other than SAP ERP. These systems cannot use the CIF for a connectionto the APO system, but SAP provides Business Application Programming Interfaces (BAPIs) for programmingdata supply between third-party systems and APO. This scenario is not covered by the present Best Practicedocument.

SAP Advanced Planning and Optimization (APO) is the planning component of SAP SCM, the Supply ChainManagement 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, andso on are performed in the SAP ERP OLTP system, which contains all functionality for (among many others)




© 2010 SAP AG page 7/47

Materials Management (MM), Sales and Distribution (SD), Production Order Processing (PP-SFC), ProcessOrder processing (PP-PI), Logistics Execution (LES), and Controlling (CO).

The online transaction processing (OLTP) system – provided by SAP ERP – also provides relevant planningdata (master data and transaction data) for the APO system. Products are planned in the APO system, andthe planning results are transferred back to the OLTP system. If necessary, the planning can be completed inthe OLTP system, for example, if not all components of a BOM structure are planned in the APO system. Ifnecessary, the planning results completed in SAP ERP can then be transferred back to the SAP APOsystem.

In general, we recommend that you plan critical products and critical components in APO, and non-criticalproducts and components in the OLTP system. However, if you plan a component in APO, you also mustplan all components in the BOM structure up to the BOM header product in APO. Conversely, if you plan acomponent in the OLTP system, you also must plan all subcomponents in the OLTP system.

The APO component Production Planning and Detailed Scheduling (PP/DS) enables you to plan multi-siteproduction, while taking product and capacity constraints into account, with the goal of reducing lead timesand increasing due-date performance. PP/DS is designed to plan critical products, for example, products with

long replenishment lead times or products that are produced with bottleneck resources.

Additional information can be found in the SAP Documentation.

2.1.1.2 Production Planning and Detailed Scheduling

The core business process you run in your company for planning your production, though it is also based onthe SAP SCM solution, may differ in various ways from the canonical process described here and illustratedon the next page.

Planned independent requirements are created either in SAP ERP Demand Management (and transferred tothe APO system) or in the APO Demand Planning component. Additional independent requirements resultingfrom sales orders entered in the ERP OLTP system are transferred to the APO system, where planned ordersare created in a production planning run to cover the requirements. Planned orders are also created within

SAP ERP, triggering the replenishment process for those materials that are not planned within APO. Theorder numbers given to the ERP planned orders are retransferred to the APO system. Planning is refined andsupplemented manually by interactive planning, for example, on the Detailed Scheduling Planning Board.Here, you can perform functions such as scheduling sequence and setting up time optimization.

Subsequently, the planned orders are converted into production orders and are transferred to SAP ERP,where the respective order conversion occurs automatically. The production execution process is performedwithin SAP ERP, and all necessary information is transferred to the APO system to keep it consistent with theERP system.

Eventually, production orders are released, components are withdrawn, goods issue is posted, andoperations and orders are confirmed. The goods receipt for the produced goods is posted, and the productionorders are settled. The corresponding APO object is deleted when the production order is closed. The goodsissue posting of the goods shipped in accordance with the delivery document closes the planning cycle withthe respective increase or decrease of supply and demand.

Normally, if the following settings for the Core Interface (CIF) are compliant with the implemented businessprocess and functionality, they should be used to ensure a high-performance, smooth-running APO systemlandscape:

Transfer changed master data (material, customer, and vendor masters) periodically via ALE changepointers, not immediately via Business Transaction Events (BTEs).

Publish PP/DS planning results to ERP periodically , not immediately.

Set the PP/DS settings in the product master to Manual Planning or Planning in Planning Run but notto Cover Dependent Requirements Immediately.

Important Note

As the CIF is an essential component of SAP APO and its business processes, CIF monitoring andadministration is of critical importance for the performance and reliability of any business process that

exchanges data between APO and the ERP systems connected to it.

Therefore, it is extremely important that you follow the business process management procedure described inthe Best Practice document dedicated to CIF.




© 2010 SAP AG page 8/47

The following diagram shows all the business process steps whose monitoring is defined by this BestPractice.

SAP APO SystemSAP ERP OLTP System

Create Sales Orders

Core Interface CIF

Perform Demand Management

Perform Planning Run

Production Planning

Create / Update Planned Orders

Detailed Scheduling

Automatic Order

Conversion

Release Production Orders

Post Goods Issue for Components

Confirm Order Processing

Post Goods Receipt for Products

Settle Production Orders

Run MRP for non-

APO Components

Create / Change Planned Orders

Convert Planned Orders

into Production Orders

Close Production Orders

Post Goods Issue in Delivery

Update Production Orders

Production Planning

Perform Interactive Planning

Demand Planning

Release DP to SNP

2.2 Monitoring ProcedureIn 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 itsrespective monitoring objects.

When adapting this concept for your company, you must specify the times, responsible teams, and escalationpaths (teams) for the monitoring activities associated with each business process step and its monitoringobjects.

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, restartability, 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 PP/DS planning processes may vary depending on your business, the monitoringfrequency in these monitoring object tables is only a rough estimate, and has to be adapted to your particularbusiness process. During the GoingLive and Stabilization phase of your APO implementation project, allitems listed in this document should be monitored closely. After becoming more experienced with system




© 2010 SAP AG page 9/47

behavior, error occurrences, and application operations, the monitoring frequency can be decreased, butshould never be reduced to zero (unless you do not use the respective function at all). Important planning

jobs usually have to be monitored after each run. Regular jobs of minor priority (for example, certain cleanup jobs) may be run less frequently, and they can be checked to find out if they are running as planned. Forexample, daily jobs can be checked weekly.

The following seems obvious but should nevertheless be mentioned: Besides the monitoring of jobsdescribed in the business process steps below, it is essential that you check all jobs that are running in yoursystem 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. Thischeck can be done easily, for instance with transaction SM37, by entering the time interval since the latestcheck and selecting all jobs with status “cancelled .” If you have no automatic notification in place that informsthe people responsible for Program Scheduling Management in your Support Organization of abnormallyterminated jobs, you need to take measures to ensure that this is done manually in a reliable and timelymanner.

A number of jobs must run periodically in a live ERP installation, for example, the jobs for deleting outdated

jobs or spool objects. For details and comments, see SAP Note 16083.

2.2.1.1 Business Process Monitoring in SAP Solution ManagerBusiness Process Monitoring (BPMon), as part of Solution Monitoring, describes the proactive and process-oriented monitoring of the most important or critical business processes, including the observation of alltechnical and business-application-specific functions that are required for a steady and stable flow of thebusiness processes.

The core business processes that are implemented in an SAP SCM system or other software and operatedby a company are of particular importance, and Business Process Monitoring is intended to ensure a smoothand reliable operation of the business processes and, thereby, ensure that the core business processes meeta company‟s business requirements in terms of stability, performance, and completeness. SAP SolutionManager provides a graphic to visualize a company‟s (distributed) system and solution landscape and all

related business processes. By using Business Process Monitoring, it is possible to define and customizealert situations from a basic set of configurable alerts provided by SAP Solution Manager. These alerts arethen visualized by green, yellow, and red alert icons for each individual business process step in the graphicalbusiness process representation. Business Process Monitoring is intended to detect and respond to criticalsituations as early as possible in order to solve problems as quickly as possible.

In addition, SAP Solution Manager offers extended functionality for error handling and problem resolution. Bythe definition of contact persons and escalation paths, Business Process Monitoring can be integrated intothe company‟s overall strategy for Business Process Management and Solution Management within theirsolution support organization.

In general, Business Process Monitoring includes the solution-wide observation of:

Business process performance (key performance indicators)

Background jobs (Job Scheduling Management tasks) Business application logs (error log, general application log, due list logs, etc.)

Data transfer via interfaces between software components

Data consistency

Technical infrastructure and components that are required to run the business processes

Required periodic monitoring tasks

For more details on Business Process Monitoring, please refer to http://service.sap.com/bpm.

2.2.1.1.1 Monitoring Types for Business Process Monitoring in SAP Solution Manager

Monitoring types are part of the functional scope of Business Process Monitoring as it is available in SAPSolution Manager. This chapter provides a short overview of available monitoring types for reference

purposes only, and serves as introduction into the concepts applied by Business Process Monitoring withSAP Solution Manager. The following monitoring types are available:

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



http://service.sap.com/bpm








© 2010 SAP AG page 10/47

Application monitor (throughput and backlog indicators, data consistency checks, mass activitymonitors, due list log, MRP key figures, user exit)

Background jobs (jobs running on SAP systems with SAP Basis) Dialog performance (dialog transaction performance)

Update error (V1 and V2 update errors from SM13 for specific transactions and programs)

Due list log (messages for deliveries and billings)

Application log (messages from the application log SLG1)

Document volume (based on table call statistics in ST10)

Other CCMS monitor (all alerts that are configured in the CCMS alert monitor)

Depending on what is executed during a specific business process step, the relevant monitoring types mustbe selected. In order to receive detailed information on how to set up the monitoring objects in SAP SolutionManager, please refer to the documentation that is available under http://service.sap.com/bpm.

One prerequisite for setting up Business Process and Interface Monitoring in SAP Solution Manager is that allbusiness processes and business process steps are maintained in the respective solution that contains allaffected system components. If you want to learn more about how to set this up, please turn tohttp://help.sap.com SAP Solution Manager Basic Settings.

2.2.1.1.2 Application Monitor

The application monitor is just one of many different monitoring types within Business Process Monitoring.The latest monitoring objects are only provided if the latest ST-A/PI plug-in is installed on the satellite system.The service tool for ST-A/PI is available via the SAP Service Marketplace: quick link /installations Entry by Application Group Plug-Ins SAP Solution Tools ST-A/PI .

Please ensure that the ST-A/PI is installed on your SAP Solution Manager system and on therespective satellite. In case of problems, refer to SAP Note 915933.

The Throughput and Backlog Indicator functionality available as of ST-A/PI 01J* is only workingproperly as of ST-SER 700_2007_1. This is due to changes in the underlying architecture.

More detailed information about the different application monitor functionalities and a detailed description onhow to define self-written monitoring collectors for the user exit are explained in the documents Setup Guide – Application Monitoring and Setup Guide - User Exit , respectively (http://www.service.sap.com/BPM Media Library ).

2.2.1.1.3 Throughput and Backlog Indicators

As of ST-A/PI 01H, a completely new set of application monitors has been introduced. While the alreadyestablished monitors all evaluate specific logs or performance data, these new monitors consider(un)processed documents in the SAP system and provide so-called Throughput and Backlog Indicators(TBIs).

These TBIs provide the automated and early detection of application error situations and backlogs in the corebusiness processes.

For SCM, application monitors are available in the following business areas:

Demand Planning (Demand Planning Run)

Supply Network Planning (SNP Optimizer Run, Heuristic Run, CTM Run)

Production Planning/Detailed Scheduling (PPDS Planning Run, Change Pointer, Planned Orders,Purchase Requisitions)

Global ATP (BOP Run)

Automotive (Model Mix Planning Run)

For more information about the different TBIs, refer to the document Setup Guide - Application Monitoring (http://www.service.sap.com/BPM Media Library ).




http://help.sap.com/


http://www.service.sap.com/










© 2010 SAP AG page 11/47

2.2.1.1.4 Data Consistency Checks

The DCC collectors are a subset of the application monitors. They are used to retrieve stored comparisonresults from data comparison check reports for SAP systems.

There are certain consistency check programs that are not only able to output their check result to a list orinto the spool, but can also permanently store a summary to database tables. Corresponding monitoringobjects can be configured to retrieve the number of found inconsistencies out of the stored summaryinformation and display that as alerts within SAP Solution Manager Business Process Monitoring(Consistency Monitoring).

Especially for SCM, the results of the following consistency check reports can be evaluated automatically:

CIF Comparison/Reconciliation for Transaction data

Consistency Check liveCache – APO DB (OM17)

For further information, refer to the document Setup Guide – Data Consistency Monitoring

(http://www.service.sap.com/ Technical Information).

2.2.1.1.5 Background Jobs

The background job monitoring should be part of a Job Scheduling Management concept (go tohttp://service.sap.com/solutionmanagerbp Topic Area “Business Process Operations” to find the BestPractice document Job Scheduling Management ). Because of several restrictions regarding background jobscheduling, e.g., time restrictions, restriction of hardware resources (CPU, main memory, etc.), or existingdependencies between different activities (e.g., invoices can only be created after the corresponding goodsissue is posted, or Back Order Processing and Material Requirements Planning should not run at the sametime) it is very important to ensure the stable run of background jobs. A cancelled background job should beidentified as soon as possible in order to react as quickly as possible. Therefore it is also necessary to definerestart procedures and escalation paths.

2.2.1.1.6 Dialog Performance

Dialog performance implies the monitoring of the dialog transaction performance of any transaction in theSAP system. This could be a standard transaction or an own developed transaction.

2.3 Procedure

2.3.1 Business Process Step 1: Release DP to SNP (APO)Independent requirements can either be created in demand management in ERP or in the APO componentDemand Planning (DP).

If DP is used, independent requirements are created from the completed DP forecasts using the function“Release DP to SNP.” This function transforms the DP time series objects into order objects with a specified

ATP category (in this case, “FA” = independent requirements) stored in liveCache. SNP denotes SupplyNetwork Planning. The name “Release DP to SNP” is a little misleading, since you may not be using SNP.You may be releasing DP to Production Planning.

This release function can be performed online with transaction /SAPAPO/MC90 or in the background byreport /SAPAPO/TS_BATCH_RUN with planning activity “Release to SNP” using an appropriate releaseprofile. The settings and background jobs needed have to be defined in the transactions /SAPAPO/MC8x.

Planned independent requirements can also be created manually in PP/DS transaction /SAPAPO/RRP1“Requirements View.”

2.3.1.1 Monitoring Activities

Apart from safeguarding the general availability and consistency of the system components SAP APO andSAP ERP OLTP, SAP recommends that you monitor the objects listed in the following table to safeguard thisbusiness step.




http://service.sap.com/solutionmanagerbp







© 2010 SAP AG page 12/47

Jobs for Running and Monitoring Release DP to SNP (APO)

To ensure a thorough and accurate release of forecasts to production planning, schedule the following job to

run on a regular basis: Demand Planning in the Background with report /SAPAPO/TS_BATCH_RUN. As well as executing

other DP planning functionality in the background, this report can release chosen DP forecasts toorder objects, in this case planned independent requirements. This mass processing job is createdwith its necessary settings and is scheduled using transactions /SAPAPO/MC8x.

To check the results of a DP mass-processing job, use the DP job log. To generate a job log, select Generatelog when you create a job. To view the job log, call transaction /SAPAPO/MC8K. The job log shows whetherthe job completed successfully (green traffic light), with warnings (yellow traffic light), or with errors (red trafficlight), and includes 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.Normally, a release of the forecasts to production planning is performed periodically at long intervals, such asonce a quarter or once a year, but not daily or weekly. Set the frequency of monitoring and deleting the DP

job logs depending on how often you run this function.

With Business Process & Interface Monitoring (BP&IMon) in SAP Solution Manager, it is possible to analyzeand evaluate the log file automatically. You can monitor the number of specific messages written during a DP

job by specifying a DP job number, a message type, message ID, and message number. You specify a valuefor the number of messages from which a yellow or red alert should be raised. It is also possible to monitorthe number of characteristic combinations with errors for a DP job and to automatically raise an alert if acertain number is exceeded.

Monitoring Recommendations Without SAP Solution Manager

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error

Monitoring Activity orError Handling Procedure

Respon-sibility

EscalationProcedure

APO report/SAPAPO/TS_

BATCH_RUNThis reportperformsspecified DPmassprocessing, inthis case,“Release DPto SNP.”

SM37 Depending on

yourneeds

Status Check if job is running asscheduled.

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

Programscheduling

management

Contactapplication

support

DP job log /SAPAPO/MC8K

Aftereachrun of/SAPAPO/TS_B

ATCH_ RUN.

Red oryellowtraffic lightsshown

According to the warning orerror reported (see messagelong text)

Applicationsupport

Contactprocesschampion

APO report/SAPAPO/TS_ BATCH_LOGFILE

This reportdeletes old DP job logs.

SM37 Depending onyourneeds



Programschedulingmanagement

Contactsoftwaremonitoringteam




© 2010 SAP AG page 13/47

Monitoring Recommendations with SAP Solution Manager

Monitoring

Type

Monitoring Object Key Figure Possible Business Process

Improvements

Monitoring

Frequency /DataCollection

Backgroundprocessing

Report/SAPAPO/TS_BATCH_RUN

Cancellation Early detection of problems ->minimize delay in businessprocess

Depending onyourrequirements


Report /SAPAPO/MC8K Job log messages Early detection of problems ->minimize delay in businessprocess

Depending onyourrequirements

2.3.1.2 Error Handling, Restartability, and Escalation

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

2.3.2 Business Process Step 2: Perform Demand Management (ERP) As an alternative to using APO Demand Planning (business process step 1, above), you can perform demandmanagement for make-to-stock production in the ERP system. This can be performed manually (for example,in transactions MC87 and MC74), based on a forecast, or by means of different functions in Sales andOperations Planning (SOP).

As a result of performing demand management, planned independent requirements are created andtransferred via the CIF into the production planning application of the APO system. Therefore, plannedindependent requirements must be added to an active CIF integration model.


Apart from safeguarding the general availability of the system components SAP APO and SAP ERP OLTP,SAP recommends that you monitor the objects related to the Core Interface (CIF) to safeguard this businessprocess step.

It is extremely important that you follow the business process management procedure described in the BestPractice document dedicated to CIF.

2.3.3 Business Process Step 3: Create Sales Orders (ERP) As further independent requirements, sales orders (created with VA01) are transferred to the APO systemboth to perform planning for make-to-order production and to increase or consume planned independentrequirements. This step is independent of whether you take planned independent requirements from ERP orfrom APO Demand Planning (DP).


Apart from safeguarding the general availability of the system components SAP APO and SAP ERP OLTP,SAP recommends that you monitor the objects listed in the Best Practice document dedicated to CIF tosafeguard this business process step.

If you transfer SD orders to APO, you have to run certain reports, such as /SAPAPO/SDORDER_DEL and/SAPAPO/SDRQCR21, on a regular basis. Please refer to the Best Practice documents on gATP and on dataconsistency for more information.

2.3.4 Business Process Step 4: Perform Planning Run (APO)The planned independent requirements are the starting point for production planning in APO. Existing storagelocation stocks are also considered in the planning. Whether or not automatic planning applies for a certain

product location can be set in the PP/DS tab of the product master. Products can be planned immediately orin a planning run.




© 2010 SAP AG page 14/47

The standard setting that should be used for most scenarios is “ planning in planning run” to plan productsusing heuristics that you have defined for each product. You can use your own heuristics or you can useheuristics provided by SAP. A large variety of heuristics are available to plan products that address particularplanning problems, including various lot-sizing heuristics and purchase order quantity optimization.

When “planning in planning run” is selected as the planning procedure for a product location, a planning fileentry is created every time a planning-relevant event occurs (for example, change of requirements or stock).These products are then planned in the next net-change planning run. Compared with immediate planning,planning products in the production planning run (with report /SAPAPO/BACKGROUND_SCHEDULING) hasthe advantage that you can control when and how often products are planned, so you can improve systemperformance by executing planning runs at less busy times of the day. See SAP Note 513827 for details onthe settings and parallel processing in the PP/DS planning runs.

Caution: Settings other than “planning in planning run” should be used only if the business scenario and the APO functionality used require it:

Setting “cover dependent requirements immediately” can be very performance-critical. Also, theplanning results depend strongly on the sequence of planning activities (see SAP Note 459694).Normally, you only need to check for a Capable-to-Promise scenario, where production is triggeredby an availability check (gATP) performed by a sales order (see SAP Note 426563).If you do not require this special feature, we recommend using “manual planning” or “planning inplanning run.”

You can use “cover dependent requirements immediately” to plan products that use lot-for-lot orderquantity or fixed lot-sizing procedures. You use “planning in planning run” to plan products using otherlot-sizing procedures that are available as heuristics, such as period lot-sizing or purchase orderoptimization heuristics.

Both types of automatic planning are triggered when new requirements are transferred to PP/DS,requirements are changed, stocks are moved, product master data is changed, the production process model(PPM) is changed, or other changes relevant to planning occur. Planning activities should not take place inparallel with (initial) data supply, but rather in a subsequent planning run based on the planning files entries.

This generally applies to SNP, CTM, and PP/DS planning runs performed on the active planning version;inactive versions are not affected by CIF activities. Refer to SAP Notes 528913 and 606320 for detailedbackground information.

Planning runs that run in different planning levels should not publish the results between each planning run,but after the last planning run is finished. Otherwise, locking problems may occur. Refer to SAP Note 307336 for details.

The planning log in PP/DS contains messages that the system creates during interactive planning or inbackground planning. You can use the planning log to analyze planning problems and identify the causes ofthe problems. The system only displays a log if it contains messages that belong to the specified exceptiongroups. Use transaction /SAPAPO/RRPLOG1 to browse the PP/DS planning log.You can call the planning log for the planning run in which a selected product was last planned. The function

is available for production planning runs with procurement planning heuristics. In the Log for Last PlanningRun view (/SAPAPO/RRPEVAL), the system displays the message with the highest priority for the log numberinstead of showing all messages that occurred during product planning. You can double-click on the lognumber to branch to the planning log. You can also navigate in the product view, the product overview, or inthe product planning table.On ERP side, you can use report RFINDLOG to search for application log entries concerning planned ordersthat have been transmitted by CIF. As this report creates a search index for the application log, it is necessaryto periodically adapt the index table to the current application log entries using report RDELBALS. You canfind more details in SAP Note 457657.

The usage of the PP/DS optimizers is fully integrated into the background PP/DS planning runs. You simplyhave to use the function “Optimization” as processing step in a variant of/SAPAPO/BACKGROUND_SCHEDULING and provide an appropriate optimizer profile. Usually, theoptimizer is invoked after the MRP planning and a preliminary scheduling of activities.

For the PP/DS Sequencing Optimizer (SEQ01) (as well as for CTM, ND, and TP/VS [VSR] optimizers), SAPrecommends that you have a minimum of 512 MB of memory and one CPU on the optimization server,
































© 2010 SAP AG page 15/47

because these optimizers (optimizer processes) can only make use of one CPU. If the business processallows you to split the optimizer model into smaller parts and you have more than one CPU available, you canperform the optimizer runs in parallel to make use of more than one CPU. To improve performance when youare dealing with larger scheduling problems, you can use decomposition to divide up the optimization rangeinto several smaller problems. From the hardware side, the CPU speed is the principal factor that determinesthe optimizer runtime.

The DPS optimizer for PP/DS (DPS01) can be configured to make use of more than one CPU (multi-agentoptimization). During multi-agent optimization, the system uses several processors (agents) in parallel for theoptimization; it can execute the optimization on each processor using a different (user-defined) objectivefunction. In each optimization step, the agents notify each other of their previously targeted solutions andexchange good partial solutions.

Depending on the data volume and the optimization scenario, the performance of the PP/DS Optimizer isdifferent. To check the feasibility of a PP/DS optimization problem in terms of performance, a dedicated sizingsheet exists: see http://service.sap.com/scm → SAP SCM IN DETAIL → Technology → PP/DS OptimizerQuestionnaire.

Fill in the Excel sheet and check the result directly. This should be done in an early phase of the project(blueprint). If necessary (depending on the output of the Excel sheet), ask for the dedicated consultancyservice for optimization mentioned on this page, too.

You need to verify the optimization time required and the results of the optimization run with a realistic datasample four to eight weeks in advance of going live. To check the runtime and get an overview of activities,planned data, and errors occurred, use the application log (transaction SLG1, object APO, sub-object PPDS)or optimizer monitoring transaction /SAPAPO/OPT11. A detailed technical trace file is also available in/SAPAPO/OPT11 or (as of SAP SCM 4.0) in /SAPAPO/PERFMON.

In the event of a short dump during the optimizer run, the optimizer run must be manually deleted intransaction /SAPAPO/OPT03 before another run can be started. See SAP Note 393634 for details. They arealso deleted by report /SAPAPO/OM_REORG_DAILY, which should be run once a day, but never concurrently with optimizer runs. In addition, if you ever run two optimizer runs simultaneously, be sure to set

the parameter enque/delay_max in transaction RZ11 as described in consulting SAP Note 572996 to avoidlock problems. You also use SAPAPO/OPT03 to check the active optimizer tasks with user and start timeinformation.

Use report /SAPAPO/OM_TB_LCHECK_CDPSOPT to check whether the PP/DS optimizer works technically.Execute the report with default settings and check the log yjsy od displayed. If all messages have a greenlight, everything is okay. Also see SAP Notes 703774 (SCM release 4.1), 857475 (5.0), 1019666 (5.1), and1216588 (7.0).

Note that you should upgrade your optimizer in parallel with support package upgrades to ensure optimalfunctionality and performance.


Apart from safeguarding the general availability and consistency of the system components SAP APO and

SAP ERP OLTP, SAP recommends that you monitor the objects listed in the monitoring object table for thisbusiness process step.

The most important high-level tool for monitoring the planning situation and an exception-driven applicationmanagement is the APO Alert Monitor .

Jobs Necessary to Run and Monitor Automatic Production Planning (APO)

To ensure correct and current production planning, certain jobs must be scheduled on a regular basis. These jobs are:

Production planning run with report /SAPAPO/BACKGROUND_SCHEDULING. This reportperforms the different processing steps in the production planning run, that is, it applies the chosenfunctions and heuristics to the selected orders, products, and so on.

Delete PP/DS logs with report /SAPAPO/SAPRRPLOG_DELETE. Old logs from planning activitiesmust be deleted regularly to maintain high performance for the related transactions. The PP/DS log isa filtered view of messages stored in the application log, which is a Basis component. The application

http://service.sap.com/scm






























© 2010 SAP AG page 16/47

log is similar to the system log; system event information is logged in the system log, and relevantapplication events are logged in the application log.

Send Alert Monitor mails with report /SAPAPO/AMON_MAIL_BROADCAST. Depending on userprofiles maintained in transaction /SAPAPO/AMONMSG, mails are sent with an overview of existingalerts. The responsible persons should then call the APO Alert Monitor, investigate the reasons forthe alerts, and take corrective actions to keep the production plan close to the needs of yourcompany.

Determine alerts in the background with report /SAPAPO/READ_ALERTS_BATCH. In transaction /SAPAPO/AMON_SETTING, select Goto → Alert Determination in the Background and define anOverall Profile. Here, you can optionally enter an e-mail address to be used by the system to send anotification mail as soon as the background run is complete. The mail will contain an overview of thedetermined alerts. To run the alert determination in the background, schedule report/SAPAPO/READ_ALERTS_BATCH as periodic job with an interval that is at least as short as theintervals used in the overall profile defined above. In the variant of the report, you specify the overallprofiles to be evaluated.

On the initial screen of the Alert Monitor (/SAPAPO/AMON1), you call up the saved alert situationusing the input help. The system repeats the alert determination at the time interval you havespecified in the overall profile, and then saves the new alert situation. The previous alert situation isdeleted automatically. This means you can only call up the last saved alert situation for an overallprofile.

Delete Alert Monitor alerts with report /SAPAPO/AMON_REORG. Deletes alerts that are older thana specified age.This is only relevant for PP/DS if database alert types are being used. Most PP/DS alerts aredynamic and not stored in the database (see APO Alert Monitor , below).

Jobs for the Maintenance of the Application Log

The application log entries are stored on tables with the 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 obsoleteapplication logs from the database regularly to prevent these tables from overflowing and to help ensure thatthe applications and log retrieval run smoothly. You can delete them using transaction SLG2 or in thebackground with the appropriate report. Application log entries are generated in the APO system by theplanning run, as well on both the ERP and APO systems by CIF.

Delete obsolete application logs with report SBAL_DELETE. A log can only be deleted when it hasreached its expiry date or if it has the “Deletion before expiry” attribute. For more information, seeSAP Note 195157.

Delete obsolete application log search index entries on ERP with report RDELBALS. For moreinformation, see SAP Note 457657.

Jobs for General APO System Maintenance

There are a lot of general housekeeping jobs that have to be run regularly on an APO system and which arenot mentioned in this document as they are not specific for the usage of PP/DS. For the use of optimizers (notonly PP/DS), the following is of particular importance.

Delete old optimizer log files and lock entries with report /SAPAPO/OM_REORG_DAILY. Thereport should be run once a day on every client with APO data, even if optimization is not used at all,as it also cleans up various liveCache data (refer to SAP Note 679118). It must never be runconcurrently with optimizer runs.
















© 2010 SAP AG page 17/47


Monitoring

Object

Monitor

TA/Tool

Monitor

Freq.

Monit

orTime

Indicator

or Error

Monitoring Activity or

Error HandlingProcedure

Respon-

sibility

Escalation

Procedure

APO report/SAPAPO/BACKGROUND_ SCHEDULING

This reportperforms thedifferentproductionplanning runs.It usually runsseveral timesa day(possibly withdifferentscopes andgoals).

SM37 Depending on yourneeds,daily orat leastonce aweek


If the report is notscheduled as providedby Application Support,schedule it accordingly.


Contactapplicationsupport

Output of APOreport/SAPAPO/BACKGROUND_ SCHEDULING

SM37 orSP01

Aftereachplanningrun

Red traffic light Application support and/or process championmust decide if planningrun must be repeated orperformed interactively.

Instead of checking thislist, you can check thePP/DS log.

Applicationsupport


APO PP/DSlog for aspecifiedplanning run

/SAPAPO/RRPLOG1

Aftereachplanningrun, afterplanningboardactivities

Yellow or redindicators Read diagnosis andsystem response of themessage long texts andfollow the describedprocedure.

Application support and /or process championmust decide whether:- Planning job results areas desired- They must be correctedinteractively- Planning run must berepeated

Applicationsupport Contactprocesschampion

APO PP/DSlog for aspecifiedproduct

/SAPAPO/RRPEVAL

Asrequired

Yellow or redindicators

Read diagnosis andsystem response of themessage long texts andfollow the describedprocedure.

Application support and/or process championmust decide whether:- Planning job results areas desired- They must be correctedinteractively- Planning run must berepeated

Applicationsupport





© 2010 SAP AG page 18/47

MonitoringObject

MonitorTA/Tool

MonitorFreq.

Monitor

Time

Indicatoror Error

Monitoring Activity orError Handling

Procedure

Respon-sibility

EscalationProcedure

APO report/SAPAPO/SAPRRPLOG_DELETE

This reportdeletes PP/DSlogs.

SM37 Weekly Status Check if job is running asscheduled.

If the report is notscheduled on a regularbasis, schedule it to runonce a day and deletelogs older than a coupleof days.



APO AlertMonitor

/SAPAPO/AMON1

At leastdaily

Check for PP/DS alertsand correct the planningand scheduling for thereported object

appropriately.

Applicationsupport


APO report/SAPAPO/AMON_MAIL_BROADCAST

This reportensuressending ofmails aboutexisting alerts.

SM37 Daily Status Check if job is running asscheduled.

If the report is notscheduled on a regularbasis, schedule it to runevery hour to at leastdaily, depending on yourrequirements.



APO report/SAPAPO/RE AD_ALERTS_

BATCHThis reportdeterminesand savesalertsituations.


If the report is not

scheduled on a regularbasis, schedule it to runat least as often asintervals are defined inthe overall profiles thatare evaluated by thisrun.


Contactsoftwaremonitoring

team

Alert Monitormails

SO01(orrespective e-mailsystem)

Depending on yourrequirements, atleastdaily

Check if the mail listsalerts that are importantfor you.

Go to APO Alert Monitorand process the alertsappropriately.

Applicationsupport


APO report/SAPAPO/AMON_REORG

This reportdeletes AlertMonitor alerts


If the report is notscheduled to runregularly, schedule it torun once a day.



ERP and APOreportSBAL_DELETE

This reportdeletesobsoleteapplicationlogs.


If the job is notscheduled as providedby Application Support,schedule it to runweekly.


Contact ApplicationSupport




© 2010 SAP AG page 19/47

MonitoringObject

MonitorTA/Tool

MonitorFreq.

Monitor

Time

Indicatoror Error

Monitoring Activity orError Handling

Procedure

Respon-sibility

EscalationProcedure

ERP reportRDELBALS

This reportdeletesobsoleteapplication logsearch indexentries.


If the job is notscheduled as providedby Application Support,schedule it to runimmediately afterSBAL_DELETE.



APOOptimizer Log

/SAPAPO/OPT11

Aftereachoptimizerrun

Exception Check whether the logfile is flagged yellow orred. In this caseinvestigate the

messages in more detail.

Softwaremonitoringteam

Contactapplicationsupport orsystem

monitoringteam,depending onerror

APOperformancemonitor

/SAPAPO/PERFMON

Fromtime totime; ifyouexperience longruntimesorproblemswith the

optimizer

Log entries Analyze optimizer tracefile and identify problemcause. If in doubt, opena customer message inSAPNet ERP front end.

Applicationsupport

Contactsystemmonitoringteam or SAP,depending onthe problem

User list foroptimizers

/SAPAPO/OPT03

In caseofproblems

Active optimizerusers

Identify long running orcancelled users.



APO report/SAPAPO/OM _REORG_DAILY

This reportdeletes oldoptimizer logfiles and lockentries.


If the report is notscheduled on a regularbasis, schedule it to rundaily.



APO report/SAPAPO/OM _TB_LCHECK _CDPSOPT

This reportchecks thePP/DSoptimizerinterface.

SLG1 Afterinstallation orupgrades; ifproblemsarise ortheoptimizerdoes notanswer

Yellow or redlight

Execute the report intransaction SA38 withdefault settings andcheck the application logbeing displayed (or go totransaction SLG1). If allmessages have a greenlight, everything is okay.


Contactsystemmonitoringteam




© 2010 SAP AG page 20/47


Monitoring

Type

Monitoring Object Key Figure Possible Business

ProcessImprovements

Monitoring

Frequency / DataCollection

Appl.Mon.: AdvancedPlanner andOptimizer

PPDS Planning Run Runtime Early detection ofproblems ->minimize delay inbusiness process

Depending on yourrequirements


PPDS Planning Run Orders createdor changed,orders deleted,pegging areasplanned

Early evaluation ofplanning results(plausibility)


Appl.Mon.: Advanced

Planner andOptimizer

PPDS Planning Run Pegging Areaswith

Termination

Early detection ofproblems



PPDS Planning Run Messagescreated duringplanning run oftype A(bortion)and E(rror)

Early detection ofproblems


BackgroundProcessing

Report /SAPAPO/BACKGROUND_SCHEDULING

Cancellation,duration,start delay

Early detection ofproblems ->minimize delay inbusiness process


Background

Processing

Reports:

/SAPAPO/SAPRRPLOG_DELETE,/SAPAPO/AMON_MAIL_BROADCAST,/SAPAPO/READ_ALERTS_BATCH,/SAPAPO/AMON_REORG,/SAPAPO/OM_REORG_DAILY,SBAL_DELETE

Cancellation Early detection of

problems

Daily or Weekly



2.3.5 Business Process Step 5: Create/Change Planned Orders (APO)Planned orders are created as a result of the APO production planning run. The APO system explodes the

production data structure (PDS) or the production process model (PPM) and performs order and operationscheduling. The scheduled planned orders can then be transferred to SAP ERP. There, they can be used totrigger the dependent requirements for those materials that are not planned within APO (in a standard MRPrun, see below), or to perform repetitive manufacturing in ERP. However, if planned orders are not needed inthe ERP system for these purposes, they should be restrained in APO until they are released into production(or process) orders.

Note: As the transfer of planned orders to ERP is critical to performance, this should onl be done inexceptional cases and if really needed by the business process. The same applies to purchase requisitions.These settings have to be done in APO customizing, Global Parameters and Default Values (transaction/SAPAPO/RRPCUST1): Set fields Transfer to ERP In-House Production and Transfer to ERP Ext.Procurement to “Create Transfer Events from Conversion Indicator.”

In contrast to Demand Planning (DP) and Supply Network Planning (SNP), the default setting for ProductionPlanning and Detailed Scheduling (PP/DS) is to publish planning results to ERP immediately. However, wealso recommend collecting and transferring the planning results periodically for PP/DS, at least whilebackground planning is active. To do this, the setting in transaction /SAPAPO/C4 is user-specific. Usedifferent users with specified settings for background planning and for online activities (note that you cannot




© 2010 SAP AG page 21/47

use wild cards here, but must specify either the full user ID or use entry “*” for all other unspecified users). Inparticular, if you have several subsequent planning runs with different scopes and goals, you can decidewhen planning results are ready for publishing. See SAP Note 307336 for details.


Apart from safeguarding the general availability of the system components SAP APO and SAP ERP OLTP,SAP recommends that you monitor the objects listed in the monitoring object table for this business processstep.

Jobs Necessary to Publish Planning Results to ERP OLTP System (APO)

To ensure that the planning results are published to ERP and that the relevant data is consistent in bothsystems, certain jobs must be scheduled on a regular basis. These jobs are:

Publish planning results with report /SAPAPO/RDMCPPROCESS. This report evaluates the APOchange pointers (not the same as ALE change pointers!) that are written during planning activities.

The corresponding objects, such as planned orders, are sent to ERP. Check processing of APO change pointers with report /SAPAPO/RDMCPPROCESS. This report

verifies that all change pointers are processed by checking that the list displayed in report/SAPAPO/RDMCPPROCESS is empty. If change pointers remain unprocessed, contact theapplication support team to clarify whether these change pointers are needed and why they are notprocessed.

Note: Deleting change pointers may cause inconsistencies, as the corresponding order changes arenot transferred to ERP.With the BP&IMon tool in SAP Solution Manager, it is also possible to monitor unprocessed changepointers automatically. In case of any backlogs in processing of the change pointers, SAP SolutionManager can be customized to create alerts in a business process monitoring session. Therefore, thenumber of change pointers that exceed an age that is defined individually during the setup of this

monitoring activity is counted regularly. Also consider the jobs mentioned in the Best Practice document dedicated to CIF, section Operation

and Monitoring of the APO Core Interface.


MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO report/SAPAPO/RDMCPPROCESS

This report

publishes theresults ofautomaticandinteractiveplanning toERP.

SM37 Depend-ing onyourneeds,daily or

at leastonce aweek


If the report is not scheduledas provided by ApplicationSupport, schedule it

accordingly.



APO report/SAPAPO/RDMCPPROCESS to displaychangepointers


If the report is not scheduledon a regular basis andperiodic publishing ofplanning results is used,schedule it to run once a day.










© 2010 SAP AG page 22/47


Monitoring

Type

Monitoring Object Key Figure Possible Business

ProcessImprovements

Monitoring

Frequency / DataCollection


Change Pointer Unprocessedchange pointer(in differentareas)


Daily


Planned Orders Orders withopening datein the past

Detection of backlog-> avoid delay inproduction andprocurementprocess

Daily


Report /SAPAPO/RDMCPPROCESS Cancellation Early detection ofproblems ->minimize delay inbusiness process




2.3.6 Business Process Step 6: Create/Update Planned Orders (ERP) A planned order is opened in the APO system with an APO order number and transferred to SAP ERP. Theplanned order is then created in the ERP System on the basis of the respective ERP number range, and theERP planned order number is retransferred to APO. This process is called key completion and allows therespective orders to be displayed in both systems with the same unique number. (This applies also to other

order types, such as production or purchase orders.)The process flow for changing an APO planned order is similar. Changes can also be made in ERP plannedorders originating from APO and these changes are then communicated to APO via the CIF.


Apart from safeguarding the general availability of the system components SAP APO and SAP ERP OLTP,SAP recommends that you monitor the objects listed in the Best Practice document dedicated to CIF tosafeguard this business process step.

2.3.7 Business Process Step 7: Run MRP for Non-APO Components (ERP)For materials that do not need to be planned in APO (and all their BOM components), dependentrequirements can be created in the standard MRP run. Materials with demand-driven replenishment arehandled there. The classic ERP production planning and shop floor control functions for non-APOcomponents follow on from this, but these are not explained in this Best Practice, as they have no influenceon data managed in APO.

You should decide carefully when determining whether or not to plan a material in APO. This is becauseresources that are included in APO must be planned with all the products that are manufactured using them;otherwise, capacity requirements are not considered correctly.

Components of non-APO materials cannot be planned by APO. For a material planned in APO, all thesupplies and demands must be transferred to APO. If they are not, there is a planning discrepancy betweenERP and APO.


Apart from safeguarding the general availability of the system components SAP APO and SAP ERP OLTP,SAP recommends that you monitor the objects listed in the monitoring object table for this business processstep.




© 2010 SAP AG page 23/47

Jobs Necessary to Run MRP for non-APO Components (ERP)

The following job must be scheduled on a regular basis to ensure the execution of replenishment for

component materials that are not planned within APO (for example, because they are not time-critical, notproduced using bottleneck resources, or purchased using demand-driven purchasing):

Material requirements planning (MRP) with report RMMRP000 (or RMMRP010 for long-termplanning, or RMMPS000 for the master production scheduling run). This report reads the new andchanged requirements, explodes the bills of materials (BOM) of the corresponding finished, semi-finished, and raw materials, and creates receipts in form of planned orders. Normally, this report runswith a frequency between daily and weekly, for example, every night from Monday to Friday withprocessing key "NETPL" (net change planning within the planning horizon) and once at the weekendwith "NETCH" (net change planning without time restriction).Results and any planning problems in the form of exception messages can be reviewed in the MRPlist, and any required corrective action can be initiated.The BP&IMon tool in SAP Solution Manager provides the functionality to monitor if the expected MRPrun is running or not. It is also possible to monitor the exceptions that were created during an MRP

run.


MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

ERP reportRMMRP000and / orRMMRP010and / orRMMPS000





ERP MRPList

MD05 orMD06,SolutionManager(BP&IMon)

Aftereachrun ofRMMRP000 /RMMRP010 /RMMPS000

Red oryellowtraffic light

Check for exceptionmessages (displayed withtraffic lights as customized).

Businessprocesschampion


ERP MRPruntimestatistics

SP01 Weekly Statisticsummary

Check spool file of the MRPrun for runtime shares,number of planned objects,and top 10 materials withlongest runtimes.

Applicationsupport

Contactbusinessprocesschampion

Technicalstatistics ofthe MRP run

ReportRMMDMONI

Fromtime totimeand ifproblems occur

Key figures Compare key figures ofplanning runs, determinemost important runtimeshares, and identifyinfluencing factors forruntime. Gain insight intochange of figures overseveral weeks.

Applicationsupport





© 2010 SAP AG page 24/47

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

MRP runstatistics – material hitlist

ReportRMMDPERF

Fromtime totimeand ifproblems occur

Times fordifferentparts ofMRP run

This report provides detailedinformation on the differenttime shares (read situation,BOM explosion, lead timescheduling, and so on)needed in the MRP run permaterial. This can be used forin-depth analysis ofperformance problems, trendanalysis for importantmaterials, etc.

Applicationsupport



MonitoringType

Monitoring Object Key Figure Possible BusinessProcessImprovements

MonitoringFrequency / DataCollection

Appl.Mon.:Manufacturing

MRP Run Runtime,number ofcancelledmaterials


Daily

Appl.Mon.: MRP List Number ofmaterials perexceptiongroup

Detectionproblems/exceptions-> avoid delay inproduction andprocurementprocess

Daily


Reports:RMMRP000 and / orRMMRP010 and / orRMMPS000

Cancellation Early detection ofproblems ->minimize delay inbusiness process




2.3.8 Business Process Step 8: Perform Interactive Planning (APO)In APO, you can manually and interactively plan products to improve the planning situation. Manually plannedproducts are usually critical products that require particular attention when planning. The tools DetailedScheduling (DS) planning board (/SAPAPO/CDPS0), resource planning table (/SAPAPO/RPT, available as ofSCM 5.0), product planning table (/SAPAPO/PPT1), product view (/SAPAPO/RRP3), heuristics, andoptimizers are available to improve the planning situation. To plan products manually, you can create ordersand change dates and quantities directly in APO. Since the planning is constantly changing, you mustregularly check the planning situation to solve new planning problems and to process the interactive planningtasks. When problems or unusual situations arise during planning, the system generates alerts to inform theplanner. These can be displayed using the APO Alert Monitor . One of the most important responsibilities of an

APO planner is the investigation and elimination of alerts, which comprises all planning tasks, methods, andtools.

The product overview provides you with an overview of either several products, or of planning segments forindividual products. It provides information on the availability situation of a product, as well as on the alertsand days‟ supplies for a product. You can access the product overview either as a sub-screen in the product

planning table or in a separate transaction (/SAPAPO/POV1). You can access both the product planning tableand the product view from the product overview.




© 2010 SAP AG page 25/47

As of SCM 5.0, the resource planning table provides the functionality for detailed scheduling in tabular form,which allows quick access to the necessary information. You can also access the resource planning tablefrom the DS planning board.

In the production planning run, in the DS planning board or in the resource planning table, several heuristicmethods can be applied to a selected set of order operations to schedule these operations in a particularsequence, dissolve backlogs, reduce lead time, schedule de-allocated operations, and so on. In the DSplanning board or in the resource planning table, you can also execute optimization algorithms and optimizethe schedule for the current simulation version.

Optimizers and heuristics are used to optimize the production dates, order sequences, and resourceassignment for existing operations, which were generated by the production planning run or manual planning.The optimizers do not create or delete orders.

The purpose of optimization is to generate feasible production plans and increase the efficiency of production.Several optimization parameters (such as setup times or due date violations) can be weighted in such a waythat the optimized schedule comes as close as possible to the desired results (for example, minimum setuptimes).

You can use the Plan Monitor (transaction /SAPAPO/PMON) to compare the results of various scheduling oroptimization runs stored in different planning versions. Based on the key figures defined (like days ‟ supply,total order delay time, scrap quantity, and so on), you can measure the performance of your supply chain andevaluate the planning situation from a business perspective. You can also call the Plan Monitor as a chart inthe product planning table /SAPAPO/PPT1.


Apart from safeguarding the general availability of the system components SAP APO and SAP ERP OLTP,SAP recommends that you monitor the objects listed under Monitoring the APO Planning Activities and thePlanning Situation and Publishing of APO Planning Results to ERP to safeguard this business step.


MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO productoverview

/SAPAPO/POV1

Typic-allyseveraltimes aday

Check the planning situationfor products with alerts,violated restrictions, values ofspecified characteristics.



APO PlanMonitor

/SAPAPO/PMON

Depending onyourbusiness needs

Key figurevalues

Check key figure valueswhether they are inside thedesired value range.Eventually compare activeversion with simulationversion(s).





2.3.9 Business Process Step 9: Convert Planned Orders into Production Orders (APO)Planned orders are converted into production orders within the APO system by setting the conversionindicator (individually or collectively). The changed in-house production orders are then transferred to theconnected SAP ERP OLTP system(s).


Apart from safeguarding the general availability of the system components SAP APO and SAP ERP OLTP,SAP recommends that you monitor the objects listed in the Best Practice document dedicated to CIF andthose listed in the following table in order to safeguard this business process step.




© 2010 SAP AG page 26/47

Jobs Necessary to Convert Planned Orders into Production Orders (APO)

The following job must be scheduled on a regular basis to ensure that after reaching the opening period,

planned orders are converted into production orders: Mass conversion of orders in the active planning version with APO report

/SAPAPO/RRP_ORDER_CONVERSION. You can limit the selection of orders to be converted byentering the product, location, production planner, and an offset to the opening period. The openingperiod is defined in the tab PP/DS in the Product Master maintenance screen and is used to controlwhich orders will be converted. The opening period is a number of work days from the current date.The APO system will only set a conversion indicator for the orders that have an order start date withinthis period.You can automatically detect planned orders for which the scheduled conversion date lies in the pastby the means of BP&IMon in SAP Solution Manager. If this is the case, Solution Manager can createalerts in the business process monitoring session to make you aware of this backlog situation. Adetailed list of all affected planned orders is provided, too.

Monitoring Recommendations Without SAP Solution ManagerMonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO report/SAPAPO/RRP_ORDER_CONVERSION






MonitoringType

Monitoring Object Key Figure PossibleBusiness

ProcessImprovements

MonitoringFrequency / Data

Collection


Planned Orders Orders withopeningdate in thepast


Daily


Reports:

/SAPAPO/RRP_ORDER_CONVERSIONCancellation Early detection of

problems ->minimize delay inbusiness process




2.3.10 Business Process Step 10: Automatic Order Conversion (ERP)Triggered by the conversion in APO, the relevant planned orders are automatically converted into productionorders in the ERP System -- or into process orders, when using Production Planning for the Process Industry(PP-PI).

In ERP, the usual steps are performed: the components are copied from the ERP planned order, the ERProuting is re-determined, and ERP lead time scheduling occurs (which is important for generating a standardcost estimate, even when using APO). In an ERP standard cost estimate, the operations are scheduledaccording to the ERP scheduling parameters you set. Components are scheduled based on the componentassignment in the ERP routing. One result of this temporary production order (which is not yet saved) is thatthe operation dates do not correspond with the scheduling situation of the APO order.

Therefore, as a last step before saving the production order in ERP, a mapping process occurs to adjust the

operations in the ERP production order to the dates of the APO operations. This is known as midpoint




© 2010 SAP AG page 27/47

scheduling. To ensure that the order duration is the same in ERP and in APO, ensure that all ERP routingoperations are transferred to the APO PPM in the ERP-APO interface.

Finally, converted orders (with status "created") are sent back to the APO system along with the productionorder number and the changed ATP category (ATP category for production order instead of planned order).Only components that are contained in an active integration model are transferred. In addition, only thoseoperations executed for resources contained in an active integration model are transferred.

Conversion of planned orders can also be done directly within the ERP system, but then the APO-plannedstart and end data of the operations are not taken over to ERP and are also lost in APO afterward.


Apart from safeguarding the general availability of the system components SAP APO and SAP ERP OLTP,SAP recommends that you monitor the objects listed in the Best Practice document dedicated to CIF in orderto safeguard this business process step.

2.3.11 Business Process Step 11: Release Production Orders (ERP)

Changes to scheduling data, quantities, resource allocations, and so on within APO are transferred to therespective ERP production orders.

In addition, changes to production orders performed in ERP will be retransferred to APO. These includechanges to quantities, release order or operation, delete order, set final issue indicator or deletion flag, batchdetermination, goods issue and goods receipt, and many more. A work center change in ERP can only bereflected in APO if the resources that represent the new work center in ERP are used in alternate modes inthe APO order (see SAP Note 629366).

The most important change is the release of production (or process) orders, which occurs in ERP in the usualway: single (CO02) or collective release (CO05N), or automatically at creation or conversion of orders by CIFtransfer.

Afterward, shop floor control documents (production order, picking list, and material staging pull list) can be

printed from ERP.

Changes to ERP orders may lead to scheduling changes in the corresponding APO orders even if thesechanges were not scheduling-relevant. Therefore, the function “Retention of APO Activity Dates” exists. Fordetails, refer to SAP Note 579758.



BP&IMon in SAP Solution Manager can be used to automatically monitor production orders where thescheduled release date is expired and to raise alerts depending on the number of orders with this kind of

backlog.

2.3.12 Business Process Step 12: Update Production Orders (APO)In CIF, releasing orders is treated in the same way as changing orders in ERP. That is, the changed ordersare again transferred to APO, where their ATP category is changed to that of a released production order.Similarly, other changes to ERP production orders are reproduced in APO.


Apart from safeguarding the general availability of the system components SAP APO and SAP ERP OLTP,there are no special objects to be monitored in order to safeguard this business step.

2.3.13 Business Process Step 13: Post Goods Issue for Components (ERP)The goods issues for the material components of the order are posted in ERP, and the stocks and the orderreservations are reduced in ERP and transferred to APO. For reduction of the order reservation, there needsto be an active integration model for manual reservations.












© 2010 SAP AG page 28/47

To keep the data volume of goods issue / goods receipt documents at a reasonable volume, you shouldensure that material documents (archiving object MM_MATBEL) are regularly archived in ERP.



2.3.14 Business Process Step 14: Confirm Order Processing (ERP)Order confirmations occur in ERP and may reduce operation quantities and remaining operation duration inboth ERP and APO. In CIF, all order confirmations are transferred as individual operation confirmations.



2.3.15 Business Process Step 15: Post Goods Receipt for Products (ERP)With posting of the goods receipt for the manufactured product in ERP, the order quantity for the receipt isreduced and the stock is increased in both ERP and APO. Using the total goods receipt for the productionorder, the quantity in the APO order is set to zero. To allow posting reversals, the order is not deleted.

To keep the data volume of goods issue / goods receipt documents at a reasonable volume, you shouldensure that material documents (archiving object MM_MATBEL) are regularly archived in ERP.



2.3.16 Business Process Step 16: Settle Production Orders (ERP)Variance determination and settlement of orders occur in ERP only and do not influence APO.


Apart from safeguarding the general availability of the system components SAP APO and SAP ERP OLTP,there are no special objects for monitoring in this business step.

2.3.17 Business Process Step 17: Close Production Orders (ERP)If you close a production order after settlement by setting the status “technically complete” or “closed,” or bysetting the deletion flag in ERP (with individual or collective processing), the production order is deleted in

APO, but not in ERP. To maintain performance, you must ensure that the APO orders are deleted regularly,and that ERP orders are regularly archived.

To archive production orders, only one archiving object (PP_ORDER) is required (PR_ORDER for PP-PIprocess orders). The settings for an archiving object and the scheduling of the archiving jobs are performed intransaction SARA. Production orders can be archived independently of other archiving programs. Thereorganization of orders is divided into three steps in the ERP system:

Activate a deletion flag in the order

Activate a deletion indicator in the order

Execute an archiving sessionOrders that have already been archived can be displayed again in the ERP system using a fourth step, calledthe retrieval function.




© 2010 SAP AG page 29/47

An order can only be archived after a deletion flag has been activated for it, either manually or automaticallyvia a background report. After an initial residence time has passed, the orders that have been flagged fordeletion are assigned with deletion indicators in a background run. After a second residence time, the ordersare archived and simultaneously deleted from the database.

Note: PP/DS orders may not be deleted in a productive APO system in any way other than that describedabove. Report /SAPAPO/RLCDELETE can be used to delete SNP orders, and for PP/DS orders there is/SAPAPO/DELETE_PP_ORDER. However, these reports are designed for use in a test environment only andshould not be used on productive APO systems. For some detailed information, read SAP Notes 660194 and690887 carefully.



2.3.18 Business Process Step 18: Post Goods Issue in Delivery (ERP) After selling a product to a customer, the stock is reduced by posting the goods issue in the ERP deliverydocument (VL02) and this is communicated to APO. Like all demand and supply information for APO-relevantproducts, the new stock is considered in the next planning run. Thus, the planning circle is closed.

To keep the data volume of goods issue / goods receipt documents and delivery documents at a reasonablevolume, you should ensure that material documents (archiving object MM_MATBEL) and delivery documents(RV_LIKP) are regularly archived in ERP.


Apart from safeguarding the general availability of the system components SAP APO and SAP ERP OLTP,SAP recommends that you monitor the objects listed in the Best Practice document dedicated to CIF andthose listed in the following table in order to safeguard this business process step.

Jobs Necessary to Clean Up Obsolete Data (APO)

The following job must be scheduled on a regular basis to ensure that obsolete data is removed fromliveCache and the APO database:

Delete obsolete pegging areas with APO report /SAPAPO/DM_PEGKEY_REORG. In a make-to-order scenario, new pegging areas are created for every new sales order. These pegging areas areno longer needed after the goods issue in the delivery is posted. Not deleting this obsolete data mayresult in performance problems, for example, in transaction /SAPAPO/RRP3. See SAP Note 693767.


Monitoring

Object

Monitor

TA/Tool

Monitor

Freq.

Monitor

Time

Indicator

or Error

Monitoring Activity or

Error Handling Procedure

Respon-

sibility

Escalation

Procedure

APO report //SAPAPO/DM _PEGKEY_REORG

This reportdeletesobsoletepeggingareas.





Output ofreport/SAPAPO/DM

_PEGKEY_REORG.

SM37 orSP01

Aftereveryrun

Messages Check for number ofreorganized objects andpossible error messages.

Applicationsupport
















© 2010 SAP AG page 30/47



2.4 Alternative ProcessesIn this section, we discuss two alternative processes in case the APO system is not available for someunplanned reason. These processes are:

Perpetuation of Production Execution - to determine how long production can continue if the APOsystem is not available

Perpetuation of Planning - to switch to ERP planning as fallback

2.4.1.1 Perpetuation of Production Execution

2.4.1.1.1 Prerequisites and Assumptions

There are two cases to distinguish:1. Conversion of planned orders to productions orders in APO

2. Conversion of planned orders to production orders in ERP

The same is also valid for purchase requisitions and purchase orders.

In general, we recommend case 1, because otherwise an ERP integration of planned orders is necessary,which can be very critical to performance.

2.4.1.1.2 Functional LimitationsYou can extend the time for continued production execution without APO by increasing the productionhorizons.

You can only continue planning when APO is available again.

2.4.1.1.3 Detailed Process DescriptionCase 1 (order conversion in APO): The buffer of available production orders to continue production in ERPdepends on the number of production orders converted from planned orders in APO.The opening period is the product-specific time period during which a planned order or a purchase requisitionshould be converted into a production order or a purchase order. The longer the opening period in APO, themore production orders should be available in the queue on the ERP side. A longer opening period extendsthe time buffer to continue with production in case of an emergency.

Case 2 (order conversion in ERP): Production can continue with all planned orders available in ERP. Thisdepends on the planning result transferred to ERP.

2.4.1.1.4 Restart Regular Business Process

2.4.1.1.4.1 System Cleanup Activities

Before the system can be cleaned up, the recovery of the APO system must be completed. The followingsteps can be taken in a system cleanup:

Consistency check with transaction /SAPAPO/OM17

Restart the queues

Delta report /SAPAPO/CIF_DELTAREPORT3

New planning run within APO

Initial data load from ERP

Navigation from the alert monitor to the product view and run heuristics

A combination of:

o Initial load of sales orders and re-planning within APO

o Recovery and handling the CIF queues




© 2010 SAP AG page 31/47

2.4.1.1.4.2 Validation

The following activities can be performed to monitor the system:

1. Check dump analysis (transaction ST22)

2. Check/restart inbound/outbound queues (transaction SMQ1/SMQ2)

3. Check background tasks (tRFC; transaction SM58)

4. Check posting tasks using transaction SM13

5. Start delta report APO - ERP

6. Check the planning file (/SAPAPO/RRP_NETCH)

7. Check the applications log (for CIF, transaction /SAPAPO/C3; for PPDS, /SAPAPO/RRPLOG1)

8. Check the result of the APO alert monitor /SAPAPO/AMON1 (re-planning in case of deficits)

9. Check the trace file (current COM trace)

10. Check DB Syslog

11. Check locks (transaction SM12)

12. Perform the consistency report /SAPAPO/OM17

2.4.1.1.4.3 Process Start

Restart the CIF queue.

Perform a re-planning based on the alert situation.

2.4.1.1.5 Follow-Up ActivitiesMonitor the planning (see above).

2.4.1.2 Perpetuation of Planning

2.4.1.2.1 Prerequisites and AssumptionsWe consider this a viable solution only if you used ERP production planning and switched to APO PP/DS onlya short time ago.

2.4.1.2.2 Functional LimitationsIn the case of planning in ERP, not all APO features are available. Examples in PP/DS are dynamic setup,PP/DS optimization, finite planning, and many features of the DS planning table.

2.4.1.2.3 Detailed Process DescriptionThis has to be defined in a major implementation project that includes the steps of a normal implementationproject, including separate customizing and detailed validation of the process (only master data common inAPO and ERP can be reused).

2.4.1.2.4 Restart Regular Business Process

2.4.1.2.4.1 System Cleanup Activities

Before the system can be cleaned up, the recovery of the APO system must be completed. The followingsteps can be taken in a system cleanup:

Consistency check with /SAPAPO/OM17

Restart the queues

Delta report

New planning run within APO

Initial data load from ERP

Navigation from the alert monitor to the product view and run heuristics A combination of

o Initial load of sales orders and re-planning within APO




© 2010 SAP AG page 32/47

o Recovery and handling the CIF queues

2.4.1.2.4.2 Validation

The following activities can be performed to monitor the system:

1. Check dump analysis (transaction ST22)

2. Check/restart inbound/outbound queues (transaction SMQ1/SMQ2)

3. Check background tasks (tRFC; transaction SM58)

4. Check posting tasks using transaction SM13

5. Start delta report APO - ERP

6. Check the planning file

7. Check the applications log (for CIF, transaction /SAPAPO/C3; for PPDS, /SAPAPO/RRPLOG1)

8. Check the result of the APO alert monitor (re-planning in case of deficits)

9. Check the trace file (current COM trace)

10. Check DB Syslog

11. Check locks (transaction SM12)

12. Run the consistency report /SAPAPO/OM17

2.4.1.2.4.3 Process Start

Restart the CIF queue.Perform a re-planning based on the alert situation.

2.4.1.2.5 Follow-Up ActivitiesMonitor the planning (see above).

2.5 Related Tools and ActivitiesThis Appendix explains:

1. APO Alert Monitor

2. Monitoring APO Planning Activities and the Planning Situation

3. Publishing of APO Planning Results to SAP ERP

4. Maintenance of PP/DS Related Master Data

5. Fixed Pegging

2.5.1.1 APO Alert Monitor

The APO Alert Monitor allows a management-by-exception strategy, so it is of special concern in this andother APO business process scenarios. The Alert Monitor (transaction /SAPAPO/AMON1) is a standalone

component of APO that enables you to have a unified approach to handling problem situations. It notifies youif a problem occurs during an ATP check or SNP run, or when production plans, demand plans, or vehicleschedules are being generated in one of the APO applications.

The Alert Monitor is a tool with which planners can monitor the state of a plan. The monitoring results can beused to readjust the plan whenever necessary. The purpose of the Alert Monitor is to inform planners if acondition of a plan has been violated. The Alert Monitor belongs to the suite of supply chain monitoringcomponents in APO, together with the Supply Chain Cockpit (/SAPAPO/SCC02), which also can displayalerts) and the Plan Monitor (/SAPAPO/PMON). It can be used by any supply chain manager or planner whopractices 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)




© 2010 SAP AG page 33/47

The Alert Monitor is a fully integrated APO application transaction that you can adapt to your needs by settingup profiles for all of the above APO areas.

To track PP/DS alerts in APO, maintain the PP/DS Alert Profile. The profile allows you to maintain a user-specific selection of alerts corresponding to your area of responsibility. You can set it up to track alerts ofinterest to individual planners, or to track alerts by specific locations, products, or resources.

The PP/DS Alert Monitor profile contains a number of alerts specific to production planning and detailedscheduling. PP/DS alert types are divided into the following groups:

Alerts on relationships between orders or operations, for example:

On dynamic pegging

On time relationships

Alerts on orders, for example:

On shortages

On days‟ supplies

Alerts that occur during planning using a procurement planning heuristic (Exception for ProcurementPlanning )

Alerts on resources, for example:

On resource capacity usage

On container resources

Alerts for activities on a resource:

On interruption of activities

About violation of synchronization

Alerts for campaigns

Alerts for container resources

Alerts for target stock and safety stock levels

Alerts for procurement scheduling agreements

Alerts for sales scheduling agreements

PP/DS alerts--with the exception of the alert type Exception for Procurement Planning --are dynamic alerts.This means that they only exist in the SAP liveCache and are not stored in the database.

Alert priorities are identified by icons displayed in the profile or in the monitoring slots of the Supply ChainCockpit control panel. The three possible priority levels in the Alert Monitor are:

1. Error2. Warning3. Information

Alert types are automatically assigned certain priority levels, but they can be changed in APO Customizing.To further refine the priority of alerts, you can define threshold values in cases where they make sense. Anexample of variants for a capacity overload alert is:

Info alert if the overload is between 100% and 120% Warning alert if the overload is between 120% and 150%

Error alert if the overload exceeds 150%

The system generates alerts for the items and alert types you included in your selection for the time frameand planning version you defined in the initial settings screen. You can view the alerts in the Alert Monitorwindow ( Alert Monitor → Display alerts). You can also take action on alerts in the Alert Monitor window (right-click for the context menu).

To track the ERP MRP alerts in APO, you must maintain the ERP MRP Alert Profile. MRP alerts refer to theresults of a materials requirements planning run. In the Alert Monitor, you see a frozen display of the latestMRP run. This profile contains an automatically generated list of ERP systems connected to your APOsystem. To see the alerts in APO, you must create a user view in the ERP system in which you want to trackMRP alerts.

To support the Alert Monitor's function as a tool for exception-based management, you can send messagesvia e-mail to other planners to inform them of the alert situation. You can also have messages sentautomatically to your own inbox to inform you of alerts in your area.




© 2010 SAP AG page 34/47

You can maintain a list of favorite Alert Monitor profiles so you can switch back and forth easily betweenvarious profiles. For example, you may have an alert profile for your own area of responsibility, but you mayalso want to look at alerts in other areas.

Most PP/DS alerts are not stored in the database, but are determined dynamically. Alerts that are stored inthe database include ATP, Forecast, SDP, VS and TLB/Deployment; when these alerts are no longer in use,they must be deleted regularly from the database using report /SAPAPO/AMON_REORG. There are alsoPP/DS database alerts (only alert type Exception for Procurement Planning ). These are only possible formessages that have a reference to a pegging area (product, location, and so on, for example, message/SAPAPO/RRP_HEUR 032: Product x in location y could not be planned).

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 on the SAP APO documentation CD under Supply ChainMonitoring - Alert Monitor .

2.5.1.2 Monitoring the APO Planning Activities and the Planning Situation

2.5.1.2.1 Monitoring Activities

Depending on the type of planning activity (production planning run, interactive production planning, productplanning table, detailed scheduling planning board, product view, and so on), the success or failure of theactivity is logged in the PP/DS planning and scheduling logs and can be displayed using transaction/SAPAPO/RRPLOG1. You will find scheduling-relevant information in the scheduling log, for example, forscheduling problems on the resources, and quantity and product-related information, such as missingcomponents, in the planning log.You can call the planning log for the planning run in which a selected product was last planned. The functionis available for production planning runs with procurement planning heuristics. In the Log for Last PlanningRun view (/SAPAPO/RRPEVAL), the system displays the message with the highest priority for the log

number instead of showing all messages that occurred during product planning. You can double-click on thelog number to branch to the planning log. You can also navigate in the product view, the product overview, orin the product planning table.

To be able to react quickly to planning exceptions and problems, it is important to get to know and use the APO Alert Monitor .

Jobs Necessary to Monitor APO Planning Activities and the Planning Situation (APO)

To ensure timely information for planners on the current planning situation, and for performance reasons,certain jobs must be scheduled on a regular basis. These jobs are:

Delete PP/DS logs with report /SAPAPO/SAPRRPLOG_DELETE. Delete old logs from planningactivities regularly to keep up the performance of the related transactions.

Send Alert Monitor mails with report /SAPAPO/AMON_MAIL_BROADCAST. Depending on userprofiles maintained in transaction /SAPAPO/AMONMSG, mails are sent with an overview of existingalerts. The responsible persons then should call the APO Alert Monitor, investigate the reasons forthe alerts, and take corrective actions to keep the production plan close to the needs of yourcompany.

Delete Alert Monitor alerts with report /SAPAPO/AMON_REORG. Deletes alerts that are older thana specified age.This is only relevant for PP/DS as far as database alert types are being used – most PP/DS alerts aredynamic and are not stored in the database (see APO Alert Monitor , above).




© 2010 SAP AG page 35/47

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APOPP/DS log

/SAPAPO/RRPLOG1

Aftereachplanningrun, afterplanningboardactivities

Yellow orredindicators

Read diagnosis and systemresponse of the messagelong texts and follow thedescribed procedure.

Application support and / orprocess champion mustdecide whether:- Planning job results are asdesired- Results must be correctedinteractively- Planning run must berepeated

Applicationsupport


APOPP/DS logfor aspecifiedproduct

/SAPAPO/RRPEVAL

Asrequired Yellow orredindicators

Read diagnosis and systemresponse of the messagelong texts and follow thedescribed procedure.

Application support and / orprocess champion mustdecide whether:- Planning job results are asdesired- They must be correctedinteractively- Planning run must berepeated

Applicationsupport Contactprocesschampion

APO report

/SAPAPO/SAPRRPLOG_DELETE

This reportdeletesPP/DSlogs.

SM37 Weekly Status Check if job is running as

scheduled.

If the report is not scheduledon a regular basis, scheduleit to run once a day anddelete logs older than acouple of days.

Program

schedulingmanagement

Contact

softwaremonitoringteam

APO AlertMonitor

/SAPAPO/AMON1

At leastdaily

Check for PP/DS alerts andcorrect the planning andscheduling for the reportedobject appropriately.

Applicationsupport


APO report/SAPAPO/ AMON_MAIL_BROADCAST

This reportensuressending ofmails aboutexistingalerts.


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



AlertMonitormails

SO01 (orrespective e-mail

system)

Depend-ing onyour

require-ments, atleastdaily

Check if the mail lists alertsthat are important for you.

Go to APO Alert Monitor andprocess the alerts.

Applicationsupport





© 2010 SAP AG page 36/47

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO report/SAPAPO/ AMON_REORG

This reportdeletes AlertMonitoralerts.


If the report is not scheduledon a regular basis, scheduleit to run once a day.



APO reportSBAL_DELETE

This report

deletesobsoleteapplicationlogs.


If the job is not scheduled asprovided by Application

Support, schedule it to runweekly.



APOOptimizerLog

/SAPAPO/OPT11

Aftereachoptimizerrun

Exception Check whether the log file isflagged yellow or red. In thiscase, investigate themessages in more detail.


Contactapplicationsupport orsystemmonitoringteam,depending onerror

APO

performance monitor

/SAPAP

O/PERFMON

From

time totime; ifyouexper-iencelongruntimesorproblemswith theoptimizer

Log entries Analyze optimizer trace file

and identify problem cause. Ifin doubt, open a customermessage in SAPNet R/3 frontend.

Application

support

Contact

systemmonitoringteam or SAP,depending onthe problem

User list foroptimizers

/SAPAPO/OPT03

In caseofproblems

Activeoptimizerusers

Identify long-running orcancelled users.



APO report/SAPAPO/OM_REORG_DAILY

This reportdeletes oldoptimizerlog filesand lockentries.


If the report is not scheduledon a regular basis, scheduleit to run daily.






© 2010 SAP AG page 37/47

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO report/SAPAPO/OM_TB_LCHECK_CDPSOPT

This reportchecks thePP/DSoptimizerinterface.

SLG1 Afterinstall-ation orupgrades; ifproblemsarise ortheoptimizerdoes notanswer

Yellow orred light

Execute the report intransaction SA38 with defaultsettings and check theapplication log beingdisplayed (or go totransaction SLG1). If allmessages have a green light,everything is okay.


Contactsystemmonitoringteam

2.5.1.2.2 Error Handling, Restartability, and Escalation

2.5.1.2.2.1 Error Handling Procedures

Error handling for background jobs is explained in detail in the SAP ERP 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 mayneed to take action. Consider the status of the job and proceed as follows:

In the case of status scheduled, the job steps have already been defined, but the start condition has notyet been defined. Contact the program scheduling management to clarify when the job will be fullydefined.

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

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

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

In the case of status finished, all steps that make up this job have completed successfully. Programscheduling management must check whether the job ran in the given timeframe, and the softwaremonitoring team and/or application support must check the respective job results, such as spool outputlists, message logs, and updates.

In the case of status canceled, the job has terminated abnormally. This can happen in two ways. If anadministrator intentionally canceled the job, find out why, and if and 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 SAPstandard program, search for appropriate messages in SAPNet and create a customer message if youcannot solve the problem.

If there are problems with the CIF or with data missing in either ERP or APO, see the TroubleshootingGuide Integration R/3 – APO, R/3 Plug-In homepage, Literature Center .

2.5.1.2.2.2 Process Step RestartabilityIf a background job is canceled, consider any following jobs or dependencies on other jobs when decidingwhether to restart the aborted job. The aborted job may also delay the start of following jobs.

2.5.1.2.2.3 Escalation Procedures

In general, we recommend that you search for related SAP Notes in the SAPNet R/3 front end for anyunknown problems or errors.

If you have questions or problems that cannot be solved, forward the issue to the next support level.If the corresponding escalation path is not well defined, contact application support.

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







© 2010 SAP AG page 38/47

If none of the defined support levels can provide a solution for some problem, we recommend thatyou create a customer problem message in the SAPNet R/3 front end.

2.5.1.3 Publishing APO Planning Results to ERP


These are basically the same as for the data transfer from ERP to APO (see the Best Practice document dedicated to CIF) and, additionally, the surveillance of the publishing report itself.

Jobs Necessary to Publish Planning Results to ERP OLTP System (APO)

To ensure that the planning results are published to ERP and that the relevant data is consistent in bothsystems, certain jobs must be scheduled on a regular basis. These jobs are:

Publish planning results with report /SAPAPO/RDMCPPROCESS. This report evaluates the APOchange pointers (not the same as ALE change pointers!) that are written during planning activities.The corresponding objects, such as planned orders, are sent to ERP.

Check processing of APO change pointers with report /SAPAPO/RDMCPPROCESS. This reportverifies that all change pointers are processed by checking that the list displayed in report/SAPAPO/RDMCPPROCESS is empty. If change pointers remain unprocessed, contact theapplication support team to clarify whether these change pointers are needed and why they are notprocessed. Note: Deleting change pointers may cause inconsistencies, as the corresponding orderchanges are not transferred to ERP.BP&IMon in SAP Solution Manager provides the functionality to monitor unprocessed changepointers automatically and to raise alerts depending on the number and type of expired changepointers that were detected.

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO report/SAPAPO/RDMCPPROCESS

This reportpublishes theresults ofautomatic andinteractiveplanning toERP.

SM37 Depend-ing onyourneeds,daily orat leastonce aweek





APO report/SAPAPO/RDMCPPROCESS to displaychangepointers

SM37,

SolutionManager(BP&IMon)

Weekly Status Check if job is running asscheduled.

If the report is not scheduledon a regular basis andperiodic publishing ofplanning results is used,schedule it to run once a day.



2.5.1.3.2 Error Handling, Restartability, and EscalationSee general issues of Error Handling, Restartability, and Escalation, above.

2.5.1.4 Maintenance of PP/DS-Related Master Data


Besides the maintenance of master data resulting from business requirements, for example, creation of newdata and deactivation or deletion of obsolete data, or updates of texts or planning settings that effect APOmaster data, there is also the need for technical maintenance of certain objects.




© 2010 SAP AG page 39/47

Jobs Necessary to Maintain APO Master Data

To ensure that the planning-relevant master data is technically okay and does not cause planning runs to end

in error, certain jobs must be scheduled on a regular basis. These jobs are:

Extend the available capacity of a resource with report /SAPAPO/CRES_CAPACITY_LENGTHEN. Forperformance reasons, you should only generate the available capacity for the time period for which youwant to schedule the resource. Since the planning-relevant data of a resource is not changed regularly,as a rule, the available capacity that reaches into the future and that can be used for planning getsshorter as time progresses, while the part that reaches into the past gets longer.The report determines the validity period of the resource relative to the point in time at which it isexecuted. It then deletes the part of the available capacity that is outside the validity period in the past forthe selected resources, and extends the available capacity into the future until the end of the validityperiod. Note that manual changes to the available capacity (e.g., additional shifts) that are in the pastoutside the newly generated validity period are also deleted by the report without any warning. Ifmessages appear while report /SAPAPO/CRES_CAPACITY_LENGTHEN is being executed in the

background, the person responsible (that is, the user who is logged on in the background job!) receivesan express document.For more information see SAP Note 550330.

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO report/SAPAPO/CRES_CAPACITY_LENGTHEN.

This reportextends theavailable

capacity of aresource.

SM37 Weeklyormonthly,depend-ing onyourbus-iness

process





APOapplication log

SLG1 Aftereachrun

Log entriesexist

Check if there are log entriesfor object „RESOURCE‟.

Applicationsupport


APOSAPofficeinbox

SO01 Aftereachrun

Expressmessage

Check whether there aremessages being sent by thereport in background (seeabove).There is no detailedinformation in this message;you have to check theapplication log instead.

Applicationsupport


APO spooloutput

SP01 Aftereachrun

Check displayed statistic forcompleteness andplausibility.

Applicationsupport


2.5.1.4.2 Error Handling, Restartability, and EscalationSee general issues of Error Handling, Restartability, and Escalation, above.

2.5.1.5 Fixed PeggingFixed pegging is used in APO to fix document flows (even multilevel document flows). The system transfersthe existing fixed-pegging relationships from a preceding document (for example, a planned order) to thesuccessor document (for example, a production order). Fixed-pegging relationships are preserved ondocument changes or document flows in SAP APO if triggered in SAP APO or SAP ERP. This ensures that

the fixed-pegging relationships between the receipt and requirement elements remain intact in productionplanning and during production execution. Therefore, fixed pegging increases transparency in planningsituations. In integrated processes using the Core Interface (CIF), you have the option to activate the retainfunctions for fixed pegging. If fixed pegging is used, certain restrictions or procedures apply to processes.








© 2010 SAP AG page 40/47

For detailed information, read SAP Notes 458996, 698427, and 704583 carefully to get an overview aboutsupported document changes and document flows.


You can call the pegging overview for the product that was last planned. The pegging overview offers allmonitoring functionality to display fixed-pegging relationships for a product. Alternatively, the context view canbe used to display fixed pegging for a selected order.

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO peggingoverview

/SAPAPO/PEG1

Depend-ing onyourbusin-essprocess

Status Check, create, change, ordelete fixed peggingrelationships.



2.5.1.5.2 Error Handling, Restartability, and Escalation

Besides monitoring functions of fixed pegging, the APO application log displays appropriate warnings or errormessages with regard to fixed-pegging relations. Use APO pegging overview to change or correct fixedpegging in SAP APO, if necessary.

MonitoringObject

MonitorTA/Tool

MonitorFreq.

MonitorTime

Indicatoror Error


Respon-sibility

EscalationProcedure

APO peggingoverview

/SAPAPO/PEG1

On error Status Repair fixed peggingrelationships.



APO

application log

/SAPAP

O/C3

On error Status Check whether reduced or

deleted fixed-peggingrelationships are listed inapplication log.

Repair them if necessaryusing APO Pegging overview/SAPAPO/PEG1.

Business

processchampion

Contact

applicationsupport
















© 2010 SAP AG page 41/47

3 Further Information

3.1 Troubleshooting

3.1.1.1 Dependencies

There are dependencies (date and time, or logical sequence) between business processes and processsteps that are not mentioned in this Best Practice. For example, these may comprise:

General SAP ERP system administration (this also applies to the SAP Netweaver Basis of the APOsystem) such as:

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 logso Updating table statistics for the DB cost based optimizer – You should not run this activity at times

when application programs are likely to be creating, deleting, or updating many table entries.

General APO-specific system administration:

o Checking internal (liveCache – APO DB) and external (APO – ERP) 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 SAP ERP 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 packagesof master data to APO when CIF is needed for the transfer of transactional data, because this canoverload CIF and cause an undesirable communication delay.

Because of these dependencies, online and background application system activity cannot always occurwhenever desired, but may need to wait, for example, for the completion of administration activity.

Therefore, program scheduling management and the software monitoring group should plan and schedulesystem 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 framesdetermined by the business process champions. Also, certain activities – such as background jobs – shouldbe started only after the respective preceding activity has finished.

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

See the Troubleshooting Guide Integration R/3 – APO, which you can find in SAPNet,R/3 Plug-In homepage, Literature Center .

Search for related SAP Notes

Open a SAP customer message describing your problem

3.2 Background Information and References

3.2.1.1 Literature

For more detailed information about how to administer an SAP NetWeaver system, see:

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

For information about the administration of SAP APO systems, see:

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





http://service.sap.com/notes









© 2010 SAP AG page 42/47

Liane Will, SAP APO System Administration, 2002

For information about how to monitor and tune general system performance, see:

Thomas Schneider, SAP Performance Optimization Guide, 2008

For background information on administrative tasks with emphasis on system planning and setup, see:

Hartwig Brand, SAP R/3 Implementation with ASAP , 1999

3.2.1.2 Other Best Practice Documents

In the SAP Service Marketplace, quick link /scm → Related Topics / Best Practices for Solution Operations(or directly under /solutionmanagerbp), you can find several Best Practice documents for solutionmanagement, like this one. In particular, Monitoring and Administration for SCM / APO helps you to analyzethe workload and performance on liveCache and the APO database.Furthermore, Manage APO Core Interface in SAP SCM deals with the Business Process Management ofthe APO Core Interface CIF and is an essential enhancement to this document. All the jobs and monitoringactivities listed in the CIF document have to be considered in every business process step listed above thatsends or receives data through CIF.If you use the APO availability check (gATP) within your PP/DS process, Manage Global ATP will be ofparticular interest for you.Document Manage Supply Network Planning in SAP SCM / SAP APO deals with the operation proceduresrelated to the APO Supply Network Planning component. Manage Demand Planning in SAP SCM / SAP APO accordingly discusses the operation of Demand Planning processes. Please also pay special attention toInternal and External Consistency for SAP APO / SAP SCM , which contains information about master dataconsistency as well as internal consistency between APO DB and liveCache.There is also a setup guide available for using SAP Solution Manager to monitor the CIF interface. You canfind this document in the service market place under the quick link /bpm in the area Media Library Technical Information Setup Guide – Interface Monitoring .

3.2.1.3 SAP Documentation

SAP APO 7.0 documentation is available on CD or in the SAP Help Portal in German or English.

SAP APO 5.1 (2007) documentation is available on CD or in the SAP Help Portal in German or English.



For some more detailed information, current events, news, and so on, see the PP/DS homepage in the SAPMarketplace for SCM: http://service.sap.com/scm → Planning → Production planning .

More information regarding Business Process & Interface Monitoring in SAP Solution Manager can be foundunder http://service.sap.com/bpm.

3.2.1.4 Benchmark

The only available benchmark for PP/DS was taken for a PP/DS planning run on an APO 3.0 system. Youcan find the respective certificate under http://www.sap.com/solutions/benchmark/pdf/Cert2702.pdf .

3.2.1.5 SAP Notes

See also http://service.sap.com/notes.

The following SAP Notes contain useful information on the performance of SAP APO:

426705: Guidelines for note searching in APO-PPS

420669: Collective note: General performance improvement APO

879531: Composite SAP Note for PP/DS performance in SCM APO 4.1 980165: Composite SAP Note for PP/DS performance in SCM APO 5.0

1146538: Composite SAP Note for PP/DS performance in SCM APO 2007 5.1







https://websmp203.sap-ag.de/bpm






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



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















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



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


















http://www.sap.com/solutions/benchmark/pdf/Cert2702.pdf











































© 2010 SAP AG page 43/47

1271308: Composite SAP Note for PP/DS performance in SCM APO 7.0

See the Best Practice document dedicated to CIF for SAP Notes with information on qRFC and CIF.

The following SAP Notes contain useful information on PP/DS:

134164: Optimizer RFC connection error

143314: APO - R/3 Integration in Production Planning

195157: Application log: Deletion of logs

307336: Object locked by user

331664: APO PP/DS: Material status

362208: Creating de-allocated orders in APO

385602: Validity in APO (Documentation)

390850: Scrap in APO and R/3 (documentation)

393437: Pegging in APO: Background information 393634: Release of the optimization server after terminations

394184: No subsequent processes after LiveCache initialization

397989: PP/DS: Scheduling (Documentation)

403050: Consulting note: Release from DP to SNP

413822: Safety stock in APO PP/DS (documentation)

417461: Scheduling error transferring orders to APO

426563: CTP: Settings, system behavior, and performance (documentation)

435366: BAdI for additional checks when converting orders

439596: Notes on Customizing planning processes

441102: Consulting notes in PPDS 441740: Planning time fence in APO: Documentation

448960: Net requirements calculation (documentation)

449565: Integration with CDP in APO (Characteristics Dependent Pl.)

457657: Search function for planned orders in application log

457723: Planning period with PP heuristics

458996: Fixed pegging in SAP APO (documentation)

459694: Finite scheduling with CTP or SAP_MRP_002 (documentation)

481906: SNP - PP/DS integration (documentation)

495166: Tips and tricks for handling Alert Monitor

507469: Why a maximum of 500 receipt elements per product?

513827: Settings/parallel processing in the PP/DS planning

517178: Relationship violations

518556: Using heuristics in the production planning run

519070: Planning without final assembly

520561: Maintaining product master in R/3 or in APO?

522569: BW: Working in several clients (especially APO 4.x/SCM 4.x)

525571: MOP: Function restrictions

528913: Lock R/3 data transfer during SNP, CTM, PP/DS planning

532979: Pegging in optimization

551124: APO: Finite scheduling with MRP heuristic (documentation)

550330: Consulting note about APO resources































































































































© 2010 SAP AG page 44/47

557731: Planning file entry + reuse mode (documentation)

560683: Resource selection for the PP/DS optimization

560969: Rescheduling: Bottom-Up (SAP_PP_009)

565972: FAQ: External procurement in PP/DS

572003: SCM operating concept

572996: Simultaneously started optimization runs

575624: Locking concept in APO PP/DS (documentation)

577158: Withdrawal from alternative plant in APO (documentation)

578044: Additional parameters for optimization

579758: R/3->APO: Retaining APO scheduled activity dates

582212: External planning (Documentation)

584051: Multiresource planning (primary resource) (documentation)

584204: Planning standard lots for continuous I/O (SAP_PP_C001)

591115: MRP areas in APO (documentation)

594982: Push production (documentation)

601990: External relationships (documentation)

606320: R/3 data transfer during PP/DS optimization run

606334: Overlap of activities after PP/DS optimization run

607428: Product planning table – FAQs

613189: Documenting heuristics

613601: Scope of ATP check of production orders

615877: Integration/delta report manufacturing orders: Performance

619898: Production in another location (documentation)

619976: Special procurement types in APO (documentation)

622428: Time management in PP/DS optimization

627377: Consulting Note : Model-Mix-Planning and Sequencing

630565: Guidelines for SAPNet - R/3 Frontend notes in PP/DS Optimizer

641858: Acceleration of the transfer to APO with mass transaction

660113: Performance: Setting up DS planning board for Release 4.0

660194: RLCDELETE does not delete the selected orders

660857: MOP FAQs: Answers to frequently asked questions about MOP

663297: Strategy settings for planning (documentation) 664022: Setting of performance functions

679118: Which operations are performed by /SAPAPO/OM_REORG_DAILY?

681656: Objective function in PP/DS optimization

689101: PP/DS optimization consulting

690887: Deletion report: No list display of undeleted orders

693767: //DM_PEGKEY_REORG inadvertently deletes pegging areas

695027: Changes in the APO-Quicksizer Q1/2004

695534: Long runtime for the optimization or MRP run

698427: Fixed pegging: supported document flows and document changes

703774: SCM 4.1: Importing an APO Optimizer version 704583: Fixed pegging in APO: symptoms and restrictions

709884: Consulting notes for PDS and ERP-PDS








































































































































© 2010 SAP AG page 45/47

711235: Project Manufacturing with SCM 4.1: Collective Note

712066: Restrictions of the PP/DS optimizer

723201: Strategy settings for planning of standard lots

778261: Prerequisites for secondary resources

784955: Displaying the log after Model-Mix-Planning and Sequencing

808671: PP: liveCache alerts out of the given validity are displayed

830673: AMON: Some consulting issues when handling alert monitor

834838: Planning board: No dialog box f. performance warning

849711: PP and DS strategy in detailed scheduling planning board

857475: SCM 5.0: Importing an APO optimizer version

876700: Project manufacturing with SCM 5.0: Composite SAP note

876821: Make-to-order production with SCM 5.0: Composite SAP note

918653: Improvement of performance for publication of MRP results

948426: Connection of SCM alerts to the portal

961569: Object selections in production planning run

1019666: Installing SCM Optimizer Version 5.1

1052331: /SAPAPO/RRPLOG2 is not deleting old logs in the system

1086885: FAQ: Component product allocations in the CTP check

1090435: MRPDS release note

1101409: LPP: Functionality restrictions for SCM 5.1 and 7.0

1126611: Docu: Fix pegging heuristic/sorting by penalty cost group

1132030: Rounding rule for calculation of shelf life expiration date

1148602: APO - R/3 Integration in Production Planning

1167150: Usage of Mode priority

1167216: Usage of Product Priority

1167219: Handling order conversion in dynamic setup scenario

1216588: Importing SCM Optimizer Version 7.0

1283261: Reducing the runtime of a planning run

1296446: Resource utilization in planning board and reporting

1315243: Consulting: MRP optimization

1330236: Flow manufacturing: Scheduling of minimum send-ahead qty

1363145: Invalid product-location combination for parallel MRP 1366621: APO-Add-On: Missing Parts Infosystem

1406424: Implementation recommendations for APO 7.0 PP/DS

1418362: Fault tolerance scheduling in both directions

1436825: Activity ends at 24:00:00 while block end time is 23:59:59

3.2.1.6 Feedback and Questions

Send any feedback by formulating an SAP customer message to component SV-SMG-SER. You can do thisat http://service.sap.com/message.









































































http://service.sap.com/message











































© 2010 SAP AG page 46/47

3.3 Index /SAPAPO/AMON_MAIL_BROADCAST 16, 35

/SAPAPO/AMON_REORG 16, 34, 35/SAPAPO/AMON_SETTING 16

/SAPAPO/AMON1 16, 18, 31, 33, 36

/SAPAPO/AMONMSG 16, 35

/SAPAPO/BACKGROUND_SCHEDULING 14, 15

/SAPAPO/C3 31

/SAPAPO/C4 21

/SAPAPO/CDPS0 25

/SAPAPO/CIF_DELTAREPORT3 31

/SAPAPO/CRES_CAPACITY_LENGTHEN 39

/SAPAPO/DELETE_PP_ORDER 29

/SAPAPO/DM_PEGKEY_REORG 30

/SAPAPO/MC8K 12

/SAPAPO/MC8x 11

/SAPAPO/MC90 11

/SAPAPO/OM_REORG_DAILY 15, 16, 37, 42

/SAPAPO/OM_TB_LCHECK_CDPSOPT 15, 37

/SAPAPO/OM17 31

/SAPAPO/OPT03 15, 37

/SAPAPO/OPT11 15, 36

/SAPAPO/PEG1 40

/SAPAPO/PERFMON 15, 37

/SAPAPO/PMON 25, 33

/SAPAPO/POV1 25

/SAPAPO/PPT1 25

/SAPAPO/RDMCPPROCESS 21, 38

/SAPAPO/READ_ALERTS_BATCH 16

/SAPAPO/RLCDELETE 29

/SAPAPO/RPT 25

/SAPAPO/RRP_NETCH 31

/SAPAPO/RRP_ORDER_CONVERSION 26

/SAPAPO/RRP1 11

/SAPAPO/RRP3 25, 30

/SAPAPO/RRPCUST1 20

/SAPAPO/RRPEVAL 14, 34/SAPAPO/RRPLOG1 14, 31, 34

/SAPAPO/SAPRRPLOG_DELETE 15, 35

/SAPAPO/SCC02 33

/SAPAPO/SDORDER_DEL 13

/SAPAPO/SDRQCR21 13

/SAPAPO/TS_BATCH_LOGFILE 12

/SAPAPO/TS_BATCH_RUN 11

CO02 28

CO05N 28

MC74 13

MC87 13

MD05 23

MD06 23

MRP 20, 22

RDELBALS 14, 16

RFINDLOG 14

RMMDMONI 24

RMMDPERF 24

RMMPS000 23

RMMRP000 23

RMMRP010 23

RZ11 15

SARA 29

SBAL_DELETE 16, 36

SLG1 15

SM12 31

SM13 31

SM58 31

SMQ1 31

SMQ2 31

ST22 31



© Copyright 2010 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9,iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes,BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporatedin the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of CitrixSystems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, MassachusettsInstitute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented byNetscape.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer and other SAP products andservices mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and othercountries.Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, andother Business Objects products and services mentioned herein as well as their respective logos are trademarks or registeredtrademarks of SAP France in the United States and in other countries. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this documentserves informational purposes only. National product specifications may vary.The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any formor for any purpose without the express prior written permission of SAP AG.This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This documentcontains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP toany particular course of business, product strategy, and/or development. Please note that this document is subject to change and may

be changed by SAP at any time without notice.SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of theinformation, text, graphics, links, or other items contained within this material. This document is provided 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 have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages thatmay result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you mayaccess through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provideany warranty whatsoever relating to third-party Web pages.