Enforce Demand Due Date (EDD) Earliest Possible Start Time (EPST) Is Too Late
Last updated on JUNE 28, 2017
Applies to:Oracle Advanced Supply Chain Planning - Version 22.214.171.124 and later
Information in this document applies to any platform.
***Checked for relevance on 16-May-2013***
On 126.96.36.199 in Development:
EDD Plan EPST Too Late
Planned order operation Constrained Earliest Possible Start Time (EPST) in an Enforce Demand Due Date (EDD) /Decision rules plan seems to be set too late in the horizon. This is causing resource overloads because earlier resource availability is not considered.
For a particular order that is allocated with an overloaded resource, note the operation EPST is equal to the operation start time. EDD logic determined this order could not be scheduled earlier. Yet, when looking at the pegging of the “upstream” activities, there are not constraints that would account for the late EPST. How does EPST get calculated in this scenario.
Expect to see Earliest Possible Start Time to be set earlier
The issue can be reproduced at will with the following steps:
1. Run an EDD plan with Decision Rules enabled and find an overloaded resource
2. Resource requirements for first planned order. Notice that the G3T-1PPIT1 Resource is
scheduled on Jun-10 and slightly into Jun-11. The UEPST is May-24, the (constrained) EPST is
Jun-10. The operation was scheduled to start right at the EPST.
3. Supply pegging shows no material constraints
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms