Maintaining the Distribution Model


The distribution model describes the ALE message flow between logical systems – that is, it determines which messages are distributed to which logical systems. This BAPI-based distribution of data to recipients can be restricted according to your specific requirements.

For example, you can make distribution dependent on conditions that you define as filters in the ALE distribution model (through the Implementation Guide: Basis ® Application Link Enabling (ALE) ® Model and Implement Business Processes ® Maintain Distribution Model.

The prerequisite for this is that a filter object type has been assigned to the corresponding BAPI in the SAP application. SAP has already defined some filter object types and assigned them to different BAPIs. You can also define your own filter object types and assign them to a BAPI.
For more information on defining filter objects, refer to the document “ALE Introduction and Administration” under
Modeling Distribution.

We differentiate between different types of filtering for BAPIs:

Receiver Filtering

Before a BAPI or generated BAPI-ALE interface is called, its receivers have to be determined. To link the receiver determination with conditions, the business object methods are assigned to filter object types during receiver filtering. The values of these objects are used to determine the permitted receivers. The valid filter object values must be defined in the distribution model.

The following dependencies can be modeled in the ALE distribution model:

·        Between a BAPI and a message type

·        Between BAPIs

If a dependency of this type is defined as a condition in the ALE distribution model, then the receiver of the referenced BAPI or message type is determined.

For more information on receiver filtering and BAPIs, see the ALE Programmer Guide under Receiver determination for a BAPI.

Data Filtering

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

·        Interface reduction

The BAPI reduction is without conditions, which means that it involves a projection of the BAPI interface.

In the process, the distribution model suppresses values for optional BAPI parameters and/or fields during data transmission.
The developer of the BAPI whose interface is to be reduced must create the BAPI as reducible using appropriate parameter types.

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

·        Parameter Filtering

BAPI parameter filtering is linked with content-specific conditions: Lines in table parameters of an asynchronous BAPI are determined depending on the values in the lines (or dependent lines) for the receiver. The table dataset of a BAPI is determined for parameter filtering.
Hierarchical relationships can also be defined between table parameters of the BAPI.
To implement parameter filtering, business object methods are assigned to the business object method of filter object types. The valid filter object values must be defined in the distribution model.

For more information on data filtering and BAPIs, see the ALE Programmer Guide under Data filtering.

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