Ansicht
Dokumentation

ABENRFC_NO_DUMP - RFC NO DUMP

TXBHW - Original Tax Base Amount in Local Currency   General Data in Customer Master  
This documentation is copyright by SAP AG.

No ABAP Short Dump in Case of Failed RFC Logon

Further information about the reason for the logon problem is also missing.

Cause and Conditions

ABAP short dumps are produced when an RFC logon fails only if the profile parameter "rfc/signon_error_log" is contained in the profile file of the corresponding :

• rfc/signon_error_log = 1

Each time there is a logon error, the short dump "CALL_FUNCTION_SIGNON_REJECTED" is displayed. The content of this dump can be analyzed using the short dump analysis transaction (ST22).

• rfc/signon_error_log = 2

In addition to the ABAP short dump "CALL_FUNCTION_SIGNON_REJECTED", further information about the cause of the problem is logged in the developer trace files (the dev_w* files).
Each RFC logon attempt is logged in the developer trace files, whether or not the logon was successful. Make sure that this profile value is only used to analyze the RFC logons and then reset. Otherwise the trace files would become very large.

Solution

Add the profile parameter rfc/signon_error_log for the corresponding with the corresponding value assignment (1 or 2, see above) to the profile file. Start the server again with this profile.

To reset the profile parameter, either remove the profile parameter from the profile file or set the profile value to zero (rfc/signon_error_log = 0). Then start the server again with this profile.

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 1913 Date: 20240419 Time: 232518     sap01-206 ( 23 ms )