A data source or metaoutline may contain duplicate member names. In Integration Services Console, you can specify a metaoutline that, when loaded into an Essbase database, creates an Essbase outline that supports duplicate member names.
In order to support shared members in a duplicate member Essbase outline, the member column in the metaoutline must be associated with a member key column from the data source. Integration Server makes use of the assigned key to uniquely identify the base member. Internally, Integration Servergenerates its own unique identifier to differentiate between duplicate members.
When Integration Services performs a member load, Integration Server applies the unique identifier to duplicate names. From Integration Services clients, the member names can be retrieved using a qualified format, for example: [Product].[300].[300-30][Diet].[300-30]
You may choose to specify a metaoutline that, when loaded into Integration Services, does not create an outline that supports duplicate member names. In this case, when Integration Server performs a member load, it performs one of the following actions:
It ignores the duplicate members. Integration Server does not load the members into the Integration Services outline.
It creates the members as shared members. The data associated with a shared member is stored in the real member.
For more information, see Essbase online help.
Note: | You should not create duplicate members as shared if the actual member or any shared member at the first leaf level has a filter. Instead, individually tag such a member as shared. You can prevent the creation of duplicate member names by transforming data when you create an OLAP model. |