Last updated on MARCH 08, 2017
Applies to:Oracle Demantra Demand Management - Version 7.3.1 and later
Information in this document applies to any platform.
Starting at 7.3.1, causal factors, tree structures and other engine settings are configured per profile.
The BASE profile acts as a template that can be modified and used to base new profiles on but not used directly anymore.
Simulation profile is always taking these settings from it's father BATCH profile (in this case profile 1).
So any causal or other settings that are now profile specific, should be configured on profile 1 and not on the BASE profile (0).
1. In some cases defined shape causal factors could have overlapped definition and may cause co-linearity. So actual configured data should be checked for not overlapping.
2. There could also be one shape causal that does not have a corresponding column in sales_data - this will cause an error when this shape is activated in profile 1 if the column is not there.
By creating a new activity factor with the following steps in Demantra 7.3.1, simulation is never 0 and the amplitude of the expected period is lower than the first periods which have initial data / overwritten / provided.
Expected behavior before the upgrade - -To have 0 Simulation where Activity Factor has a 0 value and a similar shape / amplitude in the result, where no history was over/written.
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