SAP RM_DERI_CALL_CUSTOMER_EXIT Function Module for RM Merkmalsableitung: ruft User-Exit auf
RM_DERI_CALL_CUSTOMER_EXIT is a standard rm deri call customer exit 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 Merkmalsableitung: ruft User-Exit auf 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 call customer exit FM, simply by entering the name RM_DERI_CALL_CUSTOMER_EXIT into the relevant SAP transaction such as SE37 or SE38.
Function Group: JBRDR
Program Name: SAPLJBRDR
Main Program: SAPLJBRDR
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RM_DERI_CALL_CUSTOMER_EXIT 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_CALL_CUSTOMER_EXIT'"RM Merkmalsableitung: ruft User-Exit auf.
EXPORTING
I_RMBID = "RM-Bereich
I_DATE = "Datum der Ableitung
I_STEP_ID = "Name des Ableitungsschritts
I_RM_CHAR = "Quellstruktur RM-Bereichsmerkmale
I_OBJECT = "Quellstruktur Finanzobjekt
I_TEMP = "Quellstruktur temporäre Hilfsfelder
IMPORTING
E_RM_CHAR = "Zielstruktur RM-Bereichsmerkmale
E_OBJECT = "Zielstruktur Finanzobjekt
E_TEMP = "Zielstruktur temporäre Hilfsfelder
E_EXIT_IS_ACTIVE = "Kennzeichen: Exit aktiv
E_FAILED = "Kennzeichen: Ableitung fehlgeschlagen
EXCEPTIONS
DERIVATION_FAILED = 1
IMPORTING Parameters details for RM_DERI_CALL_CUSTOMER_EXIT
I_RMBID - RM-Bereich
Data type: JBRRMBBF-RMBIDOptional: No
Call by Reference: No ( called with pass by value option)
I_DATE - Datum der Ableitung
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
I_STEP_ID - Name des Ableitungsschritts
Data type: TKEDRS-STEPIDOptional: No
Call by Reference: No ( called with pass by value option)
I_RM_CHAR - Quellstruktur RM-Bereichsmerkmale
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
I_OBJECT - Quellstruktur Finanzobjekt
Data type: JBROBJDERIOptional: No
Call by Reference: No ( called with pass by value option)
I_TEMP - Quellstruktur temporäre Hilfsfelder
Data type: JBRTEMPDERIOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RM_DERI_CALL_CUSTOMER_EXIT
E_RM_CHAR - Zielstruktur RM-Bereichsmerkmale
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
E_OBJECT - Zielstruktur Finanzobjekt
Data type: JBROBJDERIOptional: No
Call by Reference: No ( called with pass by value option)
E_TEMP - Zielstruktur temporäre Hilfsfelder
Data type: JBRTEMPDERIOptional: No
Call by Reference: No ( called with pass by value option)
E_EXIT_IS_ACTIVE - Kennzeichen: Exit aktiv
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
E_FAILED - Kennzeichen: Ableitung fehlgeschlagen
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DERIVATION_FAILED - Ableitung fehlgeschlagen
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RM_DERI_CALL_CUSTOMER_EXIT 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_rmbid | TYPE JBRRMBBF-RMBID, " | |||
| lv_e_rm_char | TYPE JBRRMBBF, " | |||
| lv_derivation_failed | TYPE JBRRMBBF, " | |||
| lv_i_date | TYPE SY-DATUM, " | |||
| lv_e_object | TYPE JBROBJDERI, " | |||
| lv_e_temp | TYPE JBRTEMPDERI, " | |||
| lv_i_step_id | TYPE TKEDRS-STEPID, " | |||
| lv_i_rm_char | TYPE TKEDRS, " | |||
| lv_e_exit_is_active | TYPE TKEDRS, " | |||
| lv_e_failed | TYPE TKEDRS, " | |||
| lv_i_object | TYPE JBROBJDERI, " | |||
| lv_i_temp | TYPE JBRTEMPDERI. " |
|   CALL FUNCTION 'RM_DERI_CALL_CUSTOMER_EXIT' "RM Merkmalsableitung: ruft User-Exit auf |
| EXPORTING | ||
| I_RMBID | = lv_i_rmbid | |
| I_DATE | = lv_i_date | |
| I_STEP_ID | = lv_i_step_id | |
| I_RM_CHAR | = lv_i_rm_char | |
| I_OBJECT | = lv_i_object | |
| I_TEMP | = lv_i_temp | |
| IMPORTING | ||
| E_RM_CHAR | = lv_e_rm_char | |
| E_OBJECT | = lv_e_object | |
| E_TEMP | = lv_e_temp | |
| E_EXIT_IS_ACTIVE | = lv_e_exit_is_active | |
| E_FAILED | = lv_e_failed | |
| EXCEPTIONS | ||
| DERIVATION_FAILED = 1 | ||
| . " RM_DERI_CALL_CUSTOMER_EXIT | ||
ABAP code using 7.40 inline data declarations to call FM RM_DERI_CALL_CUSTOMER_EXIT
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 RMBID FROM JBRRMBBF INTO @DATA(ld_i_rmbid). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_i_date). | ||||
| "SELECT single STEPID FROM TKEDRS INTO @DATA(ld_i_step_id). | ||||
Search for further information about these or an SAP related objects