My Oracle Support Banner

E1: 34: 31P: PRP Planning Of ETO For Expedite and Defer Creates Unnecessary PLO Messages (Doc ID 2725735.1)

Last updated on NOVEMBER 03, 2020

Applies to:

JD Edwards EnterpriseOne Engineer to Order - Version 9.2 to 9.2 [Release 9.2]
JD Edwards EnterpriseOne Requirements Planning - Version 9.2 to 9.2 [Release 9.2]
Information in this document applies to any platform.

Symptoms

When a child WO task request date does not match the upper level work order exactly, the PRP planning will create a net new PLO order to meet the requirement.  This is unneeded, as a defer or expedite would meet the requirement.  While the system does create a defer, but not the expedite, the excess PLO drives excess supply and excess lower level requirements.  Freezing the work orders prevents the cancel or defer but does not prevent the excess PLO.

Steps:

  1. Create a top level ETO (Stock G, line S) with a multi-level bill of material (BOM) structure, including ETO purchased (Stock H, line SC) items.  
  2. Add the top level parent item to an ETO project as multiple shippable production (WO) tasks with or without task dependencies.  
  3. Either manually add the lower level child production tasks or run PRP and process messages.  
  4. From P31P001, Edit and lock all tasks, and forward or backward schedule to set dates from within the project.
  5. Process Project and save and close.  Then reinquire and modify child production task start and end dates, as if for business or capacity constraints.  Set some dates early, to force defer messages and set some dates late such as to generate expedite messages.  
  6. Run PRP and review messages and time series.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.