2009 Jan 13 8:59 AM
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
2009 Jan 13 9:32 AM
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.
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.
2009 Jan 13 9:27 AM
2009 Jan 13 9:32 AM
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.
2009 Jan 13 12:02 PM
| User | Count |
|---|---|
| 6 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |