Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 8122

Re: RFC call ended with "Communication Failure" exception in Gateway Service testing?

$
0
0

Hi Ramana,

 

I have maintained Backend ECC RFC Destination against Backend ECC System alias. but when we are testing the service, system automatically taking NONE as RFC destination because of "For Local App" flag was checked. Based this flag, In standard code itself it's taking NONE as RFC destination even though ECC RFC destination maintained against system alias.

 

Please see the standard code in class " /IWFND/CL_DESTIN_FINDER" method "GET_SYSTEM_ALIAS_INFO".

 

here SAP hard coded if "For Local App" is checked then RFC destination as NONE.

 

The method and the class you are referring is related to IWFND component. I checked this code, this code is used while finding the destination for the IWBEP classes. They have hard coded this destination to NONE because when you have checked the 'For Local App' flag which states that the IWBEP classes are at the same system. Thus RFC destination is not required.

Please don't get confused with the above RFC destination. This RFC destination is pointing to the system which has IWBEP classes and not to the system where your FM is.

 

To check the RFC destination which is pointing towards the ECC system for calling the FM, please put an external breakpoint in the GET_ENTITYSET method like below:

debug.PNG

 

go to LO_DP_FACADE :

 

dest finder.PNG

 

Go to MO_DEST.........

 

alias.PNG

 

Here your system alias should be ECC in your case. I still doubt that you have mapped this to LOCAL. Please paste your screenshots. I still need the screenshot of the previous post which shows alias.

 

Regards,

Ekansh


Viewing all articles
Browse latest Browse all 8122

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>