Show TOC

Background documentationFiltering of Data

 

Two data filtering services are provided for asynchronous BAPI calls via the BAPI-ALE interface:

  • Interface reduction

    If you reduce the BAPI interface, you do not have to define any filter object types.

    The BAPI reduction does not have any conditions - it is a projection of the BAPI interface.

    The developer of the BAPI whose interface is to be reduced must create the BAPI as a reducible using appropriate parameter types.

    The optional BAPI parameters and/or BAPI fields are deactivated in the distribution model for the data transfer.

    You can reduce an interface in two ways, see Reduction of Interfaces:

    1. By fields (using checkbox)

    2. Complete

  • Parameter filtering

    Filter object types are assigned to the business object method. The valid filter object values must be defined in the distribution model.

    The BAPI parameter filtering is linked to conditions and is therefore content-dependent: The lines in table parameters of asynchronous BAPIs are determined depending on the values in the lines (or dependent lines) for the receiver.

    Filters are used to define conditions in the form of parameter values that must be satisfied by BAPIs before they can be distributed in ALE outbound processing.

    The table dataset of a BAPI is determined when the parameters are filtered.

    Hierarchical relationships can also be defined between table parameters of the BAPI.

    Distribution by classes is also supported.

    For more information, see Filtering of BAPI Parameters.

BAPI filtering is the term applied to the shared use of both filter services of the BAPI interface. BAPI filtering is implemented as a service in ALE outbound processing.

Prerequisites

Prerequisites for Using Filter Services

The table below lists the prerequisites that the BAPI interface must satisfy, so that ALE filter services can be used.

The BAPI can have the following parameter types:

Reduction by Fields

Full Filtering

Parameter Filtering

Unstructured without checkbox

Unstructured with checkbox

X

Single-line structured without checkbox

Single-line structured with checkbox

X

Multiple-line structured without checkbox

X

X

Multiple-line structured with checkbox

X

X

X

Multiple-line unstructured without checkbox

X

Multiple-line unstructured with checkbox

Note: The fields filled with X satisfy the prerequisites.

Explanation of above table:

  1. An unstructured parameter without a checkbox is, for example, a BAPI key field (such as the Material parameter in methods for the Material business object). This parameter type cannot be reduced.

  2. If an unstructured parameter P has an unstructured checkbox parameter PX and a data element BAPIUPDATE, parameter P is reducible. The parameter is reduced by setting the value of P and of the checkbox parameter PX to EMPTY.

  3. A single-line, structured parameter without a checkbox is not reducible.

  4. A single-line, structured parameter P with structure S and associated checkbox PX with structure SX can be reduced by fields, provided that:

    • S and SX have the same number of fields, which are identical in name and sequence.

    • The FUNCTION field and the key fields in S and SX each have the same data element.

    • All other fields in SX have the data element BAPIUPDATE.

    The FUNCTION field in P and the key fields must be marked as mandatory fields. All other fields can (but do not have to) be marked as mandatory. Mandatory fields cannot be reduced. Non-mandatory fields are reduced by setting the field value and the corresponding checkbox to EMPTY.

  5. Multiple-line structured parameters (table parameters) without a checkbox cannot be reduced by fields. Parameter filtering and full filtering are possible.

    If the hierarchy is maintained and dependent tables exist in the hierarchy, records of the dependent tables are also filtered.

  6. A multiple-line structured parameter P with checkbox PX can be reduced by fields, fully filtered or filtered by parameters.

    • For field reduction the prerequisites under 4 must be met.

    • Checkbox PX must lie directly under P in the hierarchy and have identical key fields, so that the corresponding lines from P and PX are filled when the parameters are filtered.

    • If the hierarchy is maintained and dependent tables exist in the hierarchy, records of the dependent tables are also filtered.

  7. A multiple-line, unstructured parameter can only be fully filtered and cannot be used in a hierarchy. Parameter filtering is not allowed.

  8. Multiple-line, unstructured parameters with a checkbox cannot be filtered.