1. Administrator's Guide
  2. Using FDMEE
  3. Integration Process Overview
  4. Integrating Metadata
  5. How Dimensions Are Processed

How Dimensions Are Processed

For Oracle Hyperion EPM Architect applications, the dimension extract process populates the interface tables with dimension members based on the mapping rule details created in Oracle Hyperion Financial Data Quality Management, Enterprise Edition. For Classic Oracle Hyperion Planning and Oracle Hyperion Financial Management applications, the dimension extract process populates dimension members directly into the application based on the mapping rule details created in FDMEE.

As part of the extract process, the dimension members are directly loaded into the target Performance Management Architect dimension, with specific properties defined as described in Member Properties Sourced from the Enterprise Resource Planning (ERP) System. In addition to loading dimension members, the related alias entries are also loaded to provide the appropriate language support.

Shared dimensions from EPMA are not selected directly from the shared library for loading. FDMEE presents the dimensions in the target application for inclusion in a metadata rule, and then updates the shared library automatically when updating the target application. Dimensions in the shared library cannot be directly loaded but must be included in a target application to enable loading from an Enterprise Resource Planning (ERP) source.

The FDMEE dimension extract process includes:

  1. Extracts the general ledger segment or chartfield value sets from the source system.

    • Only general ledger segment value set members or chartfield members that are relevant to the source chart of account segments or chartfields mapped to Classic Financial Management, or Planning are extracted.

    • The members are loaded into a staging table on the target instance. Before loading them into the staging table, FDMEE assigns the segment values a prefix defined for the corresponding EPM application dimension.

  2. Processes dimensions mapped to single segments or chartfields.

    For Classic applications, dimensions are loaded directly into the target application. The interface tables for dimensions map to a single general ledger segment or chartfield. This consists of filtering the data from the staging table loaded in step 1, based on the segment value set mapped to a dimension, and loading the corresponding dimension member interface table and dimension member property array table (for aliases).

    In most cases, dimensions are mapped as a single segment in E-Business Suite source systems or single chartfield in PeopleSoft source systems from the source chart of accounts to a target dimension and you select the starting node in the source dimension as the basis for the new dimension.

  3. Processes the dimensions mapped to multiple segments or chartfields.

    For Performance Management Architect, the member interface tables are populated for the dimensions mapped from more than one E-Business Suite general ledger chart of accounts segment or PeopleSoft chartfield. The individual segment values must be concatenated to create the dimension member values.

    The dimension extract process creates the required member entries, properties, and alias entries if they exist in the source system, and then applies defaults to those properties if they do not exist. Users should update member properties if the source system value was unavailable or in cases where a different value is desired.

    In some cases, you can sometimes create target dimension members based on the concatenation of one or more source segments. When dimensions are mapped as a concatenated segment, the new dimension is created based on a user-defined traversal order of the source hierarchies into the concatenated member target hierarchy.