From Performance Management Architect, Profitability and Cost Management, Essbase (ASO) and Essbase (BSO) Applications

You can create an import file from Performance Management Architect (Generic, Consolidation, or Planning), Oracle Hyperion Profitability and Cost Management (Standard or Detail), Essbase (ASO), or Essbase (BSO) applications.

Note:

You cannot use this utility with Detailed Profitability and Cost Management applications because the File Generator Utility uses Oracle Essbase to generate the import file, and Detailed Profitability applications use relational databases only.

  To create an import file for a Performance Management Architect (Generic, Planning, or Consolidation), Profitability and Cost Management (Standard or Detailed), Essbase (ASO), or Essbase (BSO) application:

  1. Click From EPMA Application.

    Use the EPM Architect File Generation Utility to create an import file for Performance Management Architect, Standard Profitability and Cost Management, Essbase (ASO), or Essbase (BSO).
  2. Enter the following information:

    • The user name and password to log in to Oracle Hyperion Enterprise Performance Management Workspace

    • The Performance Management Architect Web Services URL

    • The Performance Management Architect (Generic, Consolidation, or Planning), Oracle Hyperion Profitability and Cost Management (Standard or Detailed), Essbase (ASO), or Essbase (BSO) application name

    Note:

    You can enter a specific application to extract, or you can extract the entire Shared Library. To extract the entire Shared Library, enter "Master" in the field where you specify the application name.

  3. Specify the name for the EPMA import file or browse to find an existing file to over write.

  4. Optional: Enter a prefix for the dimensions.

  5. Optional: To view the import file in a text editor, click View.

  6. Optional: Select Save metadata file.

    When Performance Management Architect imports an application, it is imported as an .xml file (metadata.xml). Performance Management Architect runs the transformation and creates an .ads file from the metadata.xml file. Typically, this file is used for troubleshooting purposes. For extremely large applications, we recommend that you do not select this option.

  7. Click Execute.

    The .ads file is created, using the application as the source. A successful message is displayed under Status.