BAPIs Used for Outbound Processing (SAP Library - BAPI Programming Guide Reference (CA-BFA))

BAPIs Used for Outbound Processing

Use

As of Release 4.5A, BAPIs can also be defined which have been implemented outside the SAP System yet can still be called from the SAP System.

These BAPIs are known as BAPIs used for outbound processing. Unlike the conventional BAPIs that are implemented in the SAP server system and also called here (inbound), outbound BAPIs are interfaces implemented on the client system. In this case, the SAP System acts as the client.

The target system for the BAPI call is determined in the distribution model of Application Link Enabling (ALE).

Integration

BAPIs used for outbound processing are defined in the Business Object Repository as API methods of SAP interface types. Interfaces to services implemented outside the R/3 System can be standardized and made available as BAPIs. BAPIs both for outbound processing and for inbound processing can be called in the same way via the ALE distribution model.

Features

When creating BAPIs for outbound processing keep in mind:

BAPIs used for outbound processing simply require the interface definition; the function module cannot be programmed.

Use the BOR/BAPI Wizard to create a BAPI of an SAP interface type. For further information see Defining Methods in the BOR Using the BOR/BAPI Wizard.

In Release 4.5A, API methods of interface types must have the status "implemented".

BAPIs used for outbound processing can be determined from the BOR using transaction SWO1 .

The information contained in the BAPI Programming Guide refers to - with the exception of the above-mentioned points - BAPIs of both SAP interface types and SAP business object types. Any other differences are explained in detail.