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

BAPI_TRANSACTION_COMMIT with Web AS/SOAP Interface

At first glance, it does not appear possible to issue two RFC calls wrapped in a transaction/session using the WebAS SOAP interface. This would essentially make it impossible to use standard BAPIs/RFC's that "write" data and would seem to require writing "wrapper" custom RFC's that call the original RFC and commit it. Naturally, that would seem unnecessary and inconvenient. Is there a session-based protocol for WebAS using cookies and URI requests?

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Posted on Feb 08, 2005 at 11:40 AM

    In 640 we have the WebService Definitions (instead of the generic SOAP interface in 620). When you generate one of these definitions, you have the ability to activate Session-Oriented Communication for Stateful web Service Communication.

    However in 620 I have never tried to do the same thing using the generic SOAP interface. I have always done as you described and wrote wrapper classes around multiple BAPI calls. To tell you the truth, I rather like the measure of control that this provided me (considering another group(s) within my company will be calling these webservices).

    Add a comment
    10|10000 characters needed characters exceeded

    • With 640 you should be in real good shape. For details check out the following forum and weblog listings. I have screen shots of where you can set the stateful flag for exposed webservices.

      WEB SERVICES

      /people/thomas.jung3/blog/2004/11/17/bsp-a-developers-journal-part-xiv--consuming-webservices-with-abap

      /people/thomas.jung3/blog/2004/11/15/bsp-150-a-developer146s-journal-part-xiii-developing-abap-webservices

      In my weblog where I am consuming an external webservice, this is stateful. Really the generated proxy class takes care of all the details for you. Have a look and let me know if you have any questions.

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.