Skip to Content
author's profile photo
Former Member

WebAS SOAP Runtime - Transaction Commit Issue

We're calling RFC's via the Web AS SOAP Runtime, and it works perfectly when calling "atomic" RFC's that only require a single RFC call. There are a few RFC's (such as creating a maintenance notification) that need to be followed with a BAPI_TRANSACTION_COMMIT. Unfortunately, these two RFC's need to be called within a single "Transaction"/session.

With Business Connector, there is a way to maintain state and do commit/rollback functionality using cookies between each call and a URL call to do the commit or rollback. With Web AS, there does not appear to be any similar functionality (e.g. two or more SOAP calls wrapped in the same "transaction", with a commit or rollback).

Is there any solution using Web AS (without writing an ABAP wrapper for the two RFC's and remote enabling the new RFC?).

Many thanks!

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

3 Answers

  • author's profile photo
    Former Member
    Posted on Feb 03, 2005 at 02:24 PM

    Also an important note: This application is not using JCO or the .NET connector. It is an application that is issuing the appropriate HTTP calls directly. We cannot find any documentation on the HTTP (wire level) syntax and format for the Web AS/ABAP session protocol.

    Add comment
    10|10000 characters needed characters exceeded

  • author's profile photo
    Former Member
    Posted on Feb 08, 2005 at 05:36 PM

    I've run this scenario by some people and this is the advice they provided. What you should do is expose BAPI_TRANSACTION_COMMIT and BAPI_TRANSACTION_ROLLBACK using the WS Creation Wizard. You do this by choosing the appropriate function group as the endpoint and manually adding these with "other functions" when creating the VI. Set the Web service communication to "stateful" which will use HTTP cookies.

    You can find documentation on the WS Creation Wizard here http://help.sap.com/saphelp_nw04/helpdata/en/e9/ae1b9a5d2cef4ea4b579f19d902871/frameset.htm

    Hope that helps.

    Add comment
    10|10000 characters needed characters exceeded

    • You might find this weblog interesting.

      /people/thomas.jung3/blog/2005/02/14/webservices-a-real-world-implementation-experience

      Part of the reason we build our webservices the way we did was because of this very problem you describe. You can see how building wrappers around the BAPIs did end up paying off - with additional flexibility we ended up needing.

  • Posted on Feb 09, 2005 at 07:37 AM

    It appears that this forum topic is very closely related (or exactly the same) to the following. For future searches, it will be useful to reference both:

    BAPI_TRANSACTION_COMMIT with Web AS/SOAP Interface

    Add comment
    10|10000 characters needed characters exceeded