E1: 31P: PRP Messages Should be Created for Each Demands Instead of Summarized One (Doc ID 2117107.1)

Last updated on AUGUST 30, 2016

Applies to:

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

Symptoms

PRP is not planning for each lower level demands in a project. R3482/R3483 consolidates component demands with different request dates coming from multiple levels in parts list. Purchase orders are consolidated to a demand with the earliest requested date.
This requirement was rejected on Bug 11025060 - PROJECT PURCHASE PLANNING - SAR: 8943905 once. But the current function; summarizing multiple demands with different request dates to 1 demand with earliest request date in a project makes some troubles into the customer business process. If the customer uses current function, there are no spaces to store purchased materials that are used more than a month later. As you know, to keep materials in warehouse costs a lot. It is not cost effective.

Requesting PRP should plan for each demand in all levels of a multi-level Bill of Material (BOM) instead of summarizing demands.
It is OK to summarize demands with the same request date.

Cause

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 hundreds of Community platforms