SAP RD_RECEIVERS_EXIST Function Module for Determine Whether Potential Receivers Exist

Search SAP Function Modules

RD_RECEIVERS_EXIST is a standard rd receivers exist SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Determine Whether Potential Receivers Exist 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 rd receivers exist FM, simply by entering the name RD_RECEIVERS_EXIST into the relevant SAP transaction such as SE37 or SE38.

Function Group: ROUTING_LOCAL_RUNTIME
Program Name: SAPLROUTING_LOCAL_RUNTIME
Main Program: SAPLROUTING_LOCAL_RUNTIME
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RD_RECEIVERS_EXIST 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 'RD_RECEIVERS_EXIST'"Determine Whether Potential Receivers Exist
  EXPORTING
   SENDER =  "
*  RECEIVER =  "
   INTERFACE =  "Outbound Interface
*  PAYLOAD =  "

 IMPORTING
   ATTACHMENT_NEEDED =  "Boolean Value ('X'=TRUE, ' '=FALSE)
   PAYLOAD_NEEDED =  "Boolean Value ('X'=TRUE, ' '=FALSE)
   RECEIVERS_EXIST =  "Boolean Value ('X'=TRUE, ' '=FALSE)

EXCEPTIONS
   RD_SRVC = 1 

.

IMPORTING Parameters details for RD_RECEIVERS_EXIST

SENDER -

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

RECEIVER -

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

INTERFACE - Outbound Interface

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

PAYLOAD -

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

EXPORTING Parameters details for RD_RECEIVERS_EXIST

ATTACHMENT_NEEDED - Boolean Value ('X'=TRUE, ' '=FALSE)

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

PAYLOAD_NEEDED - Boolean Value ('X'=TRUE, ' '=FALSE)

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

RECEIVERS_EXIST - Boolean Value ('X'=TRUE, ' '=FALSE)

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

EXCEPTIONS details

RD_SRVC -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RD_RECEIVERS_EXIST 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 RD_RECEIVERS_EXIST

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