Dimension Aliases In EPMA Become Dimension Names In Hyperion Planning And Hyperion Essbase (Doc ID 868592.1)

Last updated on JULY 28, 2016

Applies to:

Hyperion Planning - Version 9.3.1.0.00 to 11.1.1.2.00 [Release 9.3 to 11.1]
Information in this document applies to any platform.

Symptoms

Dimension aliases in EPMA become dimension names in Planning and in Essbase after deployment. For example, consider the following scenario:

A dimension named "Centre" with an alias of "Cost Centre" is loaded into EPMA in an .ads file and deployed successfully to Planning and Essbase. A dimension called "Cost Center" is created in Planning and Essbase.

This can cause issues if the alias is then changed in EPMA. For example, if the alias in the above example was changed in EPMA to "C_Centre", then when the application was next deployed, a new dimension named "C_Centre" would be deployed to the Planning application, and to Essbase, in addition to the existing "Cost Centre" dimension.

The "Cost Centre" dimension cannot be deleted from within the Planning interface. If it is deleted from Essbase it is recreated after the next deployment, because it is being pushed to Essbase from Planning.

The information in this note applies to Planning applications only, not to native Essbase applications, which can also be managed using EPMA. Planning applications have an Essbase tier; references to Essbase in this note refer to the Essbase tier of Planning applications.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms