Continue behind COMMIT WORK.

[Former Member]

Hi all,

I am facing problem with COMMIT WORK in my STANDARD SAP modification for executing ABAP Proxy. The problem is that the program doesnt continue after COMMIT WORK (messages, screens), but return to the initial screen.

Is there any way to commit data sent via proxy and then continue (with next proxy calling, processing screens etc)?

Thank you very much.

Frantisek Holas, CZ

[Former Member]

Hi Frantisek,

The issue with the COMMIT WORK is, it closes all the LUW's after the COMMIT,i'm not sure why the next screen not coming up, but if you try to save any data after this COMMIT WORK it does not work. So try to do the COMMIT after you everything is done(if possible).

Thanks,

Srini.

[former_member191735]

This is not standard behaviour. What are the statements after COMMIT WORK? Where is it being used? I mean, is it in the subroutine like update at commit?

> I am facing problem with COMMIT WORK in my STANDARD SAP modification for executing ABAP Proxy. The problem is that the program doesnt continue after COMMIT WORK (messages, screens), but return to the initial screen.

What is your program? Where did you change the code?

>

> Is there any way to commit data sent via proxy and then continue (with next proxy calling, processing screens etc)?

Why dont you do at end of all statements? You can also create a method or FM to commit outside the program which you need to call after each proxy

[Former Member]

Hi, thanks for your answer.

I am calling subroutine from my own report from standard transaction FPY1/DME Administration/Download File (include MFDTAFD1).

The subroutine at last calls subroutine that calls the proxy and at the end of this subroutine COMMIT WORK is called. No addition AT COMMIT isn´t used.

I don´t know if I understand is correctly, but if the COMMIT WORK closes actual LUW, it will reset the transaction FPY1 after commit. But this is wrong for me, because I need to stay in DME Administration called from FPY1.

Thanks for your reply.

Regards.

Frantisek Holas

[Former Member]

Hi,

I solved the problem myself.

http://help.sap.com/saphelp_nw70/helpdata/EN/41/7af4e3a79e11d1950f0000e82de14a/frameset.htm

http://help.sap.com/saphelp_nw70/helpdata/EN/41/7af4e3a79e11d1950f0000e82de14a/frameset.htm

The point of solve the problem is place certain statements following with commit into standalone report, that you can call with SUBMIT command, passing value from ABAP memory or via select-option, as explained in documentation for SUBMIT STATEMENT.

The trick of this solution is that calling new report via submit creates new SAP LUW, which can contain COMMIT WORK, that commit ONLY SAP LUW of the called report. When the report finishes and you return to the calling report/fm/trasaction/..., the SAP LUW of the calling rept/fm/transaction/... continue not affected by this COMMIT.

It helped me to solve my problem.