Aggregating Master Data and Hierarchies for Transfer to SEM-BCS You use this procedure to aggregate hierarchies for automatic data collection into the consolidation system (SEM-BCS).
The hierarchies in operational systems can be structured at a deeper level than is supported in the consolidation system. You aggregate a source hierarchy by grouping several subordinate hierarchy nodes in one higher-level node. This summarization process is called aggregation.
The tool you use for aggregation is Mapping as it exists in the following data collection methods:
For data collection using flexible upload or load from data stream, the system initially maps the source hierarchy in an internal structure. The system transfers this by using the mapping rules that you have defined in Customizing the data collection method, line for line to the internal structure of the target hierarchy.

To aggregate a hierarchy you employ the following mapping principles:
The system deletes the edges that have higher-level and subordinate nodes with the same name in the mapping result (internal structure of the target hierarchy).
The system deletes redundant edges in the mapping result.
To assign the master data to the nodes on which you have summarized the hierarchy, you use the following mapping principle:
The system deletes redundant edges in the mapping result (by first sorting the nodes in ascending order and then deleting all nodes that have the same name up to the first node).
In the consolidation workbench, you have made the Customizing settings for the Data Basis and for the Consolidation Area in which you want to use the hierarchy. You have created a Source Data Basis and entered it in the data basis. In the source data basis you have entered the InfoObject catalog containing the InfoObjects to be loaded.
If you use
Load from Data Stream: the InfoObjects or virtual InfoObjects that supply the source hierarchy are already in
SAP NetWeaver Business Intelligence
(BI).
If you use Flexible Upload: you have created the files to be uploaded in the sender system.
Visualize the internal structures for the source hierarchy and the target hierarchy. Formulate mapping that is suitable for creating redundant entries in the target hierarchy on the edges on which you want to summarize.
In the consolidation workbench, create a data collection method and define mapping. For additional information on Customizing, see Customizing for Flexible Upload or Customizing for Load from Data Stream .
Execute the method in the consolidation workbench.
You have uploaded the source hierarchy to the consolidation system. The system has created the target hierarchy, and summarized it based on the specifications in mapping.
The example illustrates how mapping can be used for:
Aggregation when loading a profit center hierarchy
Assignment when loading the related profit center master data
Profit centers P111, P113 and P118 are to be summarized on profit center group P11, and profit centers P122 and P125 on profit center group P12. The profit centers are assigned to controlling area (CO area) 9000.

The following table sets out the internal structure of the source hierarchy:
Higher-level Object |
Lower-level Object |
|
|||
|---|---|---|---|---|---|
Hierarchy Name |
Text Node |
Text Node |
CO Area |
ProfitCenter |
Seq. No. |
H1 |
P1 |
0 |
|||
P1 |
P11 |
0 |
|||
P11 |
9000 |
P111 |
0 |
||
P11 |
9000 |
P113 |
1 |
||
P11 |
9000 |
P118 |
2 |
||
P1 |
P12 |
1 |
|||
P12 |
9000 |
P122 |
0 |
||
P12 |
9000 |
P125 |
1 |
||
The following table sets out the internal structure of the target hierarchy: This assumes the consolidation profit center (ConsPC) and consolidation profit center groups (ConsPCG) are assigned to controlling area (Co area) 9000:
Higher-level Object |
Lower-level Object |
|||||
Hier.Name |
CO Area |
ConsPCG |
CO Area |
ConsPCG |
ConsPC |
SeqNo. |
The following mapping rules are suitable for implementing the intended summarization in the target hierarchy:
Target Field |
Mapping Rule |
|---|---|
Hierarchy name (Hier.Name) |
Transfer hierarchy name from source hierarchy. |
Controlling area (CO Area) |
Assign constant
|
Consolidation profit center group (ConsPCG) |
Transfer the first two characters of the text node from the source hierarchy. |
Consolidation profit center (ConsPC) |
Transfer the first three characters of the profit center from the source hierarchy. |
The following table sets out the internal structure of the target hierarchy once the system has transferred the internal structure of the source hierarchy using the mapping rules line for line:
Higher-level Object |
Lower-level Object |
|||||
|---|---|---|---|---|---|---|
Hier.Name |
CO Area |
ConsPCG |
CO Area |
ConsPCG |
ConsPC |
SeqNo. |
H1 |
9000 |
P1 |
0 |
|||
9000 |
P1 |
9000 |
P1 |
0 |
||
9000 |
P1 |
9000 |
P11 |
0 |
||
9000 |
P1 |
9000 |
P11 |
1 |
||
9000 |
P1 |
9000 |
P11 |
2 |
||
9000 |
P1 |
9000 |
P1 |
1 |
||
9000 |
P1 |
9000 |
P12 |
0 |
||
9000 |
P1 |
9000 |
P12 |
1 |
||
The following table sets out the internal structure of the target hierarchy once the system has deleted the edges that have higher-level and subordinate nodes with the same name.
Hier.Name |
CO Area |
ConsPCG |
CO Area |
ConsPCG |
ConsPC |
SeqNo. |
|---|---|---|---|---|---|---|
H1 |
9000 |
P1 |
||||
9000 |
P1 |
9000 |
P11 |
|||
9000 |
P1 |
9000 |
P11 |
|||
9000 |
P1 |
9000 |
P11 |
|||
9000 |
P1 |
9000 |
P12 |
|||
9000 |
P1 |
9000 |
P12 |
The following table sets out the internal structure of the target hierarchy once the system has deleted the redundant edges:
Higher-level Object |
Lower-level Object |
|||||
|---|---|---|---|---|---|---|
Hier.Name |
CO Area |
ConsPCG |
CO Area |
ConsPCG |
ConsPC |
SeqNo. |
H1 |
9000 |
P1 |
0 |
|||
9000 |
P1 |
9000 |
P11 |
0 |
||
9000 |
P1 |
9000 |
P12 |
1 |
||
The graphic shows the resulting target hierarchy:

In the same way as for the profit center hierarchy, the profit center master data is to be assigned to the consolidation profit centers P11 and P12. Consolidation profit center P11 is to transfer the master data of profit center P111, P12 the master data of P122. The master data has been defined as follows:
ProfitCenter |
User-Defined Attribute |
Short Description |
Medium Description |
|---|---|---|---|
P111 |
USER111 |
TXT111 |
TXT111 |
P113 |
USER113 |
TXT113 |
TXT113 |
P118 |
USER118 |
TXT118 |
TXT118 |
P122 |
USER122 |
TXT122 |
TXT122 |
P125 |
USER125 |
TXT125 |
TXT125 |
The internal structure for the master data of the consolidation profit center is defined in the following way:
CO area |
ConsPC |
User-defined attribute |
Short description |
Medium description |
The following mapping rules are suitable for implementing the intended assignment in the target hierarchy:
Target Field |
Mapping Rule |
|---|---|
Controlling area (CO area) |
Assign constant
|
Consolidation profit center (ConsPC) |
Transfer the first three characters of the profit center. |
User-Defined Attribute |
Transfer user-defined attribute from the profit center master data. |
Short description |
Transfer short description from the profit center master data. |
Medium description |
Transfer long description from the profit center master data. |
The following table sets out the internal structure of the target master data once the system has transferred the source master data using the mapping rules line for line:
CO Area |
ConsPC |
User-Defined Attribute |
Short Description |
Medium Description |
9000 |
P11 |
USER111 |
TXT111 |
TXT111 |
9000 |
P11 |
USER113 |
TXT113 |
TXT113 |
9000 |
P11 |
USER118 |
TXT118 |
TXT118 |
9000 |
P12 |
USER122 |
TXT122 |
TXT122 |
9000 |
P12 |
USER125 |
TXT125 |
TXT125 |
The following table sets out the internal structure of the target master data once the system has sorted the nodes and deleted the nodes with the same name up to and including the first node:
CO Area |
ConsPC |
User-Defined Attribute |
Short Description |
Medium Description |
|---|---|---|---|---|
9000 |
P11 |
USER111 |
TXT111 |
TXT111 |
9000 |
P12 |
USER122 |
TXT122 |
TXT122 |