ASCP Plan When Setting Profile MSC:Include Postprocessing Lead Time When Planning For Make Orders = Yes Pushed Planned Orders Way Out In Future Unexpectedly (Doc ID 2409104.1)

Last updated on FEBRUARY 15, 2019

Applies to:

Symptoms

On 12.2.5 Constrained planning in Production and Test
 
Users are on 12.2.5 and have applied 12.2.5.2 mandatory patching.  They are testing ASCP profile  MSC: Include Post processing lead time when planning for make orders = Yes at site level and run the ASCP plan.  However it moves the Suggested Due Date for the Planned Order more than two months into future.

Ex:
Scenario1: MSC: Include Postprocessing lead time when planning for make orders -> NULL
Plan Name: ATP
Item simulation set is not attached to ATP Plan
Item : AAABB
post processing LT is NULL
Sales Order # 3357078; Scheduled Ship Date:14-MAR-2018


launch the ATP plan

Planned Order generated for Qty 20 with Suggested Due date of 14-MAR-2018


Scenario2: MSC: Include Postprocessing lead time when planning for make orders -> YES
Plan Name: ATP
Item simulation set is not attached to ATP Plan
Item : AAABB
post processing LT is NULL
Sales Order # 123; Scheduled Ship Date:14-MAR-2018


launch the ATP plan

Planned Order generated for Qty 20 with Suggested Due date of 06-JUN-2018

Expectation
========
Expected post processing lead time to be included in the planning for the make items but this item has no post processing lead time so dates were not expected to move

STEPS
--------
1. Set profile MSC: Include Postprocessing lead time when planning for make orders = Yes
2. Run ECC plan.
3. Review data in ASCP workbench and see dates have moved 20 days in the future for no apparent reason
4. Set the profile back to No and rerun the plan, the dates are pulled back in to where they are expected

Cause

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