Database Connection for Essbase and Planning

When you change a report from an Oracle Essbase database connection to a Oracle Hyperion Planning database connection or vice versa, there are several restrictions because the data source reference is the only change.

Changing From Essbase to Planning

• The dimensions and functions defined in reports and books must exist in the target data source. The following limitations apply:

  • Attribute dimensions are only supported for Essbase.

  • Hsp_Rates is not available as a dimension.

  • The cell text function cannot be used, because Linked Reporting Objects (LROs) are not supported.

  • Only the member selection using a level 0 is supported.

• Validate that dimensions exist prior to opening the report.

  If a dimension defined on a grid is not available in the Planning Details data source, no change is made. If an invalid function is used, an error is returned. Report designers must remove the invalid function or dimension.

Changing From Planning to Essbase

The following features that you can define in a Planning report are irrelevant for an Essbase report.

• Planning Annotations

• Supporting Detail

• Order By

If Supporting Detail is defined in the report, the details are ignored. If Planning Annotations or Order By are used, they return an error. Report designers must remove the Planning Annotation and Order By functions in order to run the report.