In This Section:
When you enable duplicate member names in an outline, Essbase displays multiple members in the outline using the same name. Create the names in the usual way. See Naming Restrictions for Dimensions, Members, and Aliases.
Figure 38, Duplicate Member Name “New York” shows an example of a duplicate member outline in which the New York state member and the New York city member appear in the outline as New York.
The qualified member names for the example in Figure 38, Duplicate Member Name “New York” are [State].[New York] and [City].[New York]. See Syntax for Specifying Duplicate Member Names and Aliases.
To create an outline that enables duplicate member names, or to convert a unique member name outline to a duplicate member name outline, use a tool:
Save outline changes before converting it to a duplicate member name outline. You cannot convert an outline that has unsaved changes.
After converting an outline to a duplicate member outline, save it before proceeding with other outline changes.
A duplicate member outline cannot be converted back to a unique member outline.
Within a duplicate member outline, you can tag particular dimensions, generations, and levels as unique or duplicate to restrict the use of duplicate member names within a database. Doing so enables you to specify member name uniqueness at a more granular level in a duplicate member outline.
When duplicate members are enabled in a dimension, you can tag particular generations or levels within the dimension as unique. If a member is assigned conflicting properties, the unique property takes precedence.
To disable duplicate member names in a particular generation or level of a dimension, see “Naming Generations and Levels” in the Oracle Essbase Administration Services Online Help.
Duplicate member outline attribute dimensions do not have prefixes or suffixes attached that apply to attribute dimensions in unique outlines. For example, in a duplicate member Boolean attribute dimension, members do not include dimension, parent, grandparent, or ancestors affixed to the TRUE and FALSE members. See Setting Prefix and Suffix Formats for Member Names of Attribute Dimensions.
Do not use quotation marks (" "), brackets ([ ]), or tabs in member, dimension, or alias names. For example, you cannot create a member name “[New York].[Area 1]”. Outline verification does not display an error for member names that contain the invalid sequence of characters, and you can save the outline; however, Essbase cannot accurately query the data.
Although duplicate member names appear in the outline, each nonshared member name uniquely identifies a member in the database. A qualified name format differentiates the duplicate member names. When using Administration Services editors, you can select the qualified member name for an outline tree. You can view the qualified member name for a duplicate member in the Outline Viewer Member Properties dialog box in Administration Services. A qualified name must be used to specify a duplicate member name.
Fully qualified member name
Member name qualified by differentiating ancestor
Shortcut qualified member name
A qualified name must comprise all alias names or all member names. You cannot mix member names and alias names in a qualified name.
A fully qualified member name comprises the duplicate member or alias name and all ancestors up to and including the dimension name. Each name must be enclosed in brackets ([ ]) and separated by a period (.). The syntax is as follows:
[Market].[East].[State].[New York] [Market].[East].[City].[New York]
A member name qualified by differentiating ancestor uses the member or alias name and all ancestors up to and including the ancestor that uniquely identifies the duplicate member or alias. The top ancestor in the path will always be a unique member name. Each name must be enclosed in brackets ([ ]) and separated by a period (.). The syntax is as follows:
[State].[New York] [City].[New York]
Essbase internally constructs shortcut qualified names for members in duplicate member outlines. These can be inserted into scripts using Administration Services by right-clicking the member and selecting Insert member name. You can also manually insert shortcut qualified names into scripts, spreadsheets, or MDX queries.
Essbase uses the syntax shown in Table 14 to construct shortcut qualified names. Using the same syntax that Essbase uses when you reference members in scripts, spreadsheets, and MDX queries is optimal but not required.
Table 14. Shortcut Qualified Name Syntax
Qualified Name Syntax
Duplicate member names exist at generation 2
Duplicate member names exist in an outline but are unique within a dimension
Duplicate member names have a unique parent
Duplicate member names exist at generation 3
Duplicate member names exist at a named generation or level, and the member is unique at its generation or level
In some scenarios, the differentiating ancestor method is used as a shortcut.
To specify duplicate member names in:
Smart View, see the Oracle Hyperion Smart View for Office Online Help
Spreadsheet Add-in, see the Oracle Essbase Spreadsheet Add-in Online Help
API, see the Oracle Essbase API Reference
To use duplicate member names in MaxL and MDX, see the Oracle Essbase Technical Reference.
If an alias name and member name are the same but do not represent the same member, searching by alias name is not supported in clients (for example Spreadsheet Add-in, Administration Services, or the API).
In MDX and MaxL qualified member names are not enclosed in quotation marks. See “Inserting Dimension and Member Names in MDX Scripts” in the Oracle Essbase Administration Services Online Help. The Administration Services Data Preview feature does not support duplicate member outlines.