When a metaoutline is loaded into Essbase Server, an Essbase outline is usually created with each member name being unique. This is the default behavior of Integration Server. You can change this default and specify a metaoutline that, when loaded into an Essbase database, creates an Essbase outline containing duplicate (non-unique) member names, as shown in the following example:
US-->Massachusetts-->Springfield
Oracle Essbase Integration Services generates a unique internal identifier, which is applied to any duplicate member name in a metaoutline. This process enables support for duplicate member names during member loads, data loads, and drill-through operations.
When using duplicate member names, keep in mind the guidelines described in the sections that follow: