Export a Cube to an Application Workbook

Export an Essbase cube to an Excel application workbook. Choose a build method, and optionally, export data and calculation scripts. The exported application workbook can be imported to create a new cube.

  1. Navigate to the Export to Excel dialog box.
    In the Redwood Interface:
    1. On the Applications home page, open the application and then open the database (cube).
    2. On the General page, from the Actions menu, choose Export to Excel.
    In the Classic Web Interface:
    1. In the Essbase web interface, expand the application that contains the cube that you want to export.
    2. From the Actions menu, to the right of the cube name, select Export to Excel.
  2. On the Export to Excel dialog box:
    • Select Export Data if you want to export the data from the cube. How the data is exported depends on whether the cube is block storage or aggregate storage.

      • In block storage cubes, if the size of the data is 400 MB or less, it is exported to the application workbook, on the Data worksheet. If the data size exceeds 400 MB, data is exported to a flat file named Cubename.txt, which is included in a file named Cubename.zip on the Files page.

      • In aggregate storage cubes, regardless of the size, data is always exported to a flat file named Cubename.txt, which is included in a file named Cubename.zip on the Files page.

    • Select a build method, Generation or Parent-Child.
    • Select Export Scripts if you want to export each of the calculation scripts as a separate worksheet within the application workbook.
  3. When prompted, save the exported application workbook to your local or network drive or download the exported application workbook and data .zip files from the Files page.
    File names do not include spaces because files that are imported to Essbase cannot contain spaces in the file name.

If you choose the options to include data, calculation scripts, or both in an export when they do not exist in the cube, the job completes without errors, but no data or scripts are exported.

The exported application workbook can be imported to Essbase. See: