topic Avoid 'commit-work'; LUW-Logic in Application Development and Automation Discussions

Avoid 'commit-work'; LUW-Logic

Former Member — Tue, 13 Jan 2009 08:59:27 GMT

Hello,

we have a problem in our luw! Although we do not use an explicit 'commit work' in one of our dialog-programs, a 'rollback' does not work correctly. I have tried to trace the sql-units while execution the program and find out that there are a whole of commit works in the trace-protocoll.

It looks like:

09:44:21.423 105 SAPLSEUJ PROGDIR EXECSTM 119 1 1 0 R/3 1 UPDATE SET "RSTAT" = 'S' , "UNAM" =

09:44:21.423 944 SAPLSYDB EXECSTA 0 0 R/3 1 COMMIT WORK

09:44:21.426 267 SAPLSYDB EXECSTA 0 0 R/3 1 COMMIT WORK

Is there any chance to avoid such implicit commit-works?

Greetings,

Marcel

Re: Avoid 'commit-work'; LUW-Logic

Former Member — Tue, 13 Jan 2009 09:27:29 GMT

nobody any ideas?

Re: Avoid 'commit-work'; LUW-Logic

Former Member — Tue, 13 Jan 2009 09:32:30 GMT

Some ABAP keywords have implicit commits. nothing can be done about them. For statements which requires explicit commits we can use the ROLLBACK WORK statement.

Re: Avoid 'commit-work'; LUW-Logic

Former Member — Tue, 13 Jan 2009 12:02:55 GMT

OK, thanks a lot!