Solution : https://service.sap.com/sap/support/notes/171805 (SAP Service marketplace login required)
Summary :
This SAP Note addresses errors related to Remote Function Call (RFC) such as CALL_FUNCTION_SIGNON_REJECTED, CALL_FUNCTION_SYSCALL_ONLY, and CALL_FUNCTION_SIGNON_INCOMPL, which appear within the system log and ABAP runtime error environment as a result of RFC calls with incorrect login data. The note outlines steps to track the source of error through data such as IP address, host name, R/3 instance, function module, logon details, and calling program name. Guidance includes using system dump analysis via ST22 and activating R/3 traces to gather detailed calling program data efficiently. It further recommends using SAP Note 91980 if CALL_FUNCTION_SIGNON_REJECTED errors are not logged as ABAP runtime errors.
Key words :
rfc trace files dev_rfc<workprozeß-id>, abap runtime error environment entries result, goto -> trace -> gateway -> increase level, goto -> trace -> gateway -> reduce level, goto -> trace -> gateway -> reset file, rfc calling system causing call_function_signon_rejected, rfc calling program causing call_function_syscall_only, process -> trace -> active components, process -> trace -> reset files, abap runtime error environment
Related Notes :
| 774406 | |
| 523406 | |
| 495911 | |
| 389810 | |
| 320991 | |
| 91980 | Missing output of RFC short dump after login error |
| 51367 | RFC logon under different user or client |