Consider these rules for Essbase databases and outlines:
Essbase applications and database types must be block storage.
If the Essbase database does not exist, Analytics Link creates the Essbase database with these properties:
The Essbase database Auto Configure property is set to FALSE.
The value of the Essbase database Duplicate member names allowed property is set to the same value as the Allow Duplicate Member Names database property for the bridge.
If you define an existing Essbase database as the bridge target:
The Essbase database Auto Configure property must be set to FALSE.
The value of the Essbase database Duplicate member names allowed property must be the same value as the Allow Duplicate Member Names database property for the bridge.
If the bridge Unicode database property is set to On and the Essbase application does not exist, Essbase Server must have the Permission to create Unicode-mode application property selected. If the bridge Unicode database property is set to On and the Essbase application already exists, the Essbase application should have been created in Unicode mode.
Essbase dimensions must be Label Only, because in the Data Synchronization Server replica of Financial Management, there is no dimension name member. Reports return the value of the first child.
All members ignore consolidation.
Analytics Link builds alias tables in the database for each description language of the Data Synchronization Server replica of the Financial Management application. A default alias table is built for the first defined description language. For the remaining description languages, Analytics Link builds different alias tables in the database with the same name as the description language. When you configure Analytics Link Server using the Analytics Link Configuration Tool, you specify the maximum number of alias tables for the Essbase database that Analytics Link creates.
Essbase comments are the IDs of the Financial Management members; for example (/*5*/). IDs are dimension unique.
Some Oracle Hyperion Financial Management member names and descriptions are not valid in Essbase (see Table 56, Restricted Characters for Essbase Dimension, Member, and Alias Names). When creating the Oracle Essbase outline, Analytics Link renames those members. For example:
[Member] becomes FM Member
[None] becomes FM None
<Entity Currency> becomes FM Entity Currency