Unconstrained Plan Using Projects Shows Last Demands For Specific Project Pegging To Excess When Using Fixed Order Quantity (FOQ) (Doc ID 2296021.1)

Last updated on AUGUST 10, 2017

Applies to:

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

Symptoms

On : 12.2.5 version, Memory Based Planner in Pre Production/UAT

Users upgraded from 11.5.10 to 12.2.5 and have applied 12.2.5.2 VCP patching as well as CUM patch 6 on top of 12.2.5.2 - Users are a Project-Task environment running unconstrained plans and have set the following plan options:

Reservation level = Project-Task
Hard Pegging Level = Project-Task
Apply Order Modifiers = For soft pegged items only

In 11.5.10 when a Project-Task demand ended and the order modifier Fixed Order Qty (FOQ) was being used, planned orders would honor the FOQ for the plan horizon until the last demand where if the demand qty was less than the FOQ, then and only then would the order modifier be ignored and generate a planned order less than the FOQ thus netting supply demand to zero (0) for the item on a specific project-task setup. It's not working that way in 12.2.5. Example data:

A. Only 1 project-task used for demand throughout the plan horizon
item = 10729364-001
Org = CFG:L01
FOQ = 4
End Assy/Hard Pegging - all items

This has only one project/task for the entire plan horizon for this item. For this example ASCP created planned orders for qty = 4 as expected during the early and later phases of demand. When it came to the final demand for this item, it was only qty = 2. ASCP created a planned order qty = 4 and thus qty 2 is pegged to excess. In 11.5.10 it would plan the same way except when it get to the last demand for the project-task and in this case it would create a planned order qty = 2 thus violating the order modifier but only for the last demand

B. Multiple project-task used for demand for the plan horizon - let's say there were two projects-tasks for this example. Using the same item/org and data above, it would always create a planned order for qty = 4 for each project-task, there would be no splitting of any planned order and the last demands would still get a planned order for qty = 4 for each project even if the final demand was less than the order modifier for each. In 11.5.10 this worked differently where there order modifier was honored in total, but the planned orders would split between the demands for each project but still total qty = 4 for the given demand bucket to honor the order modifier but that last demand would not honor the order modifier. So for a given demand bucket you might see the following planned orders in 11.5.10 which shows a split between projects but not they still total the FOQ order modifier for a given bucket

                               ProjA    ProjB
                             =====  ====
Day 10 Pl Ord Qty      4            0
Day 20                     3            1
Day 30                     2            2
Day 40                     1            3
Day 50                     0            4

In this case as well if the last demand for Project-Task was less than the order modifier (ie qty = 2), it would ignore the order modifier and create the planned order for qty = 2 to net supply demand to 0

EXPECTED BEHAVIOR
-----------------------
Expect the plan output to be like it was in 11.5.10 and not create any excess pegged supplies

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Run ASCP Plan in 11.5.10 and 12.2.5
2. Compare planned order outputs between the two versions in the ASCP workbench
3. See that planned orders in 12.2.5 are generated in different way in 11.5.10 vs 12.2.5 and leads to excess pegged supplies



Changes

 Upgraded from 11.5.10 to 12.2.5

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