SAP RM_DERI_VALUE_TEXT_GET Function Module for RM: Texte für Regeleinträge (Ableitung)
RM_DERI_VALUE_TEXT_GET is a standard rm deri value text get 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: Texte für Regeleinträge (Ableitung) 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 value text get FM, simply by entering the name RM_DERI_VALUE_TEXT_GET 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_VALUE_TEXT_GET 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_VALUE_TEXT_GET'"RM: Texte für Regeleinträge (Ableitung).
EXPORTING
I_STRAT = "Strategie-ID
I_ENV = "Ableitungsumgebung
I_NAME = "Feld einer Ableitungsregel
I_VALUE = "Feldwert
IMPORTING
E_TEXT = "Text zum Feldwert
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_VALUE_TEXT_GET
I_STRAT - Strategie-ID
Data type: RMDR_STRATOptional: No
Call by Reference: No ( called with pass by value option)
I_ENV - Ableitungsumgebung
Data type: KEDR_ENVOptional: No
Call by Reference: No ( called with pass by value option)
I_NAME - Feld einer Ableitungsregel
Data type: KEDR_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
I_VALUE - Feldwert
Data type: KEDR_VALUEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RM_DERI_VALUE_TEXT_GET
E_TEXT - Text zum Feldwert
Data type: KEDR_TEXTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RM_DERI_VALUE_TEXT_GET 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_e_text | TYPE KEDR_TEXT, " | |||
| lv_i_strat | TYPE RMDR_STRAT, " | |||
| lv_i_env | TYPE KEDR_ENV, " | |||
| lv_i_name | TYPE KEDR_NAME, " | |||
| lv_i_value | TYPE KEDR_VALUE. " |
|   CALL FUNCTION 'RM_DERI_VALUE_TEXT_GET' "RM: Texte für Regeleinträge (Ableitung) |
| EXPORTING | ||
| I_STRAT | = lv_i_strat | |
| I_ENV | = lv_i_env | |
| I_NAME | = lv_i_name | |
| I_VALUE | = lv_i_value | |
| IMPORTING | ||
| E_TEXT | = lv_e_text | |
| . " RM_DERI_VALUE_TEXT_GET | ||
ABAP code using 7.40 inline data declarations to call FM RM_DERI_VALUE_TEXT_GET
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