Implicit commit in ABAP Web Dynpro?

[Former Member]

I wonder if ABAP Web Dynpro is executing an implicit commit. I have two buttons on the same view. The first one inserts an entry into a table, the second one executes a "rollback work" (and to be sure calls function "DB_ROLLBACK").

However, after first pressing the insert-button and secondly the rollback-button, the rollback had no effect, i.e. one dataset has been permanently inserted into the database table.

Is it possible that until the view is ready for new processing (i.e. finished any initializations) an implicit commit is executed by SAP?

I have not used any commit nor do I use debugger mode.

The same behavior happens when I split the insert and rollback things into two views. In the second view the rollback is possible before the inbound plug is processed to the end, but afterwards (e.g. when handling a button click by an assigned method) not.

[former_member215843]

This behaviour seems strange to me. An implicit commit is executed, when the session is closed (e.g. when you close the browser), but not inbetween.

Regina

[Former Member]

Have you verified your statement or is it just a believe?

FYI: With "normal" ABAP Dynpro there is an implicit commit after leaving a dynpro (as far as I know, and I think I'm right, because there is a problem with consecutive direct inputs when one fails and a complete rollback is not possible).

[thomas_szcs]

Hi Klaus,

I was wondering if you could do a ST05 trace? It will reveal the place where the commit happens. It will be quite interesting to see if it happens inside of the WD runtime. If yes, I would consider it a bug.

Best regards,

Thomas