SAP DTL_MT_COBJS_ADD Function Module for Add conversion objects to an existing mass transfer









DTL_MT_COBJS_ADD is a standard dtl mt cobjs add SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Add conversion objects to an existing mass transfer 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 dtl mt cobjs add FM, simply by entering the name DTL_MT_COBJS_ADD into the relevant SAP transaction such as SE37 or SE38.

Function Group: DMC_DTL
Program Name: SAPLDMC_DTL
Main Program: SAPLDMC_DTL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function DTL_MT_COBJS_ADD 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 'DTL_MT_COBJS_ADD'"Add conversion objects to an existing mass transfer
EXPORTING
IM_MT_ID = "DMC: Kennzeichen einer Massenübernahme
* IM_BLOCKSIZE = 16777216 "MWB: Grösse eines RFC-Pakets
* IM_WRITE_BEHAVIOUR = 1 "Write behaviour
* IM_PACKID = "Package ID
* IM_SESSION_ID = "MBT PCL SESSION_ID
* I_READING_TYPE = "reading type (transparent, pool, cluster, indx-cluster)
* I_MAX_PORTION_ACPL = "maximum number of portions of single access plan (split)
* I_TABLE_MAX_PARALL = "number of acc.pl. per conv.obj. that can be loaded in parall

IMPORTING
EX_LOGNUMBER = "Application log: log number
EX_STATUS = "Status info for MWB activities

TABLES
IT_TABLES = "Tables to be included into the mass transfer
.



IMPORTING Parameters details for DTL_MT_COBJS_ADD

IM_MT_ID - DMC: Kennzeichen einer Massenübernahme

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

IM_BLOCKSIZE - MWB: Grösse eines RFC-Pakets

Data type: DMC_BLOCKSIZE
Default: 16777216
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_WRITE_BEHAVIOUR - Write behaviour

Data type: DMC_RTO_BEHAVIOUR
Default: 1
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_PACKID - Package ID

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

IM_SESSION_ID - MBT PCL SESSION_ID

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

I_READING_TYPE - reading type (transparent, pool, cluster, indx-cluster)

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

I_MAX_PORTION_ACPL - maximum number of portions of single access plan (split)

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

I_TABLE_MAX_PARALL - number of acc.pl. per conv.obj. that can be loaded in parall

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

EXPORTING Parameters details for DTL_MT_COBJS_ADD

EX_LOGNUMBER - Application log: log number

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

EX_STATUS - Status info for MWB activities

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

TABLES Parameters details for DTL_MT_COBJS_ADD

IT_TABLES - Tables to be included into the mass transfer

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

Copy and paste ABAP code example for DTL_MT_COBJS_ADD 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_mt_id  TYPE DMC_MT_IDENTIFIER, "   
lt_it_tables  TYPE STANDARD TABLE OF DMC_DTL_MT_TABLES, "   
lv_ex_lognumber  TYPE BALOGNR, "   
lv_ex_status  TYPE DMC_ACTIVITY_STATUS_INFO, "   
lv_im_blocksize  TYPE DMC_BLOCKSIZE, "   16777216
lv_im_write_behaviour  TYPE DMC_RTO_BEHAVIOUR, "   1
lv_im_packid  TYPE DMC_PACKAGE_ID, "   
lv_im_session_id  TYPE DMC_SESSION_ID, "   
lv_i_reading_type  TYPE DMC_READING_TYPE, "   
lv_i_max_portion_acpl  TYPE DMC_MAX_PORTION_ACPL, "   
lv_i_table_max_parall  TYPE DMC_TAB_MAX_PARALLEL. "   

  CALL FUNCTION 'DTL_MT_COBJS_ADD'  "Add conversion objects to an existing mass transfer
    EXPORTING
         IM_MT_ID = lv_im_mt_id
         IM_BLOCKSIZE = lv_im_blocksize
         IM_WRITE_BEHAVIOUR = lv_im_write_behaviour
         IM_PACKID = lv_im_packid
         IM_SESSION_ID = lv_im_session_id
         I_READING_TYPE = lv_i_reading_type
         I_MAX_PORTION_ACPL = lv_i_max_portion_acpl
         I_TABLE_MAX_PARALL = lv_i_table_max_parall
    IMPORTING
         EX_LOGNUMBER = lv_ex_lognumber
         EX_STATUS = lv_ex_status
    TABLES
         IT_TABLES = lt_it_tables
. " DTL_MT_COBJS_ADD




ABAP code using 7.40 inline data declarations to call FM DTL_MT_COBJS_ADD

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_blocksize) = 16777216.
 
DATA(ld_im_write_behaviour) = 1.
 
 
 
 
 
 


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!