Example: Creating a Change Status with Parameter Effectivity
Example: Creating a Change Status with Parameter Effectivity
The change master records used in this example are shown in graphic 1 and the table below. You should note that change master records AP1 and AP2 do not have time-related validity, as the DATE effectivity parameter is not found within the CUSTOMER effectivity type.
Graphic 1: Change Master Records
Change Master Record |
Type of Validity |
Effectivity Type |
Validity/Effectivity |
CH1 |
Date validity |
from Saturday, January 01, 2005 | |
CH5 |
Date validity |
from May 15, 2005 | |
AP1 |
Parameter effectivity |
AIRLINE |
For customer BlueAir, from serial number 456 |
AP2 |
Parameter effectivity |
AIRLINE |
For customer GreenAir, from serial number 456 to serial number 789 |
You created BOM header B earlier (see graphic 2). Its change statuses CH1 and CH5 both have date validity. For more information on creating change statuses with date validity, see
Creating a Change Status with Date Validity.Your worklist first contains BOM header B that has change statuses CH1 and CH5.
Graphic 2: Validity before Creation
On the BOM headers overview now enter change number AP1 in the Process using screen section (see graphic 3).
Graphic 3: BOM Headers Overview before Creation (Schematic)
You now process change status CH1. You then enter change number AP2 in the Process using screen section and create the new BOM header C Graphic 4 shows the newly created change statuses AP1 and AP2. The validity of both change statuses is not dependent on the date, as their change master records do not have time-related validity (see above).
Graphic 4: Validity after Creation
On the BOM headers overview, an extra line has been added for both change statuses (see graphic 5). You can tell that both change statuses have parameter effectivity, because neither a valid-from date, nor a valid-to date, nor any further change number is displayed on the overview.
Graphic 5: BOM Headers Overview after Creation (Schematic)
