Purpose

At times for many reason, inconsistence may happen b/t R3 and APO. here we don't want to look into detail of CIF or cockip how to ensure the consistence between these 2 systems, as it is a big deal we can cover in many posts later.

this article is to solve the issue, for example, if new material code CIFed/created into APO. By that time, if we want to use DP/SNP etc., we must have many master data ready and available.

This is not user-afford actions, mostly it should be performed by consultant - as it is much more technical even complex if we really want to know the core functionalities.

Here only documents some few points.

Content

1). no Livecache anchor

below is one possible case: (but not only)

we can execute the program - /SAPAPO/TS_LCM_CONS_CHECK to repair the LCA:

or we can use /MC62 to adjust time series when create CVC

2). CCR to correct inconsistence

Master or transaction data not consistent

/N/SAPAPO/CCR or program (/SAPAPO/CIF_DELTAREPORT3

then you can repair using above buttons.

3). planning file entry/pegkey

in APO, order data does not contain the id, like product, location, etc...instead it contains the pegkey.

it is like Planning file entry in R3.

if it is missed, we may encounter below error