Unconstrained Planned Orders Due Too Early and Peg Completely to Future Demands
(Doc ID 1678501.1)
Last updated on FEBRUARY 22, 2019
Applies to:Oracle Advanced Supply Chain Planning - Version 220.127.116.11 and later
Information in this document applies to any platform.
On : 18.104.22.168 version, Memory Based Planner
ASCP R12 plan - Some planned orders are showing up in the plan in incorrect places. This is after upgrade to R12. Users see differences in the planned orders compared to the 11i plan.
Screenshots show planned order too early and pegging to way out future demand - this is an unconstrained plan
Planned order qty = 15 due 27-MAY-2014 pegs all to future demand in 06-NOV-2015 - plan horizon?
Planned order qty = 60 due 21-APR-2014 peggs to demand on 16-DEC and 22-DEC (52 and 8 respectively)
Users were told to set profile MSC: Use attribute based netting = No from another SR/Bug - Users are on 12.1.3 and have applied VCP 22.214.171.124 Patch 14247039 - using 64 bit Sun MBP MSONWS64.ppc 120.14.12010000.79.1201010.4 from one off patch 16801915
Planned orders to generated to meet demand properly
The issue can be reproduced at will with the following steps:
1. Set profile MSC: Use attribute based netting = No
2. Run unconstrained plan
3. Plan has bad output. This did not happen in 11i
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