sapdev logo background
sapdev logo sapdev logo
Comments

SAP TRANSACTION documentation, setup help and example usage



Return to SAP documentation index


ARTICLE

Data Consistency
When external data is changed by application programs, it must be ensured that the data is consistent after changes have been made. This is particularly the case for the processing of data in the database. The time span during which a consistent data status is transferred to another consistent status is known as a LUW ( Logical Unit of Work
). If an error occurs during a LUW, it is possible to reset all changes made up to this point and regenerate the data in its original consistent status (rollback). When a new consistent status has been reached, this new status can be set and a new LUW can be opened (Commit).
In an AS ABAP there are two type of LUWs:
  • Database LUWs that are realized by the database system

  • SAP LUWs , that are realized using special ABAP proramming techniques

  • Accordingly, there are two lock types that are of significance:
  • Database locks that are set by the system

  • SAP locks that are set using special ABAP proramming techniques

  • Finally, the authorizations of a user are important for data consistency for accessing data whose check has an ABAP statement .
    Documentation extract taken from SAP system, � Copyright SAP AG. All rights reserved




    TRAILING_BLANKS_LITERALS_GUIDL
    TRANSACTIONS_ABEXAS




    comments powered by Disqus