SAP RS_DME_RFC_TR_CALL_TRAIN_DB Function Module for RFC Call - Training using DDIC tables - for engine with metadata in SAP
RS_DME_RFC_TR_CALL_TRAIN_DB is a standard rs dme rfc tr call train db SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for RFC Call - Training using DDIC tables - for engine with metadata in SAP 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 rs dme rfc tr call train db FM, simply by entering the name RS_DME_RFC_TR_CALL_TRAIN_DB into the relevant SAP transaction such as SE37 or SE38.
Function Group: RS_DME_RFC_TRAINING
Program Name: SAPLRS_DME_RFC_TRAINING
Main Program: SAPLRS_DME_RFC_TRAINING
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function RS_DME_RFC_TR_CALL_TRAIN_DB 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 'RS_DME_RFC_TR_CALL_TRAIN_DB'"RFC Call - Training using DDIC tables - for engine with metadata in SAP.
EXPORTING
I_MODEL = "Data Mining Model
I_ENGINE = "Data Mining Method
I_DBNAME = "Table Name
I_TASK_ID = "Training Task ID (for further reference)
TABLES
I_T_CONN_INFO = "Connection Information
I_T_MOD_PARAM = "Parameters for the Model
I_T_MOD_FIELDS = "Model Fields - Structure
I_T_FIELD_PARAM = "Parameters for the Model Columns
I_T_FIELD_VALS = "Model Field Values
I_T_FIELD_MAP = "DB Fields to Model Fields Mapping
* E_T_RETURN = "Return Parameter
IMPORTING Parameters details for RS_DME_RFC_TR_CALL_TRAIN_DB
I_MODEL - Data Mining Model
Data type: RSDMEM_MODELOptional: No
Call by Reference: No ( called with pass by value option)
I_ENGINE - Data Mining Method
Data type: RSDMEM_ANALYTICAL_SERVICEOptional: No
Call by Reference: No ( called with pass by value option)
I_DBNAME - Table Name
Data type: TABNAMEOptional: No
Call by Reference: No ( called with pass by value option)
I_TASK_ID - Training Task ID (for further reference)
Data type: RSDMEM_BATCHOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for RS_DME_RFC_TR_CALL_TRAIN_DB
I_T_CONN_INFO - Connection Information
Data type: RSDMEM_TH_CONN_PAROptional: No
Call by Reference: Yes
I_T_MOD_PARAM - Parameters for the Model
Data type: RSDMEM_TH_MODEL_PARAMOptional: No
Call by Reference: Yes
I_T_MOD_FIELDS - Model Fields - Structure
Data type: RSDMEM_TH_MOD_FLDSOptional: No
Call by Reference: Yes
I_T_FIELD_PARAM - Parameters for the Model Columns
Data type: RSDMEM_TH_FLD_PARAM_RFCOptional: No
Call by Reference: Yes
I_T_FIELD_VALS - Model Field Values
Data type: RSDMEM_TH_FLD_VAL_RFCOptional: No
Call by Reference: Yes
I_T_FIELD_MAP - DB Fields to Model Fields Mapping
Data type: RSDMEM_TH_COL_MAPOptional: No
Call by Reference: Yes
E_T_RETURN - Return Parameter
Data type: BAPIRET2_TOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for RS_DME_RFC_TR_CALL_TRAIN_DB 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_model | TYPE RSDMEM_MODEL, " | |||
| lt_i_t_conn_info | TYPE STANDARD TABLE OF RSDMEM_TH_CONN_PAR, " | |||
| lv_i_engine | TYPE RSDMEM_ANALYTICAL_SERVICE, " | |||
| lt_i_t_mod_param | TYPE STANDARD TABLE OF RSDMEM_TH_MODEL_PARAM, " | |||
| lv_i_dbname | TYPE TABNAME, " | |||
| lt_i_t_mod_fields | TYPE STANDARD TABLE OF RSDMEM_TH_MOD_FLDS, " | |||
| lv_i_task_id | TYPE RSDMEM_BATCH, " | |||
| lt_i_t_field_param | TYPE STANDARD TABLE OF RSDMEM_TH_FLD_PARAM_RFC, " | |||
| lt_i_t_field_vals | TYPE STANDARD TABLE OF RSDMEM_TH_FLD_VAL_RFC, " | |||
| lt_i_t_field_map | TYPE STANDARD TABLE OF RSDMEM_TH_COL_MAP, " | |||
| lt_e_t_return | TYPE STANDARD TABLE OF BAPIRET2_T. " |
|   CALL FUNCTION 'RS_DME_RFC_TR_CALL_TRAIN_DB' "RFC Call - Training using DDIC tables - for engine with metadata in SAP |
| EXPORTING | ||
| I_MODEL | = lv_i_model | |
| I_ENGINE | = lv_i_engine | |
| I_DBNAME | = lv_i_dbname | |
| I_TASK_ID | = lv_i_task_id | |
| TABLES | ||
| I_T_CONN_INFO | = lt_i_t_conn_info | |
| I_T_MOD_PARAM | = lt_i_t_mod_param | |
| I_T_MOD_FIELDS | = lt_i_t_mod_fields | |
| I_T_FIELD_PARAM | = lt_i_t_field_param | |
| I_T_FIELD_VALS | = lt_i_t_field_vals | |
| I_T_FIELD_MAP | = lt_i_t_field_map | |
| E_T_RETURN | = lt_e_t_return | |
| . " RS_DME_RFC_TR_CALL_TRAIN_DB | ||
ABAP code using 7.40 inline data declarations to call FM RS_DME_RFC_TR_CALL_TRAIN_DB
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