To determine the receivers of an asynchronous BAPI, the application program calls the function module ALE_ASYNC_BAPI_GET_RECEIVER.

The following mechanisms are effective:

• If a dependency for a BAPI is defined as a condition in the ALE distribution model, the receiver of the referenced BAPI or message type is determined. The application program has to pass the object ID (for example, 01815) as the value of the filter object to the receiver determination.

From the object ID the function module ALE_ASYNC_BAPI_GET_RECEIVER determines the current filter object values of the object through which the dependent BAPI references to another BAPI or message type. The application must provide a function module that enables the object data to be read. The name of the function module must be stored in an ALE Customizing table, which the receiver determination can access at runtime (Table TBD18).

• If no receivers are determined or the BAPI cannot be found in the distribution model, an empty table for the receivers is returned.
• If the forwarded filter object types and filter object values are unable to determine the receiver correctly, an error message and an exception are returned (ERROR_IN_FILTEROBJECTS).
• If any inconsistencies have arisen in the distribution model due to Customizing errors, an error message and an exception are returned (ERROR_IN_ALE_CUSTOMIZING).