FAQ SAP Order change management (OCM)
Why is the system issue messaged COCM 002 (“Since there is no similarity list for order & => no master data process”) even though the overall profile for OCM has been preserved in the material master?
The problem takes place when the overall profile is entered later in the material master however for the material for the production orders have already been created. The similarity in object is immediately written to the field CONF_KEY of the table AFKO upon creating the production order. Upon entering the profile subsequently, the system will not update the order that already persists. Hence, the order is not appropriate for OCM.
Incase you want the material to be used in OCM, then while creating the production order the overall profile should already be maintained in the material.
For some sales order changes, why does the system not create a simulation order?
While the production order is generated from the sales order is an assembly order, the changes are made automatically in the production order. This happens in consultation with the Customizing settings of the overall profile. Based on these settings, you would be required to confirm the changes in the production order.
Incase the production order is due to the planned order conversion, then the system controls the changes from the referenced sales order in transaction COCM or COCM1. In this scenario, the first step is the creation of the current bill of material explosion which is done in a simulation order. The system then controls the changes which are made to the production order by executing an order comparison for the production and simulation orders.
While updating the production resources/tools in the routing, if these are not updated in the production order. Is it an error?
The process of updating production resources/tools as part of the OCM process is not possible. In the production order, if you like the production resources/tools to be updated then you first need to delete them from the routing and then later add new data to them. This is described in SAP Note 724062 (“COCM: Inserting PRT in master record process”).
When is the system set the system status AEVB (“Changes forbidden”) done and when does the system establish the system status MABG (“Manual adjustment required”)?
As a part of the change process in transaction COCM1, the system sets the status AEVB. This takes place in the “Check Changes” step. The system performs this OCM process both for the changes in make-to-order production and in the master data. If the status is set, then you cannot alter the order.You either would have to complete the OCM process or revoke the “Check Changes” step.
The status MABG is set up as part of the “Assembly Order” change process. In the production order this takes place only if the changes are not possible automatically.
Why is the information related to the deleted components or operations not be displayed in the change steps in transaction COCM1?
Incase the changes were executed in the original order and these have been deleted from the database, then all the data related to deleted operations or components is no longer visible.
However, there are times when the data for the deleted objects can still be visible in the change steps. This is applicable if the component cannot be deleted from the database (for instance, due to its order status). In this case, in the actual order in the material list, the deletion indicator is set but the component remains visible. The OCM can then access and display the old data for the deleted component and the component therefore does not get deleted from the database.
Why the differences in the object detail are not displayed once the change steps are executed in OCM?
Once the system identifies differences, when exhibiting the changes in OCM, these cannot be displayed following the change to the original order. The values in the “Old Value” and “New Value” fields are alike.
As a part of the OCM process, all the changes or differences are visible before the changes are implemented to the original order. This is done to ensure the changes made by OCM are correct. Once these are executed, the changes, the data is not required because they were considered correct and once the user executes the last change step.
OCM is not liable for storing and displaying any old data.