SAP RM_DERI_ENTRY_CHECK Function Module for RM: prüft Eintrag Ableitungsregel auf Konsistenz (Klammerung)
RM_DERI_ENTRY_CHECK is a standard rm deri entry 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: prüft Eintrag Ableitungsregel auf Konsistenz (Klammerung) 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 deri entry check FM, simply by entering the name RM_DERI_ENTRY_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: RMDR
Program Name: SAPLRMDR
Main Program: SAPLRMDR
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RM_DERI_ENTRY_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_DERI_ENTRY_CHECK'"RM: prüft Eintrag Ableitungsregel auf Konsistenz (Klammerung).
EXPORTING
I_ENV = "Ableitungsumgebung
I_VALUES_T = "Tabelle Feldwerte des Eintrags
EXCEPTIONS
ENTRY_REJECT = 1
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLRMDR1_001 RM: Enhancement to Derivation of FO from Transaction
EXIT_SAPLRMDR2_001 RM: Enhancement in Financial Object Derivation (Internal)
EXIT_SAPLRMDRO_001 RM: Enhancement to Derivation of FO from Risk Object
EXIT_SAPLRMDRO_002 RM: Customer Exit Before Call of Characteristics Derivation
EXIT_SAPLRMDRO_003 RM: Customer Exit after Call of Characteristics Derivation
IMPORTING Parameters details for RM_DERI_ENTRY_CHECK
I_ENV - Ableitungsumgebung
Data type: KEDR_ENVOptional: No
Call by Reference: No ( called with pass by value option)
I_VALUES_T - Tabelle Feldwerte des Eintrags
Data type: KEDR_TAB_ENTRY_VALUESOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ENTRY_REJECT - Eintrag ablehnen
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RM_DERI_ENTRY_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_i_env | TYPE KEDR_ENV, " | |||
| lv_entry_reject | TYPE KEDR_ENV, " | |||
| lv_i_values_t | TYPE KEDR_TAB_ENTRY_VALUES. " |
|   CALL FUNCTION 'RM_DERI_ENTRY_CHECK' "RM: prüft Eintrag Ableitungsregel auf Konsistenz (Klammerung) |
| EXPORTING | ||
| I_ENV | = lv_i_env | |
| I_VALUES_T | = lv_i_values_t | |
| EXCEPTIONS | ||
| ENTRY_REJECT = 1 | ||
| . " RM_DERI_ENTRY_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM RM_DERI_ENTRY_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.Search for further information about these or an SAP related objects