E1: 31P: PRP / Master Planning Schedule - Multiple Plant - R3483 Suggests Incorrect PRP Messages to Increase or Create New Purchase Orders when Existing OP Orders are on Budget Hold (Doc ID 2898748.1)

Last updated on SEPTEMBER 26, 2022

Applies to:

Symptoms

When using ETO Project and PRP - Master Planning Schedule - Multiple Plant - R3483 for project planning, after processing the PRP messages to create purchase orders, they are checked against the project budget. The OP orders created from PRP messages go on hold (e.g. Hold Code B1) as per the setup.
If the purchase orders are on budget hold and then re-running MRP, the system suggests creation of new purchase orders instead of using the existing OP orders that are already on budget hold if the G and / or L messages are removed from the UDC 34/MT.
When the G and / or L messages are defined in the the UDC 34/MT, the system incorrectly suggests increasing the order quantity of certain purchase orders on hold.

The issue can be reproduced at will with the following steps:

1. P0006 - Create a Job Cost business unit and set correct accounts for the new job cost business unit
2. P4101 / P41026 - Create 2 project specific parent items (Stk Ty = G, Ln Ty = S) and 2 project specific purchase components (Stk Ty = H, Ln Ty = SC); Inventory Cost Level = 3, set for 09 actual costing
3. P4105 - Define Unit Costs for 09 Sales / Inventory Cost Method for both project specific components
4. P3002 / P3003 - Create BOM / Routing for the above project specific parents. Use component with QNTY = 1
5. P42090 - Set the Hold Codes for the B/P and Person Responsible
6. P31P001 - Create a job cost related ETO Project with multiple shippable manufactured tasks
7. P31P001 - Process MFG tasks and see that WO P.L. and WO Routing Instructions have been attached correctly; Financial Plan and Financial Actuals tabs are showing the Planned Amounts correctly
8. UDC 34/MT - Both G / L messages are defined correctly in the UDC table
9. R3483 - Run PRP to generate O - order messages for OP orders creation against project specific purchased components for all manufactured tasks
10. IV - Create a P4310 version that is called from the P3411 version and make sure the processing option # 1. Budget Hold Code on the 11-Budgeting tab is set to e.g. B1 - a hold code defined for purchased order
11. P3411 - Use the above P4310 version and create related purchase orders that go on hold: Hold Code = B1
12. P3111 - Verify work order parts detail lines for all project specific components and see that their fields Related PO/SO No (Alias: RORN), Rel. Ord Type and Related PO/SO Line No are populated correctly
13. P4310 - Verify the related purchase orders created via P3411; all details are set correctly on both the header and detail lines of the purchase orders. All related purchase orders went on budget hold, as expected
14. R3483 - Re-run PRP: same version and processing options as above
15. P3411 - The system generates some G - Increase Order Quantity messages against certain purchase orders on hold. If those messages are processed, the stock level in increased incorrectly
16. UDC 34/MT - Remove both G and L messages from the UDC table 17. R3483 - Re-run PRP: same version and processing options as above
17. P3411 - Verify PRP messages; the system triggers new O – Order messages for project specific components and disregards the existing supply orders that are on budget hold

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.