Consistency Checks

Internal and External Consistency
for SAP APO 3.x and SAP SCM 4.x / 5.x

Best Pra ctice for Solution Management
Version Date: May 2009
This document refers to the data consistency between SAP R/3 or SAP ERP and SAP APO 3.X, SAP
SCM 4.X / 5.X and within SAP APO 3.X, SAP SCM 4.X / 5.X.
Contents
Applicability, Goals, and Requirements................................................................................................2
Preliminary Information .......................................................................................................................4
Procedure .....................................................................................................................................6
Consistency Checks................................................................................................................6
Checks for Internal Consistency ..............................................................................................8
External Consistency Checks ................................................................................................22
The Consistency Check Process ...........................................................................................34
Executing the Consistency Check .........................................................................................36
Further Information ...........................................................................................................................41
Best Practice: Internal and External Consistency for SAP APO (3.x) and SAP SCM (4.x, 5.x)
Applicability, Goals, and Requirements

Goal of Using this Service
The aim of this document is to ensure consistency between SAP APO and your OLTP system, and
consistency between the SAP DB and liveCache within your SAP APO system. This document
describes the necessary tools and measures.
It supports you during the development and implementation of a consistency-oriented interface and
system management concept by:
Suggesting procedures and sequences for consistency checks according to the business
processes that you want to map with your SAP APO system.
Giving operation and performance notes for individual consistency checks
Listing the areas of responsibility for monitoring and executing consistency checks.
Alternative Practices
You can also book an on-site Solution Management Optimization (SMO) service known as SAP
Interface Management service, whereby SAP experts support you in drawing up a data consistency
concept.
Staff and Skill Requirements

To implement this Best Practice, you require the following teams:
Application Management Team
The Application Management Team should create the SAP SCM / SAP APO business process
management concept specified in this Best Practice. This team combines experts from several areas
of your company:
Business department
Solution support organization (for example, the IT department and the Help Desk)
Implementation project team
Execution Teams
The execution teams are the following groups, which are taken together from your Solution Support
Organization:
The Business Process Champion for each business process
Application Support
Development Support
Program Scheduling Management
Software Monitoring Team
System Monitoring Team
More information about roles and responsibilities of these teams can be found in the superordinate
Best Practice General Business Process Management, which you can obtain through SAP Solution
Manager.
2009 SAP AG
Necessary or Useful Training Courses:

ADM355 APO System Administration
PDEF08 LiveCache Administration
TTW060 SAP APO Technical Administration
TEWA60 SAP APO livecache Monitoring
SCM210 Core Interface APO
2009 SAP AG
Preliminary Information
This Best Practice is based on the most common integration scenario for setting up an SAP Supply
Chain Management (SAP SCM) solution using SAP Advanced Planner and Optimizer (APO) or SAP
Supply Chain Management.
The main components of an SAP SCM system landscape are summarized in the following table and
shown schematically in the subsequent illustration.
SAP APO System
The SAP Advanced Planner and Optimizer system facilitates the strategic,
tactical, and operational planning processes.
SAP APO consists of several software components: a relational database
system (RDBMS) as in any SAP R/3 or SAP ERP System, called APO DB;
an SAP R/3 Basis; the APO application programs; a separate, very fast,
object-oriented SAP DB database called liveCache; and a number of
programs that execute the optimization algorithms, called optimizers. These
components can run on the same or on different servers.
OLTP System
The Online Transaction Processing system covers functions for sales and
distribution, material and inventory management, controlling, shop floor
control, logistic execution, and so on.
OLAP System
An Online Analysis Processing system, such as SAP Business Information

Warehouse (BW), provides accumulated historical data for future
extrapolation purposes in APO Demand Planning.
OLTP
System
SAP R/3 Plug-In

RDBMS
SAP APO
System
live
Cache
OLTP
System
RDBMS
2009 SAP AG
RDBMS
RDBMS
SAP R/3 Plug-In
SAP AG
OLAP
System
In the following sections, we will refer to SAP R/3 and SAP ERP simply as SAP ERP.
The various strategies for using SAP ERP and SAP SCM in combination are called integration
scenarios.
The SAP APO system is connected to one or more SAP ERP OLTP systems via the Core Interface
(CIF), which transfers all relevant data between them. The CIF uses queued remote function calls
(qRFCs) to ensure the desired sequence and transactional security of data transmissions. For
information about solution management for CIF, see the Best Practice Manage APO Core Interface in
SCM.
You may also use OLTP systems other than SAP ERP. These systems cannot use the CIF for a
connection to the SAP SCM system, but SAP provides BAPIs (Business Application Programming
Interfaces) for programming data supply between third party systems and SAP APO. This scenario is
not covered in this document.
The SAP APO is the planning component of SAP SCM. SAP APO is used to make strategic, tactical,
and operational decisions and supports you in performing the following planning activities:
Demand Planning (DP)
Supply Network Planning (SNP)
Production Planning (PP)
Detailed Scheduling (DS)
Deployment
Transport Load Builder (TLB)
Transport Planning and Vehicle Scheduling (TP/VS)
Global Available-to-Promise (gATP)
SAP APO is primarily a planning tool, although some industry-specific execution functions are
available (such as production backflush for repetitive manufacturing).
In standard business scenarios, execution functions such as confirmations, goods receipt, purchasing,
and so on are performed in the SAP ERP OLTP system, which contains all functionality for (among
many others) Material Management (MM), Sales and Distribution (SD), Production Order Processing
(PP-SFC), Logistics Execution (LES), and Controlling (CO).
2009 SAP AG
Procedure
Consistency Checks
Overview
Implementing an SAP APO system in your system landscape increases the demand on your interface
management and system administration due to the following technical requirements:
The data required for planning is held in the liveCache database, which is stored in main
memory. This data is also stored in the SAP DB. For example, this occurs in liveCache 7.2
when savepoint is written. The consistency of the information shared by these two storage
media is called internal consistency.
Implementing SAP APO in your system landscape increases the data exchange between the
systems. In particular, a close connection is created between the SAP ERP systems and SAP
APO. Getting SAP ERP data in real-time is a prerequisite for successful planning activities in
SAP APO. This data is exchanged between SAP APO and the dedicated SAP ERP systems. It
is therefore essential that the data in SAP APO and the connected SAP ERP systems remains
consistent. This type of consistency is known as external consistency.
Causes of Inconsistency
There is inconsistency between the systems if one or more of the following has occurred:
Incomplete recovery in one of the systems in the system group
Incomplete recovery of liveCache or APO DB
Manual change to (master)data in SAP ERP or SAP APO
Program errors due to bugs or modifications/user-exits leading for example, to dumps or
update errors
Incorrect intervention in the CIF interface, for example, deletion of orders without transfer to
SAP APO
End-user error
SAP provides standard tools for checking internal and external consistency.
How you use the tools depends largely on the solution you have implemented with SAP APO.
The basic procedure recommended by SAP is first to establish internal consistency within SAP
APO and then to check the external consistency between one SAP APO system and one
dedicated SAP ERP System. Depending on the checked objects, it might be necessary to check
first the internal consistency of SAP ERP as a leading system before running the external
consistency (Example: Report SDRQCR21 and table VBBE).
As of SAP SCM 4.0 and SAP R/3 with at least Plug-In 2003.1 SAP recommends running CIF
Postprocessing after completion of master data issues and internal consistency but before
starting external consistency checks.
If more than one SAP ERP System is connected to an SAP APO system, you must use the
corresponding tool for each of these SAP ERP Systems and the SAP APO system.
2009 SAP AG
The following tables show important tools with relation to the SAP APO applications used.
Table 1: Tools for Checking Internal Consistency
Check Tool
PP/DS
Consistency Check for resources

/SAPAPO/REST021
As of SAP SCM 4.0 report
/SAPAPO/CRES_CAPACITY_LENGTHEN
should be used for the extension of time
streams
Consistency Check for Setup Matrices

Z_MATRIX_CONSISTENCY_CHECK1
TP/VS Checks
/SAPAPO/VSCC1
Consistency check for DP and SNP

/SAPAPO/TS_LCM_CONS_CHECK
Consistency check for schedule line
agreements and scheduling agreement
confirmations
/SAPAPO/PWB_KILL_INCO1
Orders
Z_CHECK_CONSISTENCY_ORDERS1
Order operations
Z_CHECK_CONSISTENCY_OPERATIONS1
Product allocations TA
/SAPAPO/ATPQ_CHKUSG
/n-handling for CTP rep.
/SAPAPO/DMOPR_REORG_CTP
ATP
DP
SNP
TP/VS
VMI
CTM
X
X
X
X
Model and version management TA

/SAPAPO/MVM (after model changes, pure
administrative tool)
Product Variants
/SAPAPO/CONFR_CHECK_VARIANTS 3
Model consistency check
/SAPAPO/CONSCHK for relevant master
data (for example, locations, resources, and
so on)
Check is included in new transaction /SAPAPO/OM17 for APO 3.1 and higher releases.
Check is included in /SAPAPO/CIF_DELTAREPORT3 as of SCM 4.0
Available as of SCM 5.0
2009 SAP AG
BOP
Table 2: Tools for Checking External Consistency

Check Tool
PP/DS
ATP
/SAPAPO/CIF_DELTAREPORT3
RCIFORDER_RESERVATIONS_COMPARE2
X
X
/SAPAPO/SDRQCR21
/SAPAPO/VSCC1
Schedule line agreements and scheduling

agreement confirmations
/SAPAPO/PWB_KILL_INCO1
Configuration
/SAPAPO/RCUIB_DELETE_CFG
RCUIB_SEND_CONFIGURATION
IPPE R/3
APO
Report IPPECIF_EKG_COMPARE
Runtime Objects
/SAPAPO/CURTO_ORDER_EXPLODE
Product Variant Configuration TA
/SAPAPO/COMP_VARIANT
DP
SNP
CTM
TP/VS
VMI
X
X
X
X
If you are using SAP 4.1/5.x, many of the consistency checks in tables 1 and 2 are available in
transaction /SAPAPO/OM17. See also the documentation for this transaction in the SAP Service
Marketplace or SAP Note 425825 for further information.
Checks for Internal Consistency

Transaction /SAPAPO/OM17 is the main tool for an overall internal consistency between liveCache
and APO-DB.
SAP recommends that you perform consistency checks during a posting-free period of time. If you
cannot do this, it is possible that inconsistencies between liveCache and the SAP APO database that
existed only briefly will be displayed. In this case, re-check the inconsistencies that were displayed
(Ctrl+F2: Button Check again).
If the inconsistencies are still displayed after the check, you can assume that the inconsistencies did
not only exist temporarily. You can then use the appropriate transaction to correct them.
It is recommended to execute the program in the background (F9 or Menu Path Program
in Background.
Execute
After running the report in background it is possible to use the functionality Evaluate Last Background
Job.
Backorder Elimination in Capable-to-Promise

The Capable-to-Promise (CTP) process is based on the use of ATP (Available-to-Promise) and PP/DS
(Production Planning & Detailed Scheduling) functions. In the CTP process, components and
capacities are visibly reserved for parallel transactions during sales order creation. This occurs before
the sales order is saved. If the sales order is not saved, the reservation of the components and
capacities must be taken back. This means that the procurement elements that were created
temporarily must be deleted again. If you terminate the sales order transaction in a controlled fashion,
that is, using the corresponding menu options or buttons, the system calls an ABAP function that
deletes the orders that are to be deleted in liveCache and in the database. If, however, you end the
transaction with /N, the system activates the task handler, which takes control of the data in
liveCache. The task handler ensures that the order data is deleted from liveCache. However, it cannot
prevent some order data remaining in the database. This remaining data is simply descriptive data
that it is not relevant for planning. You can eliminate the backlog using report
/SAPAPO/DMOPR_REORG_CTP.
2009 SAP AG
BOP
For more information on running the report, see SAP Notes 413127 (FAQs for CTP) and 426563.
Prerequisites
A prerequisite for using the check report is that you use the CTP scenario.
Process
You can plan report /SAPAPO/DMOPR_REORG_CTP to run regularly (for example, weekly) in the
background. You cannot and must not define variants. Parallel processing is not necessary as the
runtime is not critical.
Result
The program run deletes the reservations of components and capacities. A results list is not created there is no need to process or work through the results.
Internal Consistency Check for Setup Matrixes

As of SAP APO 3.1, you can execute the consistency check for setup matrices using transaction
/SAPAPO/OM17.
In SAP APO 3.0, program Z_MATRIX_CONSISTENCY_CHECK is available through SAP Note
589136. This program makes the same checks as transaction /SAPAPO/OM17 in higher releases.
Program Z_MATRIX_CONSISTENCY_CHECK checks the consistency of the data in liveCache and
the database. There is an option to generate the inconsistent setup matrixes in liveCache. You can do
this using program /SAPAPO/MATRIX_TO_LC_SEND.
Normally, the setup matrices are updated in SAP liveCache when you save the set up matrixes.
However, if a connection error occurs, the update must be repeated.
Prerequisites
As well as the case described above (connection error to liveCache), we also recommend running the
report before each consistency check for resources.
Process
Execute transaction /SAPAPO/OM17.
Result
You can view the results list in the application log (transaction SLG1). Note that this log is not stored
under the user name. You can find it under the object APO and sub-object PPDS.
Internal Consistency Check for Resources

As of SAP APO 3.1 you can run this consistency check report using the central transaction
/SAPAPO/OM17.
The internal consistency check for resources checks that the relevant data exists in liveCache and
compares the data. (Transaction /SAPAPO/REST02 - also, from the initial screen of resource
maintenance in menu Tools
liveCache Check)
You can select various options on the selection screen of the report.
Check existence in LC - liveCache check: Checks which resources do not exist in liveCache and
produces a list of these resources.
Save non-existent resource LC - liveCache save: Checks the resources and generates missing
resources in liveCache. The system displays a red traffic light for resources that cannot be saved
in liveCache and issues a corresponding error message in the results list.
Save selected resource LC liveCache save: Saves all the resources to liveCache that meet the
selection criteria. The system displays a list with yellow traffic lights for those resources for which
there is a difference between the database and liveCache. The differences are highlighted in color.
2009 SAP AG
10
The system shows a red traffic light for the resources that could not be saved to liveCache.
Corresponding error messages are displayed in the results list for these resources.
You can select resources from the results list and save them to liveCache. You can also navigate to
resource maintenance by selecting resources and choosing Change resource. You can also display
the time stream in liveCache (times in UTC) by clicking the time stream GUID and you can display the
bucket vector by clicking the green traffic light in the Bucket Vector column.
There are some differences in the checks performed by /SAPAPO/REST02 compared to
/SAPAPO/OM17:
/SAPAPO/OM17 has more checks for resources than /SAPAPO/REST02
/SAPAPO/REST02 is more flexible at the selection and it can have a look at TS (time stream)
and BV (bucket vector):
OM17:
- Resource only in DB
- Different field contents DB-LC for header data
- In LC missing or different PP-Buckets
- Different field contents DB-LC for storage attributes
- Different CDP-block definition DB-LC
REST02:
- Different field contents DB-LC for header data
- Time stream
- Bucket vector
- PP- bucket vector
Goal and Prerequisites

We recommend using transaction /SAPAPO/REST02 as follows:
SAP APO 3.x:
In releases SAP APO 3.x you should use transaction /SAPAPO/REST02 in two cases:
After liveCache recovery: First, however, you must run program
SAPAPO/MATRIX_TO_LC_SEND, since there are dependencies between the resources and
the setup matrixes. Missing setup matrixes are saved to liveCache. You should then execute
transaction /SAPAPO/REST02 so that the resource data can be transferred consistently from
the SAP APO database to liveCache.
You should execute transaction /SAPAPO/REST02 at regular intervals so that the time
streams used in resources are extended. These time streams are not extended automatically
in the system: This only occurs if you plan transaction /SAPAPO/REST02 at regular intervals.
SAP SCM 4.x, 5.x:
In releases SAP SCM 4.x, 5.x. transaction /SAPAPO/REST02 is obsolete and transaction
/SAPAPO/OM17 can be used instead.
Technical System Prerequisites

None.
2009 SAP AG
11
Process
In releases SAP APO 3.x, in the case of recovery, you should execute report
SAPAPO/MATRIX_TO_LC_SEND first, which transfers the setup matrixes back to liveCache
consistently. You can then execute the resource check either directly from the resource maintenance
menu by selecting Tools
liveCache Check, or in the background. The processing method you use
depends on the number of resources to be checked.
Performance
The runtime of the check is correlated positively with the number of resources to be checked and the
length of the time streams used. This means that an exact value cannot be determined for the runtime.
As a general rule, a value of between 2 and 4 resources can be taken, for which checks and repairs
can be executed for each second of runtime.
Consistency Check for Temporary Quantity

Assignments after a LiveCache Recovery
The following is only necessary after a liveCache recovery with SAP APO 3.0 using a liveCache
version lower than 7.4.
As of liveCache Version 7.4, the liveCache saves and restores data itself.
Some of the data of the temporary quantity assignments cannot be produced consistently after a
recovery, despite a successful checkpoint. Some quantity assignments that have already been
released exist again, and temporary quantity assignments are missing. Therefore, you MUST run
report /SAPAPO/REBUILD_TQA after every recovery. The report deletes quantity assignments that
are no longer required and generates missing quantity assignments.

The goal is to achieve consistency in the temporary quantity assignments after a recovery.
IMPORTANT: You MUST run the report only after a recovery. The report must never be run
during normal operation of the SAP APO system because temporary quantity assignments
which are still in use would be deleted.
If the report is not available (it is delivered with SAP APO 3.0 support package 21), you can implement
it using SAP Note 504133.
Use
You can execute the consistency check by running report /SAPAPO/REBUILD_TQA. Once you have
started the program, choose Execute and confirm the security check. The runtime can be several
minutes, depending on the data volume.
2009 SAP AG
12
Verification/Subsequent Processing
If you use ALE third-party order processing in connection with product allocation or checks
against forecasting: in this special case, it is not possible to construct all of the corresponding
persistent quantity assignments automatically, therefore you have to recheck all the orders
that were created and saved in the sales system (SAP ERP - A) but have not yet been
transferred to the delivery system (ERP - B) and updated there. You can determine the
corresponding orders using table APODELTA in the sales system (ERP - A). Call transaction
SE16 and enter APODELTA. Select table content (F7) and Execute (F8). The system then lists
all order items (DOC_NUMBER and ITEM_NUMBER) that are saved in the sales system but
that have not yet been created in the delivery system. If these order items have executed a
product allocation or a check against forecasting in SAP APO, you have to check these items
again (transaction VA02) and save them. This reconstructs the missing persistent quantity
assignments.
If you create orders in a CRM system with product allocation or checks against forecasting,
using persistent quantity assignment: In this special case, it is not possible to construct all the
corresponding persistent quantity assignments automatically, therefore, you have to recheck
all the orders that were created and saved in the CRM system but have not yet been
transferred to the connected SAP ERP system and updated there.
For details on the procedure, see SAP Note 435827.
Consistency Check for Temporary Quantity

Assignments
See Best Practice Manage Global ATP and note 488725 about temporary quantity assignments and
how to use report /SAPAPO/OM_DELTA_REMOVE_OLDER.
Internal Consistency Check for Procurement

Scheduling Agreements
You can run this consistency check report using the central transaction /SAPAPO/OM17.
You can use report /SAPAPO/PWB_KILL_INCO to re-establish consistency of the scheduling
agreements. You can make the consistency check either using the central transaction /SAPAPO/OM17
or with enhanced possibilities by using transaction SE38 directly.
Report /SAPAPO/PWB_KILL_INCO corrects scheduling agreements and releases and confirmations
(only available in SAP APO 3.1 and above) if they fulfill the following inconsistency criteria:
The number of input and output nodes is different but not 0.
Orders that have no input but that have materials maintained in the vendor location and are
contained in a planning version. These orders could lead to errors in the future.
Orders, which have different quantities before they have been consumed in the source and target
locations.
The cumulated quantity of goods receipt and goods issue in liveCache must correspond to the
database.
2009 SAP AG
13
Cross check with the set process: The order GUID Ordmap relates to the wrong order type. They
exist but are not defined in the process.
There are still OLTP scheduling agreement schedule lines although the scheduling agreement in
SAP ERP is already flagged as an SAP APO scheduling agreement.
There are still APO scheduling agreement schedule lines although the scheduling agreement in
SAP ERP is already flagged as an OLTP scheduling agreement.
Neither an outbound delivery nor a goods issue exists in the database, but they are allocated in
liveCache.
Since the data in liveCache is deleted and recreated, you must proceed with the utmost caution. You
should only use the check if inconsistencies have been noted or if liveCache crashes. In the first case,
you should focus on one scheduling agreement and in the second case you should check all of the
scheduling agreements.

The goal is the restoration of consistency between the scheduling agreements following a liveCache
recovery and a consistency check as part of a regular maintenance cycle.
First implement SAP Note 414908.
While the report is running, you must not process any planning runs, goods receipts, shipping
notifications, and so on, that affect the scheduling agreements.
Use
In the case of a recovery:
Execute the report in test mode first. This does not change the operational data in any way: It
lists all the inconsistent orders that are found. Afterwards, it is possible to correct the
inconsistent orders.
In live operation
Normally, you would not expect any inconsistencies in live operation mode. We therefore
recommend that you run the report only in test mode.
Runtime/Performance
The runtimes for the report are not critical. You can run the check in parallel. To do this, use suitable
selection criteria when creating variants for mass processing.
2009 SAP AG
14
Internal Consistency Check for In-House Production

Orders
In-house production orders can exist in liveCache that do not have any operations in the database
table for the operations /SAPAPO/OPR. This leads to planning problems.
You can use report Z_CHECK_CONSISTENCY_ORDERS to determine in-house production orders
from SAP APO liveCache for which there are no operations in the database table /SAPAPO/OPR.
These orders are displayed in a list alongside the output product.
Using this information, you can analyze the cause of the inconsistencies (for example incorrect PPM
maintenance). To rectify inconsistencies, you should plan report
Z_CHECK_CONSISTENCY_ORDERS to run weekly. If this report is not already in your system, you
can implement it using the instructions in SAP Note 539199.

To use this correction report, you must be using in-house production orders in PP/DS. This means that
you should not need to use this report in any applications other than PP/DS and CTP.
This report identifies inconsistent in-house production orders from liveCache. You should run the
report following a recovery and, where applicable, at regular weekly intervals.
You should not run the report if you execute multi-user planning. We recommend that you run the
report at a time when the system workload is at a minimum (for example at night or during
maintenance periods). It is possible to run other consistency checks or repair reports at the same time.
Internal Consistency Check for Operations

You can run this consistency check report using the central transaction /SAPAPO/OM17.
The database table for operations, /SAPAPO/OPR, may contain operations that do not have any
orders in liveCache, do not have any operations for a simulation version, or do not have an external
operation number. These operations are an unnecessary load on the database table and can lead to
poor system performance in some cases.

Before you execute the consistency check, you must implement report
Z_CHECK_CONSISTENCY_OPERATIONS from SAP Note 458854. This report deletes unnecessary
operations from the database. This improves system performance and reduces the load on the
database (only valid for SAP APO 3.0).
Use
Redundant information is deleted from liveCache and the database. We recommend that you run this
report weekly.
In test mode (UPDATE flag not set), the system simply issues a log of possible inconsistencies.
Depending on the results, you can start the report again with the UPDATE flag set. The superfluous
data records are deleted from table /SAPAPO/OPR. No further activities are required.
2009 SAP AG
15
Internal Consistency Check for Product Allocations

You can check the internal consistency for Product Allocations with central transaction
/SAPAPO/OM17.
In product allocation, the incoming order quantities are updated directly in liveCache through a direct
connection to the planning area. Using transaction /SAPAPO/ATPQ_CHKUSG, you can compare the
data in liveCache with the product allocation in the database. If a direct connection is not available,
both the time series and the product allocation assignment are in the database and can also be
compared with this tool. The transaction allows you to check the data and then correct it.
The following checks are possible:
Product allocation without (corresponding) incoming order quantity
You can copy the total product allocation quantity of the orders to the incoming order quantity in the
product allocation group. You should do this if you have:
Copied the planning data from the OLTP system to SAP APO using transaction QTSA,
overwriting the incoming order quantity in the process.
Transferred data from a planning area to a product allocation group, overwriting the incoming
order quantity in the process.
Changed the incoming order quantity in the planning area (using the direct connection to the
planning area)
Used the direct connection to the planning area following a liveCache crash.
Incoming Order Quantity without Product Allocation

If there is an incoming order quantity in a time series that can no longer be traced back to a product
allocation (the product allocation is no longer available), you can delete the incoming order quantity
with this tool.
Product Allocation without an Existing Order Item
In rare cases, a sales order is deleted and the product allocation remains nonetheless. You can delete
this product allocation and, in doing so, reduce the incoming order quantity accordingly.
2009 SAP AG
16
Product Allocation without Existing Product Allocation Group

You find individual assignments without characteristics combinations if the characteristic combination
has been deleted. You can also delete individual assignments here.
This function does not influence the incoming order quantity.
For more details on the individual options of the correction transaction, see the documentation on
transaction /SAPAPO/ATPQ_CHKUSG (click in the SAP Easy Access menu).
Transaction /SAPAPO/ATPQ_CHKUSG is a repair tool that you can use primarily in the rampup phase to check and correct your product allocation data. For example, if you change the
definition of the product allocation group or take the data from other systems (for example,
from an SAP ERP System or via the DP from other systems) for the transportation allocation,
this tool enables you to bring together the product allocation data with the already available
product allocation to a consistent status.
You can also use transaction /SAPAPO/ATPQ_KCGRP_U regularly. This transaction executes
the same activities as /SAPAPO/ATPQ_CHKUSG with the check for product allocation
assignment without incoming order quantity. The product allocation is compared with the
incoming order quantity. If the quantities are different, the system adjusts the incoming order
quantity automatically for all affected time series.
SAP recommends the use of the repair tools in the ramp-up phase. During the production
operation of your system, you can schedule these tools for monitoring your data consistency
on a weekly or monthly basis.
Note that for a large number of characteristic combinations and a large volume of customer
orders, the repair tools require a longer runtime.

This tool establishes consistency between the product allocation assignment of the orders and the
incoming order quantity in the product allocation time series (it does not matter whether the time series
are used with or without a direct connection to the planning area).
After a recovery, the product allocations have to be recreated in the planning area. You must then
reactivate the CIF integration model. You cannot execute the transaction until after the order data has
been transferred to SAP APO.
In operational mode, you can execute the transaction without any particular prerequisites. Note,
however, that you must not run a consistency check on the corresponding planning area
(/SAPAPO/TS_LCM_COMS_CHK) at the same time.
Use
The repair of inconsistencies with transaction /SAPAPO/ATPQ_CHKUSG is intended only for
interactive processing, where you use the result list to choose the time series for which a repair is to
be performed. Additionally, you can schedule transaction /SAPAPO/ATPQ_KCGRP_U as a
background job, by creating a batch input file for this transaction and letting this batch input file run in
the background.
2009 SAP AG
17
Consistency Check for Transportation Planning /

Vehicle Scheduling (TP/VS)
You can start the main consistency check report for TP/VS using the central transaction
/SAPAPO/OM17. This report checks the consistency between liveCache and the TP/VS anchor table
for shipments in SAP APO. Consistency means that for each shipment in liveCache, a corresponding
entry exists in the anchor table and vice versa.
Additionally, you can check the following data by selecting it on the initial screen of transaction
/SAPAPO/VSCC:
SAP APO master data that is relevant for TP/VS, for example vehicle resources, transportation
lanes, and locations
Customizing and optimization profiles
SAP ERP OLTP and SAP APO TP/VS integration customizing and transportation service
provider selection settings
If the system finds inconsistencies, they can be repaired to a certain extent using transaction
/SAPAPO/VSCC.
Transaction /SAPAPO/VSCC is primarily designed to recognize any inconsistencies. If inconsistencies
are displayed and you cannot rectify the inconsistency by navigating forward, open a problem
message.

Since transaction /SAPAPO/VSCC checks both the internal and external consistency of transportation
planning data, all other consistency checks for external consistency must previously have been
executed using /SAPAPO/CIF_DELTAREPORT3, and the relevant data must have been made
consistent. This means that the consistency check for transportation planning should be the last
check to be executed.
Use
The consistency check for TP/VS can be scheduled daily. As well as running report
/SAPAPO/VS_CONS_CHECK online, you can also schedule it with corresponding variants.
We are not aware of any performance bottlenecks, but you should check the runtime for a consistency
check in your productive environment. It is possible to perform checks in parallel by creating an
individual variant for each data object type for background processing. This means that you can run a
check for Customizing, master data, shipments, and so on.
You process the results using the list produced at the end of the check. You can branch to the
corresponding transaction to process the data by double-clicking on the relevant message of the
individual check results. You can then work through the inconsistencies.
If you run the check in the background, you can display the results using the application log
(transaction SLG1). Depending on the error priority, you may have to run a new check for the
corresponding data object type or rectify the inconsistency directly based on the error message.
2009 SAP AG
18
Internal Consistency Check for SAP APO Models

and Versions
The model consistency check checks that the master data assigned to a model or work area is
complete and that it can be used as a model in SAP APO without inconsistencies. It provides you with
important information about the current status of the master data and whether it is suitable for SAP
APO planning functions.
IMPORTANT: You have to run the model consistency check when maintaining master data or after
activating the integration models (master data transfer). The model consistency check performs logical
checks only and does not make any technical checks (such as checking liveCache consistency). A
technical check, for example, the consistency between liveCache and the Database, can be done by
transaction /SAPAPO/OM17.

The goal is the consistency check results in an overview of the (in)completeness of the master data
objects within the model concerned. Missing data (for example, coordinates of a location are
initialized) will be displayed by error, warning or information messages. It can be checked and if
necessary be corrected from the log.
A prerequisite for using the consistency check is that a check profile is entered that defines which
master data objects are checked.
Use
You use online transaction /SAPAPO/CONSCHK to start the model consistency checker. You can
also run the check in background processing from the initial screen.
In case of a high data volume, use transaction SM36 to create a background-processing job for report
/SAPAPO/CONSCHK and run it in cycles. It is possible to perform checks in parallel by creating a
variant for each master data object for background processing.
A log file is issued after you have run transaction /SAPAPO/CONSCHK interactively. You can navigate
to corresponding maintenance transactions directly from this log file to correct the inconsistencies.
During background processing, the log file is written to the database and can be processed
subsequently using transaction /SAPAPO/CONSSHOW. This subsequent processing is no different to
that of the online consistency check.
Consistency Check for Locations in SCM

Report /SAPAPO/CHECK_LOC has many check options for location-specific fields (for example,
geographical coordinates) and also different result options (for example, show warnings and errors
versus show errors). In addition, the report can check and reorganize different location tables, for
example, /SAPAPO/LOCMAP.
2009 SAP AG
19
Report /SAPAPO/DELETE_LOCATIONS is a housekeeping tool to clean up old locations that are not
and will not be needed anymore. All directly mapped table entries belonging to such a location will
also be deleted. Only locations that are indicated by a Deletion Flag (LVORM) = X or a temporary
location flag (OSTA_FLAG) are deleted. The number of locations with a deletion flag can be seen in
table /SAPAPO/LOC.
Internal Consistency Check for Demand Planning,

SNP Time Series and SNP Master Data
Report /SAPAPO/TS_LCM_CONS_CHECK_ALL checks all the existing time series networks of
Demand Planning. Inconsistencies are displayed for each planning area and version but they cannot
be repaired.
Report /SAPAPO/TS_LCM_CONS_CHECK makes the same checks as report

/SAPAPO/TS_LCM_CONS_CHECK_ALL but only for a selected planning area and, if required, for
each planning version. You can activate the 'Repair' option here.

This report is used to keep planning areas consistent in SNP and DP. The following consistency
checks are made:
Storage buckets profile in liveCache: The system first checks that the storage bucket profile
exists and then checks that the start dates of the time buckets and the weighting factors are
correct. The storage buckets profile settings of the planning area are checked (see transaction
/SAPAPO/TR32). Inconsistencies cannot be repaired here. However, inconsistencies here are
very rare (an example would be if the fiscal year variant were subsequently changed).
Inconsistencies can only be repaired by recreating (initializing) time series. Planning data
cannot be restored if you do this.
Key figure descriptions in liveCache (SAP SCM 4.x): The system checks whether the
descriptions for the used key figures in the planning area exit and are correctly created in the
liveCache. Using the repair option, inconsistencies in the key figure descriptions can be
repaired.
Time series: The system checks all the characteristic combinations into the planning object
structure (database) to see whether the associated liveCache anchor and all associated time
series exist in liveCache. Missing anchors or time series are created. These time series are
created with an INITIAL status. If data is lost during a liveCache crash, it has to be restored
(by restarting a planning run, by reloading historical data from an Info Cube, or by some other
action)
liveCache Anchors: The system checks all the liveCache anchors for the respective planning
area to see whether the associated characteristic combinations exist in the planning object
structure. Anchors for characteristic combinations that do not exist anymore will be deleted
when running the Consistency Check in repair mode
DP relationships: Here, the system checks the planning object structure and associated
aggregates to see that all the relationships exist. It also checks whether there are any
redundant relationships. Missing relationships are created; redundant ones are deleted. If the
data still exists in the associated planning object structure, DP relationships can be completely
restored (with the exception of fixing information). If time series of the planning object structure
were recreated with initial values after a liveCache crash, this initial information is also
adopted into the DP relationships. When restoring time series of the planning object structure
(see above), the DP relationships are adjusted automatically.
2009 SAP AG
20
DP BOM relationships (as of SAP SCM 4.X or SAP APO 3.0, support package 19 (extended
form 25)/APO 3.1 support package 03 (extended form 17) or SAP Note 458666 (extended
form 636465)): The system checks the existing characteristic combinations and master data to
see whether all the relationships between dependent characteristic combinations exist in
liveCache. (Characteristic combinations are dependent if they have the same PPM and the
same free characteristics.) The system also checks whether the BOM coefficients of the PPMs
are consistent with the coefficients in liveCache. A prerequisite for checking the DP BOM
relationships is that all characteristic combinations exist. Missing BOM relationships are
created, changed BOM coefficients are adjusted.
DP Seasonality checks: Here, the system checks if the planning area is relevant for
Seasonality. If so, the system checks if all characteristic combinations have a seasonal pattern
assigned, if the assigned seasonal patterns are valid, if the periodicities used in the seasonal
patterns match with one of the periodicities in the storage bucket profile of the planning area
and if the liveCache objects for each used seasonal pattern matches their configuration in the
seasonal planning settings.
If time series are used in an SNP planning area in Supply Network Planning, the
/SAPAPO/TS_LCM_CONS_CHECK report can also be used to check this time series network and
repair inconsistencies, if required. This report is used in the same way here as it is in Demand
Planning. It is also possible for the SNP master data to be checked and corrected.
However, report /SAPAPO/TS_LCM_CONS_CHECK_ALL cannot be used for SNP planning areas.
As of Support Package 17, and in extended form as of Support Package 19, you can also check the
consistency of SNP data that is stored in time series. For more details, see SAP Notes 446360 and
441398.
If time series are used in an SNP planning area in Supply Network Planning, the report
/SAPAPO/TS_LCM_REORG_SNP can also be used. This report is used in a similar way to the report
/SAPAPO/TS_LCM_REORG in Demand Planning. For more details, see SAP Note 669287.
Use
The consistency check using report /SAPAPO/TS_LCM_CONS_CHECK can be run independently of
other activities in SAP APO. Multiple planning areas or versions can be processed in parallel. To do
this, you might have to create several variants for report /SAPAPO/TS_LCM_CONS_CHECK.
However, if the Repair option is set, any inconsistencies within the chosen planning area and planning
version are repaired. If it is set, no other processes are allowed to be active for the chosen
planning area. To ensure this, a corresponding locking logic has been provided in SAP Note 543304
and Support Package 22.
You should run report /SAPAPO/TS_LCM_CONS_CHECK regularly in check mode (daily, for
instance). You do not have to restrict other system activities here.
Before performing planning runs in the background, you should run the
/SAPAPO/TS_LCM_CONS_CHECK report in repair mode. No activities with data changes should
take place in time series in the version for the planning area.
This means that no other activities are allowed to take place within the planning area, version, and
time series combination to be checked.
CIF changes to orders do not cause problems. It is also possible to plan in a different planning area of
the same version.
2009 SAP AG
21
The type and number of inconsistencies are the decisive factor in implementing the repair mode. If a
check mode does not find any errors, you do not have to run the procedure for preventing concurrent
system activities or repair mode.
If there are a large number of inconsistencies, repair mode might have to be used more often than
described above to reduce errors in day-to-day planning.
Depending on the processing mode, the report provides a list of all the inconsistencies in the version
and the planning area.
If repair mode is active, inconsistencies are repaired automatically. However, this does not apply to the
storage buckets profile in liveCache.
Any storage bucket profile inconsistencies cannot be repaired. However, inconsistencies here are very
rare (an example would be if the fiscal year variant was subsequently changed). Inconsistencies can
only be repaired by recreating (initializing) time series. Inconsistent master data/PPM cannot be
repaired, either. This has to be done manually or by reactivating or deleting the PPM from the relevant
models.
2009 SAP AG
22
External Consistency Checks

As mentioned previously, you should usually schedule the tools for checking and restoring external
data consistency after those for checking and restoring internal data consistency. Different tools are
available depending on the application being used.
External Consistency Checks Using CIF

Postprocessing
As of SAP SCM 4.0 and SAP R/3 Plug-In 2003.1, CIF error handling can be used for the change
transfer of transaction data. It ensures that all queue entries are processed during the data transfer.
Faulty objects no longer lead to queue blocks; instead, they are logged in Postprocessing records.
You can then call these Postprocessing records in CIF Postprocessing, rectify the errors, and
retransfer the objects to the relevant target system. The original sequence of transfers is retained for
this.
CIF error handling offers you the following options:
The logging of faulty transfers in Postprocessing records
A program for Postprocessing the faulty transfers
A jump to the application log
The Postprocessing of faulty transfers by new transfers to the target system.
The possibility of creating notes for Postprocessing records in order to support processing in
several steps or by different processors (available as of SAP SCM 4.1).
A message issued to the person who triggered the faulty transfer (for example, through an
order change) using SAP Office Mail (Express)
See also:
Restrictions for CIF error handling that are outlined in SAP Note 602484.
You can find release information about earlier SAP R/3 Plug-In releases in the SAP Service
Marketplace under Media Center SAP R/3 Plug-in
External Consistency Checks Using

CIF_DELTAREPORT3
Report /SAPAPO/CIF_DELTAREPORT3 can be used to check the external consistency of the
majority of transaction data used in SAP APO. The object types checked in SCM5.0 are as follows
(some object type checks are not included in lower releases):
1. Manufacturing Orders
Receipt/Requirements Comparison of Production/Process Orders
Comparison of Operations for Production/Process Orders
2. Project Orders
Comparison of Receipts/Requirements for Project Orders
Comparison of Operations for Project Orders
3. Maintenance Orders
Comparison of Receipts/Requirements for Project Orders
Comparison of Operations for Maintenance Orders
Comparison of Downtimes for Maintenance Orders
4. Planned Orders
5. Purchase Orders, Purchase Requisitions, and Confirmations
6. Sales Orders, Scheduling Agreements, Planned Independent Requirements
2009 SAP AG
23
7. Inspection Lots
8. Shipments
9. Maintenance and Service Planning
10. Different kinds of Stock Quantities:
Warehouse Stock, Project Stocks, Stocks in Transit, Sales Order Stocks, Special Stock at
Vend, Special Stocks at Customer
11. Extended Configuration checks can be performed (characteristic value assignments across the
systems for different order types) starting from SAP SCM 4.1
12. Manual Reservations
13. Production Campaigns
Basically, the DELTAREPORT checks that the data exists. It then compares, for example, important
quantities and times. The level of detail varies between the different kinds of transaction data
compared.
Typical and possible cases of inconsistencies for different kinds of orders (for example for the object
type manufacturing orders) across a system landscape are
Case 1: Order missing in SCM
Case 2: Order missing in ERP and does not yet have an external number
Case 3: Order missing in ERP and already has an external number
Case 4: Order has differences in content in SCM and ERP (for example, different deadlines or
quantities)
Case 5: Order is not contained in an active integration model in ERP
You can correct these inconsistencies as follows:
Case 1: Send order to SCM
Case 2: Send order to ERP
Case 3: Delete order in SCM
Case 4: Send order to SCM or send order to ERP

Report /SAPAPO/CIF_DELTAREPORT3 ensures that the data transferred using the Core Interface
(CIF) is or remains consistent between SAP ERP and SAP APO. If inconsistencies between the
systems are detected, you can also use this tool to repair them. This report corrects problems quickly
and easily. In the majority of cases, CIF can be used to resend the missing data. However, you need
to completely understand the CIF model and integration between SAP APO and SAP ERP. This
includes knowledge about master and transaction data in the relevant SAP ERP and SAP APO
systems. If inconsistencies occur between the systems, it is always advisable to analyze the causes of
the error, to be able to rule out software errors, for example. Knowledge of ABAP is also useful to be
able to perform on-site error analyses.
Depending on the system settings in SAP APO, changes to transaction data are only listed and are
not transferred synchronously to SAP ERP. This results in these changes being identified as
inconsistencies, although they are not. Therefore, it is necessary to set a change pointer when the
data is transferred from SAP APO to SAP ERP before running /SAPAPO/CIF_DELTAREPORT3. You
use transaction /SAPAPO/C5 to do this. As of SAP SCM 4.0 existing change pointers will be displayed
in the result screen of report /SAPAPO/CIF_DELTAREPORT3 and as of SAP SCM 5.0 additional
functionality is provided to process or delete these change pointers directly from the result screen of
the report.
2009 SAP AG
24
Technical System Prerequisites

SAP APO 3.0 Support Package 19 or note 459402
PI.2001.1 with note 458164 and the associated note prerequisites.
Use
To start the report in SAP APO 3.0, you can use transaction SE38, program name
/SAPAPO/CIF_DELTAREPORT3. As of SAP APO 3.1, you can use transaction /SAPAPO/CCR.
Required entry fields are the Partner System field and at least 1 object type that you want to be
checked.
Important Notes
Choosing fewer restrictions when selecting data and selecting a large variety of object types
will cause a longer runtime of the transaction. If the quantity of data you have chosen is too
large, there is the possibility that a short dump (TIME_OUT) will occur. In this instance, you
have to run the report in background processing or reduce the quantity of data.
You should start the compare/reconcile report only if there is a small data load in the Core
Interface (for example, no initial data transfer). For instance, you could do this during the night,
when no planning runs that would generate CIF-relevant documents are taking place. Otherwise,
the report could display and send false temporary inconsistencies due to parallel processing. As
of SAP Note 496779 or SAP APO 3.0A with SAPKY30A21 it is recommended to prevent this from
happening by using iteration.
Iteration Functionality (Online and Background)
With SAP notes 496779 and 488747 applied, the iteration functions for the CIF_DELTAREPORT3 are
implemented: Due to long delta report runtimes, objects may have been changed and may no longer
be inconsistent. Temporary data inconsistencies occur during the transfer of data between SAP APO
and SAP ERP and disappear again after the transfer. Note, however, that in the case of lengthy
transfers, inconsistencies may still be displayed as errors.
You should use the iteration for the online comparison and for the comparison in the background, as
well as when saving and loading results.
When using the online comparison, the user should interactively compare the displayed incorrect
objects from the result list again (iteratively) after the DELTAREPORT3 has performed a comparison
and displayed the result. If you execute the iteration several times in a row, you can further minimize
the number of errors caused by temporary data inconsistencies.
For the comparison in the background, saving the results, and loading the results, set the indicator
Iteration. In this case, the system automatically executes the iteration when saving and loading the
results. Then, temporary errors or already solved errors are cleansed and dont appear in the result list
anymore. As a next step, a manual triggering of the update of the errors is performed.
You can also use the iteration after the reconciliation to check whether the correction was successful
or not. In this way, you can determine whether an error still exists after the reconciliation or not.
Compare/reconcile reports can be run in parallel. Define multiple variants for report
/SAPAPO/CIF_DELTAREPORT3. Avoid overlapping of the same combinations of selected
object types and product location ranges. To ensure this, you can assign a dedicated variant to
each object type (for example, sales order, production order, and purchase requisition).
2009 SAP AG
25
Online Processing
Once the compare/reconcile is complete, an output screen appears, displaying an overview of the
results. This is done separately according to documents (orders) and stocks. A line is displayed for
every object type selected on the screen for comparing, showing the following information:
Total: The number of SAP ERP objects that have been selected for comparison
Error: The total number of errors found
All other columns: Distribution of errors to individual error areas
A tab page displaying detailed lists of the individual faulty orders or stocks is displayed for every object
type that is shown to have errors in the results overview. As of SAP SCM 4.1 the comparison results
are displayed using a navigation tree on the left side and a details view on the right side of the output
screen. Tab pages are no longer used.
In the case of faulty orders and stocks, there may be an additional tab page on every tab page, or sub
nodes in the navigation tree for an incorrect object type, listing the orders or stocks for each error
area.
If required, execute a reconcile:
Choose a tab or a sub node in the navigation tree to show a detailed list of incorrect objects and
select the lines you wish to reconcile (to make multiple selections, hold down the CTRL button at
the same time).
Choose the appropriate button (for example, Send to APO) to start the reconcile.
In the dialog box that appears, confirm that you have initiated the Send.
The current state of the data is read from the database. Depending on the transaction, the data is
transferred asynchronously using the standard CIF interface of the object type.
A selection icon/deletion icon appears beside the selected lines in the Sent/Action column indicating
that the Send has been initiated for the relevant objects. An object that has a selection icon/deletion
icon cannot be processed, even if it is reselected for this purpose.
Background Processing
Up to SAP APO 3.1, the spool list is the only result of the compare function in background mode. To
view the spool list for a job that ended without errors, choose your job in the job overview (transaction
SM37), choose Spool, choose your spool list from the spool list overview, and choose Display (F6). As
of SAP APO Support Package 7, you also have access to all detailed lists of the faulty objects. To
view these, see the spool list beside the summary results overview of the comparison for documents
and stocks.
As of SAP SCM 4.0 the results of the comparison can be saved in background processing. Then they
can be loaded at a later point in time and processed afterwards. The upload is much faster than a
complete program run. However, the loaded results reflect only the inconsistencies that were found
when the comparison results were saved. Inconsistencies that were newly created in the system
afterwards are not recognized.
2009 SAP AG
26
Compare/Reconcile Report Performance

In general, the consistency compare/reconcile of /SAPAPO/CIF_DELTAREPORT3 has four stages.
Stage 1: It evaluates the integration models to be checked. The runtime of this stage is linearly related
to the size of the integration model.
Stage 2: Due to performance reasons, it selects the data parallel from SAP ERP and SAP APO. We
cannot provide a blanket statement about performance for this stage. The runtime is determined by
the relationship between filter objects and the data objects to be checked. We cannot provide a
general recommendation. For more detailed information, see SAP Note 439438.
Stage 3: It checks that the data exists in SAP APO. After the integration models are evaluated and the
corresponding data is read from SAP ERP, SAP APO is checked to see that the corresponding data
exists here. The runtime is linearly related to the size of the integration model.
Stage 4: It checks whether the APO data does NOT exist in the SAP ERP system. If you have a large
integration model, this step will have a shorter runtime.
Important notes:
For more information, see SAP Notes 439438 and 451446.
To optimize the runtime, change the block size of the filter object. We cannot provide a general
recommendation for the block size of the filter object since the ideal setting is always based on
the relationship between the filter objects and the data objects to be checked.
Compare/Reconcile Report Performance Parallel Processing

As of SAP SCM 5.0 and SAP SCM 4.1 SP5, parallel processing profiles can be maintained for the
data selection in report /SAPAPO/CIF_DELTAREPORT3 for systems SAP ERP and SAP SCM (in
transaction /SAPAPO/CCR_PAR. The parallel selection of data works block wise via RFC based on
material/plant combinations and has to be maintained in the selection screen of CIF Delta report
(variant). Parallel profiles improve performance significantly and are applicable to all object types
except transports, inspection planning and stocks.
Correction of Incorrect Sales Order Requirements

Use the report /SAPAPO/SDRQCR21 if /SAPAPO/CIF_DELTAREPORT3 cannot correct all
inconsistencies. It checks sales orders more precisely and also can check the SD Order tables.
However, only the DELTAREPORT checks inactive integration models and should therefore be run
from time to time.

Inconsistencies can basically occur due to:
Program errors
Manually deleted queues (for example, because of non resolved sysfail queues)
Modifications/ User-exits
If you use BackOrder Processing (BOP), it is strongly recommended to use this report to check the
consistency of SD order tables (/SAPAPO/POSMAPN, /SAPAPO/ORDADM_H,
/SAPAPO/ORDADM_I, /SAPAPO/SCHEDLIN). BOP relies on these tables being consistent
(particularly when using RBA). CIF_DELTAREPORT3 does not include these checks.
2009 SAP AG
27
The report is delivered in the standard version as of the following releases:

SAP R/3:
SAP R/3 plug-in 2002.2
SAP APO:
SAP APO 3.0A Support Package 22

SAP APO 3.10 Support Package11
SAP SCM 4.0 and higher releases
The report does not change any data directly in SAP APO. Instead, it sends corresponding events
from the SAP ERP System to SAP APO for correction (create/update/delete). To ensure that these
events can be created, sent, and processed correctly so that inconsistencies can be eliminated, check
that the list of notes given in SAP Note 444641 and Composite SAP note 607742 for report
/SAPAPO/SDRQCR21 are implemented.
Functions
Order and delivery requirements are first gathered in SAP APO and SAP ERP. When requirements
are determined in the SAP ERP System, reorganization may be executed in line with the functions of
the ERP report SDRQCR21 (table VBBE).
The requirements are then compared at field level (MBDAT, open quantity, confirmed quantity,
plan quantity, plant, and so on) and the corresponding create/update/delete events sent.
If the option to check SD order tables is selected, the system checks that these mapping tables in
SCM exist and are consistent.
If the report is executed in test mode, the table VBBE in the SAP ERP System with the selectable
result of the reorganization is not updated, nor are any events sent. If the report is not executed in
test mode, the VBBE table may be updated with the result of the reorganization. In addition,
events for creating, updating and deleting between SAP APO and SAP ERP are sent according to
the inconsistencies found.
Both the output of the result and the processing of the events can be controlled using different
parameters.
Recent enhancements of /SAPAPO/SDRQCR21 (implemented by SAP note 987299)
The redesign of SAP ERP report SDRQCR21 to new SDRQCR21 with Processing per position
resulted in a complete new coding compared to the previous version for regenerating the
requirements. The reason was to enable this report to run in parallel to sales order business activity
and to recognize and filter such temporary errors. To avoid redundancy, a new common interface was
created and /SAPAPO/SDRQCR21 will then also use the coding of the new SDRQCR21.
For further information regarding the new version of ERP report SDRQCR21 (by SAP note 998102)
check the Best Practice Manage Global ATP.
In addition, the following improvements were made to /SAPAPO/SDRQCR21 (by SAP note 987299)
It is possible to check specific order numbers or order items with /SAPAPO/SDRQCR21
Iteration (quite similar to the iteration of the DELTAREPORT3):
o The report first selects orders in SCM, then in ERP and compares
o In case of inconsistencies, a new check is triggered as long as the inconsistencies
disappear or the number of maximal iterations is reached.
o From one iteration step to the next, a waiting time [s] can be defined.
Table /SAPAPO/OBREF was only checked for RBA sub items. With note 987299, mapping
table /SAPAPO/OBREF is checked for all document types, also Stock Transfer Orders
delivery document flow.
2009 SAP AG
28
The product allocation assignment check can be filtered for the open orders only (flag exclude
delivered orders).
For details, see the report documentation and the F1 help for the individual selection fields.
Caution: If this report is not executed in test mode and without the iteration functionality, it should only
run at a time when no change is made to sales and distribution documents in the system.
Performance
To sustain performance of the deltareport3, the /SAPAPO/SDRQCR21 and generally GATP checks
and BOP, you need to clean up entries for closed requirements and check the consistency of SD order
tables. To do this, run SCM report /SAPAPO/SDORDER_DEL regularly. Make sure to implement the
most current version with all notes listed in composite SAP Note 553476.
In case of severe performance problems with /SAPAPO/SDORDER_DEL, check the Best Practice
Manage Global ATP for specific versions of /SAPAPO/SDORDER_DEL.
Additional Information:
Note that performance issues with /SAPAPO/SDORDER_DEL (for example, runtime is longer than
one or several days or database-related short dumps like DBIF_DSQL2_CONNECTERR), typically
occur because the SD-tables in APO have grown very large and you did not run the report for a long
time.
Therefore, first check if you have applied notes 1086364 and 1061860. If this is not sufficient,
evaluate if table /SAPAPO/CIFLOOKU contains a large number of records that do not refer to sales
orders. Then, you can use report ZAPO_LOOKU_PURGE (note 997241) in addition to handle this
table also for orders other than sales orders.
/SAPAPO /SDORDER_DEL should not run in parallel to ZAPO_LOOKU_PURGE because they can
delete the same entries in tables /SAPAPO/CIFLOOKU and /SAPAPO/CIFBEFCR, thus DEADLOCK
situations can occur!
It also recommended to schedule the report ZAPO_BEFCRIT_LOOKU_ADJUST to clean up table
/SAPAPO/CIFBEFCR in accordance with table /SAPAPO/CIFLOOKU. See notes 567601
(Unnecessary entries in the table /SAPAPO/CIFBEFCR) and 1085987 (performance problems with
report ZAPO_BEFCRIT_LOOKU_ADJUST).
External Consistency Check for Production Order

Items
/SAPAPO/CIF_DELTAREPORT3 is used to check the cross-system consistency of order reservations
for production and process orders. The delta report in SAP APO (/SAPAPO/CIF_DELTAREPORT3) up
to release SAP APO 3.1 only provides a comparison at the order header and main item level.

For SAP APO 3.X, you can use report RCIFORDER_RESERVATIONS_COMPARE to compare and, if
necessary, reconcile order reservations for production and process orders on a cross-system basis.
All production and process orders (that is, all orders that have not been technically completed, have
been deleted, or are marked for deletion) are selected according to the selection criteria in SAP ERP.
For this, orders are only considered if their end products are contained in an active integration model
for production orders for the target system specified. All order reservations relevant to SAP APO are
selected in SAP ERP and the order reservations themselves are selected in SAP APO for all orders
that meet these criteria. Then, the order reservations of the two systems are compared. Order
reservations are only compared if the orders exist in both systems. If inconsistencies exist at the order
level, these can only be found in SAP APO by using /SAPAPO/CIF_DELTAREPORT3. We
2009 SAP AG
29
recommend that you run /SAPAPO/CIF_DELTAREPORT3 before starting the comparison of order
reservations because this enables you to rectify inconsistencies at the order level before the
comparison. The comparison can determine the following, cross-system inconsistencies:
Reservations in the SAP ERP order (with quantity still relevant to MRP) that do not exist in the
SAP APO order are listed under the category Missing in APO.
Reservations in the SAP APO order that do not exist in the SAP ERP order are listed under the
category Missing in ERP.
Differences in material or plant in the order reservations are listed under the category Difference
in Material/Plant.
Differences in the quantity relevant to MRP are listed under the category Difference in Quantity.
Note that a comparison is not made for co-products and by-products.
Use
Report RCIFORDER_RESERVATIONS_COMPARE can be started in dialog mode using transaction
SE38 or in background processing if you create a suitable variant and background job. If parallel
activities in the system lead to inconsistencies being displayed that do not actually exist, you can
execute an iterative comparison that compares the orders that were identified as inconsistent again.
This significantly reduces the possibility of an inconsistency being displayed that does not actually
exist. Note that this function cannot be executed selectively (only for selected orders). The iteration is
executed for all orders that are identified as inconsistent.
You are also recommended to check in the corresponding CIF queues to see if the orders concerned
are currently in a queue.
If you are working in dialog mode, all orders with inconsistencies for order reservations are displayed
after the comparison.
To receive detailed information about the inconsistencies, you can use the Display Faulty
Reservations for Order function to display all inconsistencies along with the relevant error category
Note that this function displays the details for the order on which the cursor is currently placed.
To rectify the inconsistencies, the report enables you to retransfer the orders from SAP ERP to SAP
APO. This adjusts the orders in SAP APO to the current status of the SAP ERP orders. Once you have
done this, the orders should no longer display any inconsistencies. The block size, on the initial
selection screen is used to define the number of orders that are transferred in each LUW, when data is
reconciled from SAP ERP to SAP APO. This function is executed for all orders that you have marked
in the dialog.
After the reconciliation, you should again execute an iterative comparison to repeat the comparison for
orders that were identified as inconsistent. This enables you to check whether the orders have been
transferred correctly. Note that this function cannot be executed selectively (only for selected orders).
The iteration is executed for all orders that are identified as inconsistent.
You are also recommended to check in the corresponding CIF queues to see if the (faulty) orders
concerned are currently in a queue. You can also check this using the delta report in SAP APO.
After a comparison in the background, the inconsistencies that were found are logged in detail for
each order in the spool list. Under print options, you should select a report width of at least 140
columns to ensure that you receive all information about the inconsistent reservations in the spool list.
If the comparison is executed using Reconcile Errors Automatically, the inconsistencies that are found
are reconciled using an automatic retransfer of the orders from SAP ERP to SAP APO. Only use this
option if you have made extensive tests in dialog mode.
2009 SAP AG
30
See also SAP Notes 542805 and 538111.

Important:
As of SAP SCM 4.0 the functions of report RCIFORDER_RESERVATIONS_COMPARE are fully
contained in /SAPAPO/CIF_DELTAREPORT3, which means that report
RCIFORDER_RESERVATIONS_COMPARE is no longer necessary.
External Consistency Check for TP/VS

/SAPAPO/CIF_DELTAREPORT3 should be the first step to be executed to check external consistency
for TP/VS.
Additionally, transaction /SAPAPO/VSCC checks both the internal and external consistency of
transportation planning data, but all other consistency checks for external consistency must previously
have been executed using /SAPAPO/CIF_DELTAREPORT3, and the relevant data must have been
made consistent. For more details about using the report, see the Internal Data Consistency section.
External Consistency Check for Faulty

Configurations
Program errors, faulty transfers, or transfers that have been terminated can lead to inconsistent data
statuses for configurations in SAP APO. Possible errors could be terminations during the transfer of
configurations for example, when changing sales orders or when deleting orders. There is currently no
consistency check for configurations. The only possibility to restore data consistency is to delete the
configurations using report /SAPAPO/RCUIB_DELETE_CFG (delivered with SAP Note 457988). You
should only do this if this configuration is no longer used.
Then, the configurations can be retransferred from SAP ERP to SAP APO using report
RCUIB_SEND_CONFIGURATION. This function is the same as an initial data transfer and any
existing configurations in SAP APO are overwritten. The report only transfers configurations. It does
not transfer configured sales orders, and so on.

Prerequisites for a successful transfer:
Master data exists in SAP APO (characteristics, products, and so on)
Configured objects exist in SAP APO. This means that the sales orders exist in SAP APO, only
the configuration is faulty or missing.
Use
It is not currently possible to determine data inconsistencies for configurations. However, report
/SAPAPO/RCUIB_DELETE_CFG requires an exact specification of the configuration to be deleted.
For this reason, it is not possible to recommend a regular procedure for avoiding inconsistencies. The
tool can only be used to rectify inconsistencies that have already been identified.
After the configuration(s) have been deleted, they have to be retransferred from SAP ERP. To do this,
use report RCUIB_SEND_CONFIGURATION.
2009 SAP AG
31
External Consistency Check for Integrated Product

and Process Engineering (iPPE)
If an iPPE model is transferred to SAP APO, this model can be compared between SAP ERP and SAP
APO using the report IPPECIF_EKG_COMPARE.
You start the comparison tool by calling this report via SE38 in SAP ERP. Enter the production
versions to be compared and the relevant SAP APO system. You then receive an overview of all
inconsistencies in the iPPE model between SAP ERP and SAP APO.

The aim of this report is to ensure data consistency between SAP ERP and SAP APO for iPPE.
Use
The comparison tool can be used online or in the background. It is possible to parallelize the process
by creating suitable variants. For example, it is possible to process different plants in parallel.
External Consistency Check for PP/DS runtime

objects Production Data Structures (PDS)
As of SAP SCM 4.1 and PI 2004.1 R/3 master data can be compared with the corresponding PPDS
runtime objects in SAP APO. With report /SAPAPO/CURTO_ORDER_EXPLODE data can be
compared or if necessary transferred again.
The following options are available:
1.
Comparison of the Change Date
On the basis of the last change in SAP ERP, it can be checked if the data still has been transferred to
SAP APO or not. The following results are possible:
Inconsistent master data exist
The results are listed and can be transferred again, compared again or a protocol can be
displayed. When starting a new transfer, the existing PPDS runtime objects are overwritten.
Objects without errors get a green status. When starting a new comparison, they are no longer
compared.
No inconsistent master data exist
You are directly routed to the application log.
2.
Comparison of the Results of the Master Data Explosion
A manufacturing order is simulated on ERP and on APO side to compare the consistency of the
master data on both sides. Here, you can get a detailed list of inconsistent data. The ERP and APO
master data explosion result including operations, phases, input- and output products and
relationships are listed next to each other in a tree. It is now possible to transfer again.
2009 SAP AG
32
Comparison in the Background

For background processing, it can be determined if PP/DS runtime objects/ Production Data Structures
(PDS) should be transferred automatically, when inconsistent data has been detected or if just a
protocol should be written.
Prerequisites
This report just compares APO-relevant data like routing/recipe, production version, work center,
components. On ERP side, relevant data for creating a manufacturing order has to exist. An active
integration model for the PP/DS runtime object / Production Data Structure (PDS) has to exist as well.
Restrictions
When using customer exits or BAdIs to modify the results of master data explosion, it is necessary to
adapt them if the comparison your modifications should be taken in account.
External Consistency Check for Product Variants

The report /SAPAPO/CONFR_CHECK_VARIANTS is the APO and ERP consistency check for product
variants. It is available as of SCM 5.0.
Use
If indicator extended check is set, the system also checks whether the characteristic values of the
product variants are consistent in SAP APO and in the ERP system (plug-in).
Note: The check for the characteristic values of the product variants is very time-consuming. Only
execute the check if you suspect inconsistencies in the valuation.
External consistency check for Manual Reservations

The deltareport (Transaction /SAPAPO/CCR) is the APO and ERP consistency check for Manual
Reservations. It is available as of SCM 5.1. This also requires the corresponding SAP ERP system to
be ECC 600 or higher.
Use
If indicator Manual Reservations is set, the system checks if Manual reservations are consistent
between the two systems with regard to key attributes like date and quantity.
Reconciliation options are available like in other objects, which allow the user to retransfer the
reservation or delete it.
2009 SAP AG
33
External consistency check for Production

Campaigns
The deltareport (Transaction /SAPAPO/CCR) is the APO and ERP consistency check for Production
Campaigns. It is available as of SCM 5.1. This also requires the corresponding SAP ERP system to be
ECC 600 or higher.
Use
If indicator Production Campaigns is set, the system checks if Production Campaigns are consistent
between the two systems. The consistency may concern to the absence of the campaign in either of
the systems or a different set of planned orders contained in them. If there is an issue with the planned
orders, they need to be corrected separately first.
Standard reconciliation options are available like in other objects.
2009 SAP AG
34
The Consistency Check Process

Measures before the Check, Check, and Follow-Up
Before executing an external consistency check, you have to ensure that SAP APO is consistent
internally. The procedure and the number of checks needed depend on the applications that you want
to use in your SAP APO system. Therefore, the steps for each individual application are described
below by step-by-step lists.
The general secure procedure for internal consistency, which is independent of a specific version, is
as follows:
General remark:
It is possible that inconsistencies between liveCache and the SAP APO database that existed only
briefly will be displayed. In this case, re-check the inconsistencies that were displayed (Ctrl+F2:
Button Check again) and run the check again, for example one day later, and compare the
common errors. In case of very few or no errors after iteration, the following steps are not
necessary. In case of errors that persist during several days, you can assume after further
verification that those errors are not temporary due to other system activity.
In case of critical and/or many errors, the following procedure could be performed typically on a
Sunday when there is no or few business activity.
1. Lock the Users

For some stages of a consistency check between liveCache and the APO database, there are not
allowed to be any active processes in the SAP APO system (this depends on the object being
checked). Therefore, all users apart from administrators should be locked. Users, who are already
logged on, are not locked and they could carry on working (see next step). The descriptions of the
individual check programs specify whether a lock is required for that specific program. For all SAP
APO release levels, you can use transaction /SA PAPO/OM17 and the option Lock/Unlock Users to
activate the lock.
2. Check and End System Activities

Within transaction /SAPAPO/OM17, choose the option Overview of Active Users/Tasks/Jobs. Users
who are already logged on have to leave the system and scheduled background jobs must be stopped
for the duration of the consistency check. Messages can be sent to the users affected. Active tasks
and jobs must be terminated or you have to wait until they have finished.
3. Lock CIF Queues

Depending on the object to be checked, it may also be necessary to stop CIF queues so that data
transfers are not made from the OLTP system(s) for the duration of the consistency check.
If you are using INBOUND queues, you can stop the transfer by using report RSTRFCI1.
If you are using OUTBOUND queues, you have to use transaction SMQ1 and program RSTRFCQ1 in
the relevant OLTP system(s) to stop the transfer.
Select the Object Types to be Checked and Execute the Consistency Check
Check the results Overview and rectify the inconsistencies. For more details, see the relevant
sections.
2009 SAP AG
35
Follow-up Processing:
Unlock the CIF Queues
After the consistency checks, or once you have restored internal data consistency, you can restart the
CIF queues. If you are using inbound queues, use report RSTRFCQ3. If you are using outbound
queues, you have to restart the queues using transaction SMQ1 and program RSTRFCQ3.
Release The Background Jobs That You Stopped Earlier.
You can select from all jobs with the status 'planned' for which the start date lies between the previous
day and the following day.
2009 SAP AG
36
Executing the Consistency Check

Consistency Check for PP/DS
1. Check Procedure/Restoration of Internal Consistency for PP/DS.
Step Object for
Consistency Check
Check Tool
Check
OM17
Parallel
Frequency (APO3.1) Processing
SAP APO 3.0:

/SAPAPO/MATRIX_TO_LC_SEND
Once a day Y
if needed
Once a day Y
if needed
Limited Y
Setup Matrices
See note 589136

SAP APO 3.1, SAP SCM 4.X / 5.0:
Transaction /SAPAPO/OM17
1
Resources
SAP APO 3.0: Transaction

/SAPAPO/REST02
Pegging Areas
If needed
once per
day
Pegging Areas maketo-order scenario
SAP APO 3.X: Report

/SAPAPO/PEGKEY_REORG
SAP SCM 4.X / 5.0: Report
/SAPAPO/DM_PEGKEY_REORG
If needed
once per
month
Procurement
Scheduling
Agreements
SAP APO 3.0: Report

/SAPAPO/PWB_KILL_INCO
Only if
errors
occur
Order Operations
SAP APO 3.0: Report

Z_CHECK_CONSISTENCY_OPERATIONS
SAP APO 3.1, SAP SCM 4.X / 5.0::
Please see the following notes for

additional modification reports if needed:
458854 Reorganizing the operation table
539199 Make-to-order production orders
for APO 3.X
574976 Inconsistencies with order
status/operation status for APO 3.X
3
Campaigns
SAP APO 3.1, SAP SCM 4.X / 5.0:: Tcode

/SAPAPO/OM17
If needed
once per
day
Handling for CTP
Report /SAPAPO/DMOPR_REORG_CTP
If needed
(e.g. CTP
used) once
per week
(depends
on volume)
Models & Versions
Report /SAPAPO/CONSCHK. See results

and corrections via transaction
/SAPAPO/CONSHOW
Once a day Y
if needed
2009 SAP AG
37
2. Check Procedure/Restoration of External Consistency for PP/DS

Step Object for
Consistency Check
Check Tool
Report /SAPAPO/RCUIB_DELETE_CFG
Configuration
Check
Frequency
OM17
(APO3.1)
Parallel
Processing
After
N
Deltareport3
if needed
After delta
report 3
After Delta- Y
transfer of
iPPE data, if
needed.
If needed
Report RCUIB_SEND_CONFIGURATION
(ERP)
3
Documents and
Stocks
Report /SAPAPO/CIF_DELTAREPORT3
Parallel Processing Profile available as of
Once a day
if needed
SCM 4.1 SP 5
4
Sales Order
Requirements
Report /SAPAPO/SDRQCR21
Production Order
Reservations
APO 3.X: Report

RCIFORDER_RESERVATIONS_COMPARE
(ERP)
see note 444641
SAP SCM 4.X / 5.0:

6
iPPE
PP/DS Runtime Object As of SCM 4.0 Report

/ Production Data
Structure (PDS)
Consistency Checks for SNP, CTM and VMI

Check Procedure/Restoration of Internal Consistency
The following sequence of internal consistency checks is recommended for SNP:
Step Object for
Consistency Check
Check Tool
Check
OM17
Frequency (APO3.1)
Parallel
Processing
SAP APO 3.0: Transaction

/SAPAPO/REST02
Once a day Y
if needed
Limited Y
Once a day N
if needed
Limited Y
Resources
SAP APO 3.1, SCM 4.X / 5.0:

2
Time Series Objects
Reports:
/SAPAPO/TS_LCM_CONS_CHECK_ALL
/SAPAPO/TS_LCM_REORG_SNP
Order Operations (only SAP APO 3.0: Report

for CTM)
Z_CHECK_CONSISTENCY_OPERATIONS
Once a day Y
if needed
APO 3.1, SCM 4.X / 5.0:

4
Models & Versions
2009 SAP AG
Report /SAPAPO/CONSCHK. See results

and corrections via transaction
/SAPAPO/CONSHOW
38
Check Procedure/Restoration of External Consistency

Step Object for
Consistency Check
Check Tool
Check
OM17
Frequency (APO3.1)
Parallel
Processing
Report: /SAPAPO/CIF_DELTAREPORT3
Once a day N
if needed
After
Deltareport
3 if needed
Documents and
Stocks
SCM 4.1 SP 5
2
Sales Order
Requirements
Report: /SAPAPO/SDRQCR21
see note 444641
Consistency Checks for DP

Check Procedure/Restoration of Internal Consistency for DP
Step Object for
consistency Check
Check Tool
Check
Freq.
Report:
Once a day N
if needed
Time Series Objects
OM17
(APO3.1
Parallel
Processing
N
Consistency Checks for GATP

Product availability check: This type of availability check is carried out on the basis of the ATP quantity
(Available-to-Promise). The ATP quantity is calculated from stock, planned receipts (production orders,
purchase orders, planned orders, and so on), and planned requirements (sales orders, deliveries,
reservations, and so on). Depending on the operation, this type of availability check makes dynamic
checks with or without the check horizon, taking into account stocks and planned goods movements. A
consistency check is made as follows for this scenario:
Internal Consistency Checks for CTP

Step Object for
Consistency Check
Check Tool
Check
New OM17 Parallel
Frequency (APO3.1)
Processing
Report
Once a day N
if needed
Handling for CTP
/SAPAPO/DMOPR_REORG_CTP
2009 SAP AG
39
Internal Consistency Checks for GATP, for example, Backorder Processing

Step Object for
Consistency Check
Check Tool
Check
New OM17 Parallel
Frequency (APO3.1)
Processing
Reports:
Once a day N
if needed
Limited Y
if used
Time Series Objects
2
Product Allocations
Transaction /SAPAPO/ATPQ_CHKUSG
Check Procedure/Restoration of External Consistency for GATP, for example,

Backorder Processing
Step Object for Consistency
Check
Check Tool
Report : /SAPAPO/RCUIB_DELETE_CFG
Configuration
Check
Frequency
OM17
(APO3.1)
Parallel
Processing
Once a day
if needed
After
Deltareport
3 if needed
Report: RCUIB_SEND_CONFIGURATION
(ERP)
2
Schedule Line
Agreements
Report: /SAPAPO/PWB_KILL_INCO
Documents and
Stocks
SCM 4.1 SP 5
4
Sales Order
Requirements
Report: /SAPAPO/SDRQCR21
Production Order
Reservations
After delta
APO 3.X: Report
RCIFORDER_RESERVATIONS_COMPARE report 3
(ERP)
see note 444641
SAP SCM 4.X / 5.0:

6
iPPE
After Delta
transfer of
iPPE data,
if needed.
PP/DS Runtime Object /

Production Data
Structure(PDS)
As of SCM 4.0 Report
If needed
Internal Consistency Checks for Time Series and Product Allocation

After a recovery, the product allocations have to be recreated in the planning area. In contrast to the
usual procedure, the CIF integration model must be activated AFTER the product allocations have
been made. Transaction /SAPAPO/ATPQ_CHKUSG can only be executed after the order data has
been transferred to SAP APO. Transaction /SAPAPO/ATPQ_ALERT must then also be executed to
identify any shortfalls that may exist.
2009 SAP AG
40

Check
Check Tool
Monitor
OM17
Frequency (APO3.1)
Parallel
Processing
Report s:
Once a day N
if needed
Limited Y
Time Series Objects
2
Product Allocations
Transaction /SAPAPO/ATPQ_CHKUSG
Product allocations
Transaction: /SAPAPO/ATPQ_ALERT
After step 2 N
Consistency Checks for TP/VS

External and Internal Consistency Checks for TP/VS
Check
Check Tool
Monitor
OM17
Frequency (APO3.1)
Parallel
Processing
TP/VS internal
consistency checks
As of APO 3.1: Transaction
Once a day Y
if needed
TP/VS external
consistency checks
Report : /SAPAPO/CIF_DELTAREPORT3
Once a day N
if needed
Once a day N
if needed
/SAPAPO/OM17
SCM 4.1 SP 5
3
Additional TP/VS
external and internal
consistency checks
2009 SAP AG
Transaction: /SAPAPO/VSCC
Further Information
Troubleshooting
If the information contained in this Best Practice did not produce the desired results, check whether
the following SAP Notes provide a solution to your problem:
998102
sdrqcr21: Enhancements to support the check in parallel
987299
Report /sapapo/sdrqcr21: Iteration options
872607
Report for transferring maintenance orders
843435
Suggestions for note searching in SCM-APO-INT
625755
Performance in TP/VS: using new shipment structure
607742
Composite SAP note: Report /sapapo/sdrqcr21
602484
Restrictions CIF error handling/Postprocessing
597248
Report for the consistency check of CDP master data II
589136
Consistency check for setup matrices
587496
Reconciling APO and R/3 batch stock
574976
Inconsistencies with order status/operation status
566319
Composite Consulting note APO TP xx VS
543304
TS_LCM_CONS_CHECK: Optional lock for planning version
539199
Make-to-order production orders in LC without operations
538111
Compare and reconcile production order reservations
504133
Report for processing temp. qty. assignments after LC recovery
488725
FAQ: Temporary quantity assignments in Global ATP
481281
Documentation on delta report 3 for APO 3.0
458854
Reorganizing the operation table
451446
Delta report: Variable filter object size for data
446360
Repair tool for versions of a SNP planning area (2)
444641
Correction of incorrect sales order requirements with APO
441398
Repair tool for versions of a SNP planning area
439438
Collective note: CIF delta report performance
436527
CFC3 - Block Size Recommendations
425825
Consistency Checks, /SAPAPO/OM17, /SAPAPO/CIF_DELTAREPORT
2009 SAP AG
41
414908
Shipping notif. incorrectly consumed with sched. ag. rel.
391408
/SAPAPO/CCR comparison report reports crashes
42
If you experience problems with the delta report functions, create a SAPNet message in SAPNet R/3
front end under the component SCM-APO-INT. http://service.sap.com/message.
Literature
For more detailed information about how to administer an SAP NetWeaver System, see:
Frank Fse, Sigrid Hagemann, Liane Will, SAP NetWeaver AS ABAP System Administration,
2008
For information about the administration of SAP APO and SAP SCM systems, see:
Liane Will, SAP APO System Administration, 2002
For information about how to monitor and tune general system performance, see:
Thomas Schneider, SAP Performance Optimization Guide, 2008
For background information on administrative tasks with emphasis on system planning and setup, see:
Hartwig Brand, SAP R/3 Implementation with ASAP, 1999
Other Best Practice Documents

In SAP Service Marketplace, quick link /scm
Related Topics
Best Practices for Solution
Management: SAP SCM, you can find several Best Practice Documents for Solution Management
similar to this one.
In particular, there is Monitoring and Administration for SCM / APO, which helps you analyzing the
workload and performance on liveCache and the APO database.
Furthermore, there is Manage APO Core Interface in SAP SCM, which deals with the Business
Process Management of the APO Core Interface CIF and is an essential enhancement to this
document. All the jobs and monitoring activities listed in the CIF document have to be considered in
every business process step listed above that sends or receives data through CIF.
If you use the APO availability check (gATP), Manage Global ATP will be of particular interest for you.
Document Manage Supply Network Planning & CTM in SAP SCM / SAP APO deals with the operation
procedures related to the APO Supply Network Planning component. Manage Demand Planning in
SAP SCM / SAP APO discusses the operation of Demand Planning processes. Furthermore, there are
Manage Production Planning SAP SCM / SAP APO for the Production Planning and Detailed
Scheduling part and Manage the Transportation Management Solution in SAP SCM / SAP APO for the
APO TP/VS module.
Background Information and References

SAP Documentation
SAP APO 5.1 (2007) documentation is available on CD or in the SAP Help Portal in German or
English.
SAP APO 5.0 documentation is available on CD or in the SAP Help Portal in German or English.
Print files (PDF format) of several chapters in both languages are available in the Media Center of the
SAP Marketplace for SCM.
2009 SAP AG
43
Important: Check SAP Service Marketplace regularly to see if new notes exist for all important check
reports, for example, /SAPAPO/CIF_DELTAREPORT3. In particular, you are recommended to check
composite SAP Note 439438.
Known Problems
A heavy data load at the interface can lead to inconsistencies being reported that do not actually exist.
This is because the data that is being transferred cannot be posted fast enough. Use the iteration
functions if available or run the report again.
Root Cause Analysis

A retransfer has no effect/the inconsistency cannot be rectified.
Use qRFC monitor to check the relevant entry in the queue and then use the error number specified to
solve the issue. First evaluate if there is a master data problem, otherwise find a relevant note in SAP
Service Marketplace. If this procedure and the debugging of the relevant queue do not produce any
results, create a customer message for SAP. Provide details about the queue name and all relevant
logon data for your system.
Feedback and Questions

If you have any feedback, send an SAP customer message to component SV-SMG-SER. You can do
this at http://service.sap.com/message.
Copyright 2009 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, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,
pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner,
WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or
registered trademarks of IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems
Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks
of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts
Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by
Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, and other SAP products and services
mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several
other countries all over the world. All other product and service names mentioned are the trademarks of their respective
companies. Data contained in this document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP
Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for
errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set
forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
2009 SAP AG
44
Disclaimer: SAP AG assumes no responsibility for errors or omissions in these materials. These materials are provided as is
without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability,
fitness for a particular purpose, or non-infringement.
SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that
may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics,
links or other items contained within these materials. SAP has no control over the information that you may access through the use
of hot links contained in these materials and does not endorse your use of third party Web pages nor provide any warranty
whatsoever relating to third party Web pages.
2009 SAP AG

Consistency Checks

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Consistency Checks

Загружено:

Авторское право:

Доступные форматы

Internal and External Consistency

for SAP APO 3.x and SAP SCM 4.x / 5.x

Applicability, Goals, and Requirements

Staff and Skill Requirements

Necessary or Useful Training Courses:

An Online Analysis Processing system, such as SAP Business Information

SAP R/3 Plug-In

SAP R/3 Plug-In

Consistency Check for resources

Consistency Check for Setup Matrices

Consistency check for DP and SNP

Model and version management TA

Check is included in /SAPAPO/CIF_DELTAREPORT3 as of SCM 4.0

Available as of SCM 5.0

Table 2: Tools for Checking External Consistency

Schedule line agreements and scheduling

Checks for Internal Consistency

Backorder Elimination in Capable-to-Promise

Internal Consistency Check for Setup Matrixes

Internal Consistency Check for Resources

Goal and Prerequisites

Technical System Prerequisites

Consistency Check for Temporary Quantity

Goal and Prerequisites

Consistency Check for Temporary Quantity

Internal Consistency Check for Procurement

Goal and Prerequisites

Internal Consistency Check for In-House Production

Goal and Prerequisites

Internal Consistency Check for Operations

Goal and Prerequisites

Internal Consistency Check for Product Allocations

Incoming Order Quantity without Product Allocation

Product Allocation without Existing Product Allocation Group

Goal and Prerequisites

Consistency Check for Transportation Planning /

Goal and Prerequisites

Internal Consistency Check for SAP APO Models

Goal and Prerequisites

Consistency Check for Locations in SCM

Internal Consistency Check for Demand Planning,

Report /SAPAPO/TS_LCM_CONS_CHECK makes the same checks as report

Goal and Prerequisites

External Consistency Checks

External Consistency Checks Using CIF

External Consistency Checks Using

Goal and Prerequisites

Technical System Prerequisites

Compare/Reconcile Report Performance

Compare/Reconcile Report Performance Parallel Processing

Correction of Incorrect Sales Order Requirements

Goal and Prerequisites

The report is delivered in the standard version as of the following releases:

SAP R/3 plug-in 2002.2

SAP APO 3.0A Support Package 22

External Consistency Check for Production Order

Goal and Prerequisites

See also SAP Notes 542805 and 538111.

External Consistency Check for TP/VS

External Consistency Check for Faulty

Goal and Prerequisites

External Consistency Check for Integrated Product

Goal and Prerequisites

External Consistency Check for PP/DS runtime