I have a very simple scenario which is implemented in WDJ 7.2 CE ARFC1 where the transaction BAPI_PRODORDERCONF_CREATE_TT is executed and committed right after by BAPI_TRANSACTION_COMMIT. Everything works fine and I have even checked in SE37 by a remote breakpoint that the execution of the BAPI_TRANSACTION_COMMIT is triggered and COMMIT WORK line is executed to commit the results of the previous confirmation. Everything is perfect.
However the exact the same code ported to ARFC2 fails to commit the confirmation.
BAPI_PRODORDERCONF_CREATE_TT is executed successfully and returns the confirmation is OK but the BAPI_TRANSACTION_COMMIT call seems to be in another session/scope and COMMIT WORK (ABAP) line is simply bypassed, in the same as you would just call this BAPI only from WDJ.
The only explanation for this I have is that the transactions are running in decoupled JCo connections or scopes,
but I can't imagine that this the implementation of ARFC2 since COMMITS and ROLLBACKS would become useless.
Is there a hint or probably a setting I missed to accomplish that allow me to commit a transaction chain from WDJ?
This currently causes a lot of head scratching here 😉...
Any help would be great.