ABAP Runtime Errors

GENERAL_TRANSACTION_RFC SAP ABAP Runtime Error general transaction rfc







GENERAL_TRANSACTION_RFC is an ABAP runtime error which you may come across when using or developing within an SAP system. See below for the standard details explaining what it means and how you can avoid or fix this runtime error.

Short Dump Classification: & - Text Include (no Short Dump, only Text Module)

You can view further information about a runtme error by using transaction code ST22 which will show you this and all runtime erros that have happen in your SAP system.

Also check out the Comments section below to view or add related contributions and example screen shots.


GENERAL_TRANSACTION_RFC ABAP Runtime Error

Information on caller of Remote Function Call (RFC): System.............. <runtime parameter>
Installation number <runtime parameter>
Database Release..... <runtime parameter>
Kernel Release...... <runtime parameter>
Connection type..... <runtime parameter> (2=R/2, 3=ABAP-System, E=External, R=Reg.External) call type....... <runtime parameter>
Inbound TID..........<runtime parameter>
Inbound Queue Name...<runtime parameter>
Outbound TID.........<runtime parameter>
Outbound Queue Name..<runtime parameter>

Client................. <runtime parameter>
User.................. <runtime parameter>
Transaction......... <runtime parameter>
Call program............<runtime parameter>
Function module..... <runtime parameter>
Call destination..... <runtime parameter>
Source server...... <runtime parameter>
Source IP address.. <runtime parameter>

Additional information on RFC logon:
Trusted relationship.. <runtime parameter>
Logon return code.... <runtime parameter>
Trusted return code.. <runtime parameter>

Comment:
- In all releases prior to 4.0, no information is provided about the caller.
- The installation number is provided in caller Release 700 and higher. Additional information on RFC logon:
Trusted relationship.. <runtime parameter>
Logon return code.... <runtime parameter>
Trusted return code.. <runtime parameter>

Comment: In Releases < 4.0, information about the RFC caller might be missing or incomplete.