Working with Hyperion Financial Management and Hyperion Planning Data Sources

Learn about importing and querying metadata from Hyperion Financial Management and Planning data sources.

This topic contains the following sections:

• Importing Metadata From Hyperion Financial Management Data Sources

• Importing Metadata From Hyperion Planning Data Sources

• About Query Support for Hyperion Financial Management and Hyperion Planning Data Sources

Importing Metadata From Hyperion Financial Management Data Sources

When you import metadata from Hyperion Financial Management data sources, both measures and dimensions are imported into the Physical layer.

The Hyperion Financial Management hypercube model is exposed in the Physical layer in the following ways:

• There is only one measure in Hyperion Financial Management, called Value. This measure is modeled as a single fact column in the Physical layer, also called Value.

• The measure column Value - data type DOUBLE is imported for Hyperion Financial Management.

• The Value measure has three base properties: CellText, CurrencyType, and Attribute. These properties are all represented as additional fact columns.

• The Attribute property has additional sub-properties, such as IsReadOnly. These properties are also exposed as additional columns.

The following image shows how Hyperion Financial Management data is modeled in the Physical layer.

Description of the illustration GUID-61AA5B9A-E435-4CE7-845C-334AECE28F1B-default.gif

All Hyperion Financial Management dimensions are modeled as parent-child hierarchies in the Physical layer. Shared members, alternate hierarchies, and unbalanced hierarchies are supported.

Dimension member properties are exposed as columns such as Name, Description, and ShortName. An additional column called Sort Order is also displayed for each dimension. This column contains custom sort information retrieved from the Hyperion Financial Management data source.

Each Hyperion Financial Management dimension has a corresponding Point of View (POV) value that provides customized information for different users. This POV value is exposed as the Default Member in the Hierarchies tab of the Dimension dialog. Although the Default Member field is populated upon import, note that you may need to update the default values according to the needs of the user base.

Note:

Do not select the Default member type ALL option for Hyperion Financial Management hierarchies.

Importing Metadata From Hyperion Planning Data Sources

When you import data from Hyperion Planning data sources, both measures and dimensions are imported into the Physical layer.

Hyperion Planning Server version 11.1.2.4 or above is required for importing and querying metadata from Hyperion Planning Data Sources.

The Hyperion Planning model is exposed in the Physical layer in the following ways:

• The imported Hyperion Planning data source contains multiple Value columns to support measures of different data types.

• Some measures specific to Hyperion Financial Management are not imported for Hyperion Planning data sources.

• The Attribute property has additional sub-properties, such as IsReadOnly. These properties are also exposed as additional columns.

The following image shows how Hyperion Planning data is modeled in the Physical layer.

Description of the illustration GUID-78FF6DFC-8808-4EB0-951B-E7FF9F154C96-default.gif

All Hyperion Planning dimensions are modeled as parent-child hierarchies in the Physical layer. Shared members, alternate hierarchies, and unbalanced hierarchies are supported.

Dimension member properties are exposed as columns such as Name, Description, and ShortName. An additional column called Sort Order is also displayed for each dimension. This column contains custom sort information retrieved from the Hyperion Planning data source.

Each Hyperion Planning dimension has a corresponding Point of View (POV) value that provides customized information for different users. This POV value is exposed as the Default Member in the Hierarchies tab of the Dimension dialog. Although the Default Member field is populated upon import, note that you may need to update the default values according to the needs of the user base.

Note:

Do not select the Default member type ALL option for Hyperion Planning hierarchies.

About Query Support for Hyperion Financial Management and Hyperion Planning Data Sources

Both member queries (dimensional browsing) and data queries (measure analysis) are supported for Hyperion Financial Management and Hyperion Planning data sources.

Use the EVALUATE_PREDICATE Logical SQL function to access these functions specific to Hyperion Financial Management and Hyperion Planning:

• PeriodOffset used to access prior or future periods through an offset.

• SuppressDerived, SuppressInvalidIntersection, SuppressNoAccess, SuppressZero, SuppressError NA suppression functions specific to Hyperion Financial Management.

• Base to return the leaf members below a given ancestor member.

• CommonChildren.

• User-defined functions.

See EVALUATE_PREDICATE for detailed information about syntax and usage.

Oracle BI EE supports PERF_PREFER_SUPPRESS_EMPTY_TUPLES for inserting the SuppressMissing function into the Hyperion Financial Management or Hyperion Planning data query to suppress missing cells. The PERF_PREFER_SUPPRESS_EMPTY_TUPLES function controls whether empty tuples with empty cell values are eliminated. PERF_PREFER_SUPPRESS_EMPTY_TUPLES does not change the null suppression behavior on the final result set.

There is no native support for time series functions. Time series functions are only supported through data modeling.