Consistency Check for Changes
Purpose
If changes relevant to the derivation are made to the order or batch after the derivation has been performed, the validity of this derivation is no longer guaranteed. The consistency of a derivation is no longer guaranteed, since the derivation might have different results using the new conditions.
For this reason, a dialog box informs the user who changes the data about the derivations that are affected by the change.
Caution
The consistency check is not integrated into the old batch master transaction (MSC2).
The consistency check is not performed if components are added to orders, or when additional batches are posted, than were originally planned in the order.
Features
The consistency becomes questionable when you make the following changes:
Changes in the Order:
You exchange a component batch that has sent attributes to a produced batch in a previous derivation.
You exchange a component batch that has sent attributes to a produced batch in a past derivation. One of the batches that was included in this component batch, was a sender batch. When the component batch is exchanged, the subsequent levels of the batch where-used list become obsolete.
You exchange the produced batch of an order that was used as a component batch of a subsequent order. One of the component batches was a sender batch for the produced batch in one of the subsequent orders. This means that part of the batch where-used list is now invalid.
See Consistency Check in the Derivation - Example .
Changes to Batches
If you change an attribute of a batch that was involved in a derivation, this derivation becomes obsolete.
Derivation Status
If you make changes in the order or to the batch that are relevant for this derivation, the status of the derivation also changes, as follows:
O.k., but data changed
Warning and data change
Error and data change