E1: 34: Allow MRP (R3482, R3483) to Allocate Supply for Production Number (PMPN) Demands on an Item That Uses Minimum Reorder Quantity
(Doc ID 3065983.1)
Last updated on JANUARY 02, 2025
Applies to:
JD Edwards EnterpriseOne Requirements Planning - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
Currently, when an item is set up to use Production Number (PMPN) and also has a Minimum Reorder Quantity, MRP (R3483) will create separate order messages per production number for the same reorder quantity. The following steps illustrate how this happens:
1. Add a manufactured item with stocking type M in F4101 and F4102; select Production Number Controlled.
2. Add a component item with stocking type P in F4101 and F4102. Turn on Production Number Controlled; Minimum Reorder Qty to 400 in Quantities page.
3. Add a BOM (P3002) for the parent; set the quantity of the purchased component to 1EA for 1EA parent item.
4. Add forecast of the parent item (10 EA) for 3 different request dates where the P3460 Production Number processing options are active.
5. Set MPR (R3483) processing options where Project Planning option is set to 2 (include PMPN Planning).
6. Run MRP over the parent and child items.
7. Check Detail Message Revisions (P3411) for the purchased component. Notice that there are three order messages for 400 EA for each Production Number.
Based on the findings under Bug 37070938, this is functioning as designed. With the Minimum Reorder Quantity and PMPN settings, MRP may create an unexpected oversupply situation.
The request is to add functionality where MRP can allocate supply to different production number demands when an item is set with both Production Number enabled and a Minimum Reorder Quantity.
Changes
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 |
Changes |
Cause |
Solution |
References |