Checking Changes
Use
To control the execution of the change steps, you can enter a customer-specific checking control in the Change Profile . By doing so, you define how conflicts are to be handled in order change management. Conflicts arise because changes are to be made to a production order for which production has already commenced (for example, deletion of a partially confirmed operation).
Features
The checking control entered in the change profile ensures that you are informed via messages of conflict situations. The message type determines the options for continuing processing. In the case of warning messages and error messages, however, you must make a decision in the Change Step Overview (see Processing Change Steps ):
Handling an information message or no conflict
If, according to the settings in the change profile, no conflict is present or an information message is issued, then the change steps are executed automatically. You do not need to process these change steps.
Handling a warning
In the case of a warning, you must decide whether or not the relevant change step is to be executed. Until you have done this, the change in the production order is not carried out.
If the indicator
When warning appears, execute and mark changes
is set in the change profile, change steps to which a warning has been assigned are executed automatically (see
Execution with Marked Objects
). However, you can set these change steps manually to
Do not execute
. The objects are marked accordingly in the production order (inserted, changed, to be deleted). The markers are removed only when the
change actions have been confirmed or rejected
.
Handling an error message
In the case of an error, you must set the corresponding change step to
Do not execute
. Until you have done this, the change in the production order is not carried out.
For change steps that have lead to an error and are marked as a change (
Change object), you can define in the
Change Profile
that the change step is automatically set to
Do not execute
.
Handling Conflict Types
Conflict type |
Change of production order |
Manual intervention |
No conflict |
Yes |
No action necessary |
Information |
Yes |
No action necessary |
Warning |
Yes/no |
Manual decision in the Change Step Overview |
Error |
No |
Manual confirmation in the Change Step Overview |
Examples
This is demonstrated in the following examples. You can decide that the deletion of a component
In an operation that is not released leads to an information message being issued. The change is executed without any further processing.
In an operation that is released leads to a warning being issued. You decide manually whether the change is to be executed (see Executing Change Steps ).
For which goods issue has already been carried out leads to an error message. The changes are not executed. You must process this error message manually (see Processing Change Steps ). Afterwards, the other change steps can be executed.
Activities
The execution of these process steps is described in Executing Process Steps .
See also:
Executing a Comparison in customer enhancement COOCM001