Structure of a Flat Hierarchy File for Loading Using a PSA

Prerequisites

You have created a sorted hierarchy and the system generates a structure with the following hierarchy format. The hierarchy basis characteristic has n node attributes, is compounded m times, and has additional node characteristics that contain additional fields with compounding l:

Description	Field Name	Length	Type
Node ID	NODEID	8	NUMC
InfoObject name	INFOOBJECT	30	CHAR
Node name	NODENAME	32	CHAR
Catalog ID	LINK	1	CHAR
Parent node	PARENTID	8	NUMC
First subnode	CHILDID(*)	8	NUMC
Next adjacent node	NEXTID(*)	8	NUMC
	DATETO*	8	CHAR
	DATEFROM*	8	CHAR
	LEAFTO*	32	CHAR
	LEAFFROM*	32	CHAR
Language key	LANGU	1	CHAR
Description - short	TXTSH	20	CHAR
Description - medium	TXTMD	40	CHAR
Description- long	TXTLG	60	CHAR
<Node attribute 1>
...
<Node attribute n>
<Node field 1 >*
...
<Node field m >*
<Node field m+1 >
...
<Node field m+1>
<To field 1>*	TO-**
...	TO-**
<To field m>*	TO-**

The rows marked in green(*) are only generated automatically if a sorted hierarchy is being used.

The rows marked blue* are only automatically generated if you have created an InfoObject with a time-dependent hierarchy and/or intervals.

The rows marked red are only automatically generated if you have permitted additional node attributes.

The rows marked red* are only automatically generated if you have set the Expand Leaf Values and Node InfoObjects indicator in the maintenance of the hierarchy header in the InfoSource maintenance. The to- fields are inserted with the same name as the from- fields, but in their own sub-structure (TO-**).

Note

Choosing the Expand Leaf Values and Node InfoObjects pushbutton displays the hierarchy structure. For additional details about this function, also refer to the Hierarchy Maintenance section ofUploading Hierarchies from Flat Files.

Process

You can find out how you need to fill the fields in the section Process inStructure of a Flat Hierarchy File for Loading Using an IDoc.

Result

You have created a flat file with a hierarchy, which you must save as a CSV or ASCII file. You can then upload it into the BW using the PSA.

Structuring a Simple Hierarchy File - Example:

Without expanded leaf values and node InfoObjects:

With expanded leaf values and node InfoObjects:

Here the columns controlling area (CO_AREA) and cost element (COSTELMNT), as well as interval controlling area (CO_AREA) and interval cost element (COSTELMNT) are added.

The files displayed above would correspond to the following hierarchy:

This hierarchy of cost elements has the following properties:

It has 0COSTELMNT as a hierarchy basic characteristic, which is compounded to 0CO_AREA. That is why both characteristics have to be included in the file. For expanded leaf values and node InfoObjects both characteristics have to be included twice for intervals: An interval is assigned to the USA node, which includes the cost element 20-25. The file needs the fields 0CO_AREA and 0COSTELMNT twice for the interval, for both the from- and to- value. The interval description is made up from a combination of the specifications for these two characteristics: 0002 for 0CO_AREA and 0000000020 for 0COSTELMNT.
The controlling area (0CO_AREA) has to be maintained as an external characteristic for the cost element InfoObject (0COSTELMNT).
The hierarchy is a sorted hierarchy.
This node also has the node attribute sign change, meaning that the cost element can be displayed as a negative in the query. For this reason, an X is uploaded for this node representing the sign change (SIGNCH)