Show TOC

Special Features when Loading using the PSALocate this document in the navigation structure


When loading hierarchies using the PSA transfer method, a much more flexible option is at your disposal for processing hierarchies in comparison with the Idoc transfer method.


A hierarchy DataSource from a SAP source system must support loading by using a PSA.


Error treatment

By storing hierarchies in PSA tables, the system allows you to make manual corrections when errors arise.

The system generates up to 5 PSA tables for a hierarchy DataSource. These tables contain the following hierarchy segments:

  • ·        Hierarchy header
  • ·        Texts for hierarchy header
  • ·        Hierarchy node
  • ·        Node texts
  • ·        Intervals

You only need the interval segment when the DataSource supports intervals in hierarchies and this is indicated in InfoObject maintenance.

If you are editing the hierarchy in the PSA, you can select a hierarchy segment in the selection dialog. The system displays each segment individually in a table.

Flexible attributes for the hierarchy header and hierarchy node

  • ·        Attributes for the hierarchy header are settings that are valid for the display and processing of the entire hierarchy in the query. You can find additional information in the table Functions for Displaying and Processing Hierarchies in a BEx Query underFunctions of Hierarchy Processing.
  • ·        Attributes for hierarchy nodes are hierarchy attributes that are selected for the hierarchy basic characteristic in InfoObject maintenance and which are valid for all hierarchies for this characteristic. SeeHierarchy Properties andTab Page: Hierarchy.

Checking permitted node characteristics

When transferring hierarchies via the RFC, the system checks for which characteristics characteristic values with hierarchy nodes are allowed to be identified.  The permitted InfoObjects must be selected via External Characteristics in Hierarchies.

  • ·        If no InfoObject is selected, only text nodes (for the artificial characteristic) are allowed as inner nodes.
  • ·        All selected InfoObjects are included together with the characteristics compounded to them in the communication structure for hierarchy nodes.

Communication structure and transfer rules for hierarchies

If a hierarchy structure is loaded via the transfer method PSA, you can then define the transfer rules. The result is the same flexible transformation options as is the case for transaction data, attributes and texts, excluding the fact that it is not possible to create a start routine.

In the InfoSource maintenance, there are the following views of the transfer rules:

  • ·        View for the hierarchy header segment
  • ·        View for the hierarchy node segment

For the hierarchy header, you can set the properties of the hierarchy header and the properties of the file structure via Hierarchy Structure.

In the following example, the field KOKRS is assigned to the field Controlling Area (0CO_AREA) and the field KOSTL is assigned to the field Cost Center (0COSTCENTER) using the transfer rules. The alpha conversion routine is executed for KOKRS. The node has the hierarchy property Reversing the Sign(0SIGNCH). This is also uploaded. As InfoObject 0COSTCENTER is compounded to InfoObject 0CO_AREA, the characteristic values in NODENAME are saved added to one another.

See also:

Structure of a Flat Hierarchy File for Loading Using a PSA