Requirements

Before you begin using Oracle Hyperion Financial Data Quality Management, Enterprise Edition, consider the following:

• Verify that you have met the EPM dimension requirements:

  You can build EPM applications with any combination of dimensions. The combination must include required dimensions for the selected application. Member Properties Sourced from the Enterprise Resource Planning (ERP) System describes how member properties are sourced from the Enterprise Resource Planning (ERP) source system.

• Verify that you have met the EPM member requirements:

  • Duplicate Members—To avoid issues with duplicate member names, as a best practice, include a unique prefix or suffix for each dimension so each member is always unique.

  • Duplicate Alias Members—If your application has duplicate alias members, it is important to remove any duplicates in the target application or validation errors occur when you deploy the application in Oracle Hyperion EPM Architect.

    Note:

    Source descriptions must be unique to avoid alias validation errors with Performance Management Architect.

When moving dimensions and members from a source system into a target EPM application, it is important to understand the naming restrictions. For Performance Management Architect, see the Oracle Hyperion Enterprise Performance Management Architect Administrator’s Guide. For Oracle Hyperion Planning, see the Oracle Hyperion Planning Administrator’s Guide. For Oracle Hyperion Financial Management, see the Oracle Hyperion Financial Management Administrator’s Guide.