SAP DMC_IUC_START_EXPORT Function Module for MWB-Upgrade: Startet den Export für die Kaskadierung
DMC_IUC_START_EXPORT is a standard dmc iuc start export SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for MWB-Upgrade: Startet den Export für die Kaskadierung 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 dmc iuc start export FM, simply by entering the name DMC_IUC_START_EXPORT into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNV_MWB_IU
Program Name: SAPLCNV_MWB_IU
Main Program: SAPLCNV_MWB_IU
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function DMC_IUC_START_EXPORT 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 'DMC_IUC_START_EXPORT'"MWB-Upgrade: Startet den Export für die Kaskadierung.
EXPORTING
IM_CLNT = "Mandant
IM_JOBS = "Anzahl paraleller Jobs
TABLES
EX_IT_EXP_TRKORR = "Exportierte Transportaufträge
EX_IT_EXP_TRKORR_ERROR = "Transportaufträge mit Exportfehlern
EX_IT_TRKORR_NOT_EXIST = "Nicht gefundene Transportaufträge
EX_IT_TRKORR_ALREADY_EXP = "Bereits exportierte Transportaufträge
EX_IT_TPPROTOCOL = "Transportprotokoll
EXCEPTIONS
DIFFERENT_CLIENT = 1 STEP_ALREADY_DONE = 2 PREVIOUS_STEP_NOT_FINISHED = 3 TPPARAM_NOT_SPECIFIED = 4
IMPORTING Parameters details for DMC_IUC_START_EXPORT
IM_CLNT - Mandant
Data type: SY-MANDTOptional: No
Call by Reference: No ( called with pass by value option)
IM_JOBS - Anzahl paraleller Jobs
Data type: DMC_IU_DTYPE-INT1Optional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for DMC_IUC_START_EXPORT
EX_IT_EXP_TRKORR - Exportierte Transportaufträge
Data type: DMC_IU_UPGTROptional: No
Call by Reference: No ( called with pass by value option)
EX_IT_EXP_TRKORR_ERROR - Transportaufträge mit Exportfehlern
Data type: DMC_IU_UPGTROptional: No
Call by Reference: No ( called with pass by value option)
EX_IT_TRKORR_NOT_EXIST - Nicht gefundene Transportaufträge
Data type: DMC_IU_UPGTROptional: No
Call by Reference: No ( called with pass by value option)
EX_IT_TRKORR_ALREADY_EXP - Bereits exportierte Transportaufträge
Data type: DMC_IU_UPGTROptional: No
Call by Reference: No ( called with pass by value option)
EX_IT_TPPROTOCOL - Transportprotokoll
Data type: DMC_IU_TP_PROTOCOLOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
DIFFERENT_CLIENT - Abweichender Mandant (zur RFC Verbindung)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
STEP_ALREADY_DONE - Arbeitsschritt wurde bereits ausgeführt
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PREVIOUS_STEP_NOT_FINISHED - Vorheriger Arbeitsschritt nicht abgeschlossen
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
TPPARAM_NOT_SPECIFIED - Transportparameter nicht definiert
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DMC_IUC_START_EXPORT 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_clnt | TYPE SY-MANDT, " | |||
| lv_different_client | TYPE SY, " | |||
| lt_ex_it_exp_trkorr | TYPE STANDARD TABLE OF DMC_IU_UPGTR, " | |||
| lv_im_jobs | TYPE DMC_IU_DTYPE-INT1, " | |||
| lv_step_already_done | TYPE DMC_IU_DTYPE, " | |||
| lt_ex_it_exp_trkorr_error | TYPE STANDARD TABLE OF DMC_IU_UPGTR, " | |||
| lt_ex_it_trkorr_not_exist | TYPE STANDARD TABLE OF DMC_IU_UPGTR, " | |||
| lv_previous_step_not_finished | TYPE DMC_IU_UPGTR, " | |||
| lv_tpparam_not_specified | TYPE DMC_IU_UPGTR, " | |||
| lt_ex_it_trkorr_already_exp | TYPE STANDARD TABLE OF DMC_IU_UPGTR, " | |||
| lt_ex_it_tpprotocol | TYPE STANDARD TABLE OF DMC_IU_TP_PROTOCOL. " |
|   CALL FUNCTION 'DMC_IUC_START_EXPORT' "MWB-Upgrade: Startet den Export für die Kaskadierung |
| EXPORTING | ||
| IM_CLNT | = lv_im_clnt | |
| IM_JOBS | = lv_im_jobs | |
| TABLES | ||
| EX_IT_EXP_TRKORR | = lt_ex_it_exp_trkorr | |
| EX_IT_EXP_TRKORR_ERROR | = lt_ex_it_exp_trkorr_error | |
| EX_IT_TRKORR_NOT_EXIST | = lt_ex_it_trkorr_not_exist | |
| EX_IT_TRKORR_ALREADY_EXP | = lt_ex_it_trkorr_already_exp | |
| EX_IT_TPPROTOCOL | = lt_ex_it_tpprotocol | |
| EXCEPTIONS | ||
| DIFFERENT_CLIENT = 1 | ||
| STEP_ALREADY_DONE = 2 | ||
| PREVIOUS_STEP_NOT_FINISHED = 3 | ||
| TPPARAM_NOT_SPECIFIED = 4 | ||
| . " DMC_IUC_START_EXPORT | ||
ABAP code using 7.40 inline data declarations to call FM DMC_IUC_START_EXPORT
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 MANDT FROM SY INTO @DATA(ld_im_clnt). | ||||
| "SELECT single INT1 FROM DMC_IU_DTYPE INTO @DATA(ld_im_jobs). | ||||
Search for further information about these or an SAP related objects