Documentation >
MAC-PAC Reference Library >
Manufacturing >
Design Engineering >
Key Concepts and Procedures >
Product Structure Mass Change >
Considerations
Considerations
The in-effectivity date on the mass change transaction is the date on which the new component should replace the original component in all product structures. The life cycle of the original component, however, will determine the actual in-effectivity and out-effectivity dates on the transactions MAC-PAC writes for each product structure. The following exhibits illustrate how this processing works.
Example 1
In the simplest case, the original component is always in effect (that is, it has no effectivity dates). The new component will come into effect on the date on the mass change transaction. The original component will come out of effect at the end of the preceding day.
|
<-------------------------------------------------------------------------------------------------------->
|
|
|
|
|
|
|
|
|
1/31
|
2/28
|
3/31
|
In-Effectivity Date on Mass Change Trans.
|
|
|
2/28
|
Original component will be in effect through the end of the day 2/27. In other words:
In-Effectivity date = blank
Out-effectivity date = 2/27
|
|
|
New component will come into effect at the beginning of the day 2/28:
In Effectivity date = 2/28
Out-effectivity date = blank
|
Example 2
The original component is scheduled to come into effect 2/28 and go out of effect on 4/30. The date when the original component is replaced is determined by the date in the Effectivity Date - In field on the mass change transaction screen, as shown in the table.
Original Component Life
X---------------------------------------------------X
1/31 2/28 3/31 4/30 5/31
In-Effectivity Date on Mass Change Trans.
|
|
|
Any date before 2/28
|
The original component will never come into effect. The replacement component will come into effect on 2/28 and go out of effect on 4/30:
Original record will be deleted.
New component record will have
In effectivity date = 2/28
Out-effectivity date = 4/30
|
|
2/28
|
The original component will never come into effect. The replacement component will come into effect on 2/28 and go out of effect on 4/30.
Original record will be deleted.
New component record will have
In effectivity date = 2/28
Out-effectivity date = 4/30
|
|
3/31
|
Original component will be in effect from the 2/28 through the end of the day 3/30:
In-effectivity date = 2/28
Out-effectivity date = 3/30
|
|
|
Replacement component will go into effect at the beginning of the day 3/31 and remain in effect until the end of the day 4/30:
In-effectivity date = 3/31
Out-effectivity date = 4/30
|
Original Component Life
X--------------------------------------------------X
1/31 2/28 3/31 4/30 5/31
In-Effectivity Date on Mass Change Trans.
|
|
|
4/30
|
Original component will be in effect through the end of the day 4/29:
In-effectivity date = 2/28
Out-effectivity date = 4/29
|
|
|
Replacement component will be in effect only for one day on 4/30:
In-effectivity date = 4/30
Out-effectivity date = 4/30
|
|
5/31
|
Since the replacement will not take place until after the original component comes out of effect, no change will be made to the original product structure record.
|
Example 3.
The original component is scheduled to be used through the end of the day 2/28. At the beginning of the day on 4/30, the component is scheduled to come back into effect.
<------------------------------------------X X------------------------------------>
| | | |
1/31 2/28 3/31 4/30 5/31
In-Effectivity Date on Mass Change Trans.
|
|
|
1/31
|
Original component will remain in effect through the end of the day 1/30:
In-effectivity date = blank
Out-effectivity date = 1/30
|
|
|
New component will come into effect 1/31 and remain in effect until the end of the day 2/28:
In-effectivity date = 1/31
Out-effectivity date = 2/28
|
|
|
New component will come back into effect at the beginning of the day 4/30:
In-effectivity date = 4/30
Out-effectivity date = blank
|
|
2/28
|
Original component will remain in effect through the end of the day 2/27:
In-effectivity date = blank
Out-effectivity date = 2/27
|
|
|
New component will be in effect during the day 2/28:
In-effectivity date = 2/28
Out-effectivity date = 2/28
|
|
|
New component will come back into effect at the beginning of the day 4/30:
In-effectivity date = 4/30
Out-effectivity date = blank
|
<-------------------------------------------X X------------------------------------>
| | | |
1/31 2/28 3/31 4/30 5/31
In-Effectivity Date on Mass Change Trans.
|
|
|
3/31 or 4/30
|
Original component will be in effect until the end of the day 2/28:
In-effectivity date = blank
Out-effectivity date = 2/27
|
|
|
New component will come into effect at the beginning of the day 4/30:
In-effectivity date = 4/30
Out-effectivity date = blank
|
|
5/31
|
Original component will be in effect until the end of the day 2/28:
In-effectivity date = blank
Out-effectivity date = 2/28
|
|
|
Original component will come back into effect at the beginning of the day 4/30 and remain in effect until the end of the day 5/30:
In effectivity date = 4/30
Out-effectivity date = 5/30
|
|
|
New component will come into effect 5/31:
In-effectivity date = 5/31
Out-effectivity date = blank
|
Example 4.
The original component is scheduled to be used for one day only--3/31.
X
| | |
2/28 3/31 4/30
In-Effectivity Date on Mass Change Trans.
|
|
|
2/28
|
Original component will never be used:
parent/component record will be deleted
|
|
|
New component will come into effect at the beginning of the day 3/31 and go out of effect at the end of the day:
In-effectivity date = 3/31
Out-effectivity date = 3/31
|
|
3/31
|
Original component will never be used:
parent/component record will be deleted
|
|
|
New component will come into effect at the beginning of the day 3/31 and go out of effect at the end of the day:
In-effectivity date = 3/31
Out-effectivity date = 3/31
|
|
4/30
|
Since the replacement will not take place until after the original component comes out of effect, no change will be made to the original product structure record.
|