Hi Jefersen,
This error is raised by external non-ABAP system. The tRFC implementation in the external program will need to be checked.
The destination in question is a TCP/IP-type RFC destination which points to an external (registered) server program. This error occurs when the function "IDOC_INBOUND_ASYNCHRONOUS" is called in a program which does not contain this function. A typical scenario is when somebody registers the program, i.e. rfcexec to the gateway with the program ID which is in the RFC destination. Please note that rfcexec is only a sample program from the RFC SDK package. It does not contain the function "IDOC_INBOUND_ASYNCHRONOUS". If in your case the issue is caused by a similar scenario with a wrong registration, you have to do the following:
1) De-register the wrong external program (by killing the respective process on the external machine)
2) Then you have to register the correct program (which contains the function "IDOC_INBOUND_ASYNCHRONOUS") on the ABAP gateway
Regards,
David