My Oracle Support Banner

IO Forecast Quantity Is In Decimals While Original Demantra Forecast And ASCP Show Whole Number Integers (Doc ID 2445800.1)

Last updated on DECEMBER 03, 2019

Applies to:

Oracle Inventory Optimization - Version 12.1.3 and later
Information in this document applies to any platform.


On : 12.1.3 version, Engine Comp for Oracle RiskOpt in PROD

Users are on 12.1.3 and have applied VCP aka R12.SCP_PF.B.Delta.4 - Patch 22706126 - Users are running an IO plan and notice the forecast is showing in decimal qty's whereas in Demantra and ASCP they are whole numbers. Example data:

In Demantra users are using a Period forecast for
Item = 7210-024173
Qty = -2 from 01-OCT-2018 to 31-OCT-2018
Qty = -2 from 01-JAN-2018 to 31-JAN-2019

The ASCP workbench that has this forecast attached to this organization also shows qty = 2 like the above in the ASCP workbench after the plan run. However the IO workbench shows the following:

Order Type Sugg Due Date Orig.Qty
Forecast 10/5/2018 -0.451613
Forecast 10/12/2018 -0.451613
Forecast 10/19/2018 -0.451613
Forecast 11/16/2018 -0.645161
Forecast 1/18/2019 -1.290323
Forecast 2/15/2019 -0.709677

It should be noted that adding the first 4 values together = -2 and adding 5th and 6th together also = -2 so the overall total match. The issue is it seems to be spreading the forecast

Expected IO to show only -2 integer values for forecast in the IO workbench

The issue can be reproduced at will with the following steps:
1. Run IO plan
2. Review forecast entries in IO workbench vs Demantra and ASCP forecast
3. IO shows decimal values while Demantra and ASCP show whole integer values


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.