Show TOC

Hierarchies Between BAPI ParametersLocate this document in the navigation structure

Use

When hierarchical dependencies exist between the table parameters of a BAPI, these hierarchies must be explicitly defined to allow parameter filtering.

Example

A BAPI for material master data contains the tables for plant data and associated storage data. The table containing plant data has a reference to the table containing storage data via the key field PLANTS. There is a hierarchical dependency between the plant and storage data. If plant 001 of a material is not to be replicated due to parameter filtering, then none of the storage data for plant 001 will be replicated.

There is a hierarchical dependency between the plant and storage data. These references must be defined before you create the BAPI-ALE interface, as this information is generated with the interface.

Procedure

You can define hierarchical dependencies in ALE development using Start of the navigation path BAPI Next navigation step Data Filtering Next navigation step Maintain Hierarchy of Table Parameters End of the navigation path (transaction BDBP).

To do this, enter the object type and method of the BAPI. You can display existing BOR object types and their associated methods using the input help (F4).

The following processing options are available in the Hierarchy menu:

  • Create

  • Change

  • Display

  • Delete

For more information on creating parameter hierarchies, see the ALE Programming Guide under Defining Hierarchies between BAPI Parameters.