Compression Days For Existing Supplies Calculated Incorrectly For Constrained Plans (WIP Jobs, PR's, PO's, IR's)
(Doc ID 1634372.1)
Last updated on APRIL 30, 2020
Applies to:Oracle Advanced Supply Chain Planning - Version 18.104.22.168 and later
Information in this document applies to any platform.
On : 22.214.171.124 version, Constrained planning
Users are on 12.1.3 and have applied VCP 126.96.36.199 Patch 14247039 - Using Sun 64 bit MBP MSONWS64.ppc 120.14.12010000.93 from one off patch 17792427. They run EDD Classic Constrained plan. The issue revolves around how compression days are reported in the ASCP workbench for Purchase Orders.
From Discussion with MBP DEV - here's how compression should work on existing Purchase Orders when viewed in the ASCP workbench:
A. If Action column is None or Reschedule out - no compression days should be calculated (ie set compression days = 0)
B. If Action column is Reschedule In - calculate compression and populate as appropriate.
C. Constrained and unconstrained should work the same
We've seen that an unconstrained plan works as expected above. However for a constrained plan, it reports compression and changes the compression on a day to day basis whether it's a reschedule in, reschedule out, or none in the ASCP workbench. Support ran several test cases for this issue on 188.8.131.52 and 184.108.40.206.1 for both Constrained and Unconstrained plans and duplicated the issue with Constrained Plans. Unconstrained plans seem to follow the correct logic. We'll use example data from the customer:
Item = JMCompress
There's a PO qty = 5 due 03-MAR-2014
Compression days = 28
Action = None
Expected this PO to have 0 compression days not 28
Expect compression for both unconstrained and constrained plans to use the same logic for existing PO's
The issue can be reproduced at will with the following steps:
1. Run Unconstrained and Constrained Plans on existing PO's and make changes so that the PO will action = None, Reschedule In, and Reschedule Out messages
2. Note that Unconstrained plan seems to follow the logic described in bug 2398353
3. Note the Constrained plans do not follow this logic and show compression for all types of actions in the ASCP workbenc
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