ATP Pegging For The Resources Is Not Honoring The Material Constraint
(Doc ID 1945119.1)
Last updated on MARCH 08, 2017
Applies to:Oracle Global Order Promising - Version 184.108.40.206 and later
Information in this document applies to any platform.
Qn1:We are running an ATP plan which is capacity constraint plan, we have a supply chain scenario as below
|Level||Item||Requested Date||ATP Date / Source||CTP Resource pegged date|
|0||Model A||9th Oct||11th April / Make at 101||13th Nov 2014|
|1||Model Phantom||16th March 15|
|2||Model Phantom||16th March 15|
|3||Buy Component||16th March 15 / External Supplier|
|2||Model D||27th Oct 14 / Other Org,201|
|2||Model E||27th Oct 14 / Other Org,201|
Lead Time : 23 Days of Processing lead time , 7 Days of pre processing lead time
My Request date for Top ATO Model is today I,e 9th of October, getting the 2 other models from other Org on 27th of October , a buy component required to make top model have a material constraint and available date is 16th March 2015 but the resources to make the Top model are pegged on 13th November 2014 which is Manufacturing lead time as Manufacturing lead time constraint and also all the resources are pegged on 13th November 2014.
Since we have a material constraint and we can start manufacturing the Top model only from 16th March 2015 ,I see the resources are pegged on 13th November instead of 16th of March which is Incorrect and also all the resources pegged to 13th November only instead of their exact required date as per the routing sequence than on completion date.
ATP should check the availability of these resources from 16th March onwards.
We see this behavior in all of the ATP pegging details .
Qn2:When we use MSC: Use Enhanced Forward ATP - Yes, we are seeing all the resource requirements on the Due date of the planned order created by ATP for the finished good item.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|