SAP DMCMON_MAINTAIN_MASS_TRANSFER Function Module for
DMCMON_MAINTAIN_MASS_TRANSFER is a standard dmcmon maintain mass transfer SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 dmcmon maintain mass transfer FM, simply by entering the name DMCMON_MAINTAIN_MASS_TRANSFER into the relevant SAP transaction such as SE37 or SE38.
Function Group: DMCMON_UTILITIES
Program Name: SAPLDMCMON_UTILITIES
Main Program: SAPLDMCMON_UTILITIES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DMCMON_MAINTAIN_MASS_TRANSFER 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 'DMCMON_MAINTAIN_MASS_TRANSFER'".
EXPORTING
* IM_WMODE = '3' "MWB: Editing Mode (1=Display, 2=Change, 3=Create...)
* IM_NO_DIALOG = '-' "MWB: Display Option (X = No Dialog, - = Dialog)
* IM_MT_ID = "DMC: Indicator for Mass Transfer
* IM_DESCR = "Description
* IM_IS_ACTIVE = "Boolean Variable (X=true, -=false, space=unknown)
* IM_BLOCKSIZE = "MWB: Size of an RFC Package
* IM_SUBPROJECT = "Subproject IDs
IMPORTING Parameters details for DMCMON_MAINTAIN_MASS_TRANSFER
IM_WMODE - MWB: Editing Mode (1=Display, 2=Change, 3=Create...)
Data type: DMC_WMODEDefault: '3'
Optional: Yes
Call by Reference: Yes
IM_NO_DIALOG - MWB: Display Option (X = No Dialog, - = Dialog)
Data type: BOOLEANDefault: '-'
Optional: Yes
Call by Reference: Yes
IM_MT_ID - DMC: Indicator for Mass Transfer
Data type: DMC_MT_IDENTIFIEROptional: Yes
Call by Reference: Yes
IM_DESCR - Description
Data type: DMC_DESCROptional: Yes
Call by Reference: Yes
IM_IS_ACTIVE - Boolean Variable (X=true, -=false, space=unknown)
Data type: BOOLEANOptional: Yes
Call by Reference: Yes
IM_BLOCKSIZE - MWB: Size of an RFC Package
Data type: DMC_BLOCKSIZEOptional: Yes
Call by Reference: Yes
IM_SUBPROJECT - Subproject IDs
Data type: DMC_SIDENTOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for DMCMON_MAINTAIN_MASS_TRANSFER 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_im_wmode | TYPE DMC_WMODE, " '3' | |||
| lv_im_no_dialog | TYPE BOOLEAN, " '-' | |||
| lv_im_mt_id | TYPE DMC_MT_IDENTIFIER, " | |||
| lv_im_descr | TYPE DMC_DESCR, " | |||
| lv_im_is_active | TYPE BOOLEAN, " | |||
| lv_im_blocksize | TYPE DMC_BLOCKSIZE, " | |||
| lv_im_subproject | TYPE DMC_SIDENT. " |
|   CALL FUNCTION 'DMCMON_MAINTAIN_MASS_TRANSFER' " |
| EXPORTING | ||
| IM_WMODE | = lv_im_wmode | |
| IM_NO_DIALOG | = lv_im_no_dialog | |
| IM_MT_ID | = lv_im_mt_id | |
| IM_DESCR | = lv_im_descr | |
| IM_IS_ACTIVE | = lv_im_is_active | |
| IM_BLOCKSIZE | = lv_im_blocksize | |
| IM_SUBPROJECT | = lv_im_subproject | |
| . " DMCMON_MAINTAIN_MASS_TRANSFER | ||
ABAP code using 7.40 inline data declarations to call FM DMCMON_MAINTAIN_MASS_TRANSFER
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.| DATA(ld_im_wmode) | = '3'. | |||
| DATA(ld_im_no_dialog) | = '-'. | |||
Search for further information about these or an SAP related objects