Help Portal
Technology Platform
Search within this release
Sitem ap Global Search
The Best-Run Businesses Run SAP
Analytics
Data Management
Human Capital Management
Supply Chain Management
Content and Collaboration
Enterprise Management
Product Lifecycle Mgmt
Technology Platform
Customer Relationship Mgmt
Financial Management
Supplier Relationship Mgmt
Additional Information
SAP Business Warehouse
SAP NetWeaver BI Content
ABAP Programming (BC-ABA)
Fullscreen
ABAP Programming (BC-ABA)
Print
Download
Select language: en - English
Exam ple
Exam ple
Exam ple
Exam ple
Exam ple
open in browser PRO version
Database Logical Unit of Work (LUW)
From the point of view of database programming, a database LUW is an inseparable sequence of database
operations that ends with a database commit. The database LUW is either fully executed by the database system
or not at all. Once a database LUW has been successfully executed, the database will be in a consistent state. If
an error occurs within a database LUW, all of the database changes since the beginning of the database LUW are
reversed. This leaves the database in the state it was in before the transaction started.
Are you a developer? Try out the HTML to PDF API
pdfcrowd.com
Linking ABAP Strings to Screen Fields
Exam ple
Overview Graphics for Interfaces
Exam ple
Top-Level Binding
Introduction to ABAP
The ABAP Program m ing Language
ABAP Syntax
Data Types and Data Objects
Operations on Data Objects
Controlling the Program Flow
Byte and Character String
Processing
Internal Tables and Extracts
Database Accesses
Data Interfaces
Data Clusters
Data Consistency
open in browser PRO version
Implicit Database Commits
A work process can only execute a single database LUW. The consequence of this is that a work process must
always end a database LUW when it finishes its work for a user or an external call. Work processes trigger an
implicit database commit in the following situations:
Field Sym bols and Data
References
Saving Data Externally
The database changes that occur within a database LUW are not actually written to the database until after the
database commit. Until this happens, you can use a database rollback to reverse the changes. In the SAP System,
database commits and rollbacks can be triggered either implicitly or using explicit commands.
When a dialog step is completed
Control changes from the work process back to the SAP GUI.
When a function module is called in another work process (RFC).
Control passes to the other work process.
When the called function module (RFC) in the other work process ends.
Control returns to the calling work process.
When a WAIT statement interrupts the work process.
Control passes to another work process.
Error dialogs (information, warning, or error messages) in dialog steps.
Control passes from the work process to the SAP GUI.
Are you a developer? Try out the HTML to PDF API
pdfcrowd.com
Transactions and Logical
Units of Work
Database Logical Unit of
Work (LUW)
SAP LUW
Explicit Database Commits
There are two ways to trigger an explicit database commit in your application programs:
Call the function module DB_COMMIT
The sole task of this function module is to start a database commit.
Use the ABAP statement COMMIT WORK
This statement starts a database commit, but also performs other tasks (refer to the keyword documentation for
COMMIT WORK).
SAP Transactions
Checking Authorizations
Implicit Database Rollbacks
The following cases lead to an implicit database rollback:
The SAP Lock Concept
Update Techniques
Creating Update Function
Modules
Calling Update Functions
Special LUW Considerations
Error Handling for Bundled
Updates
Obsolete Techniques
Runtime error in an application program
This occurs whenever an application program has to terminate because of an unforeseen situation (for example,
trying to divide by zero).
Termination message
Termination messages are generated using the ABAP statement MESSAGE with the message type A or X. In
certain cases (updates), they are also generated with message types I, W, and E. These messages end the
current application program.
Explicit Database Rollbacks
You can trigger a database rollback explicitly using the ABAP statement ROLLBACK WORK. This statement
starts a database rollback, but also performs other tasks (refer to the keyword documentation for ROLLBACK
WORK).
From the above, we can draw up the following list of points at which database LUWs begin and end.
Executing ABAP Program Units
A Database LUW Begins
ABAP Objects
ABAP and Unicode
Each time a dialog step starts (when the dialog step is sent to the work process).
Whenever the previous database LUW ends in a database commit.
Whenever the previous database LUW ends in a database rollback.
ABAP User Interfaces
A Database LUW Ends
Appendix
open in browser PRO version
Each time a database commit occurs. This writes all of the changes to the database.
Each time a database rollback occurs. This reverses all of the changes made during the LUW.
Are you a developer? Try out the HTML to PDF API
pdfcrowd.com
Database LUWs and Database Locks
As well as the database changes made within it, a database LUW also consists of database locks. The database
system uses locks to ensure that two or more users cannot change the same data simultaneously, since this could
lead to inconsistent data being written to the database. A database lock can only be active for the duration of a
database LUW. They are automatically released when the database LUW ends. In order to program SAP LUWs, we
need a lock mechanism within the R/3 System that allows us to create locks with a longer lifetime (refer to The SAP
Locking Concept).
Share this page: Tweet
Copyright/Legal Notice
Im pressum
open in browser PRO version
Privacy Statem ent
Disclaim er
Are you a developer? Try out the HTML to PDF API
Icons Used
License Keys
Contact Us
pdfcrowd.com
