E1: 34: PRP Requirements Planning With Lower Level Phantom And Subassembly Components Does Not Plan Components Below Phantom As Expected (R3483) (Doc ID 3071302.1)

Last updated on FEBRUARY 21, 2025

Applies to:

Symptoms

 When using a lower level Phantom in an ETO project, the planning of requirements below the phantom does not consider the actionable firm supply orders, for the phantom components, when planning with project requirements logic.  This results in net new planned orders, in excess of requirements. 
.
Steps:  

1. P4101/P41026 - Enter fresh planning data consisting of G, H, and 0 Phantom, Stock Type Items, in hard commit branch plant, such as M40. 
2. P3002 - Enter a multilevel bill of material structure with the G, H, and 0, Stock Types, such as the following, level - item:  
   0 - Parent
   1 - G
   2 - Phantom
   3 - G
3. P31P001 - Enter an ETO project and add a shippable WO work order task for top level parent item.  
4. R3483 - Master Planning Schedule - Multiple Plant - Run Project requirements planning (PRP) with messages and time series enabled for phantoms on the performance tab.  
5. P3411 - Review messages by project number.  As an aside, note that no messages for the phantom.  Process Project in P31P001 and Process P3411 planned order messages, as appropriate, to populate the work bench with the multiple level structure, with attached parts list at each level.  Alternately, manually create the multilevel structure within P31P001.  
6. R3483 - Rerun PRP to verify that no further planned order s or action messages, before proceeding.  
7. P31P001 - In Project Workbench, reschedule lowest level work order to completed at least 1 day prior to start date of upper level order.  Meaning that the lower level firm work order supply no longer matches the component demand line on the upper level work order parts list, or the upper level work order header start date.  
8. R3483 - Rerun PRP and review messages.  
9. P3411 - Note that the firm work order, below the phantom level, that is expected to get a planning action message to defer to the requirement date, has no message.  The item is replanned, using the parent work order as the source of demand.

Changes

Cause