My Oracle Support Banner

Classic Constrained Plan With Post Processing Lead Time For Make Items Moving WIP Discret Job Sugg Due Date But Not Sugg Start Date (Doc ID 2290027.1)

Last updated on APRIL 01, 2021

Applies to:

Oracle Advanced Supply Chain Planning - Version and later
Information in this document applies to any platform.


On : version, Constrained planning in SIT

Users are on 12.1.3 and have applied VCP aka R12.SCP_PF.B.Delta.4 - Patch 22706126

Users are running an EDD Classic Constrained Plan with profile MSO: Lead Time Control = Do not violate minimum processing lead times. They are seeing an issue after applying the latest patch above where they saw component planned orders violating the Planning time fence. Further investigation showed that downstream wip job had start date of the anchor date of the plan which explained why the component planned orders were due inside the PTF. In looking at the WIP job, however we discovered it was being pushed out more than a year in the future with it's sugg due date, but the sugg start date remained the anchor date of the plan. Example data:

Item = 133016-01
Fixed Order Qty = 1

They have a WIP job qty = 1 (trans id = 1064909039) that shows the following dates in ASCP
Sugg Start Date = 27-JUN-2017
Sugg Dock Date = 12-OCT-2018
Sugg Due Date = 09-NOV-2018
Old Due Date = 03-AUG-2017

Lead Times for this item are as follows:
Pre processing LT = 5
Fixed LT = 3.497846
Var LT = 0.472524
Post Processing LT = 22 - They are using Post Processing capability for make items in ASCP
Planning Time Fence Date = 05-JUL-2017

In the EBS source instance the wip job has the following dates
Start = 27-JUN-2017
Completion = 03-JUL-2017

Profile MSO: Firm Work Orders/Operations Within Time Fence = Yes.

Analysis: In thinking on this further, the old due date of the WIP job includes the 22 days post processing LT which would be outside the PTF date as the old due date = 03-AUG-2017. So ASCP can move this job as it's original due date is outside the PTF. However, if it does this, then it has to move the Sugg Start Date along with it. In this case before the job was moved it was 27-JUN-2017 and after the job was moved to 09-NOV-2018, the Sugg start date is still 27-JUN-2017. So if the job due date moves, the Sugg Start Date has to move with it as currently it's well over a year lead time when the actual lead time is only 4 days fixed and var + 22 days post processing which is at most 1 month

Expected the sugg start date to move out in the future to correspond with the moved sugg due date

The issue can be reproduced at will with the following steps:
1. Run EDD Classic Constrained Plan after patching
2. See item orgs where discrete jobs due date is pushed well out in the future while the sugg start date remains unchanged


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

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