SAP Function Modules
DTL_MT_DATA_LOAD SAP Function module - schedule jobs for data migration
DTL_MT_DATA_LOAD is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name DTL_MT_DATA_LOAD into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
DMC_DTL
Released Date:
Not Released
Processing type: Remote-Enabled
Pattern for FM DTL_MT_DATA_LOAD - DTL MT DATA LOAD
CALL FUNCTION 'DTL_MT_DATA_LOAD' "schedule jobs for data migration
EXPORTING
im_mode = " char1 Single-character flag
* im_applic = 'SLO' " dmc_applic DMC Tool: Application
im_mt_id = " dmc_mt_identifier DMC: Kennzeichen einer Massenübernahme
* im_acc_prec_id = " dmc_id DMC: Key
* im_test = 'X' " boolean test run
* im_write_behav = 1 " dmc_rto_behaviour
* im_packid = " dmc_package_id Package ID
im_session_id = " dmc_session_id MBT PCL SESSION_ID
* im_restart = '-' " boolean restart mode
* i_no_of_jobs = 999 " dmc_num_jobs_parallel number of jobs
* i_ddic_check = 'X' " dmc_boolean DDIC check
* i_keep_failed_flag = '-' " dmc_boolean don't reset FAILED flags in MT TABLES
IMPORTING
ex_lognumber = " balognr Application log: log number
ex_statistics = " dtl_mt_statistics Structure for PCL function module / STATUS
* TABLES
* it_tables = " dmc_ranges_tabname Ranges Table for Table Name
* et_status = " dmc_activity_status_info_t Status info for MWB activities
* et_lognumbers = " dmc_dtl_logs_and_times_t table of application log numbers
* et_mt_status = " dtl_mt_state Load status of tables of a mass transfer (for API / DTL)
. " DTL_MT_DATA_LOAD
ABAP code example for Function Module DTL_MT_DATA_LOAD
The ABAP code below is a full code listing to execute function module DTL_MT_DATA_LOAD including all data declarations. The code uses 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 original method of declaring data variables up front. 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).
| ld_ex_lognumber | TYPE BALOGNR , |
| ld_ex_statistics | TYPE DTL_MT_STATISTICS , |
| it_it_tables | TYPE STANDARD TABLE OF DMC_RANGES_TABNAME,"TABLES PARAM |
| wa_it_tables | LIKE LINE OF it_it_tables , |
| it_et_status | TYPE STANDARD TABLE OF DMC_ACTIVITY_STATUS_INFO_T,"TABLES PARAM |
| wa_et_status | LIKE LINE OF it_et_status , |
| it_et_lognumbers | TYPE STANDARD TABLE OF DMC_DTL_LOGS_AND_TIMES_T,"TABLES PARAM |
| wa_et_lognumbers | LIKE LINE OF it_et_lognumbers , |
| it_et_mt_status | TYPE STANDARD TABLE OF DTL_MT_STATE,"TABLES PARAM |
| wa_et_mt_status | LIKE LINE OF it_et_mt_status . |
DATA(ld_im_mode) = 'Check type of data required'.
DATA(ld_im_applic) = 'Check type of data required'.
DATA(ld_im_mt_id) = 'Check type of data required'.
DATA(ld_im_acc_prec_id) = 'Check type of data required'.
DATA(ld_im_test) = 'Check type of data required'.
DATA(ld_im_write_behav) = 'Check type of data required'.
DATA(ld_im_packid) = 'Check type of data required'.
DATA(ld_im_session_id) = 'Check type of data required'.
DATA(ld_im_restart) = 'Check type of data required'.
DATA(ld_i_no_of_jobs) = 'Check type of data required'.
DATA(ld_i_ddic_check) = 'Check type of data required'.
DATA(ld_i_keep_failed_flag) = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_it_tables to it_it_tables.
"populate fields of struture and append to itab
append wa_et_status to it_et_status.
"populate fields of struture and append to itab
append wa_et_lognumbers to it_et_lognumbers.
"populate fields of struture and append to itab
append wa_et_mt_status to it_et_mt_status. . CALL FUNCTION 'DTL_MT_DATA_LOAD' EXPORTING im_mode = ld_im_mode * im_applic = ld_im_applic im_mt_id = ld_im_mt_id * im_acc_prec_id = ld_im_acc_prec_id * im_test = ld_im_test * im_write_behav = ld_im_write_behav * im_packid = ld_im_packid im_session_id = ld_im_session_id * im_restart = ld_im_restart * i_no_of_jobs = ld_i_no_of_jobs * i_ddic_check = ld_i_ddic_check * i_keep_failed_flag = ld_i_keep_failed_flag IMPORTING ex_lognumber = ld_ex_lognumber ex_statistics = ld_ex_statistics * TABLES * it_tables = it_it_tables * et_status = it_et_status * et_lognumbers = it_et_lognumbers * et_mt_status = it_et_mt_status . " DTL_MT_DATA_LOAD
IF SY-SUBRC EQ 0. "All OK ENDIF.
ABAP code to compare 7.40 inline data declaration with original syntax
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_ex_lognumber | TYPE BALOGNR , |
| ld_im_mode | TYPE CHAR1 , |
| it_it_tables | TYPE STANDARD TABLE OF DMC_RANGES_TABNAME , |
| wa_it_tables | LIKE LINE OF it_it_tables, |
| ld_ex_statistics | TYPE DTL_MT_STATISTICS , |
| ld_im_applic | TYPE DMC_APPLIC , |
| it_et_status | TYPE STANDARD TABLE OF DMC_ACTIVITY_STATUS_INFO_T , |
| wa_et_status | LIKE LINE OF it_et_status, |
| ld_im_mt_id | TYPE DMC_MT_IDENTIFIER , |
| it_et_lognumbers | TYPE STANDARD TABLE OF DMC_DTL_LOGS_AND_TIMES_T , |
| wa_et_lognumbers | LIKE LINE OF it_et_lognumbers, |
| ld_im_acc_prec_id | TYPE DMC_ID , |
| it_et_mt_status | TYPE STANDARD TABLE OF DTL_MT_STATE , |
| wa_et_mt_status | LIKE LINE OF it_et_mt_status, |
| ld_im_test | TYPE BOOLEAN , |
| ld_im_write_behav | TYPE DMC_RTO_BEHAVIOUR , |
| ld_im_packid | TYPE DMC_PACKAGE_ID , |
| ld_im_session_id | TYPE DMC_SESSION_ID , |
| ld_im_restart | TYPE BOOLEAN , |
| ld_i_no_of_jobs | TYPE DMC_NUM_JOBS_PARALLEL , |
| ld_i_ddic_check | TYPE DMC_BOOLEAN , |
| ld_i_keep_failed_flag | TYPE DMC_BOOLEAN . |
ld_im_mode = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_it_tables to it_it_tables.
ld_im_applic = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_et_status to it_et_status.
ld_im_mt_id = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_et_lognumbers to it_et_lognumbers.
ld_im_acc_prec_id = 'Check type of data required'.
"populate fields of struture and append to itab
append wa_et_mt_status to it_et_mt_status.
ld_im_test = 'Check type of data required'.
ld_im_write_behav = 'Check type of data required'.
ld_im_packid = 'Check type of data required'.
ld_im_session_id = 'Check type of data required'.
ld_im_restart = 'Check type of data required'.
ld_i_no_of_jobs = 'Check type of data required'.
ld_i_ddic_check = 'Check type of data required'.
ld_i_keep_failed_flag = 'Check type of data required'.
SAP Documentation for FM DTL_MT_DATA_LOAD
For each conversion object of the specified mass transfer, the data load
is performed either for a certain access plan, or for all access plans
...See here for full SAP fm documentation
Contribute (Add Comments)
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name DTL_MT_DATA_LOAD or its description.
DTL_MT_DATA_LOAD - schedule jobs for data migration DTL_MT_CONVOBJS_RESET - Delete conversion objects of a mass transfer DTL_MT_CONVOBJS_DEFINE - Create conversion objects of a mass transfer DTL_MT_COMPARE_DDIC_TIMESTAMP - Compare DDIC timestamp in sender / receiver with MWB data DTL_MT_COBJS_REMOVE - Remove conversion objects from an existing mass transfer DTL_MT_COBJS_ADD - Add conversion objects to an existing mass transfer