The adapter uses the BAPI interface to request BAPI functions
or transactions. The request is sent to the SAP system, and the response is
returned.
The following steps describe how the adapter supports
outbound processing for the BAPI interface.
Note: The client application that
makes the BAPI call uses the interface information that was generated by the
enterprise service discovery wizard.
- The adapter receives a request, which includes a BAPI business object,
from a client application.
- The adapter converts the BAPI business object to an SAP JCo function call.
- The adapter uses the Remote Function Call (RFC) interface to execute the
BAPI/RFC function call in the SAP application.
- After passing the data to SAP, the adapter handles the response from SAP
and converts it back into the business object.
- The business object is then sent to the calling component (the client
application).
BAPI transactions
The adapter does not provide an automated
rollback mechanism for BAPI transactions. Rollback of a BAPI transaction can
be achieved in one of the following ways:
- Do not put explicit COMMITs in the application-specific information sequence.
When an error occurs in one of the BAPIs, the sequence of BAPI calls is terminated
and BAPI_TRANSACTION_ROLLBACK is called. If there is no intrinsic COMMIT in
any of the BAPIs already called, no further steps are required. Most BAPIs
do not have an intrinsic COMMIT.
- Call another BAPI that can compensate for the work that is already committed,
as in the case of the BAPIs that have an intrinsic COMMIT.
Local transactions
The adapter
supports J2C local transactions for the BAPI interface.
Terms of use |
Last updated: Mon 30 Oct 2006 03:34:55
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)