Last updated on MARCH 08, 2017
Applies to:Oracle Demantra Demand Management - Version 7.3.1 to 7.3.1 [Release 7.3.0]
Information in this document applies to any platform.
***Checked for relevance on 04-Dev-2013***
On version 220.127.116.11 in Production:
Using Business Modeler:
First set the parameter 'RunProportInMdp_add' to a value of Yes so that the mdp_add procedure will call the Proport procedure during the data load.
Then set 'Run_full_matrix_proport' parameter to a value of "all combinations".
This will set both parameters to a PVAL of 1 in the sys_params table, which is expected.
Problem is when the Proport is run, it acts as though the "only flagged combinations" setting was used for the 'Run_full_matrix_proport' parameter as opposed to the "all combinations" setting.
The "only flagged combinations" setting will set the PVAL = 0 in sys_params and will only update combinations that prop_changes = 1 in mdp_matrix table.
Expect the Proport to update all combinations when the parameter 'Run_full_matrix_proport' is set to "all combinations".
The issue can be reproduced at will with the following steps:
1. Log in to the Business Modeler.
2. NAV: Parameters -> System Parameters.
3. Click on the Database tab.
4. Find the parameter 'Run_full_matrix_proport' and set to "all combinations".
5. Find the parameter 'RunProportInMdp_add' and set to "Yes".
6. Save the changes.
7. Run the Data Load.
The issue has the following business impact:
The proport procedure is not updating combinations according to the parameter settings which will impact the forecast of the combinations.
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