Show TOC

Development and Delivery of Hierarchy NodesLocate this document in the navigation structure


In the Data Warehousing Workbench, BW objects are divided into tree structures using hierarchy objects:

  • InfoAreas

    InfoAreas are used to structure InfoObjects and InfoProviders.

  • Application Components

    These application components are used to structure InfoSources and should not be confused with application components for DataSources, which are created and delivered in the source system (OLTP).

Scenario 1: Nodes as Subnodes of the Root at Any Position of the Tree

In the content development system, in the Modeling functional area of the Data Warehousing Workbench, create one or more nodes as subnodes for your customer content object by using the context menu for the root node of the relevant tree. You can create any number of additional nodes below this node.


More information about importing hierarchy nodes into the customer system: Development and Delivery of Hierarchy Nodes of the partner content.

Scenario 2: Nodes as Subnodes of the Root at Any Position in the Tree

If you create a node in the Data Warehousing Workbench tree for your customer content object, the system also registers nodes which mark their position in the hierarchy at the same time.



Field Name in the RSAPPL Table


Superordinate application component(parent node)



Subordinate application component(child node)

The system (only) enters the first subnode, even if there are several nodes.



Next application component (neighbor node)


If you insert a node, under which your customer content objects hang, in a particular position on the child level under the root node of the respective tree, the system inserts your customer content node as NEXT in the predecessor node.


With the delivery of customer content, the system attempts to insert a customer content node in accordance with the table entries. If the tree in the customer system is structured differently than in the customer content development test system, and as a result, the node cannot be assigned, the system then decides to insert the node under Non Assigned Nodes.

The following graphic illustrates the relations between different objects for this node, under which all customer content objects are placed, using the example of the Content1 node. Content1 is to be inserted after the SAP1 node:


To enable the system to insert the Content1 node in field APPLNM_N of its predecessor node SAP1 in table RSAPPL, you first need to set SAP1 to changeable. Do this by assigning the value 2 to the CONTENT_CHANGE field in the RSOCONTCHNGABLE table: External Objects Also Changeable in D Version - CTO Connection. In this way, you ensure that the table entry ( Content 1 as NEXT in SAP1) is also delivered to all subsequent systems. More information: Setting Object Changeability in Customer Content Systems.