SAP RM_EVAL_MTASK_SETUP Function Module for Parallel Processing: Set Up Multitasking Environment









RM_EVAL_MTASK_SETUP is a standard rm eval mtask setup 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: Set Up Multitasking Environment 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 setup FM, simply by entering the name RM_EVAL_MTASK_SETUP into the relevant SAP transaction such as SE37 or SE38.

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



Function RM_EVAL_MTASK_SETUP 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_SETUP'"Parallel Processing: Set Up Multitasking Environment
EXPORTING
AUSWTYP = "Risk Management Evaluation Category

IMPORTING
GRPNAME = "
MAXWPS = "
PCKSZE = "
MTASK = "
JOB_ABORT = "Feld zum Ankreuzen

CHANGING
* ERRORTAB = "

TABLES
* FOB_SINGLE_PACK_T = "Financial Object List for Individual Packages

EXCEPTIONS
SPBT_INIT_ERROR = 1 SPBT_ENV_ERROR = 2
.



IMPORTING Parameters details for RM_EVAL_MTASK_SETUP

AUSWTYP - Risk Management Evaluation Category

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

EXPORTING Parameters details for RM_EVAL_MTASK_SETUP

GRPNAME -

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

MAXWPS -

Data type: I
Optional: No
Call by Reference: No ( called with pass by value option)

PCKSZE -

Data type: I
Optional: No
Call by Reference: No ( called with pass by value option)

MTASK -

Data type: C
Optional: No
Call by Reference: No ( called with pass by value option)

JOB_ABORT - Feld zum Ankreuzen

Data type: XFELD
Optional: No
Call by Reference: No ( called with pass by value option)

CHANGING Parameters details for RM_EVAL_MTASK_SETUP

ERRORTAB -

Data type: TVEH_ERROR_ITAB_TAB
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for RM_EVAL_MTASK_SETUP

FOB_SINGLE_PACK_T - Financial Object List for Individual Packages

Data type: TABLE
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

SPBT_INIT_ERROR -

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

SPBT_ENV_ERROR -

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

Copy and paste ABAP code example for RM_EVAL_MTASK_SETUP 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_auswtyp  TYPE JBRHSSPARI-AUSWTYP, "   
lv_grpname  TYPE VTVMTSK-GRPNAME, "   
lv_errortab  TYPE TVEH_ERROR_ITAB_TAB, "   
lv_spbt_init_error  TYPE TVEH_ERROR_ITAB_TAB, "   
lt_fob_single_pack_t  TYPE STANDARD TABLE OF TABLE, "   
lv_maxwps  TYPE I, "   
lv_spbt_env_error  TYPE I, "   
lv_pcksze  TYPE I, "   
lv_mtask  TYPE C, "   
lv_job_abort  TYPE XFELD. "   

  CALL FUNCTION 'RM_EVAL_MTASK_SETUP'  "Parallel Processing: Set Up Multitasking Environment
    EXPORTING
         AUSWTYP = lv_auswtyp
    IMPORTING
         GRPNAME = lv_grpname
         MAXWPS = lv_maxwps
         PCKSZE = lv_pcksze
         MTASK = lv_mtask
         JOB_ABORT = lv_job_abort
    CHANGING
         ERRORTAB = lv_errortab
    TABLES
         FOB_SINGLE_PACK_T = lt_fob_single_pack_t
    EXCEPTIONS
        SPBT_INIT_ERROR = 1
        SPBT_ENV_ERROR = 2
. " RM_EVAL_MTASK_SETUP




ABAP code using 7.40 inline data declarations to call FM RM_EVAL_MTASK_SETUP

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 JBRHSSPARI INTO @DATA(ld_auswtyp).
 
"SELECT single GRPNAME FROM VTVMTSK INTO @DATA(ld_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!