Comparison of Receipts and Requirements for
Manufacturing Orders
The compare/reconcile function checks receipts and requirements from manufacturing orders in SAP APO and SAP R/3 for the following inconsistencies:
Inconsistency |
The receipt or requirement only exists in one system. |
Possible Manifestation of Inconsistency |
Possible Cause and Solution |
The receipt or requirement only exists in SAP APO. |
Possible cause: The receipt or requirement was added to the order in SAP APO, but the transfer to SAP R/3 failed. The receipt or requirement was deleted in SAP R/3, but it was not deleted in SAP APO. Correction: Send the order to SAP R/3 or SAP APO. Note that if you choose Send to R/3, receipts and requirements that are deleted in SAP R/3 are also deleted in SAP APO. If you choose Send to R/3, the order is first transferred from SAP APO to SAP R/3. When the order is then resent from SAP R/3 to SAP APO, the receipts or requirements are also deleted in SAP APO. |
The receipt or requirement only exists in SAP R/3. |
Possible cause: The receipt or requirement was added to the order in SAP R/3, but the transfer to SAP APO failed. Correction: Send the order to SAP APO. |
The receipt or requirement exists in SAP APO but does not have an external (R/3) number. |
Possible cause: The receipt or requirement was added to the order in SAP APO, but the transfer of reservation number and item from SAP R/3 failed. Correction: Send the order to SAP APO. |
Inconsistency |
The receipt or requirement has differences in content. |
Possible Manifestation of Inconsistency |
Possible Cause and Solution |
The receipt or requirement has differences in the MRP quantity. |
Possible cause: Changes to the quantity were not transferred correctly to the other system. Correction: Send the order to SAP R/3 or SAP APO. |
The receipt or requirement has different ATP categories. |
Possible cause: The order was created in SAP R/3 but was not transferred correctly to SAP APO. Correction: Send the order to SAP APO. |
The receipt or requirement has a different production plant or storage location. |
Possible cause: The order was created or changed in SAP R/3 but was not transferred correctly to SAP APO. Correction: Send the order to SAP R/3 or SAP APO. |
The receipt or requirement has different account assignment information. |
Possible cause: The order was created in SAP R/3 but was not transferred correctly to SAP APO. Correction: Send the order to SAP R/3 or SAP APO. |
The receipt or requirement is marked as not relevant for pegging in SAP APO. |
Possible cause: The order was created in SAP R/3 but was not transferred correctly to SAP APO. Correction: Send the order to SAP APO. |
The receipt or requirement is assigned to different operations in SAP R/3 and SAP APO. |
Possible cause: The assignment of the receipt or requirement to the operation was changed in SAP R/3 but the order was not transferred correctly to SAP APO. Correction: Send the order to SAP APO. |
Restrictions
· It is not intended that the system compares the dates for receipts or requirements.
· 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.

When comparing the assignment of operations, the system only takes into account receipts and requirements whose operations or phases are relevant to SAP APO.
Choose APO Administration → Integration → CIF Comparison/Reconciliation of Transaction
Data. (See
Determination and
Correction of Inconsistent Transaction Data)
To display the differences that have been determined, expand the node Manufacturing Orders and click Receipts/Requirements.
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.
You can use the method RELEVANT_FOR_COMPARE_IONODES (deactivating comparisons for receipts/requirements) of BAdI /SAPAPO/CIF_DELTA3 to deactivate individual comparisons.