Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

CALL_FUNCTION_RECEIVE_ERROR

raghug
Active Contributor

‎11-17-2016 5:12 PM - edited ‎01-21-2024 9:51 PM

0 Kudos

This is in reference to the error detailed in the previous CALL_FUNCTION_RECEIVE_ERROR question from the archive. I have the exact same issue, but I cannot find the any information about the Note 2101119 that is mentioned by 28f4b37a40894f18a22abc696b8154f4. The solution does appear to make sense, but I can't find the note.

Does anyone have any other note number that I can look at and apply?

2 REPLIES 2

Sandra_Rossi
Active Contributor

‎02-09-2017 7:09 PM

0 Kudos

Maybe the note was deleted or is internal (to be asked to SAP support). Lukasz said "Problem comes from inconsistency in function module SADT_REST_RFC_ENDPOINT.
It should be delivered with "BasXML supported" checkbox on, but wasn't." I guess you just have to check this attribute of the function module. Otherwise, ask SAP support.

raghug
Active Contributor

‎02-10-2017 2:04 PM

Yes, the BasXML was not checked and I was trying to apply the note instead of opening a support message. Some other patches - which did not change the BasXML - however did "fix" the issue, so I didn't end up opening the support message either. I am not sure what drives the behavior, but as a consultant I have not had much luck driving my clients to open support messages - so, usually I do anything that I can do to avoid getting to that point 🙂