Get Example source ABAP code based on a different SAP table
Database LUW A database LUW (also referred to as a database transaction) is a non-separable sequence of database operations that is completed with a database commit. The database LUW is either executed completely by the database system or not at all. After a database LUW has been completed successfully, the database returns to a consistent state and a new database LUW is opened. If an error is detected within a database LUW, all database changes made since the start of the database LUW can be undone using a database rollback. The database is subsequently restored to the same status as before the start of the database LUW. Isolation levels determine whether other users can perform reads on data modified in a database LUW before a database commit is performed.
Database commit
Database rollback
Isolation levels The ABAP statements used to execute database commits or database rollbacks explicitly are as follows:
COMMIT CONNECTION
ROLLBACK CONNECTION
Latest notes:
At the end of a database LUW, all reader streams and locators created in it are closed implicitly. A writer stream that is still open is only closed as part of a database rollback and causes a runtime error during a a database commit. NON_V5_HINTS
Any database commits or database rollbacks that occur within the update cancel the update with a runtime error. See Forbidden Statements in Updates. ABAP_HINT_END
