SAP RM_EVAL_MTASK_INIT Function Module for Parallel Processing: Read Settings from VTVMTASk









RM_EVAL_MTASK_INIT is a standard rm eval mtask init SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Parallel Processing: Read Settings from VTVMTASk 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 eval mtask init FM, simply by entering the name RM_EVAL_MTASK_INIT into the relevant SAP transaction such as SE37 or SE38.

Function Group: RMR3
Program Name: SAPLRMR3
Main Program: SAPLRMR3
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function RM_EVAL_MTASK_INIT 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_EVAL_MTASK_INIT'"Parallel Processing: Read Settings from VTVMTASk
EXPORTING
I_AUSWTYP = "
* I_RFCUSER = SY-UNAME "

IMPORTING
E_MTASK = "
E_PCKSIZE = "
E_MAXTSKS = "
E_GRPNAME = "
.



IMPORTING Parameters details for RM_EVAL_MTASK_INIT

I_AUSWTYP -

Data type: VTVMTASK-AUSWTYP
Optional: No
Call by Reference: No ( called with pass by value option)

I_RFCUSER -

Data type: VTVMTASK-RFCUSER
Default: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for RM_EVAL_MTASK_INIT

E_MTASK -

Data type: C
Optional: No
Call by Reference: Yes

E_PCKSIZE -

Data type: I
Optional: No
Call by Reference: Yes

E_MAXTSKS -

Data type: I
Optional: No
Call by Reference: Yes

E_GRPNAME -

Data type: VTVMTASK-GRPNAME
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RM_EVAL_MTASK_INIT 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_mtask  TYPE C, "   
lv_i_auswtyp  TYPE VTVMTASK-AUSWTYP, "   
lv_e_pcksize  TYPE I, "   
lv_i_rfcuser  TYPE VTVMTASK-RFCUSER, "   SY-UNAME
lv_e_maxtsks  TYPE I, "   
lv_e_grpname  TYPE VTVMTASK-GRPNAME. "   

  CALL FUNCTION 'RM_EVAL_MTASK_INIT'  "Parallel Processing: Read Settings from VTVMTASk
    EXPORTING
         I_AUSWTYP = lv_i_auswtyp
         I_RFCUSER = lv_i_rfcuser
    IMPORTING
         E_MTASK = lv_e_mtask
         E_PCKSIZE = lv_e_pcksize
         E_MAXTSKS = lv_e_maxtsks
         E_GRPNAME = lv_e_grpname
. " RM_EVAL_MTASK_INIT




ABAP code using 7.40 inline data declarations to call FM RM_EVAL_MTASK_INIT

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 AUSWTYP FROM VTVMTASK INTO @DATA(ld_i_auswtyp).
 
 
"SELECT single RFCUSER FROM VTVMTASK INTO @DATA(ld_i_rfcuser).
DATA(ld_i_rfcuser) = SY-UNAME.
 
 
"SELECT single GRPNAME FROM VTVMTASK INTO @DATA(ld_e_grpname).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!