Hello,
I have a RFC called from the WEB.
I have 2 steps in the RFC.
.1 CALL a BAPI (no commit inside the BAPI).
.2 Update a ZTABLE.
When I execute the RFC, the BAPI update nothing.
This is correct because the 'BAPI_TRANSACTION_COMMIT' is not executed.
But the ZTABLE is UPDATED and I don't want to update it.
<b>How I can manage the commit of the table?</b>
Thank you very much
Syme
Hi,
You can call your rfc enabled function module and the function module 'BAPI_TRANSACTION_COMMIT' in the same LUW.You can do this calling your FMs using 'in background task' addition of the Call Function(if it is an ABAP environment)
Hello,
Like I said, the RFC is call from the WEB by a JAVA program.
We want to give to the JAVA program the control of the COMMIT.
The JAVA program call the RFC:
inside the RFC we have:
in step 1, a call of a BAPI_CHANGE_anything*
in step 2, an update of a Ztable.
The JAVA program in the next steps valid the return code.
Call others RFCs, and at the end, do the BAPI_TRANSACTION_COMMIT if everything is ok.
But if an error occurs during this process, we don't do the BAPI_TRANSACTION_COMMIT.
The problem is when we don't do the COMMIT, the Ztable is update anyway.
We don't want to update this Ztable.
The only way I see, is to code a BAPI for every modifications we have to do in the Database.
Add a comment