Unconstrained Project ASCP Plan Nets Supply Demand Correctly. However Review of Pegging Shows Certain Project Demands Peg To Late Planned Order Supplies Unexpectedly

(Doc ID 1547127.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Advanced Supply Chain Planning - Version 12.1.3 and later
Information in this document applies to any platform.
***Checked for relevance 02-SEP-2014***


On : 12.1.3 version, Memory Based Planner in PROD:
Users are on 12.1.3 and have applied VCP patch 13833266 - no one offs for MBP found at this time.
This is a Project/Task environment and key plan options:

Reservation level = Planning Group (so they can use common on hand which is not assigned to any project nor task)
Hard Pegging Level = Project-Task
This is an unconstrained ASCP plan and they're seeing planned orders specific to the project/task being late to the demand (There's no planning group for these specific project/task example). They are pegging supply by demand priority and profile MSC: Use FIFO Pegging = No. Planning Time Fence is disabled. About 40 items run into this problem. It didn't seem to be an issue before but they're running across it now.
Item = JM123
Org = TST:M1
Fixed Order Quantity = 1
Fixed Days Supply = 30
Pegging = End Assembly/Hard Pegging
MSO: Demand Window Size = 1
MSO: Supply Window Size = 1
Planned order Qty = 1 due 06-FEB-2013 (Project = 118966) Pegs late to a Work Order Demand qty = 1 due 25-JAN-2013 (Project = 118966). The question is why is the planned order due later than the demand in unconstrained plan.

We do notice on export of supply demand data that they line up nicely for any given bucket. The problem is ASCP is not assigning the right project to the planned order in the correct bucket. We can see a supply work order qty = 1 due 25-JAN-2013 but that's for project = 118970
Things we tried:
A. We set the following profiles:
MSC: Minimize Project Cross Peg within Window was NULL and we set this to Yes
MRP: Create Time Fence from Yes to No. However these did not help
B. Set profile MSC: Use attribute based netting from No to Yes. This caused us to get cross project pegging
C. Tried setting item attribute from End Assembly/Hard Pegging to just Hard Pegging. Results of the two scenarios we tested here:
Scenario 1:
1. Set pegging to 'Hard Pegging' for a few items in source instance
2. Ran complete refresh collections
3. Set profile MSC: Use attribute based netting = No in ASCP
4. Ran ASCP Plan
Results: Late Supplies created for demands.
Scenario 2:
1. Set pegging to 'Hard Pegging' for a few items in source instance
2. Ran complete refresh collections
3. Set profile MSC: Use attribute based netting = Yes in ASCP
4. Ran ASCP Plan
Results: Supplies pegged across projects.
At this point we ran out of ideas
  Expect Supplies and demands for project/task to line up with one another in
  an unconstrained plan and not be late
  The issue can be reproduced at will with the following steps:
  1. Run Unconstrained Plan with Project/task
  2. Review workbench and see late supplies and early supplies for


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