Occasionally, a company will need to change a production BOM but they don’t want to lose the information that’s contained in the existing BOM. Alternatively, the company doesn't want to create a new BOM to manage changes because that approach will require changes to the product structure.
Using starting and ending dates only partially resolves these problems, especially in situations where you want to replace a component temporarily. The result could be cluttered sets of BOM lines because the same components can be listed many times.
For example, in February 2022, the AutoDrip coffee machine will be produced with a glass carafe instead of a stainless steel one because of a company promotion. However, from March 2022 onward, the coffee machine should have the stainless steel carafe back in production.
To achieve this task, you should enter the stainless steel carafe twice in the BOM, but with different dates.
Instead of working with starting and ending dates on BOM lines, you can create a new BOM version. Versions usually start as a copy of the production BOM or another version of that BOM, and then you’d make changes to the copied data.
Version codes and starting dates identify each version. A BOM version automatically becomes active on its starting date, and all versions with a starting date older than this date will become invalid. To be active means that the version is automatically used in place of the BOM as of that date.
red hat enterprise linux rhel training courses malaysia
