Validity of Recipes: Example 

This example illustrates how different editing methods influence change state creation and validity. It describes the editing process of a recipe for which change master records are allowed but are not mandatory.

Process Flow

...

       1.      You create a recipe with change number C1. The recipe obtains 01/05 as the valid-from date, which is entered in the relevant change master record. The validity of the recipe is unrestricted.

 

       2.      You change the recipe without a change number on the key date 03/20. Since there is only one change state in the recipe so far, the changes apply to the recipe’s entire validity period.

 

       3.      You change the recipe with change number C2. A new change state is created on the valid-from date 12/07 that is entered in the relevant change master record. The validity is unrestricted. The validity period of the existing change state is shortened accordingly; it ends with the day immediately before.

 

       4.      You change the recipe with change number C3. A new change state is created on the valid-from date 06/11 that is entered in the relevant change master record. Its validity period ends on 12/06, that is, immediately before the validity-from date of the following change state. The validity period of the preceding change state is shortened accordingly; it ends on 06/10.

 

       5.      You change the recipe without a change number on the key date 11/03. The change state with change number C3 that is valid on this key date is changed. Your changes are valid for the entire validity period of this change state.

 

       6.      You notice that the changes made in the second change state of the recipe must already take effect in May. For this reason, you replace the valid-from date 06/11 in the change master record with change number C3 with the date 05/01. The valid-from date of the second change state is shifted to 05/01. The validity period of the first change state ends on 04/30.