topic Re: Do I have to issue commit statement after modify dbtab? in Application Development and Automation Discussions

Do I have to issue commit statement after modify dbtab?

Former Member — Mon, 25 Jan 2016 17:02:47 GMT

Hello to all,

Is it necessary for me too issue an explicit commit statement after using modify dbtab from wa, or this is done implicitly?

Best Regards to all.

Re: Do I have to issue commit statement after modify dbtab?

jhilden — Mon, 25 Jan 2016 17:29:23 GMT

You do not *have* to issue an explicit COMMIT afterwards to successfully complete the db update (the end of the program will be the end of the logical unit of work), but there may be reasons why you may want to:

The COMMIT executes a database commit and thus closes a logical processing unit or Logical Unit of Work ( LUW ).

This means that

all database changes are made irrevocable and cannot
be reversed with ROLLBACK WORK and
all database locks are
released.

Re: Do I have to issue commit statement after modify dbtab?

ibrahim_u — Tue, 26 Jan 2016 13:03:08 GMT

You dont have to use COMMIT statement. SAP LUW concept responsible for it.

SAP LUW Concept

Database Logical Unit of Work (LUW) - ABAP Programming (BC-ABA) - SAP Library

But you may want to use the data that you insert or modify in DB table before the LUW ends. In this case, yes you can use COMMIT.

Re: Do I have to issue commit statement after modify dbtab?

RaymondGiuseppi — Tue, 26 Jan 2016 14:04:08 GMT

No need for COMMIT/ROLLBACK WORK with simple open-sql statement, but you can use those, just read their documentation, COMMIT WORK, they execute more than a database commit. To insure success (or force rollback) you may consider using FM DB_COMMIT (resp. DB_ROLLBACK) to trigger a database commit. Or you can wait for an Implicit Database Commit as triggered by any dialog step.

Regards,

Raymond.