SAP RM_RC1_RT_CHECK_REF Function Module for Check Reference to Original Transaction
RM_RC1_RT_CHECK_REF is a standard rm rc1 rt check ref SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check Reference to Original Transaction 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 rm rc1 rt check ref FM, simply by entering the name RM_RC1_RT_CHECK_REF into the relevant SAP transaction such as SE37 or SE38.
Function Group: RMRC1
Program Name: SAPLRMRC1
Main Program: SAPLRMRC1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RM_RC1_RT_CHECK_REF 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 'RM_RC1_RT_CHECK_REF'"Check Reference to Original Transaction.
EXPORTING
I_OBJNR = "Pointer to Original Transaction
* I_RIDXRT = "Internal Number for Extended Risk Object
IMPORTING
E_FLG_REF = "Reference Available ('X') or Not Available (' ')
E_RIDEXT_REF = "External Number for Risk Object
IMPORTING Parameters details for RM_RC1_RT_CHECK_REF
I_OBJNR - Pointer to Original Transaction
Data type: JBPOBJNROptional: No
Call by Reference: Yes
I_RIDXRT - Internal Number for Extended Risk Object
Data type: JBRIDXRTOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RM_RC1_RT_CHECK_REF
E_FLG_REF - Reference Available ('X') or Not Available (SPACE)
Data type: XFELDOptional: No
Call by Reference: Yes
E_RIDEXT_REF - External Number for Risk Object
Data type: JBRIDEXTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for RM_RC1_RT_CHECK_REF 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.| DATA: | ||||
| lv_i_objnr | TYPE JBPOBJNR, " | |||
| lv_e_flg_ref | TYPE XFELD, " | |||
| lv_i_ridxrt | TYPE JBRIDXRT, " | |||
| lv_e_ridext_ref | TYPE JBRIDEXT. " |
|   CALL FUNCTION 'RM_RC1_RT_CHECK_REF' "Check Reference to Original Transaction |
| EXPORTING | ||
| I_OBJNR | = lv_i_objnr | |
| I_RIDXRT | = lv_i_ridxrt | |
| IMPORTING | ||
| E_FLG_REF | = lv_e_flg_ref | |
| E_RIDEXT_REF | = lv_e_ridext_ref | |
| . " RM_RC1_RT_CHECK_REF | ||
ABAP code using 7.40 inline data declarations to call FM RM_RC1_RT_CHECK_REF
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