If you want to associate aliases or UDAs with members created from a recursive source table, you must prepare the data:
If the alias or UDA data is in a separate table, you must complete specific steps when creating an OLAP model. These steps vary, depending on whether the column, with which you are associating the alias or UDA, is fully defined (see Table 4 and Table 2).
If the alias or UDA data is in the recursive source table, the column with which you associate the alias or UDA must be fully defined, and all alias or UDA information must relate to the fully defined column.
If you want to associate an alias or UDA with the parent column of a recursive table, the parent column must be fully defined. A recursive table parent column is fully defined when the parent column contains every value (every member proposed for the Essbase hierarchy). Thus the parent column contains the lowest-level value in the hierarchy with a NULL value in the child column. In Table 4, the GEO_PARENT column is fully defined because the GEO_PARENT column contains the lowest-level value, 01010, with a NULL child in the GEO_CHILD column.
If you want to associate an alias or UDA with the child column in a recursive table, the child column must be fully defined. A recursive table child column is fully defined when the child column contains every value (every member proposed for the Essbase hierarchy). Thus the child column contains the highest-level value in the hierarchy, with a NULL value in the parent column.
In Table 5, the GEO_CHILD column is fully defined because the GEO_CHILD column contains the highest-level value, USA, with a NULL parent in the GEO_PARENT column.