Skip to Content
1
Former Member
Mar 29, 2017 at 01:06 AM

Fiori/Odata error - RFC call ended with \"Communication Failure\" exception

3897 Views Last edit May 27, 2020 at 08:38 AM 4 rev

Hello,

I hope you are well.

My Fiori applications in SAP WebIDE were working fine a short while ago. But after trying to maintain a new Odata service, all of my Fiori applications now have a similar error. An example error is "RFC call ended with \"Communication Failure\" exception (The function call of ZHCT_CS_GET failed; a field may have been assigned to the parameter IV_CS whose type is not compatible with this parameter)".

I have tested all of my Function modules in question, and they all seem to be working properly. My Odata services seem to be working when testing with the gateway client as well.

My Fiori apps were correctly retrieving and displaying the data using my Odata services a few days ago. I fear that I may have broken something by trying to maintain/delete some services or ICF nodes.

Please see screenshots and full error attached/below:

{

"message": "HTTP request failed",

"headers": {

"Content-Type": "application/xml",

"Content-Length": "1198",

"DataServiceVersion": "1.0"

},

"statusCode": "500",

"statusText": "Internal Server Error",

"responseText": " /IWBEP/MC_SB_DPC_USR/004 http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"> /IWBEP/MC_SB_DPC_USR/004 xml:lang=\"en\">RFC call ended with \"Communication Failure\" exception (The function call of ZHCT_CS_GET failed; a field may have been assigned to the parameter IV_CS whose type is not compatible with this parameter). FB1CD7D0141111E7A0C2000014C1D2F3 20170329000558.3379710 Run transaction /IWFND/ERROR_LOG on SAP NW Gateway hub system and search for entries with the timestamp above for more details See SAP Note 1797736 for error analysis ( https://service.sap.com/sap/support/notes/1797736) /IWBEP/CX_SD_GEN_DPC_TECH RFC call ended with \"Communication Failure\" exception (The function call of ZHCT_CS_GET failed; a field may have been assigned to the parameter IV_CS whose type is not compatible with this parameter) error "

}

Attachments

error.png (18.5 kB)
error.png (18.5 kB)
error.png (35.3 kB)
error2.png (66.9 kB)
error3.png (219.5 kB)
error4.png (161.1 kB)
error5.png (23.0 kB)