My Oracle Support Banner

E1: 34: Duplicate P4021 Demand for Components of Phantoms with Attached WO Parts List (R31410) (Doc ID 2784042.1)

Last updated on MARCH 09, 2022

Applies to:

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

Symptoms

Work Order Processing of phantom item parent work order attaches the phantom components, but R31410 does not update the phantom component pegging from the FO firm order and phantom item to the upper level parent item and work order. This is incorrect. The phantom component pegs to the phantom item prior to attaching the work order parts list, but once the phantom components are attached, the pegging records for the phantom components are left unchanged. This means that the supply and demand inquiry will now see a component pegged to both the upper level parent item work order, due to the attached parts list, as well as the pegging record to the phantom item and the firm work order header number, duplicating the demand.

Also, when the parent item planned work order message is processed, the phantom item pegging record to the parent item is updated with the assigned work order number. Again, the pegging records for the phantom components are left unchanged. At this point, the P4021 inquiry for the phantom components will show this firm order as a demand, but planned order demand (via pegging ) also shows, creating a display issue that appears to 'double' requirements.

This means that the supply and demand inquiry will now see a component pegged to both the upper level, parent item work order, due to the attached parts list, as well as the pegging record to the phantom item and the firm work order header number, duplicating the apparent demand in Supply and Demand Inquiry P4021.

Steps:

  1. Set up a P4102 Manufactured Item with a P3002 BOM that uses a Phantom Item and the Phantom BOM having at least 1 Component
  2. Enter Forecast Demand for the Parent Item
  3. Run MRP (R3482 or R3483) to create WO Message for the Parent and Order Message for the Component.
  4. View the P4021 for Parent and Component and confirm that the Component shows WP Demand with no Order Number.
  5. Process the P3411 WO Message for the Parent.
  6. Review Pegging Records for the Component and the Phantom. Note the Phantom now has an Order Type of WO but the Component still pegs to WP and to the Phantom Item even though the WO Header now exists.
  7. Run R31410 to attach the Parts List. Confirm the Parts List is updated for the Component.
  8. Review the Pegging records (P3412) and note Component still shows Doc Type WP, while the Phantom now pegs to the Parent with a FO Order Type.
  9. Review P4021 for the Component and note that demand is doubled. The quantity shows up for both WP and WO on the same date.

Note that the MRP planning messages themselves are not doubled. So to create a planning issue or oversupply situation, a user would have to inquire on P4021 and make planning decision accordingly, independent of reviewing the time series, planning messages or reprocessing MRP. There is no part of planning logic that would create a message, which would double the supply, based on the doubling shown in P4021.

P4021 has never been recommended as a planning tool but rather as a means to gather order number details and such particulars.

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.