database commit End of a database LUW, in which changed sets are written to the database. Until database-commit, all changes are temporary and only visible to the executing program. After that, the changes are visible to all users of the database. In an ABAP-based SAP system, database-commits are triggered implicitly, as well as through explicit requests. ABAP_MORE_INFO
ARTICLE ( Version: 0008)
database commit End of a database LUW, in which changed sets are written to the database. Until database-commit, all changes are temporary and only visible to the executing program. After that, the changes are visible to all users of the database. In an AS ABAP, database-commits are triggered implicitly, as well as through explicit requests. ABAP_MORE_INFO
ARTICLE ( Version: 0009)
Database Commit Final step of a database LUW, in which changed records are written to the database. Until the data is committed to the database, all changes are temporary and only visible to the executing program. After the commit, the changes are visible to all users of the database. In an AS ABAP, database commits are triggered implicitly, as well as through explicit requests. ABAP_MORE_INFO
ARTICLE ( Version: 0010)
Database commit End of a database LUW, in which changed data records are written to the database. All changes are temporary until they have been written using a database commit. Changes are always directly visibile to the executing program. The database system that is used determines whether other users can see the database changes immediately or only after the database commit. In AS ABAP, database commits are triggered implicitly, as well as by being requested explicitly. ABAP_MORE_INFO
Message text extract from SAP system. Copyright SAP SE.
Search for further information about these or an SAP related objects
Comments on this SAP object
What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!