Skip to Content

Introduction

Who would have thought that I’d ever blog about an ABAP feature… well, not me! 😉

Anyway, during this year’s SDN Community Day at TechEd’08 in Berlin I witnessed a very interesting podium discussion about ‘ABAP, the future, the downport and the tools’ (check out Craig Cmehil’s blog ABAP at Community Day Berlin).

In the Q&A part of the session, SDN Mentor Gregor Wolf asked the question if transaction SE37 would support nested structures and special datatypes as typically required when trying to test function modules in SAP CRM (check out his blog SAP Community Day: ABAP rockt).

I spoke to him after the session and he then he revealed a little-known secret about transaction SE37: the possibility to chain multiple RFCs/BAPIs within one transactional bracket.

 For more details about this functionality please refer to:

Now, that may be one of the features that they teach in ABAP 101 and even though I had my good share of ABAP development in the past I’d not call myself an expert. Yet I personally know a lot of seasoned ABAP developers that were not aware of it and who used to write small test reports to execute a ‘BAPI_TRANSACTION_COMMIT‘ after calling a BAPI. These days are now officially gone (I hope)… so, without further ado…

How-to chain multiple RFCs/BAPIs in transaction SE37

 

  • 1. Execute the particular BAPI:

    image


  • 2. Select ‘Other Function module’ from the ‘Function modules’ menu:

    image


  • 3. Select ‘BAPI_TRANSACTION_COMMIT’ (or any other BAPI/RFC) to be executed next:

    image

Outro

Those of you who yawn now and say that they have known this for a long, long time – shame on you for not spreading the word! /JK 😉 Well, there may be developers out there (like me) who did not know about this time-saving feature and who appreciate it… if I just reach one of them -> mission accomplished!

PS: Very special thanks to Gregor for taking his ‘job’ as SDN Mentor so seriously… keep up the good work!!!

To report this post you need to login first.

14 Comments

You must be Logged on to comment or reply to a post.

        1. Matthias Steiner Post author
          Thanks Peter! Before writing that post I tried to find that note, but did not succeed due to the big result list returned when searching for these terms.

          Like I said, from my personal experience this knowledge may not be known to all the ABAP developers, hence I thought I just quickly summarize it 😉

          (0) 
          1. Gregor Wolf
            Hi Martin,

            thanks for writing this Blog. I think it’s better to have more keywords matching for that kind of problem. Perhaps you can include the link to the OSS Message and the SDN Wiki entry on top of your Blog too.

            Best regards
            Gregor

            (0) 
          2. Peter Inotai
            Hi Matthias,
            I think it was a good idea to blog about this feature. It makes sense to add all the references to your blog. It’s cool now I believe.
            Cheers,
            Peter
            (0) 
  1. Thorsten Franz
    Hi,
    it works with remote calls, too. I sometimes use it when I have locked myself out of one SAP system but can still logon to another one which has a system user RFC connection to the target system: BAPI_USER_CHANGE and BAPI_TRANSACTION_COMMIT, called from transaction SE37, make a wonderful backdoor.
    Cheers,
    Thorsten
    (0) 
  2. Matthias Steiner Post author
    Hi Thorsten,

    thanks for the info!

    Despite the fact that so far everybody that replied apparently knew about the feature, I really enjoy how this post develops. 😉

    Thankf for all the comments so far… keep it coming!!!

    (0) 
    1. Thorsten Franz
      *Grin* Sometimes it turns out oneself is the only person unaware of a “little-known function” or suffering from a “wide-spread misunderstanding”. 😉 But I think in this case it’s very good that you blogged about it, because I have frequently heard that colleagues are unaware of this possibility.
      Cheers,
      Thorsten
      (0) 
      1. Matthias Steiner Post author
        I know excatly what you mean! But honestly, if I would have been the only one unaware of this fature I would not have dared to blog about it, since I spend most of my time on the Java side of things these days.

        It was my respected colleagues who are very seasoned ABAP developers that ranted about the lack of automatic commits in SE37 just the other day, that made me think it may be a good idea…

        😉

        (0) 

Leave a Reply