SAP TRFC_RECEIVER_INFO Function Module for Gets Information About Any tRFC/qRFC Calls (Receiver Side)

Search SAP Function Modules

TRFC_RECEIVER_INFO is a standard trfc receiver info SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Gets Information About Any tRFC/qRFC Calls (Receiver Side) processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for trfc receiver info FM, simply by entering the name TRFC_RECEIVER_INFO into the relevant SAP transaction such as SE37 or SE38.

Function Group: ERFC
Program Name: SAPLERFC
Main Program: SAPLERFC
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TRFC_RECEIVER_INFO pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'TRFC_RECEIVER_INFO'"Gets Information About Any tRFC/qRFC Calls (Receiver Side)
 IMPORTING
   TRFCTYPE =  "T/O/I: tRFC/qRFC Outbound/qRFC Inbound
   S_USER =  "ABAP System, User Logon Name
   S_HOST =  "Sender Host Name
   S_PROG =  "Sender Program
   S_TCODE =  "Sender Transaction Code
   S_ID =  "Sender ID (hostname_sysid_sysnr)
   MODE =  "'L': Local Execution of Current qRFC LUW
   TID =  "Transaction ID on Receiver Side
   FNAME =  "Function Name
   FNUM =  "Function Number Within LUW
   FTOTAL =  "Number of Functions in LUW
   S_DATE =  "Sender Date
   S_TIME =  "Sender Time
   S_CLIENT =  "Sender Client

.

EXPORTING Parameters details for TRFC_RECEIVER_INFO

TRFCTYPE - T/O/I: tRFC/qRFC Outbound/qRFC Inbound

Data type: SY-INPUT
Optional: No
Call by Reference: No ( called with pass by value option)

S_USER - ABAP System, User Logon Name

Data type: SY-UNAME
Optional: No
Call by Reference: No ( called with pass by value option)

S_HOST - Sender Host Name

Data type: ARFCRSTATE-ARFCRHOST
Optional: No
Call by Reference: No ( called with pass by value option)

S_PROG - Sender Program

Data type: SY-CPROG
Optional: No
Call by Reference: No ( called with pass by value option)

S_TCODE - Sender Transaction Code

Data type: SY-TCODE
Optional: No
Call by Reference: No ( called with pass by value option)

S_ID - Sender ID (hostname_sysid_sysnr)

Data type: RFCDES-RFCDEST
Optional: No
Call by Reference: No ( called with pass by value option)

MODE - 'L': Local Execution of Current qRFC LUW

Data type: SY-INPUT
Optional: No
Call by Reference: No ( called with pass by value option)

TID - Transaction ID on Receiver Side

Data type: ARFCTID
Optional: No
Call by Reference: No ( called with pass by value option)

FNAME - Function Name

Data type: ARFCRSTATE-ARFCFNAM
Optional: No
Call by Reference: No ( called with pass by value option)

FNUM - Function Number Within LUW

Data type: ARFCRSTATE-ARFCLUWCNT
Optional: No
Call by Reference: No ( called with pass by value option)

FTOTAL - Number of Functions in LUW

Data type: ARFCRSTATE-ARFCLUWCNT
Optional: No
Call by Reference: No ( called with pass by value option)

S_DATE - Sender Date

Data type: SY-DATUM
Optional: No
Call by Reference: No ( called with pass by value option)

S_TIME - Sender Time

Data type: SY-UZEIT
Optional: No
Call by Reference: No ( called with pass by value option)

S_CLIENT - Sender Client

Data type: SY-MANDT
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for TRFC_RECEIVER_INFO Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM TRFC_RECEIVER_INFO

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects