Hierarchy
SAP_BW (Software Component) SAP Business Warehouse⤷
BW-PLA-BPS (Application Component) Business Planning and Simulation⤷
UPP (Package) SEM-BPS: Planning Processor and Layout Builder
Basic Data
| Data Element | UPP_Y_BUDGET_HIE |
| Short Description | BW Hierarchy with Postable Nodes |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR1 | |
| 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 | 10 | Budget |
| Medium | 20 | Budget Hie. |
| Long | 40 | Budget Hierarchy |
| Heading | 50 | Budget Hierarchy |
Documentation
Definition
Every BW hierarchy is created for a charateristic. If a node with a successor node is a characteristic value on a hierarchy-bearing characteristic, then this node is called postable. In manual planning, an end node with the same characteristic value is always generated for a postable node at runtime in the BW hierarchy. This end node holds the values which are not yet distributed. Only the values of end nodes can be posted in BW. As with text nodes or nodes on characteristics other than the hierarchy-bearing characteristic, the values for postable nodes are determined at runtime. In manual planning, the postable nodes are ready for input, however not the end nodes with the same characteristic value generated by the system. Changes to postable nodes or successor nodes are then adjusted by the system to the end node of the postable node analog to the functions in BPS Characteristic Hierarchies.
Logically the same rules apply to hierarchies as to BPS characteristic hierarchies. The pages belonging to the postable nodes with the characteristic value of the node, correspond with BPS characteristic hierarchies exactly to the dummy pages.
Note: Consequently BW hierarchies are an alternative to characteristic hierarchies. They have the advantage of a great flexibility when changing hierarchies. However, since the values to the nodes can always be calculated first at runtime, you should only work with small hierarchies or only with small subtrees (less than 1000 nodes) in manual planning. You can always only work on complete subtrees of the hierarchy. Characteristic hierarchies do not have these restrictions. However, the effort when changing a hierarchy is usually greater. Both of these aspects should be carefully weighed up when modeling manual planning.
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 3.1A |
