Comparison of Manufacturing Orders

Use

The comparison of manufacturing orders is part of the CIF Comparison/Reconciliation of Transaction Data . This comparison is used to determine and correct inconsistencies between SAP APO and SAP R/3.

You can also compare receipts and requirements and operations for manufacturing orders in SAP R/3 and SAP APO.

You can also check the assignment of receipts and requirements to SAP APO-relevant operations and phases in combination with the comparison of operations and phases.

To display the differences that have been determined, expand the node Manufacturing Orders and click Receipts/Requirements or Operations.

For more information, see Comparison of Operations .

Features

The CIF comparison/reconciliation checks manufacturing orders for the following inconsistencies:

Inconsistency	Possible Manifestation of Inconsistency	Possible Cause and Solution
The order only exists in one system.	The order exists only in SAP APO and does not have an external (R/3) key.	Possible Cause : The order was not yet published from SAP APO to SAP R/3. Correction : Send the order to SAP R/3. If the order is to be deleted in SAP APO, you must do this manually. Note that queue entries or any change pointers that might exist (for periodic transfer) are not checked.
	The order exists only in SAP R/3 and does not have an external (R/3) key.	Possible cause : The order was deleted in SAP R/3 but the deletion was not transferred to SAP APO. Correction : Delete the order in SAP APO.
	Order only exists in SAP R/3.	Possible cause : The order was created in SAP R/3 and not transferred to SAP APO. Or, the order was deleted in SAP APO and the deletion was not transferred to SAP R/3. Correction : Send the order to SAP APO.
	Special case: An error occurred during the transfer of a planned order.
The order exists in SAP APO, but it is not contained in an active integration model.		Possible cause : The order materials are no longer planned in SAP APO. Correction : Delete the order in SAP APO.
The order has differences in contents.	In the order header: Different GUID Same GUID, but different type or number (for example, after planned order conversion) Different Released status In primary product: Different material Different plant Different original quantity Different MRP-relevant quantity Different receipt date (without goods receipt processing time) Note Note that receipt dates are not checked after confirmation because SAP APO and SAP R/3 have different scheduling behavior. End of the note. Different ATP category Note Note that the ATP category is not checked for SNP orders. End of the note. Different item number s	Possible cause : Changes to the relevant fields were not transferred correctly to the other system. Correction : Send the order from the system in which the contents are correct to the other system. In some cases, you are only allowed to send in one direction. Change the order manually, if required.