My Oracle Support Banner

E1: 31P: PRP - MRP/MPS Requirements Planning - R3482 Creates Incorrect Cancel Messages for Shippable Tasks Linked to SO Detail Lines if One of the WOs is Already Completed but Not Shipped Yet (Doc ID 3062035.1)

Last updated on DECEMBER 04, 2024

Applies to:

JD Edwards EnterpriseOne Engineer to Order - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

When having different ETO Projects created for the same project-specific parent item, with multiple manufacturing shippable tasks linked to SO detail lines and one of the WOs is already completed but not shipped, the PRP creates a cancel message for another WO / manufacturing shippable tasks. It seems that the system considers the quantity completed for one ETO task as being available to be allocated to another task within a different ETO Project, which is not correct.

The issue can be reproduced at will with the following steps:

  1. P4101 / P41026 - Create the following items:
    - A and B - project specific parent items (Stk Ty = G, Ln Ty = S)
    - C - project specific component item (Stk Ty = H, Ln Ty = SC)
    - D and E - two different purchased items (Stk Ty = P, Ln ty S).
  2. P3002 – Create the following BOMs:
    - Parent item A contains items B, C and D.
    - Parent item B contains item E.
  3. P31P001 - Create ETO Project # 1 with 2 ETO manufactured shippable tasks for WO # 1 and WO # 2 for the top parent item A. The ETO Project has Interface to Job Cost activated and Billing Method set to 2-Contract.
  4. P31P001 - Process ETO Project and have the WO P.L. and WO Routing attached for both WO # 1 and WO # 2 by taking the Process Project option from the drop-down menu More Project Actions.
  5. P31P001 – From the More Task Actions drop-down menu, take the options Mfg Issues and Mfg Hrs Quantities to report material issues and time entry for the first WO created for the first ETO task of the first ETO Project.
  6. P31P001 - Create a new ETO Project with 2 different manufactured shippable tasks for WO # 3 and WO # 4, for the same ETO project specific parent item A. The ETO Project has Interface to Job Cost activated and Billing Method set to 2-Contract.
  7. P31P001 - Process ETO Project and have the WO P.L. and WO Routing attached for WO # 3 and WO # 4 by using the Process Project option from the drop-down menu More Project Actions.
  8. P31P001 – Open the first ETO Project, select the first ETO shippable task (WO # 1) and from the More Task Actions drop-down menu, take MFG Completions option. During WO Completion assign the lot number of the completed quantity for the first MFG shippable task as the WO Number # 1.
  9. BV – R3482 – Run PRP and generate messages for both project specific and non-project specific items.
  10. P3411 – Review the PRP messages. All items are planned correctly.
  11. P31P001 - Select each ETO project and for each manufactured task, select the line and take More Task Actions option and then select the 'Create SO Lines' option.
  12. P31P001 - Once processing all tasks for both ETO projects, notice that the related SO Numbers for each shippable manufacturing task are displayed in the View Related Orders form.
  13. R3482 - Run PRP again to generate planning messages for all project-specific and non-project specific item.
  14. P3411 - Check the PRP messages. Notice that there is a C - Cancel message generated for the first work order (WO # 3) of the second ETO Project. This is incorrect because even if the WO # 1 (attached to ETO Project # 1) has been completed in stock but not yet ship confirmed, the quantity completed in stock should not be considered as available to be allocated to a different project.

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!


In this Document
Symptoms
Cause
Solution
References


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