Has anyone successfully implemented a multi-level Master Schedule structure where a MS Level 1 part's structure includes a MS Level 1 subassembly/ component that has its own forecast?

Hi Vernon,

In Apps10 - Master Scheduling we introduced:
 

So in above case, if I sell Sink separately and have forecast figures for the sink and that forecast is only covering when I sell the Sink separately (oboy I am repeating myself) then I will USE Planned Dependent Demand but I will NOT USE Dependent Demand in Forecast Consumption.

Because:

• I want the exploded planned demand from parent ms planned part (the exploded MPS), so that this contributes to the projected onhand equation, and drive my MPS for the Sink.
• But I don’t want the exploded demand (coming from Sink&Tap kit Part No) to consume my forecast for the Sink Part No.That exploded demand IS not part of my statistical forecast in this example.

Run a site MS Level 1 calculation (it orders by Low Level code)

OR

parent MS part first and then child MS part

Hope this helps

-Mats