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.
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:
2. Select ‘Other Function module’ from the ‘Function modules’ menu:
3. Select ‘BAPI_TRANSACTION_COMMIT’ (or any other BAPI/RFC) to be executed next:
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!!!