Hierarchy
SAP_BW (Software Component) SAP Business Warehouse⤷
BW-WHM-DBA (Application Component) Data Basis⤷
RSSH (Package) BW: Hierarchy Processing - General
Basic Data
| Data Element | RSSUBTREEUPD |
| Short Description | Store Hierarchy as Subtree |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | RSSUBTREEUPD | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 20 | Subtree |
| Medium | 40 | Hierarchy as Subtree |
| Long | 60 | Store Hierarchy as Subtree |
| Heading | 60 | Store Hierarchy as Subtree |
Documentation
Definition
There are three options for storing loaded hierarchies in the Business Information Warehouse:
- Full Update:
The hierarchy is stored under the selected technical name. If a hierarchy exists already in the BW it is overwritten. - Subtree Insert:
The hierarchy is inserted as a subtree without deleting the nodes in the original hierarchy. This means, among other things, that if you insert a hierarchy as a subtree more than once, it appears in duplicate in the target hierarchy (see below for details). - Subtree Update:
The hierarchy is inserted as a subtree and all the nodes under the interface node in the target hierarchy are deleted. Unlike a subtree insert, the old subtree is replaced each time a new upload takes place (see below for details).
The loaded hierarchy is stored as a subtree if a hierarchy with the specified technical key exists already. The key consists of the technical name of the hierarchy.
For the remainder of this document, the hierarchy that exists in the system already is referred to as H1, and the hierarchy that is to be loaded into the system is referred to as H2.
If you want to store hierarchy H2 as a subtree in H1, the root node of H2 must already be contained as a node in H1. There must be no other nodes from hierarchy H2 present in H1, unless they meet the requirements of a valid double-node. All subtrees that hang under the H2 root node are hung in H1 under the node with the same technical name (and "date to") as the root node in H2. With a subtree update, all the nodes that hang in H1 below this interface node are deleted beforehand.
Example 1.
The hierarchy for InfoObject 0CUST_SALES has the same root node as the InfoObject 0HIER_NODE. The rest of the hierarchy consists of nodes that can be posted to from the InfoObject 0CUST_SALES. If you compound the InfoObject 0SOURSYSTEM to 0CUST_SALES, it is possible to combine several hierarchies from different ERP systems into a single hierarchy in BW. When a hierarchy is loaded, the InfoObject 0SOURSYSTEM is filled automatically with the relevant source system ID. No duplicate nodes are generated. If all additional hierarchies are stored as subtree inserts, you get a hierarchy with a root node under which hang all the nodes that previously hung under a root node of the current hierarchy from one of the source systems. If you use a subtree update in this example, only the sub-tree that was loaded most recently appears in the target hierarchy, because all the nodes below the interface node are deleted before the subtree is inserted.
Example 2.
There are different SET-hierarchies for the InfoObject 0COSTCENTER, for example, for Europe, Mexico, and USA. The hierarchy nodes do not appear in any other hierarchies. In the hierarchy maintenance screens, a hierarchy with the name World has been created for BW. Three nodes that refer to the same InfoObject as the three root nodes of the SET hierarchy and have the same technical names are created under the root node. An entry is made in the scheduler, specifying that the three SET hierarchies are to be saved as sub-trees under the technical name of the World hierarchy. The result is a hierarchy with the three hierarchies for Europe, Mexico, and USA hanging under the root node. If, in this example, you used the sub-tree inset the scenario would have to be reconstructed each time a new upload took place, otherwise the hierarchy would be inserted twice. If, on the other hand, you use the sub-tree update option, the individual hierarchies can be reloaded as often as you like, because the old sub-tree is deleted every time.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 30A |
