Determining Receivers of Synchronous BAPIs

The application program calls the function ALE_SYNCH_BAPI_GET_RECEIVER to determine the receiver of a synchronous BAPI.

The following points apply:

• If no receivers are determined or the BAPI cannot be found in the ALE distribution model, an empty table for the receivers is returned.

• 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 has to pass the object ID (for example, 01815) as the value of the filter object to receiver determination.

  Receiver determination uses the object ID to read the current filter object values for the object using which the dependent BAPI references another BAPI or message type. The application provides a function module that enables the object data to be read. The name of the function module is stored in an ALE Customizing table, which the receiver determination can access at runtime (table TBD18). As well as the logical system the RFC destination is also returned.

• If the filter object types and filter object values that are passed are not sufficient to determine the receiver correctly, an error message and an exception are returned (ERROR_IN_FILTEROBJECTS).

• If the RFC destination for a logical receiver system has not been maintained, an error message and an exception are returned (NO_RFC_DESTINATION_MAINTAINED).

• If any inconsistencies arise in the distribution model due to Customizing errors, an error message and an exception are returned (ERROR_IN_ALE_CUSTOMIZING).

• Example Programs with Synchronous BAPI Calls