Excess Planned Order Created Post VCP 22.214.171.124 Patching Specific For Constrained Without Detailed Scheduling ASCP Plan - Pegs Completely To Excess
(Doc ID 1553325.1)
Last updated on AUGUST 19, 2019
Applies to: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 SCO Without Detailed Scheduling in PROD
This issue is a direct hit with bug 14608996. However this fix is not available until 126.96.36.199 comes out. Users upgraded from VCP 188.8.131.52 to VCP 184.108.40.206 patch 14247039. Using 64 bit Linux MBP with one off patch 14514908 with file MSONWL64.ppc 120.3.12010000.250 with no one offs. They run EDD Constrained Plan Without Detailed Scheduling (SCO). In 220.127.116.11 they did not have this problem but they do have it in 18.104.22.168
In uploaded file VCP_Excess_PlnOrd_Screenshots.docx there are 3 examples. However the first example was from a prior set of data files which we do not have however the 2nd and 3rd example transaction id's are in the current set of data files.
item name = JEM1 Org Code = PRD:M1
In 22.214.171.124 code line there's plenty of on hand and supplies to cover the demand. However there's a planned order qty = 200 which pegs to excess completely. This planned order is not needed at all and was not dropped.
item name = JEM2 Org Code = PRD:m1
In 126.96.36.199 code line there's plenty of on hand and supplies to cover the demand. However there's a planned order qty = 3 which pegs to excess completely. This planned order is not needed at all and was not dropped. Transaction id = 58191947
The screenshots show that 188.8.131.52 code line did not have this problem for the same example. Customer did run tests on 184.108.40.206 in test prior to moving to PROD but they missed this problem and confirm it does happen in Test on 220.127.116.11 as well
Expect planned orders not to be generated pegging completely to excess
The issue can be reproduced at will with the following steps:
1. Apply 18.104.22.168 patching
2. Run SCO Without Detailed Scheduling EDD plan
3. Review workbench output
4. issue did not occur on 22.214.171.124 code lin
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