When Profile MSC: Use FIFO Pegging = No, New Planned Orders Created Earlier Than Firm Planned Orders - Plan Is Run With Overwrite = None
(Doc ID 1518502.1)
Last updated on FEBRUARY 02, 2021
Applies to:Oracle Advanced Supply Chain Planning - Version 12.1.3 and later
Information in this document applies to any platform.
****Checked for relevance 11/20/14****
On : 12.1.3 version, Memory Based Planner
Users are on 12.1.3 and have applied VCP 22.214.171.124 Patch 10389190. They are using 32 bit MSONEW. They run EDD Classic Constrained plan and see planned orders being created before firm planned orders.
Example from an internal instance:
MSC: Use FIFO Pegging = No
MSO: Net all firm supplies before creating a planned order = All supply Types
MSO: Schedule All Firm Planned Orders First = No (IMPORTANT - We did try Yes but it didn't help - please note in current data files this is set to No)
Item = JMake
Org Code = TST:M1
Users schedule the planned orders in particular batch runs and increase the qty to cover several demands and they will schedule the date at a future date and firm it. Then they'll rerun the ASCP plan but they see planned orders generated prior to the firm planned order. They are not expecting any planned order to be generated earlier than the firm planned order
Plan run date 31-DEC-2012
They review the workbench data and schedule a large batch run for a single early planned order. In the example they use qty = 32000 with due date 21-JAN-2012. They then firm this planned order
After they rerun the plan the previous firm planned order qty = 32000 is still there and firm but two earlier planned orders are created as there is unmet demand prior to 21-JAN-2013 that can't be satisfied by on hand:
Qty = 6688 due 14-JAN-2013
Qty = 8360 due 14-JAN-2013
Customer expects no planned order to be created earlier than 21-JAN-2013 in this case. Overwrite = None is correctly set in the plan options so it won't overwrite the firm planned orders
IMPORTANT: If we set profile MSC: Use FIFO Pegging from No to Yes. This fixed the problem above and no planned order is generated prior to 21-JAN-2013 as expected but leads to a different problem which is why they keep the profile = No. What happens when the profile = Yes is that on hand pegs to future demands and near term demands peg to planned orders
Things we tried:
We did set profile MSO: Schedule All Firm Planned Orders First from No to Yes but it didn't help
Do not expect planned orders to be generated prior to the firm planned order when profile MSC: Use FIFO Pegging = No
The issue can be reproduced at will with the following steps:
1. Run Constrained plan with MSC: Use FIFO Pegging = No
2. See new planned orders created prior to firm planned order unexpectedly
3. Set the profile to Yes and the above problem does not occur. However this has another effect that near term demands peg to planned orders and future demands peg to on hand which is unacceptable
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