1. Administrator's Guide
  2. Using FDMEE
  3. Administration Tasks
  4. Registering Target Applications
  5. Defining Application Options for Essbase and Planning
  6. Working with Duplicate Members in Essbase

Working with Duplicate Members in Essbase

The table below provides details how duplicate members are referenced in an Oracle Essbase application

Table 1-13 How Duplicate members are referenced in an Essbase application

Scenario Qualified Name Syntax Example
Duplicate member names exist at generation 2 [DimensionMember].[DuplicateMember] [Year].[Jan]
Duplicate member names exist in an outline but are unique within a dimension [DimensionMember]@[DuplicateMember] [Year]@[Jan]
Duplicate member names have a unique parent [ParentMember].[DuplicateMember] [East].[New York]
Duplicate member names exist at generation 3 [DimensionMember].[ParentMember].[DuplicateMember] [Products].[Personal Electronics].[Televisions]
Duplicate member names exist at a named generation or level, and the member is unique at its generation or level DimensionMember]@[GenLevelName]|[DuplicateMember] [2006]@[Gen1]|[Jan]
In some scenarios, the differentiating ancestor method is used as a shortcut. DifferentiatingAncestor].[Ancestors...].[DuplicateMember] [2006].[Qtr1].[Jan]