Ownership Information:
Chapter 4. Managing Metadata
Defining Consolidation Methods
http://download.oracle.com/docs/cd/E17236_01/epm.1112/hfm_admin.pdf
Chapter 8. Managing Ownership
http://download.oracle.com/docs/cd/E17236_01/epm.1112/hfm_user.pdf
Chapter 4. Managing Metadata
Defining Consolidation Methods
http://download.oracle.com/docs/cd/E17236_01/epm.1112/hfm_admin.pdf
Chapter 8. Managing Ownership
http://download.oracle.com/docs/cd/E17236_01/epm.1112/hfm_user.pdf
Applies to:
Hyperion Financial Management - Version: 4.0.1.0.00 to 11.1.2.0.00 - Release: 4.0 to 11.1
Goal:
An explanation is required of how to extract Ownership Management data from HFM system accounts.
Solution:
The ownership management data in HFM is just like any other piece of data, it can also be extracted through the "Extract Data" option and loaded through the "Load Data" option (as long as the "File Contains Ownership Information" check box is selected prior to load).
Apart from when being loaded from a data file, the data should normally be adjusted only via the Ownership Management module of the web user interface of Financial Management. This is discussed at length in the HFM User Guide documentation, chapter "Managing Ownership" section "Entering Ownership Information".
The User Guide for the 11.1.1.3 release of Financial Management can be found by clicking here.
However, it is sometimes important to understand where this information is stored within the 12 fixed data dimensions of HFM. The below hints should be understood in the context of the existing information in the User Guide.
For example..
[Active] account
The "Active" Yes / No information is stored in a system account [Active] of the Parent Entity in Entity dimension against the child entity in ICP dimension, and indicated by the number "1" in that account. Normally a blank value or a zero is "Not Active". This is unless the application settings metadata have "DefaultValueForActive" set to 1.... then all blank values are counted as being "Active". For more information on "DefaultValueForActive" metadata property, see the HFM Administrators guide for the relevant version of the software.
[Method]
The Method account data is indicated by a "1" in the account [Method] for the Parent entity in Entity dimension, Child entity in ICP dimension and the name of the method in Custom 1 dimension. It is very important that only one C1 method member has a "1" stored against it, in any particular Scenario-Year-Period-Entity-ICP combination, otherwise it can lead to system problems.
The POWN, PCON, PCTRL, SharesOutstanding, VotingOutstanding, SharesOwned and VotingOwned are all numeric values stored in Custom1-Custom4 [None] member.
To see this data you must be looking at the [None] member in the Value dimension, and also the [None] member in the custom 1-4 dimensions (except Method account).
As with any other HFM data it is not recommended to build integrations directly into the relational database data store underneath HFM. Oracle reserves the right to change the relational database schema in future releases without prior notification. The correct way to access this data is by loading/extracting of data files, using Smartview, FDM, HAL or DIM, Extended Analytics or Livelink (Hyperroll). Any integration between HFM data and external sources should be done in cooperation with Oracle Consulting Services or an approved 3rd party partner company of Oracle Corporation.
For example..
[Active] account
The "Active" Yes / No information is stored in a system account [Active] of the Parent Entity in Entity dimension against the child entity in ICP dimension, and indicated by the number "1" in that account. Normally a blank value or a zero is "Not Active". This is unless the application settings metadata have "DefaultValueForActive" set to 1.... then all blank values are counted as being "Active". For more information on "DefaultValueForActive" metadata property, see the HFM Administrators guide for the relevant version of the software.
[Method]
The Method account data is indicated by a "1" in the account [Method] for the Parent entity in Entity dimension, Child entity in ICP dimension and the name of the method in Custom 1 dimension. It is very important that only one C1 method member has a "1" stored against it, in any particular Scenario-Year-Period-Entity-ICP combination, otherwise it can lead to system problems.
The POWN, PCON, PCTRL, SharesOutstanding, VotingOutstanding, SharesOwned and VotingOwned are all numeric values stored in Custom1-Custom4 [None] member.
To see this data you must be looking at the [None] member in the Value dimension, and also the [None] member in the custom 1-4 dimensions (except Method account).
As with any other HFM data it is not recommended to build integrations directly into the relational database data store underneath HFM. Oracle reserves the right to change the relational database schema in future releases without prior notification. The correct way to access this data is by loading/extracting of data files, using Smartview, FDM, HAL or DIM, Extended Analytics or Livelink (Hyperroll). Any integration between HFM data and external sources should be done in cooperation with Oracle Consulting Services or an approved 3rd party partner company of Oracle Corporation.
No comments:
Post a Comment