You run CIF Delta report (CCR) in APO using transaction /SAPAPO/CCR for manufacturing order and result in error
/sapapo/cif161 - order difference for receipt date in SAP APO and SAP R/3
The following are the possible reasons and solutions
1) PUBLICATION SETTINGS:
APO is the default scheduling leading system and that means that every order coming from R/3 system will be scheduled in APO and the new scheduled dates will be sent to R/3 in order to make the system consistent. In order to send the data, the publication settings has to be maintained . Execute T-code /SAPAPO/CP3 in APO system, and maintain the following setting
Publication type – In-House production
Block size – 600 (based on business scenario)
Retransfer – Always retransfer
Refer to the notes 423626 and 1803658
2) DISTRIBUTION DEFINITION
By maintaining the objects in the distribution definition the planning results are published from APO to an external system. Execute T-code /SAPAPO/CP1 in APO system and maintain the following setting
Publication type – In-House production
Location number – Location of the order
Logsystem - The integrated R/3 system
SAPRel - Release for the connected R/3 system
3) TIME ZONE
The plant which has the order should have the same time zone maintained in APO and R/3 system
a) Execute T-code OX10 for the plant and check the time zone of the plant in R/3 system
b) Execute T-code /SAPAPO/LOC3 and check the time zone of the plant in APO system
4) FACTORY CALENDAR
The factory calendar maintained for the resource should be maintained the same in R/3 and APO system so that the shift and other work center parameters of the order are consistent between the
systems
a) Execute T-code CR03 and enter the work center of each operation, and check the factory calendar under the scheduling relevant capacity header
b) Execute T-code /SAPAPO/RES01 and enter the same work resource to check the factory calendar under the “General” tab
5) SOURCE OF SUPPLY
Check if the order is using source of supply (PPM / PDS) in APO and that it is consistent between APO and R/3 systems.
a) Check if the operations of the R/3 order are present in APO order; there are cases where some of R/3 operations do not exist in APO order
I) The operations may go missing in APO order if it is not relevant to scheduling in APO; refer to note 367658 for filtering of operations
ii) If business scenario doesn’t want some operations to be in APO then it can be made not relevant to APO. In this case dates inconsistencies may happen because the end date of an order is determined by the end date of the operation. Since some operations are present in R/3, but not in APO, the end dates may differ between the systems
b) If the order do not use source of supply then refer to note 788266 for creation of manufacturing orders with no source of supply
6) OTHER CIF DELTA REPORT ERROR
Execute T-code /SAPAPO/CCR in APO system for the material and plant in the order and check if there are other related errors to the order which could be the cause for the date inconsistency
7 ) IMPLEMENTATIONS
Check in R/3 and in APO system if there is any customer exit or BADI implemented that modifies the dates that are sent across
Refer to note 645597 that has the user exit solution to activate the comparison of order deadline in the CIF delta report