Show TOC

Example: Old BAPI Transaction Model (with Commit)Locate this document in the navigation structure

Use

There is one BAPI call for each transaction in the old transaction model (valid for Release 3.1). BAPIs can only be called synchronously. A BAPI call is essentially the call of the underlying RFC capable function module. The process flow of the program consists of the following steps below (see graphic below):

  • Log on

    (Program Code)

  • Call BAPI to read and/or change data

    (Program Code)

  • Call BAPI to read and/or change data

    (Program Code)

  • Log off

Transaction Model with Commit

The (write) BAPIs developed in Release 3.1 along with a few further exceptions execute a COMMIT WORK command themselves.

Caution

If a BAPI executes a COMMIT WORK command, this must be mentioned in the BAPI documentation. This is the only way users are able to know that the BAPI contains a COMMIT WORK command.