Last updated on JUNE 29, 2017
Applies to:Oracle Rapid Planning - Version 12.2.4 and later
Information in this document applies to any platform.
On : 12.2.4 version, Planning Engine in UAT
Users are on 12.2.4 and have applied VCP Cum Patch 18.104.22.168 - 19549533. The currently have the following RP file versions
Important: They are currently testing another one off patch for RP that is NOT in this instance, yet which is patch 22571209 which provides engine.zip 120.134.12020000.120 - They also have bug 22378404 opened in RP Dev at this time, too.
Users are running an Unconstrained RP plan with Mfg Org calendar 5 on 2 off. However planned order compression days do not appear to be calculating correctly for buy items. Example data:
Item name = FA SCW1301 Item id = 44019 - Buy item
Org code = UBD:WEI Org id = 85
Pre processing = 1
Processing = 14
Post processing = 1
Total LT = 16
They show a planned order qty = 100 due 08-FEB-2016 which is the anchor date of the plan. Compression days = 12. They expected at least to show Compression days = 14 or perhaps include Pre and Post processing = 16. The exception (Orders with Insufficient Lead Time) also shows the same number of days (12). In the exception it also shows field Min Processing Time = 12 - so this appears wrong too.
Questions that customer would like answered as part of this investigation:
A. What should the Min Processing Time include for this example
B. What should Compression days include for this example
According to Bug 10145266 - it should be looking at the Org Mfg Calendar. This calendar has been reviewed and is 5 on 2 off.
Expected the compression days/Min Processing Time to be 14 or 16 depending on how A and B are answered above
The issue can be reproduced at will with the following steps:
1. Run Unconstrained RP plan
2. Review Supply Demand output and Compression Days/Exceptions
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms