My Oracle Support Banner

E1: 31P: PRP Should not Create Unnecessary Planned Order Messages After Changing Planned Effective Date of a Purchase Order from Default Date to Another Date (Doc ID 2684394.1)

Last updated on JUNE 29, 2020

Applies to:

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

Symptoms

A customer is ETO project user who creates purchase orders from components in parts list attached to ETO WO tasks. If  the requested date in the parts list (DRQJ.F3111) and planned effective date in purchase order detail (DLEJ.F4311) are different,
unexpected planned order messages are created by PRP (R3483) b
ecause the purchase order is related with the parts list attached to ETO WO tasks.

Unexpected plan order messages are created by R3483 only when the request date in the parts list (DRQJ.F3111) and planned effective date in thepurchase order detail (DLEJ.F4311) are the same date.

The planned effective date in the purchase order detail (DLEJ.F4311) is different from the requested date in the parts list (DRQJ.F3111). 

The steps to replicate the issue are:

  1. Create an ETO project, insert a WO task and attach parts list to the WO task. There is a component in the parts list.
  2. Run PRP (R3483)
  3. PRP creates a PLO (order type is OR) for the component. Process the PLO to add a purchase order 'Requisition'.
  4. Generate purchase order 'Quote' from the purchase order 'Requisition'.
  5. Suppler of the 'Quote' order answers back New Date. So dates of the 'Quote' order are changed. As a result, new planned effective date in purchase order detail (DLEJ.F4311) is different from request date in ETO related parts list (DRQJ.F3111).
  6. Run PRP(R3483) again.
  7. PRP creates a PLO (order type is OR) for the component again. A customer requests that this PLO should be created.

If the purchase order (PO) is generated from  a Quote (OQ) order, the purchase order (PO) has requested date that is different from the requested date of parts list. PRP should not create the PLO again even if the requested date in the parts list (DRQJ.F3111) and planned effective date in the purchase order detail (DLEJ.F4311) are different.

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.