Skip to Content
author's profile photo Former Member
Former Member

Separate Commit Workaround?

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.

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Dec 07, 2004 at 09:37 AM

    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 😊

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.