Project Manufacturing Past Due WIP Discrete Job/Work Order Supplies Are Not Getting Scheduled Correctly In MRP Workbench
(Doc ID 2399452.1)
Last updated on MAY 16, 2018
Applies to:Oracle Materials Requirement Planning - Version 12.2.6 and later
Information in this document applies to any platform.
On : 12.2.6 version, Materials Requirements Plan in PROD
Users are running MRP plans which also includes Project Mfg module as they are using Project and Task. They notice for a particular item/org combination there are two past due discrete jobs for qty = 4 and qty = 9 respectively. Both jobs have different Completion Dates that are past due on the actual jobs. Early in the plan horizon there's a demand qty = 4 for this item/org combination. They notice sometimes the plan output shows using the qty = 4 work order to satisfy the early demand and moves the qty = 9 job out in the future to satisfy later demand. The next day the reverse may happen where the qty = 9 is used first and the qty = 4 moved out into the future. Both supplies have the same project/task setup. They also show the wip job qty = 4 is further along in the routing operations whereas the qty = 9 has yet to start the routing. Example data:
Item = 820-4445811-4.REV.AK
Org = TRI
There are two wip discrete jobs and in the wip module they show
WIP job = 306301 qty = 9 with start date = 02-MAR-2018 and completion date = 06-APR-2018. Operationally all qty = 9 is in queue at the first operation and has not been started
WIP Job = 306302-1 qty = 4 with Start date = 29-DEC-2017 and Completion date = 31-JAN-2018 shows that the first operation has been completed and qty = 4 is now running in the 2nd operation. So this job is ahead of the other one in the routing.
Both wip jobs are past due to anchor date of the MRP plan. The MRP plan wants the due date of the work order qty = 9 to be 09-APR-2018 and pushed the other qty = 4 out to 03-AUG-2018. They notice on successive runs the job for qty = 4 is used first to satisfy near term demand and the qty = 9 work order is pushed out to Aug-2018. So the issue is intermittent
Users expect that for multiple past due wip jobs/work orders, the MRP plan will use the supply that is further along in it's routing to satisfy the earliest demands, then use the other work orders based on the same criteria
The issue can be reproduced at will with the following steps:
1. Run MRP plan
2. Review MRP workbench supply demand output
3. Notice for a given item/org there are two past due wip jobs A and B
4. Sometimes the MRP plan uses wip job A first to satisfy the earliest demand and sometimes uses wip job B to satisfy the earliest demand
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