Planning Time Fence Date For Items Is Affected By Non Standard WIP Discrete Jobs When Profile MRP:Create Time Fence = Yes (Doc ID 1351421.1)

Last updated on JULY 15, 2015

Applies to:

Oracle Advanced Supply Chain Planning - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.

Symptoms

Users are on base 12.1.3 apps but have applied 12.1.3.1 code line (patch 9771731). They've run into a strange problem affecting about 14-15 items that they've found so far. Users run an unconstrained ASCP plan with Overwrite = Outside planning time fence. They have found these problem items generate a planning time fence date which is tremendously different when compared with Planning Time Fence Days shown in the Organization Item Attributes. The planning time fence date is being pushed out well into the future. A couple of examples are:

Note: Profile MRP:Create Time Fence = Yes per business requirements. Plan run date is 15-JUL-2011

A. Item = JMake
Org Code = PRD:M1
Planning Time Fence in Org item Attributes = Total Lead Time
Planning Time Fence Days in ASCP = 10
Planning Time Fence Date in ASCP = 26-MAR-2012 (correct 2012!!!)
No planned orders are created inside of 26-MAR-2012
There are No firm supplies in reviewing all supplies throughout the plan horizon that we can find and we checked all supplies - but there's many planned order demands unsatisfied before this.
Other items with this same exact setup for lead times work just fine
We did find one non standard discrete job which was not firm out on 17-MAR-2012. We pulled it in to Oct 2011, ran collections and plan - and the PTF data changed to Oct 2011.

B. Item = Jmake1
Org Code = PRD:M1
Planning Time in Org item Attributes = Total Lead Time
Planning Time Fence Days in ASCP = 6
Planning Time Fence Date in ASCP = 06-APR-2012 (correct 2012!!!)
No planned orders are created inside of 06-APR-2012
No non standard jobs - no firm supplies. In fact the only supplies were on hand

The customer workaround is to set profile MRP:Create Time Fence = No. They don't like this as when they need to firm a true supply (ie wip job, PR/PO), they don't want any other commitments for supply inside the barrier that the profile creates when set to Yes. This is the exact same issue described in Bug 9505806 but the issue was never pursued since that customer went with setting the profile to No


STEPS:
1. Run unconstrained ASCP plan
2. Review supply demand for items
3. Find 14 -15 items that have unusually large calculated planning time fence date

Cause

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