184.108.40.206.1 OPM Firm Planned Order Batches ASCP Plan Creating Planned Orders Too Early Generating High PAB vs Saftety Stock
(Doc ID 1680120.1)
Last updated on FEBRUARY 03, 2019
Oracle Advanced Supply Chain Planning - Version 12.1.3 and later Information in this document applies to any platform.
On : 12.1.3 version, Constrained planning
Users are on 12.1.3 and have applied VCP 220.127.116.11.1 Patch 17350769 - Users using 64 bit MBP for Linux MSONWL64.ppc 120.3.12010000.355 no one offs. For 64 bit Linux Snapshot they've applied one off patch 18045950 which gave them MSCNPL64.ppc 120.2.12010000.87
Users run EDD Classic Constrained Plan. They say they did not have this problem on 18.104.22.168 code line. This is an OPM integrated with ASCP and users do firm batches and firm planned orders for batches
MSO: Lead Time Control = Do not violate minimum processing lead times MRP:Create Time fence = No
They're seeing planned orders being scheduled earlier driving high PAB vs Safety Stock. Example:
Org = TST:M1 Item = JMOPM Looks like Hard INV Safety Stock that can increase or decrease over time
Early on in the horizontal plan they have a lot of firm work orders and also have planning time fence setup for the item. On 04-APR-2014 PAB = 237,463 and SS = 158,659. It's high at this point because of the firm work orders (firm orders are NOT allowed to move) so no issue there.
However on 05-APR-2014 there's no new demand but there's two planned orders qty 67,200 each which drives PAB = 371,863 and SS = 158,659. There are other future firm work orders beyond this as well. From what we can see, there's no need for planned order until maybe July/August time frame
EXPECTED BEHAVIOR ----------------------- Expect planned orders not to be generated with such a huge PAB when they're not actually needed for several months
STEPS ----------------------- The issue can be reproduced at will with the following steps: 1. Upgrade from 22.214.171.124 to 126.96.36.199.1 patching 2. Run ASCP plan 3. Find PAB much higher than SS in many cases which they state did not occur in 188.8.131.52 code line
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!