1. Administrator's Guide
  2. Using FDMEE
  3. Integration Process Overview
  4. Integrating Metadata
  5. Loading Source System Hierarchies into EPM Dimensions

Loading Source System Hierarchies into EPM Dimensions

Metadata within the source system changes over time, as well as the metadata and hierarchies in the target system.

The management of hierarchies is an ongoing process, with frequent changes due to updates in business functions and organizations. When managing hierarchies between source and target systems, users generally create new hierarchies, replace old hierarchies with new hierarchies or update hierarchies.

Managing hierarchies between systems becomes difficult because of the size of the hierarchies, the latency between system updates, and the needs of operational systems versus analytical systems. When managing hierarchies as part of the general ledger integration process, consider:

  • The only operations between hierarchy management in the source system and target application are creating and updating the hierarchies by merging in the target. Oracle Hyperion Financial Data Quality Management, Enterprise Edition never deletes hierarchies or members in a target application. If additional members or hierarchies are not specified, FDMEE ignores them.

  • When you integrate a hierarchy from the source system to the target system, select the node from the source that serves as the root node in the target.

  • The integration pushes the hierarchy into the target system and reports any errors encountered during the process.

    You can use the Process Details page to view errors logged in FDMEE. You can also select the Log link to review the Oracle Data Integrator log file. For Oracle Hyperion EPM Architect applications, you can also view profile creation errors in the Job Console. See Viewing Process Details or the appropriate product documentation for additional information.

  • A hierarchy selection in the dimension mapping is optional; however, you must at least determine how to handle members not in a hierarchy. For example, you can create children of a selected node as orphans, or you can choose not to carry over orphans. (This option applies only to Performance Management Architect).