In This Section:
The information in this chapter applies to Essbase target databases. The Essbase tab does not appear in the bridge window when the bridge target is an RDBMS database.
Data Synchronization Server must be running and, on the Data Synch tab, the status of the Data Synchronization Server database (Analytics Link Data) must be set to On. If the status of Analytics Link Data is Off, load the Data Synchronization Server database by clicking the Resume button.
You must create the Data Synchronization Server database for the bridge before Analytics Link can create an Essbase database. See Creating the Data Synchronization Server Database for the Bridge.
To create an Essbase database:
See Creating a Bridge.
Allow Duplicate Member Names
Add Parent to Entity Members
Solve Uniqueness Problems
Extract Currencies from Custom Dimensions
Under Status, verify that the Essbase Server is available.
For Connection Type, select how the Essbase outline is connected to the Data Synchronization Server.
Connection type options:
For Security, select whether to migrate user and data security from the Financial Management application to the Essbase database.
Security migration options:
Migrate Users and Data Security
Do Not Migrate
Analytics Link builds the Essbase database and outline (block storage only), and the Essbase application if the application defined in the bridge does not exist.
Each time Analytics Link creates an Essbase target database, Analytics Link reads the mapping grid definition and mapping table data, saves this information in the Analytics Link repository, and sends it to Data Synchronization Server database. Therefore, if you make changes to the mapping grid definition and mapping table data, and then save these changes, the changes are automatically read and the mapping information in the Analytics Link repository and Data Synchronization Server database is updated during the creation of the Essbase database.
If you create an Essbase replicated partition database, see Extracting Financial Management Data to an Essbase Replicated Partition Database Target.
When creating an Essbase database as the bridge target, the connection type determines how the Essbase outline is connected to the Data Synchronization Server and whether data queries are served from Data Synchronization Server or Essbase. See Determining the Type of Bridge Target Database.
The connection type is specified on the Essbase tab of the bridge window.
In Essbase, a transparent partition allows users to manipulate data that is stored remotely as if it were part of the local database. The remote data is retrieved from the data source each time that users at the data target request it.
In Analytics Link, Financial Management data that is transformed and stored in Data Synchronization Server is visible to Essbase through a transparent partition.
Essbase queries return data directly from Data Synchronization Server, for those Essbase members that are assigned the “eal” UDA. See About User-Defined Attributes (UDAs).
Transparent Partition is the default connection type for an Essbase target database.
In Analytics Link, Financial Management data that is transformed in Data Synchronization Server is copied to the Essbase database through the replicated partition.
Essbase queries return data directly from the Essbase replicated partition target database, not from Data Synchronization Server database (which is the replicated partition source database).
In Financial Management, a user's or group's ability to access application elements depends on the security classes to which the user or group belongs and on the security class associated with the application elements. When creating an Essbase database as the target database, security options, which are specified on the Essbase tab of the bridge window, determine whether user and data security in the Financial Management application is migrated to the Essbase database.
After Analytics Link creates the Essbase database for the first time, the database outline always exists:
If you delete the Essbase database, dimensions that Analytics Link creates with Dimension Creation, Measure, and Currency transformation types are removed from the outline. Additionally, database objects that Analytics Link creates, such as partitions, UDAs, security filters, and groups, are removed.
If you delete all of the dimensions from the grid, the outline will be empty.
When recreating an Essbase database, Analytics Link deletes the dimensions created with the Dimension Creation, Measure, and Currency transformation types and then recreates these dimensions.
Data is not smoothly and uniformly distributed.
Data does not exist for the majority of member combinations. For example, all products may not be sold in all areas of the country.
Essbase maximizes performance by dividing standard dimensions into two dimensionality types:
Sparse—A sparse dimension has a low percentage of available data positions filled. Most multidimensional databases are inherently sparse; they lack data values for the majority of member combinations.
Dense—A dense dimension has a high probability that one or more cells is occupied in every combination of dimensions.
Dimensionality information is stored in Data Synchronization Server when Analytics Link creates the Essbase database and you synchronize mapping information.
Analytics Link follows these rules to determine dimensionality when an Essbase database is created for the first time:
If the target grid includes some dimensions created with Dimension Creation, Measure, and Currency transformation types, those dimensions are created as sparse dimensions. The dimensionality of dimensions that do not use these transformation types remains unchanged.
If all dimensions in the target grid are created with Dimension Creation, Measure, and Currency transformation types:
If the Financial Management Period dimension is created with the Dimension Creation transformation type, Analytics Link creates the Period dimension as dense. Other dimensions that are created in the Essbase database are sparse.
If the Period dimension is not created with the Dimension Creation transformation type, the first dimension in the grid that is created with the Dimension Creation transformation type is created as dense. Other dimensions that are created in the Essbase database are sparse.
If the target grid does not include any dimensions created with Dimension Creation, Measure, and Currency transformation types, the dimensionality of all dimensions in the Essbase database remains unchanged.
When Analytics Link recreates a dimension that already exists in an Essbase database, the dimension dimensionality remains unchanged.
If you manually change the dimensionality of dimensions in an Essbase database, you must manually synchronize mapping information so that the dimensionality information is updated in Data Synchronization Server. If the Essbase database is a replicated partition database and you do not synchronize mapping information, the data that Analytics Link copies to the Essbase database through the replicated partition might be affected. See Synchronizing Mapping Data Changes for RDBMS Bridge Targets and About Extracting Data into an Essbase Replicated Partition Database.