E1: 34: R3483 Does not Consolidate Demand as per Order Policy Code "4" when Availability Checking is Activated
(Doc ID 2305880.1)
Last updated on SEPTEMBER 09, 2017
Applies to:
JD Edwards EnterpriseOne Requirements Planning - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
R3483 - MRP Multi-Plant
R3483 does not respect Order Policy Value with Order Policy Code=4 and Branch Relationship with Availability Checking. Instead of collecting all the demand for Order Policy Value (e.g. 50 days), it works just as Lot for Lot, as Required (OPV=1).
You can see the goods are collected once per week instead of collecting all the demand for 50 days in advance.
When removing Availability Checking flag from Branch Relationship and re-run R3483, the demand for 50 days is aggregated as it should.
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 |