27/11/2020 Document 452817.

PowerView is Off Last Login: November 27, 2020 8:40 PM IST Saidaiah (Not Available) (0) Contact Us Help

Dashboard Knowledge Service Requests Patches & Updates Community

Give Feedback...
Copyright (c) 2020, Oracle. All rights reserved. Oracle Confidential.

How To Get Forecasting Buckets Generated For The Entire Horizon When The Item Location Combination Is Dead To Bottom
(Doc ID 452817.1)

In this Document Was this document helpful?

Goal Yes
No
Solution
References
Document Details

APPLIES TO: Type:

HOWTO
Status:
PUBLISHED
Oracle Demantra Demand Management - Version 7.1.1 and later Last Major
Sep 5, 2014
Information in this document applies to any platform. Update:
Dec 5, 2019
***Checked for relevance on 04-Sep-2014*** Last Update:

Related Products

GOAL Oracle Demantra Demand

Management

Q1: We have few combinations in Demantra for which there are only few forecast buckets. We need the buckets to be available
Information Centers
for all periods from now, until the end of planning/forecast horizon. What is the best approach to achieve this?
Information Center Overview
Q2: Also, why does Demantra not create complete buckets for all periods from now until the end of the planning/forecast and Alerts: Oracle Demand
Management (Demantra)
horizon? [1400486.2]

Document References

Understanding Poor Forecast

SOLUTION Results, Bad Forecast Results,
or Confusing Forecast Results
generated by the Demantra
Note that before reviewing this document it should be verified that the Demantra engine completed successfully. Analytical Engine [744602.1]
This can be done by going to the Demantra Worksheet --> Data --> Forecast Detail. Any status other than
Success will need to be investigated starting with the Engine Logs detailed in Note 741464.1
Recently Viewed
What creates the forecast rows in the future is the Insert_Units* procedure that runs as part of the analytical forecast engine
run. The filter that this procedure uses to analyze each combination is: Demantra Forecasts Go To
Zero All Of A Sudden For A
SELECT DISTINCT item_id, location_id, '|| vs_extra_pk_list_sd ||' is_fictive' || vs_levels_list || ' Week [2007480.1]
FROM mdp_matrix m Running Integration
WHERE prediction_status <> 99 Interface with no errors but
the Data Is Not Downloaded
AND do_fore <> 0 - Transfer Step, the Data
AND level_id > 0 does not get Loaded into the
Demantra Tables
So basically, make sure those combinations meet the following rules in the mdp_matrix table: [1956515.1]
- prediction_status <>99 (99 = Dead Address from lack of recent sales) Zero Forecast In Demantra
for some Combinations
-do_fore <> 0 (0 = User told the system not to forecast this combination anymore) [2036384.1]
No Demantra Forecast
-level_id > 0 (0 = internal flag set by engine) Generated - Common Issues
[848205.1]
Fusion Demand Planning:
If the combinations in question don't meet all of the above criteria, that's the reason the forecast buckets aren't generated by Demand Plan fails with error
&quot;The Plan&#39;s
the latest engine run.
Population Contains
Products, But The Products
Note that on the front end of the application the end users can view the prediction_status and do_fore flag by adding the Do Not Have Any
following two levels to the worksheet that they are running: Historic&quot; [2555578.1]
Show More
Forecast System Status - this will tell the prediction status of the combination

A value of Good for Forecast (1), Young Address (98), or Zero Forecast (97) will satisfy the first rule for Insert_Units

Forecast User Status - this will tell the user if the combination was turned off

A value of Do Forecast (1) or Do Zero Forecast (2) will satisfy the second rule for Insert Units

If these levels are not available to the users in the Demantra tool then the system administrator will need to turn them to be
enabled. To do this go to Business Modeler --> Components --> Create/Open Component. After double clicking on the
component then go to the Levels screen, scroll down and find the two levels in question, right click on them and choose Full
Control. After saving it then the web server will need to be restarted for the changes to appear to the end users.
https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=475851396913273&id=452817.1&displayIndex=52&_afrWindowMode=0&_adf.ct… 1/2
27/11/2020 Document 452817.1
Possible Scenarios and Resolution Paths (note that this is not an exhaustive list)

1) The combination seems to have recent sales and the only issue appears to be that the Forecast System Status
value is set to Do Not Do Forecast (do_fore = 0).

If this is the case then add the series 'Stat forecast Y/N' (or it might be called Do Forecast in later versions), re-run the
worksheet, and change the problem combinations from a value of Do Forecast to Do Zero Forecast. After that is done then
press the update button, re-run the worksheet and confirm that the Forecast System Status level is set to a value not equal to
Dead Address.

The next Batch Engine run should then insert the values into the forecast

Note that just running the Simulation engine alone on these combinations will not create the future buckets as the Simulation
engine does not run the Insert_Units procedure.

2) Forecast User Status is set to Do Forecast (Do_Fore =1) but Forecast System Status = Dead Address
(Prediction_Status = 99)

This indicates that the system considers this combination dead as the result of not enough demand being found. To turn it back
from dead then either load more sales for this combination or use one of the historical override series to put in some pseudo
Demand so that the system thinks it has enough sales for it to become either Young or Good for Forecast.

Confirm that you have added in sufficient demand to flip the Forecast System Status flag by re-running the worksheet and
ensuring the the Forecast System Status is not equal to Dead Address anymore. When this is complete then the next time the
full engine runs, you should see future forecast buckets.

If your goal here is to merely create future buckets so that a pipe line forecast can be created for the next X number of months
or you don't want the engine to run yet (e.g. you're in the middle of the month or week), then you can go to the Member
Management application and manage the combinations in question by using the option to create zero forecast rows.

3) Forecast Engine Executable is a different version from the database.

We have seen in some cases that the engine executable is on a different version from the database version. Confirm this is not
the case by the going into the engine manager log and in the first few lines, it will give the engine version. Compare this value
to the database by running the following sql:

select * from version_details_history;

We have seen this mismatch occur when a client continues to use an automated process that calls an old engine executable.
Make sure that the automated process is looking at the latest Demantra application folder. Also, ensure that if a patch was
recently applied that it was applied to all machines that are running the engine if you are using the distributed mode.

* Before Insert_Units will even run then the value in the parameter RunInsertUnits needs to be set to 1 - Run Insert Units (3 -
Run Insert Units without Executing Rolling Profiles is also an option). The value of this parameter is found by going to the
Business Modeler --> Parameters --> Engine --> Shell.

Note that we have seen instances where the value in the Business Modeler is not in synch with the database entry so the way to
see the true value is by running the following sql:

select value_float from init_params_0 where pname ='RunInsertUnits';

If the Business Modeler is showing 1-Run Insert Units but the database is showing 0 then change the value (in the BM) to
something other than 1 - Run Insert Units, press Save, then change the value back to 1- Run Insert Units and press Save one
more time.

Re-run the sql again and ensure that the value is now set to 1 (or 3 if you don't want to run Rolling Profiles as per the
parameter's description in BM).

REFERENCES

NOTE:744602.1 - Understanding Poor Forecast Results, Bad Forecast Results, or Confusing Forecast Results generated by the
Demantra Analytical Engine
Didn't find what you are looking for? Ask in Community...

Related
Products

More Applications & Technologies > Value Chain Planning > Oracle Demantra > Oracle Demantra Demand Management > Engine > Batch_Engine

Keywords
DEMANTRA; FORECAST; ORACLE DEMANTRA; OVERRIDE; PARAMETER; VERSION

Back to Top
Copyright (c) 2020, Oracle. All rights reserved. Legal Notices and Terms of Use Privacy Statement

https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=475851396913273&id=452817.1&displayIndex=52&_afrWindowMode=0&_adf.ct… 2/2