1. Integrating Oracle Data Relationship Management Suite with Enterprise Performance Management
  2. Using Data Relationship Management with FDMEE
  3. Configuring FDMEE Metadata in Data Relationship Management
  4. Locating and Loading the Application Template

Locating and Loading the Application Template

The Oracle Hyperion Financial Data Quality Management, Enterprise Edition application template is installed as part of the Oracle Data Relationship Management installation. You use the template to configure the Data Relationship Management metadata to enable integration with FDMEE.

To locate the FDMEE application template:

  1. On the computer where Data Relationship Management is installed, navigate to C:\Oracle\Middleware\EPMSystem11R1\products\DataRelationshipManagement\server\app-templates.

    Note:

    This is the default installation directory for application templates.

  2. Locate the application template file named fdmee-app-template.xml.

You use the Data Relationship Management Migration Utility to load the application template. See the Oracle Data Relationship Management Administrator's Guide topic “Loading Metadata” for details on how to use the Migration Utility to load the application template.

The FDMEE application template includes Data Relationship Management metadata objects for FDMEE and references to property definitions in the Planningapplication template. During the template load process, you can select all metadata objects from the template or select only objects specific to a particular EPM application type. For example, you might select property definitions, imports, and exports specific to Planning.

The property category, node type, and blender included in the FDMEE template reference properties of multiple application types. In situations where you are using the FDMEE template with a single EPM application type, the template load process will identify missing dependencies to properties of other application types. Select the "Ignore Dependencies" option in the Migration Utility to load these metadata objects without these references.

Possible Conflicts to Review Before Loading the Application Template

This application template contains a modification to the EPMA.MemberType formula that adds the FDMEE ERP Node Type for ERP nodes from FDMEE. If you have modified the original formula for the EPMA.MemberType property in the Performance Management Architect or Planning templates, then your changes will be overridden unless you deselect this property during the migration utility load process. The View Differences function of the Data Relationship Management Migration Utility can be used to compare the difference of this property before loading. If the formula has been customized, then it is recommended that you not load the value from the FDMEE application template. The formula will need to be manually updated to include the logic for the FDMEE ERP node types.

This application template contains two system preferences (InvName and InvDescr). Before loading the application template, review the values for these preferences against the values currently set in your system. This can be done manually or with the View Differences function of the Data Relationship Management Migration Utility. You do not have to migrate these preferences especially if your configuration is more conservative for business reasons. The import is set up to not enforce invalid node name characters so that the FDMEE nodes can be imported even if they have invalid characters in them.

Supported Languages

The FDMEE application template includes support for 10 languages for node descriptions loaded into Data Relationship Management during a FDMEE metadata load process. Supported languages are:

  • Brazilian Portuguese

  • English

  • French

  • German

  • Japanese

  • Korean

  • Latin American Spanish

  • Portuguese

  • Spanish

  • Traditional Chinese