Query On Attribute Versioning On Dimension Component (Doc ID 420094.1)

Last updated on OCTOBER 04, 2016

Applies to:

Oracle Enterprise Performance Foundation - Version: 11.5.10.2
Oracle Profitability Manager - Version: 11.5.10
Information in this document applies to any platform.

Goal

Q1. Attribute values against dimension members are versioned.  However, the behavior of attribute versioning seems to be different than hierarchy versioning.  This is presumably because dimension members are not versioned.  While hierarchy versions are defined with an explicit effective date range (effective start and end dates), attribute versions have no such effective date range. Attribute versions do however, have a creation date and a last updated date.

How does the mapping rule engine select the appropriate version of an attribute given an effective date in the past?

Q2. Currently developing a Profitability Manager (PFT) model against SEP-2006 data.  Subsequently, the effective date applied to the mapping rules at run time is SEP-2006. However, the dimension members and attributes have been created on this instance in February and March 2007.

Would an attribute-based dimension component use the attribute version with the highest "creation date" not greater than the effective date selected at run time? If so, is there any way to "back date" an attribute version?

Q3. On a related issue, have loaded the dimension attributes using the WebADI spreadsheet.  Have noticed that it is possible to overwrite the attribute values that were previously loaded into Oracle Enterprise Performance Foundation (EPF).  After originally loading incorrect attribute values loaded into EPF, these values were reloaded.  Expected that a new version of the attribute would be created, but instead the existing version was overwritten with the new attribute values.

If this is the expected behavior, then it is implied that there is no versioning capability for attribute-based dimension components.

STEPS TAKEN
1. Load dimension members and attributes using the WebADI spreadsheet loader.
2. Change the attribute values on the WebADI spreadsheet and reload.
3. No new Version ID will be created for that Attribute ID. Attribute values in the related dimension's attribute table will be updated.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms