Comparison of Operations and Phases for
Manufacturing Orders
Use
You can compare operations and phases for manufacturing orders in SAP R/3 and SAP APO.
The system displays whether operations, phases, suboperations or secondary resources are missing in SAP R/3 or SAP APO. The system also checks whether there are any differences in the contents of operations and phases.
Prerequisites
You can only compare operations if you are also comparing manufacturing orders. The comparison of operations can be carried out independently of the comparison of the receipts/requirements.
If orders already contain inconsistencies, for example, they only exist in one system or their contents are not consistent, the system does not compare the operations.
Only APO-relevant operations and phases are compared.
For more information about the SAP APO-relevance of operations and phases, see SAP Note 367658.
Features
The CIF comparison/reconciliation checks manufacturing orders for the following inconsistencies:
Inconsistency |
The operation/phase only exists in one system |
Possible Manifestation of Inconsistency |
Possible Cause and Solution |
The operation/phase only exists in SAP R/3. |
Possible cause: Due to a parallel change in SAP R/3 and SAP APO, operations and phases cannot be mapped (that is, assigned). Operations/phases only exist in one system because queues from SAP R/3 that contain deleted master data or master data that has been read have been lost. Correction: Send the order to SAP APO. |
Suboperation or secondary resource (PP-PI) only exists in SAP R/3.
Suboperations and secondary resources can only be partly compared, due to their limited integration. The comparison is limited to their existence and suboperation number because changes to the date, work center, and status are not transferred from SAP APO to SAP R/3. |
Possible cause: Suboperation or secondary resource (PP-PI) cannot be mapped. Correction: Send the order to SAP APO. |
The operation/phase only exists in SAP APO. |
Possible cause: The queues from SAP R/3, which contain master data that has been changed or deleted, may have been lost. Correction: Send the order to SAP APO. The operation/phase is deleted in the production order in SAP APO. |
Suboperation or secondary resource (PP-PI) only exists in SAP APO. |
Possible cause: The queues from SAP R/3, which contain master data that has been changed or deleted, may have been lost. Correction: Send the order to SAP APO. The suboperation or secondary resource is deleted in the production order in SAP APO. |
Inconsistency |
Operation/phase has differences in content. |
Possible Manifestation of Inconsistency |
Possible Cause and Solution |
The visible operation or phase numbers are different. |
Possible cause: The queues from SAP R/3, which contain operation data that has been changed or deleted, may have been lost. Correction: Send the order to SAP APO. |
The visible suboperation or secondary resource numbers (PP-PI) are different. |
Possible cause: The queues from SAP R/3, which contain operation data that has been changed or deleted, may have been lost. Correction: Send the order to SAP APO. |
The work center assignments (primary resource of the active mode) are different.
A comparison is not carried out for alternative modes. |
Possible cause: The work center has been changed in SAP APO and not transferred to SAP R/3. Correction: Send the order to SAP R/3 or SAP APO. |
The operation has an inconsistent status. The status can be released, partially confirmed, confirmed, scheduled, or deallocated. |
Possible cause: Changes were made in SAP APO and SAP R/3 at the same time. Correction: Send the order to SAP APO. |
The operation or phase has an inconsistent quantity.
Operation scraps and rework quantities are taken into account equally in the comparison. |
Possible cause: Operation and phase quantities are reduced by confirmations or adjusted by quantity changes to the order header. These quantities may be incorrect or may not be adjusted in SAP APO if for example, the order transfer which is supposed to transfer current operation quantity to SAP APO has been lost. Correction: Send the order to SAP APO. |
Operation or phase in SAP R/3 is missing status DSEX (scheduling operations in an external system).
You can deactivate the check of status DSEX using BAdI /SAPAPO/CIF_DELTA3. This means that the comparison of dates is also deactivated. |
Possible cause: Dates from SAP APO were not adopted because: · The mapping in SAP R/3 has failed. · The SAP APO Customizing is not configured for retransferring data to SAP R/3 (Basis Settings → Integration → Publication → Maintain Object-Specific Settings). It could be that changes were made in SAP R/3 that resulted in the status being reset. Correction: Send the order to SAP R/3. |
The operation has inconsistent dates. The start and end dates of the following operation segments are compared: · Setup · Produce · Teardown
The date comparison only occurs until the status Released. |
Possible cause: It could be that an operation could not be mapped. Correction: Send the order to SAP R/3. |
The phase has inconsistent dates. The dates for the following phases are compared: · Phases for operations that have not been confirmed (Process Industry (PP-PI)) · Phases that have not been confirmed that belong to partially confirmed operations (PP-PI) You can deactivate the comparison using BAdI /SAPAPO/CIF_DELTA3.
The date comparison only occurs until the status Released. In the case of process orders, only phase dates and not operation dates are compared. This is because operation dates in SAP APO and SAP R/3 do not agree, if scheduling-relevant phases exist that are not relevant to SAP APO. |
Possible cause: It could be that a phase could not be mapped or that the retransfer has been lost. Correction: Send the order to SAP R/3. |
The setup information is inconsistent. · Setup group category · Setup key
The dates can only be compared, if the SAP R/3 setup information is maintained. If only the operation of the order in SAP APO contains setup information, only the operation is compared. If a phase in SAP APO became a sequence-dependent setup activity (because it contained setup information in SAP R/3), the phase is also compared. If you have only maintained setup information in SAP APO, you must deactivate the comparison in BAdI /SAPAPO/CIF_DELTA3. |
Possible cause: It could be that the setup information was changed in SAP APO. Correction: Send the order to SAP APO, if setup information is maintained in the order in SAP R/3. You cannot, however, delete the setup information in the order in SAP APO by sending the order. Check and adjust the setup information in SAP APO and SAP R/3 as required. · In the SAP APO menu: Advanced Planning and Optimization → Master Data → Production Planning Master Data → Setup Group/Setup Matrix · In SAP R/3 Customizing: Production → Capacity Requirements Planning → Master Data → Routing Data |
Only the first inconsistency is displayed in the overview for each order, since you can only rectify inconsistencies by retransferring the order. You can have the system display all the errors for an order in the detail view.
Restrictions
· The system does not compare dependent objects such as relationships.
· It is not intended that the system compares the dates for partially confirmed/finally confirmed operations/phases or for confirmed phases of a partially confirmed operation.
· For the comparison, operations and phases are filtered out that would also be filtered out for order integration.
However, operations and phases that are prevented from being filtered out by customer exit EXIT_SAPLCOVA_002 (enhancement PPAPO003 R/3 -> APO: Check whether operation is APO-relevant) are taken into account.
The assignment of receipts and requirements to operations is executed as part of the comparison of receipts and requirements. Here the dates for receipts and requirements are not compared.
The assignment of operations is only compared for operations and phases that are relevant to SAP APO.
Activities
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 or Operations.
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.
Business Add-In (BAdI)
You can use the method RELEVANT_FOR_COMPARE_OPRS (filtering operations that are not relevant) of BAdI /SAPAPO/CIF_DELTA3 to deactivate individual comparisons.