Separate Commit Workaround?

[Former Member]

Hi

I am facing the need to call a BAPI which requires a separate call to the transaction commit, as we all now now this is not feasible with XI 3.0 and the RFC adapter.

The recommended solution to build a wrapper is fine, except that right now we are days from going live and the ABAP programmers are not going to give us any time, so is there an alternative that doesn't involve any aditional coding????

Maybe a PROXY server generation? Or a two-step invocation of the bapi and commit method using the BPM to relate them? a new RFC adapter version with a "perform commit" option??? (Hint )

Thanks

-Sam.

[Former Member]

Hi,

Sorry the only way is to call BAPI_TRANSACTION_COMMIT in your wrapper function module.

Surely this would have be discovered during testing not days before go live ??????

Kind regards

Colin