SAP RM_RC_CHECK Function Module for RM: CHECK der FDÜ erweiterter Risikoträger
RM_RC_CHECK is a standard rm rc check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for RM: CHECK der FDÜ erweiterter Risikoträger 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 rc check FM, simply by entering the name RM_RC_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: RMY2
Program Name: SAPLRMY2
Main Program: SAPLRMY2
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RM_RC_CHECK 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_RC_CHECK'"RM: CHECK der FDÜ erweiterter Risikoträger.
EXPORTING
* CHECK_LEVEL = '3' "Verprobungslevel
TABLES
IT_JBIPXSFGDT = "übergebene xSFGDTs
ERROR_ITAB = "Fehler-Tabelle
EXCEPTIONS
ERROR_FOUND = 1
IMPORTING Parameters details for RM_RC_CHECK
CHECK_LEVEL - Verprobungslevel
Data type: JBISTRU-CHECKDefault: '3'
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RM_RC_CHECK
IT_JBIPXSFGDT - übergebene xSFGDTs
Data type: JBIPXSFGDTOptional: No
Call by Reference: No ( called with pass by value option)
ERROR_ITAB - Fehler-Tabelle
Data type: SPROT_XOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_FOUND - Fehler-Flag
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RM_RC_CHECK 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_check_level | TYPE JBISTRU-CHECK, " '3' | |||
| lv_error_found | TYPE JBISTRU, " | |||
| lt_it_jbipxsfgdt | TYPE STANDARD TABLE OF JBIPXSFGDT, " | |||
| lt_error_itab | TYPE STANDARD TABLE OF SPROT_X. " |
|   CALL FUNCTION 'RM_RC_CHECK' "RM: CHECK der FDÜ erweiterter Risikoträger |
| EXPORTING | ||
| CHECK_LEVEL | = lv_check_level | |
| TABLES | ||
| IT_JBIPXSFGDT | = lt_it_jbipxsfgdt | |
| ERROR_ITAB | = lt_error_itab | |
| EXCEPTIONS | ||
| ERROR_FOUND = 1 | ||
| . " RM_RC_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM RM_RC_CHECK
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.| "SELECT single CHECK FROM JBISTRU INTO @DATA(ld_check_level). | ||||
| DATA(ld_check_level) | = '3'. | |||
Search for further information about these or an SAP related objects