1

2
 Because of the separate data pools an overall consistency between OLTP, APO and
liveCache has to be guaranteed at any time.

3
 Some data is stored in APO DB, other data is only in liveCache, and some data is in
both.
Planning is an operation in liveCache, so liveCache includes the data that is needed
for planning.
Planning results are transported into APO DB and also to related external R/3 Systems
and external OLTP systems.
Internal consistency means consistency between the data in APO DB and the data in
liveCache.
External consistency means consistency between the data in external R/3 Systems,
or other OLTP systems that import data into APO DB, and the data that is held in APO
DB.

4
5
 The SAP APO system includes all planning basis data:
Master data
Plants, vendors, customers
Materials, products, bills of material and routing (production process models)
Characteristics, capacities
Transactional data
Planned/production orders
Sales orders, purchase orders, stocks, ATP requests
Planning data
ATP results, manufacturing orders, procurement orders, VMI sales orders
The SAP R/3 OLTP system includes:
All master data
All transactional data
Results of production and execution of orders

6
7
8
9
 For detailed recommendations about consistency checks please refer to
service.sap.com/scm -> Best Practices for Solution Management: SAP SCM
-> Data Consistency for SAP APO (3.x) / mySAP SCM (4.x/5.0).

10
 In case of incomplete recovery it is very important to check internal before external
consistency. The reason is shown in the following example : If the internal consistency
check finds data fragments in APO or liveCache database which are not linked any
more, it will delete them. This data can only be repaired by the external consistency
check, who will detect the missing data in APO and cares to retransfer the information
from the OLTP system.

11
 To synchronize APO DB and liveCache, you can choose Tools APO Administration
liveCache / COM Routines Tools liveCache Consistency Check (transaction
/SAPAPO/OM17):
Flag all the checkboxes and select a planning version. If you do not specify a plan
version, the check is carried out for all plan versions.
Choose either Immediate check or Check (Batch).
This check compares transactional data in APO DB and liveCache.
Orders and stocks that exist either only in APO DB or only in liveCache are
deleted.
If orders or stocks were modified and these modifications are available either only
in APO DB or only in liveCache, the objects are returned to their previous status.
This causes loss of data, but APO internal data consistency is restored.
Transaction /SAPAPO/OM17 also compares master data and restores changes if
necessary. As all master data is available in APO DB, modified or new objects can be
copied from the APO database into liveCache in case of inconsistencies.

12
 There are several possible objects types which can be checked by an internal
consistency run the parameterization depends on your business.
It is SAP recommended to flag all used object types and run the consistency check in
background, because the chosen object types are then checked in parallel background
jobs ( performance optimal ).
If you run the internal consistency check in dialog, the object types are checked
sequentially.

13
 If you use certain modules there are consistency checks which are recommended to
run regularly at times of low workload.

14
15
16
 An external consistency check does not check objects in the CIF queues, so there may
be temporary inconsistencies.
An internal consistency check cannot check objects that have already been created in
liveCache but are still under construction in APO DB or vice versa.
Because of this fact, the best way to perform an internal consistency check is to stop
all user activity.
If that is not possible, execute the check twice to eliminate temporary inconsistencies.

17
 External consistency (OLTP APO system) is restored through resubmission
(initial load) of transaction data with the compare/adjust report
/SAPAPO/CIF_DELTAREPORT
You can choose the target system (logical system name) and the objects that are to be
checked.
If there is more than one dedicated R/3 System, you need to execute the report for
every one of the dedicated systems.
The program /SAPAPO/CIF_DELTAREPORT (transaction /SAPAPO/CCR) for
restoration of external consistency
identifies and corrects data inconsistency between SAP APO and a selected SAP
OLTP system
checks only transactional data.
The external consistency check in general checks all objects which are included in the
active integration models of the selected OLTP system. Additionally it checks whether
there are objects in APO which are not covered in active integration models.
This function only checks existence, not contents (for example, due/delivery dates).

18
19
 Background processing results have to be reorganized with report
/SAPAPO/CIF_DELTAREPORT3_REORG. In default the report removes results
older 7 days.

20
 How to run the deltareport in background to get the results for later processing in
dialog ?
First go to CIF deltareport in /SAPAPO/CCR
Mark the desired objects
Execute the program in background (F9)
Save the results for later processing in dialog

21
 How to see the results of the deltareport ?
First go to Overview in SM37
Mark the corresponding job
Display the step list (Ctrl + Shift + F9)
Step List Overview appears
Mark the program name
Display the spool list (Ctrl + F10)
List of spool requests appears
Double click the ABAP List and the result of the deltareport appears

22
 How to get the results of the deltareport for later processing in dialog ?
First go to CIF deltareport in /SAPAPO/CCR
Click Load results and load the desired result
Execute the program (F8)
Dissolve inconsistencies as usual

23
24
 As of SAP SCM 5.0, you can convert the data access for the CIF
comparison/reconciliation to parallel processing in the SAP APO system and/or
ERP system, and thus improve performance.
By default, parallel processing is not configured.
You set this up using parallel processing profiles which are defined in Customizing.
Parallel processing was also down-ported for SCM 4.1 where it is available as of
SP4/SP5.
Please refer to note 882865 for limitations on the parallelization with application
servers with different hardware.

25
 So far: When you perform the CIF comparison/reconciliation of transaction data, we
recommend that you have already processed any existing change pointers. In the
results screen of the comparison, you can see if change pointers still exist for
individual inconsistencies in the Change Pointer column. Until now, you had to have
found and processed the relevant change pointer in the transaction Publish Orders
(/SAPAPO/C5).
As of SCM 5.0: The Change Pointer pushbutton is available to you in the results
screen of the comparison. You can use this pushbutton to directly process selected
change pointers. The system automatically deletes these change pointers after they
have been processed. You can use this pushbutton to delete change pointers that
are no longer relevant.
If you rectify the inconsistency for which a change pointer exists using the CIF
comparison/reconciliation and not the Change Pointer pushbutton, the change
pointer remains although the inconsistency has been rectified. If you want to make
sure that the change pointer is deleted in this case too, set the Deletion of Change
Pointers After Processing indicator in the selection screen for the CIF comparison/
reconciliation. The indicator is not set by default.

26
 The results of the external consistency checks have to be frequently reorganized by the
report /SAPAPO/CIF_DELTAREPORT3_REORG.

27
28