Skip to Content

Remote function call from Gateway service operation.


We have developed a Gateway service completely using SEGW (Service builder). We are trying to call a RFC in a remote Backend system to get data while the service is executing from the Gateway system (IW_BEP installed in Gateway hub).

While doing the mapping (using mapping tool of SEGW) we had mentioned the Data source to be remote and gave the RFC destination of the remote system (this is also visible in the ‘service implementation’ details of SEGW).

However during the runtime we get an error saying RFC could not be found, which means that the RFC is been searched in the local Gateway system where it does not exist. We even did a runtime debugging of the Data Provider classes’ Get Entityset operation and found that the destination for remote call (indicated with lv_destination in the auto generated code) does not return anything and hence the RFC is been executed in the local system where it does not exist.

Is there any special configuration/BADI implementation, to be done to call a RFC in a remote system other than the one done while mapping in SEGW.

Thanks a lot for your attention and help.



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    May 20, 2013 at 01:14 PM

    Hi Avishek,

    Did you add the system-alias for the service that you registered,

    if you had added then check the sytem-alias configuration,

    it has two check boxes ,

      1.Local GW

      2.Local APP

    if the RFC is in remote system then you have check the 1st check box.

    Best Regards,


    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      I have the same problem, I have marked Local App. Changing the settings and always get the same error.

      <error xmlns="">

      <code> /IWFND/CM_BEC/026 </code>

      <message xml:lang="en">

      RFC Error: Function module "/IWBEP/FM_MGW_READ_ENTITYSET" not found.



      <transactionid> E3CE5AE406E0F115A74C000C29248DA1 </transactionid>