About Adding Essbase Cube Tables to the Physical Layer

When you drag and drop an Essbase cube table into a physical database, Semantic Modeler prompts you to specify how you want the import to handle the items in the table.

See Add Oracle EPM Cloud Cube Tables to the Physical Layer.

Be sure to understand these important points before you import an Essbase cube table:

• After import the cube table, you can't change the settings you chose for the import.
• If you need to adjust the settings for a cube table, then reimport the cube table.
• When you import more than one table, the import options you select are set for all cube tables. If the cube tables require different import settings, then import them individually.

You can choose the following Essbase cube table import options. Remember that you can't change these settings after you import a cube table.

• Create columns for UDAs - Select to flatten user defined attributes rather than model them as dimension properties.
• Convert measure dimensions to flat measures - Select to include each measure as an individual column rather than a single measure column that represents all measures.
• Convert alternative hierarchies into a single hierarchy - Select to include alternative hierarchies as a single hierarchy rather than modeled as separate hierarchies.
• Create columns for alias table - Select to flatten aliases dimension properties.