Uploading Hierarchies from Flat
Files
Prerequisites
If you want to load InfoObjects in the form of hierarchies, you have to activate the indicator with hierarchies for each of the relevant InfoObjects in the InfoObject maintenance. If necessary, you need to specify whether the whole hierarchy or the hierarchy structure is to be time-dependent, whether the hierarchy can contain intervals, whether additional node attributes are allowed (only when loading using a PSA), and which characteristics are allowed.
Procedure
...
1. Defining the source system from which to load data
Choose the source system tree File → Create.
2. Defining the InfoSource for which you want to load data
Optional: choose InfoSource Tree → Root (InfoSources) → Create Application Components.
Choose InfoSource Tree → Your Application Component → Other Functions → Create InfoSource 3.x → Direct Update.
Choose an InfoObject from the proposal list, and specify a name and a description.
3. Assigning the source system to the InfoSource
Choose InfoSource Tree → Your Application Component → Your InfoSource → Assign Source System. The transfer structure maintenance screen appears.
The system automatically generates DataSources for the three different data types to which you can load data.
○ Attributes
○ Texts
○ Hierarchies (if the InfoObject has access to hierarchies)
The system automatically generates the transfer structure, the transfer rules, and the communication structure (for attributes and texts).
4. Maintaining the transfer structure / transfer rules
Select the DataSource for uploading hierarchies.
IDoc transfer method: The system automatically generates a proposal for the DataSource and the transfer structure. This consists of an entry for the InfoObject for which hierarchies are loaded. With this transfer method, the structure is converted to the structure of the PSA during loading, which affects performance.
PSA transfer method: The transfer methods and the communication structure are also generated here.
5. Maintaining the hierarchy
Choose Hierarchy Maintenance, and specify a technical name and a description of the hierarchy.
You load a sorted hierarchy without expanded leaf values and node InfoObjects. The system generates a table with the following hierarchy format:
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 |
Higher-level node |
PARENTID |
8 |
NUMC |
First subnode |
CHILDID |
8 |
NUMC |
Next adjacent node |
NEXTID |
8 |
NUMC |
Language key |
LANGU |
1 |
CHAR |
Description - short |
TXTSH |
20 |
CHAR |
Description - medium |
TXTMD |
40 |
CHAR |
Description - long |
TXTLG |
60 |
CHAR |
We recommend that you use the transfer method PSA: Here you can set the indicator Expand Leaf Values and Node InfoObjects. As a result, characteristic values are not transferred to the hierarchy fields NODENAME, LEAFFROM and LEAFTO as is normally the case, but to their own transfer structure fields. With this option you can load characteristic values whose node name length corresponds to the maximum length possible for characteristics (currently 60). Prerequisite is that you activated the option Expanded leaf values.
The system transfers the settings for the intervals and for time-dependency from the InfoObject maintenance. Depending on which settings you have defined in the InfoObject maintenance, further table fields can be generated from the system.
The valid from and valid to field is filled if you select Total Hierarchy Time-dependent in the InfoObject maintenance. The time-dependent indicator is activated if you select the Hierarchy Nodes Time-dependent option in the InfoObject maintenance.
6. Save your entries.
Depending on which settings you defined in the InfoObject maintenance, additional fields can be generated by the system. Also note the detailed description for Structure of a Flat Hierarchy File for Loading via an IDoc and for Structure of a Flat Hierarchy File for Loading Using a PSA.
Further Steps: