RFC call ended with "Communication Failure" exception (Function call failed; could not find the function

[#1]

Hi All,

I am getting error while executing oDATA service from SAP Netweaver Gateway

Error details:

RFC call ended with "Communication Failure" exception (Function call failed; could not find the function

I am using SAP NG 740

Project is created in Gateway system using SEGW having Map to Datasource option used.

in SPRO manage alias, I had seleted Local App option. Screen attached

I had tried all troubleshooting like delete and add service and alias in "/IWFND_MAINT_SERVICE".

but still getting same error for all service.

Kindly advise.

Regards

Vivek

[former_member184867]

Hi,

RFC communication error can occur in various levels

      1.     When Gateway HUB connects to BEP system

      2.     When BEP connects to ERP System

      3.     When BEP connects to Other Data source such as BW system

I think you need to find where the the RFC communication is failing. For that, the best option would be to check the stack from error log transaction. This will help you to identify the reason of the error.

Regards,

Atanu

[Former Member]

Hi Vivek,

Apart from check points suggested - I believe for RFC failure you can find dump in ST22 and also check for authorization in SU53 or try to connect through defined RFC in SM59.

Regards,

Rajesh

[vivek_gaurav1]

Hi All,

     After debugging I found that GetRFCConnection Method is not able to return RFC Connection.

     It is returning blank.

     Actually, In same system we had integrated HANA with gateway, for that we had implemented one BADI Method called GetDBConnection. which is part of same Class.

So, kindly advise can we integrate same gateway with HANA or we have to keep Gateway for HANA seperate.

Regards

Vivek

[Former Member]

Hi Vivek,

I am also facing the same issue.

The OData connection with backend ECC was working fine initially.

When I tried to integrate HANA with gateway with GetDBConnection method,  the ECC OData connection is not working now.

Please let me know if you have any workaround.

Thanks!

Praveen.

[vivek_gaurav1]

Hi Praveen,

                    Since this method is internally used by Gateway service, also. it does not work.

               You need to do coding in such a way that it will not effect ECC oData connection.

               Ask ABAP guy to Debug the method and make both separate.We had rectified this issue by the help of Changing Method.

Regards

vivek

[AshwinDutt]

Hello Vivek,

Service builder would have also generated code for RFC Exception handling to catch exceptions raised when communication fails between your GW and BE for some reasons.

Handling is done for 1. System Failure 2. Communication Failure & 3. Business Failure;

Put a BP in your DPC or DP_EXT class where exception code is written to check what exactly is has caused communication failure.

Check if that RFC is existing in that destination or not.

For your reference  : Code would be something like this. Put BP here and check the problem.

* Error and exception handling

*-------------------------------------------------------------

IF lv_subrc <> 0.

* Execute the RFC exception handling process

   me->/iwbep/if_sb_dpc_comm_services~rfc_exception_handling(

     EXPORTING

       iv_subrc            = lv_subrc

       iv_exp_message_text = lv_exc_msg ).

ENDIF.

Go inside this method and check to get info on what has to be done to resolve issue.

Check carefully what has gone wrong and fix it accordingly.

No need of adding service & deleting as problem is not because of that.

Regards,

Ashwin