Free Form Application Sources

You can build Free Form applications by creating dimensions using a graphical wizard. Alternatively, you can use an Outline file or snapshot from an on-premises release 11.1.2.400 single cube Essbase application to create a Free Form application.

When you use an outline (OTL) file or Essbase application snapshot as the source for an application, Account, Period (time), and Entity (country) dimensions are created and mapped automatically. Additionally, Version and Scenario dimensions of the Essbase application are created as custom dimensions. As a result, out of the box Workflow functionality is not supported in Free Form applications.

Service Administrators build a Free Form application using a graphical wizard or these sources:

  • An Outline file from on-premises release 11.1.2.400 single cube Essbase application

    You may use an outline (OTL) file from an on-premises release 11.1.2.400 single cubed Essbase application to create the structure of the Free Form application.

    Because the OTL file name is assigned to the cube created for the Free Form application, the file name must be eight characters or less. Longer file names will cause the process to fail.

    Generally, the OTL file is available in the EssbaseServer/essbaseserver1/app/<app_Name> directory within your on-premises Essbase deployment.

    Because the OTL file does not contain application data, you must extract Essbase data to a file. Use MaxL, Essbase Studio, or another tool to export data from an Essbase application. The data must be exported in an Essbase data file format.

    After creating the application, import the extracted data, selecting Essbase as the source type. You can import from a locally stored data file or from a file that was uploaded to the Oracle Enterprise Performance Management Cloud inbox. For detailed instructions, see Importing Data in Administering Planning.

  • An application snapshot from an on-premises release 11.1.2.400 single cube Essbase application

    This option simplifies application creation by migrating an existing Essbase application snapshot (ZIP file) that was created using Lifecycle Management. This process automates dimensions loading, substitution variables creation, calculation scripts conversion as graphical rules, and data load.