Content

In this example, the structure data does not include the information needed to define to which hierarchy a member belongs. If the members belonged to different hierarchies, the structure data would have to be modified to include either the group name or the hierarchy name for the top members of each hierarchy. (See the section that follows.)

Name,Parent Name
Total Company,*
TC Eliminations,Total Company
Division,TC Eliminations
Cost Center,Division
Country,Cost Center
Unit,Country
Legal Rollup,* 
Entity,Legal Rollup
Country,Entity
Unit,Country
Name,Parent Name	 
No Company,*
Total Company,*
Operations,Total Company	 	 
North America,Operations
US,North America
New York,US
Los Angeles,US
Canada,North America
Toronto,Canada
Vancouver,Canada
Latin America,Operations
Brazil,Latin America
Mexico,Latin America
Mexico City,Mexico
Vera Cruz,Mexico 

When all members in the structure data are part of the same hierarchy, the hierarchy name can be given a default value during the mapping session.

Conflicts resulting in a failed import occur if multiple hierarchies reside in the structure data and a hierarchy default is used during mapping. This is because there would be multiple top members and more than one top member would have child members that are not allowed in a single hierarchy.