WebSphere Adapter for SAP Software

Features of the BAPI interface

The adapter supports simple BAPIs as well as BAPI transactions managed by the application server. The adapter also supports the use of local (JCA) transactions for calling BAPIs.

Simple BAPIs

A simple BAPI call is a synchronous blocking call. A client can invoke a BAPI to perform a single operation, such as retrieving a list of customers. The adapter supports simple BAPI calls by representing each with a single business object schema.
Note: The BAPI interface supports after-image updates only. An after-image update is a complete snapshot of an object with information about whether the object was created, updated, or deleted but without the specifics of exactly what changed.

Make sure you install the CWYAP_SAPAdapter.rar file to work with simple BAPIs.

BAPI transactions

A BAPI transaction, also referred to as a BAPI logical unit of work, consists of a set of BAPIs that are executed in sequence to complete the entire transaction.

For example, to update an employee record in the SAP system, the record needs to be locked before being updated. This is accomplished by calling three BAPIs, in sequence, in the same transaction. The following three BAPIs illustrate the kind of sequence that forms such a transaction:
  • BAPI_ADDRESSEMP_REQUEST
  • BAPI_ADDRESSEMP_CHANGE
  • BAPI_ADDRESSEMP_APPROVE

The first BAPI in the transaction locks the employee record, the second updates the record, and the third approves the update. The advantage of using a transaction is that the client can invoke the employee record change with a single call, rather than with three separate calls. In addition, if SAP requires that the BAPIs execute in a specific sequence for the business flow to complete correctly, the transaction supports this sequence.

Make sure you install the CWYAP_SAPAdapter.rar file to work with BAPI transactions in which the transaction is managed within the application server.

J2C local transactions for BAPIs

The adapter supports calling BAPIs from within a J2C local transaction. Local transactions are managed internally and involve no external transaction managers.

You can invoke multiple BAPIs as part of a J2C local transaction before issuing a COMMIT operation.

Use CWYAP_SAPAdapter_Tx.rar file if you are calling BAPIs from J2C local transactions.


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)