Skip to content

ABAP Keyword Documentation →  ABAP − Reference →  Processing External Data →  ABAP Database Access →  Data Consistency →  SAP LUW 

ROLLBACK WORK

Quick Reference

Other versions: 7.31 | 7.40 | 7.54

Syntax


ROLLBACK WORK.

Effect

The statement ROLLBACK WORK closes the current SAP LUW and opens a new one. This cancels all changes requests made by the current SAP LUW. In this case, ROLLBACK WORK performs the following actions:

  • Executes all subroutines registered using PERFORM ON ROLLBACK.

  • Deletes the registrations of all subroutines registered using PERFORM ON COMMIT.

  • Raises an internal event in the Object Services that makes sure that the attributes of persistent objects are initialized.

  • Deletes all update function modules registered with CALL FUNCTION ... IN UPDATE TASK from the database tables VB... and deletes all Remote Function Calls registered with CALL FUNCTION ... IN BACKGROUND UNIT or CALL FUNCTION ... IN BACKGROUND TASK (obsolete) from the database tables ARFCSSTATE and ARFCSDATA.

  • Removes all SAP locks set in the current program for which the formal parameter _SCOPE of the lock function module was set to the value 2.

  • Triggers a database rollback on all currently open database connections, which also ends the current database LUW.

    • After the statement ROLLBACK WORK is completed, the event TRANSACTION_FINISHED from the system class CL_SYSTEM_TRANSACTION_STATE is raised. Here, the parameter KIND has the value of the constant CL_SYSTEM_TRANSACTION_STATE=>ROLLBACK_WORK.


    Notes

    • All open database cursors in the database connections concerned are closed during ROLLBACKs, which means that a runtime error occurs when the system attempts to continue a SELECT loop after a ROLLBACK. For the same reason, a FETCH after a ROLLBACK on the cursor that is now closed also causes a runtime error. Make sure that cursors that are still open are no longer used after the ROLLBACK.
    • After a ROLLBACK statement, sy-subrc is always zero. It is not necessary to query whether sy-subrc is not equal to zero after ROLLBACK.
    • ROLLBACK must not be used during updates (CALL FUNCTION ... IN UPDATE TASK) or when subroutines registered using PERFORM ... ON COMMIT or PERFORM ... ON ROLLBACK are being executed.
    • The statement ROLLBACK WORK must not be executed in units or LUWs that are managed by background RFC calls (bgRFC and the obsolete tRFC and qRFC).
    • The ROLLBACK WORK statement is executed implicitly if a message of type A is handled by the addition error_message when calling a function module with CALL FUNCTION.
    • ROLLBACK WORK empties global temporary tables of all currently open database connections and prevents the runtime error COMMIT_GTT_ERROR in the case of implicit database commits.


    Example

    The statement ROLLBACK WORK deletes the registration of update function modules made using the statements CALL FUNCTION IN UPDATE TASK and calls the subroutine cleanup.

    PERFORM cleanup ON ROLLBACK. 

... 

CALL FUNCTION 'DEMO_UPDATE_DELETE' IN UPDATE TASK. 

... 

DATA(values) = VALUE demo_update_tab( 
  ( id = 'X' col1 = 100 col2 = 200 col3 = 300 col4 = 400 ) 
  ( id = 'Y' col1 = 110 col2 = 210 col3 = 310 col4 = 410 ) 
  ( id = 'Z' col1 = 120 col2 = 220 col3 = 320 col4 = 420 ) ). 

CALL FUNCTION 'DEMO_UPDATE_INSERT' IN UPDATE TASK 
  EXPORTING 
    values = values. 

... 

ROLLBACK WORK. 

... 

FORM cleanup. 
  ... 
ENDFORM.

    Exceptions

    Non-Handleable Exceptions

    • Cause: ROLLBACK WORK is not permitted within a FORM that is called using PERFORM ... ON COMMIT or PERFORM ... ON ROLLBACK.
      Runtime error: ROLLBACK_IN_PERFORM_ON_COMMIT
    • Cause: ROLLBACK WORK is not permitted within updates.
      Runtime error: ROLLBACK_IN_POSTING