BAPIcommit
The service commits a transaction with a single or multiple BAPI calls.
Note: You need to use clientLockSession or clientReleaseSession to make sure to keep your connection
in transaction scenarios as the transaction context is stored with the session in the SAP
system.
- Input parameters
-
- serverName
- Alias of the SAP system on which the transaction must be committed. This name must match an RFC connection alias at SAP® ERP.
- $client
- Optional. Client for the session. If no client is specified, the default client is used.
- $user
- Optional. User name for the session. If no user is specified, the default user is used.
- $pass
- Optional. Password for the session. If the password is not specified, then the user and password is looked up in the SAP User store.
- $language
- Optional. Language used during the session. If no language is specified, the default language is used.
- wait
- Optional. A flag that indicates whether call must wait until data is written to the database.
- Return values
-
- Return
- Return code in BAPI style that keeps the success or failure of the commit.