Setting Target Database Properties

In This Section:

About Target Database Properties

Allow Duplicate Member Names Database Property

Add Parent to Entity Member Database Property

Solve Uniqueness Problems Database Property

Extract Currencies from Custom Dimensions Database Property

Unicode Database Property

The information in this chapter applies to Essbase and RDBMS target databases. Financial Management data examples are based on the Simple Demo Financial Management application.

About Target Database Properties

Target database properties control how the target database works with dimensions and members, and are specified on the Properties tab in the bridge window.

In working with a bridge, you typically recreate the target database multiple times, and even select different database properties, as you fine-tune the outline. Therefore, Analytics Link provides status information so that you know which properties were selected each time the target database was created. Status information appears to the right of the property name and is enclosed in parentheses; for example, (On).

Database property statuses:

  • None—If the bridge target database has not been created, the status of each property is None.

  • On—The property was selected when the target database was created last.

  • Off—The property was not selected when the target database was created last.

After you create the Essbase target database, return to the Properties tab and click the Refresh button to see the updated status of each database property.

Allow Duplicate Member Names Database Property

The Allow Duplicate Member Names database property creates a nonunique name database, in which multiple members with the same name, where the values are not shared, are allowed. A qualified name format differentiates the duplicate member names.

When creating an Essbase target database for the first time and Allow Duplicate Member Names is selected:

  • If the Essbase database referenced in the bridge definition does not exist, Analytics Link creates a nonunique name database.

  • If the Essbase database exists, it must allow duplicate names. If the Essbase database requires unique names, Analytics Link generates an error and the database is not created.

To create a unique member name outline, clear Allow Duplicate Member Names. See Creating a Unique Member Essbase Outline.

By default, this property is set to Off.

Add Parent to Entity Member Database Property

In the Entity dimension, the Add Parent to Entity Member database property displays each entity member name, and alias name, at generation 3 and above as parentName.memberName and aliasParentName.aliasMemberName, respectively.

For example, the following representation of the Entity dimension outline shows default member names (for example, UnitedStates and California) and alias names (for example, United States of America and State of California):

ESSEntity
...
   Regional (Alias:Regional Operations)
      UnitedStates (Alias: United States of America)
         California (Alias: State of California)
            Sunnyvale
...

When the Essbase outline is created with Add Parent to Entity Member selected, the following representation of the Entity dimension outline shows member names in parentName.memberName format (for example, Regional.UnitedStates and UnitedStates.California) and alias names in parentAlias.memberAlias format (for example, Regional Operations.United States of America and United States of America.State of California):

ESSEntity
...
   Regional (Alias: Regional Operations)
      Regional.UnitedStates(Alias:Regional Operations.United States of America)
           UnitedStates.California (Alias: United States of America.State of California)
            California.Sunnyvale
...

By default, this property is set to On.

When the Add Parent to Entity Member database property is set to On, and Entity dimension member name mapping is specified in a mapping table, the mapping table specification takes precedence over the database property. See Member Naming Considerations when Add Parent to Entity Member is Set to On.

Solve Uniqueness Problems Database Property

The Solve Uniqueness Problems database property solves duplicate member names before creating an Essbase target database. Analytics Link collects member names from:

  • Financial Management metadata for all selected members in Essbase dimensions that are created by Analytics Link (Dimension Creation transformation type)

  • User-created Essbase dimensions (ones that were created by the user, not Analytics Link) that use a (transformation types other than Dimension Creation)

  • Names of target dimensions on the Target Design Grid tab in the bridge window

The Solve Uniqueness Problems property, when the Allow Duplicate Member Names property is not selected, resolves duplicate member issues in the following ways:

  • If a member name duplicates a dimension name, member name, or alias name, Analytics Link adds the name of the dimension in which the duplicate member name exists to the member name. For example: dimName.memberName.

  • If the description (or alias) of a member name duplicates a dimension name, member name, or alias name, Analytics Link adds the member name to the description in the following format: memberName (Alias: aliasDescription (memberName))

    For example, in Financial Management, California-State of California is a member in the Entity and ICP dimensions. In the Essbase outline, the member is represented in the ESSEntity dimension as:

    California   (Alias: State of California)

    In the ESSIPC dimension, Analytics Link resolves the duplicate alias as:

    ESSICP.California   (Alias: State of California (ESSICP.California))
  • If a member name appears multiple times in the same dimension, the first occurrence of the member remains unchanged; subsequent occurrences of the member are tagged as shared members, and any descendants are removed. (In Essbase, shared members must be in the same dimension and cannot have children. Unlimited shared members can have the same name.)

If Solve Uniqueness Problems and Allow Duplicate Member Names are selected, Analytics Link ignores the Solve Uniqueness Problems property.

See Allow Duplicate Member Names Database Property.

Note:

If the Essbase outline is not enabled to allow duplicate member names, and duplicate names exist in the dimensions that are used to create the database, you must select the Solve Uniqueness Problems property to resolve the duplicate names. If you do not select Solve Uniqueness Problems, creation of the Essbase database will fail.

By default, this property is set to On.

Extract Currencies from Custom Dimensions Database Property

The Extract Currencies from Custom Dimensions database property extracts currency members from the Financial Management Custom1 and Custom2 dimensions to the ESSCustom1 and ESSCustom2 dimensions in the Essbase outline.

  • When the Essbase outline is created with Extract Currencies from Custom Dimensions and Allow Duplicate Member Names selected, the extracted currency dimension members in the Essbase dimensions are children of a parent member named currencies. The child currency members retain their Financial Management member names (such as EUR, JPY, and USD). For example, the following representation of the ESSCustom1 dimension outline shows currencies under the currencies parent:

    ESSCustom1
       None
    ...
       currencies
    ...
          EUR
          JPY
          USD

    See Allow Duplicate Member Names Database Property.

  • When the Essbase outline is created with Extract Currencies from Custom Dimensions and Solve Uniqueness Problems selected, the extracted currency dimension members in the Essbase dimensions are children of a parent member named Cn.currencies (in the ESSCustom1 dimension, the parent member name is C1.currencies). The child currency members are named Cn.currency_name (the euro is named C1.EUR). For example, the following representation of the ESSCustom1 dimension outline shows currencies under the C1.currencies parent:

    ESSCustom1
       FM.None
    ...
       C1.currencies
    ...
          C1.EUR
          C1.JPY
          C1.USD

    See Solve Uniqueness Problems Database Property.

By default, this property is set to Off.

Unicode Database Property

The Unicode database property creates a Unicode-mode database that can support multiple character sets. Essbase uses the UTF-8 encoding form to interpret and store character text. Character-based artifacts, such as member and alias names, can include characters from different languages.

When creating an Essbase target database for the first time and Unicode is selected:

  • If the Essbase application and database referenced in the bridge definition do not exist, Analytics Link creates them in Unicode mode.

  • If the Essbase database exists, it must be in Unicode mode. If the Essbase database is in non-Unicode mode, Analytics Link generates an error and the Essbase database is not created.

By default, this property is set to Off.