Skip to Content

Up to now, there was no officially released or documented possibility to create a fully fledged dynamic RFC destination that can be entered behind CALL FUNCTION DESTINATION.

If you crawl the Web for “dynamic RFC destination”, you find one or the other hint how to achieve that, but the general recommendation is: Don’t do that!

In order to direct that uncontrolled growth into the right channels, a new class is delivered with ABAP 7.50:

DATA(dest) =

  cl_dynamic_destination=>create_rfc_destination(

    logon_client   = …

    logon_user     = …

    logon_language = …

    sid            = …

    server         = …

    group          = …

    … ).

  

CALL FUNCTION ‘DEMO_RFM_PARAMETERS’

      DESTINATION dest

      EXPORTING …

From ABAP 7.50 on, CL_DYNAMIC_DESTINATION is the officially released and documented possibility to create a dynamic RFC destination and the only one to be used if SM59 is not sufficient.

To report this post you need to login first.

6 Comments

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

      1. Prasenjit Singh Bist

        A general question is there any way that in future we see a ABAP runtime on HCP allowing ABAP on public s4/hana clouds. also any work on classical screens to allow for screen personas like and in fiori style outputs or it’s going to be ui5 and abap mix in future?

        (0) 

Leave a Reply