Commit changes on SAP BAPI Transaction

You are correct that in order for the changes done by BAPI to come into effect, you need to call the commit function. The BAPI_TRANSACTION_COMMIT function module is essential for persisting changes made through BAPI calls to the database.

It will commit all the changes which are uncommitted, not only the last transaction. This means that if you have multiple BAPI calls or database operations in your program, calling BAPI_TRANSACTION_COMMIT will save all pending changes.

BAPI_TRANSACTION_COMMIT vs COMMIT WORK

There are two primary ways to commit transactions in SAP ABAP when working with BAPIs ?

• BAPI_TRANSACTION_COMMIT ? Specifically designed for BAPI transactions and includes additional error handling capabilities
• COMMIT WORK ? Standard ABAP commit statement that commits all open transactions

Example

Here's how to properly use BAPI_TRANSACTION_COMMIT after a BAPI call ?

" Call your BAPI function
CALL FUNCTION 'BAPI_CUSTOMER_CHANGE'
  EXPORTING
    customerno = '1000'
    customerx  = customer_data
  IMPORTING
    return     = return_messages.

" Check for errors
IF return_messages-type NE 'E'.
  " Commit the transaction
  CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait = 'X'
    IMPORTING
      return = commit_return.
ENDIF.

The wait = 'X' parameter ensures that the commit operation waits for the database update to complete before continuing with the next statement.

You can refer to the SAP Community Wiki to know more about the differences between BAPI_TRANSACTION_COMMIT and COMMIT WORK.

Conclusion

Always remember to call BAPI_TRANSACTION_COMMIT after successful BAPI operations to ensure your changes are permanently saved to the database. Without this commit, all your BAPI changes will be lost when the program ends.