To synchronize order horizons between BOM levelsIn situations where multilevel BOM and BCM structures are used, it is important that the order horizons and planning horizons at the various levels are properly synchronized. Without such synchronization, strange planning situations can occur. This is illustrated in the following example. Example Item A is manufactured using subassembly B. B is manufactured using component C. C is purchased from a business partner. A and C are critical items; B is not critical. This results in the following BOM and BCM structures.
The effective lead times are as follows:
Consider the following planning situation, in which there are three requirements for item A, labeled X, Y, and Z. In principle, each requirement is passed on to the next BOM or BCM level, shifted in time on the basis of either routing data or BCM data.
This results in a strange planning situation for item C when the scenario is rolled forward (at weekly intervals). If a requirement for 100 piece of A is present in week 18, the following will occur:
In other words, a gap occurs in the planning of item C. This is due to the fact that requirements that fall just inside A's order horizon fall outside B's order horizon (and planning horizon). In this situation, B's order horizon should be at least one week longer. Rule To avoid situations like the one described here, LN applies the following rule to noncritical items when checking horizons (in the Check Horizons (cprpd1200m000) session):
In the above example, LN will indicate that the order horizon of item B must be extended to 7 weeks (the same as item A).
| |||||||||||||||