SAP DX_RUN_BATCH_START Function Module for
DX_RUN_BATCH_START is a standard dx run batch start 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 dx run batch start FM, simply by entering the name DX_RUN_BATCH_START into the relevant SAP transaction such as SE37 or SE38.
Function Group: DX_RUN
Program Name: SAPLDX_RUN
Main Program: SAPLDX_RUN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function DX_RUN_BATCH_START 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 'DX_RUN_BATCH_START'".
EXPORTING
PROJECT = "
SUBPROJECT = "
RUNDEF = "
RESTART = "Checkbox: 'X' = True, ' ' = False
* JOBNAME = "Background job name
* TARGETSERVER = "Server Name
IMPORTING
JOBCOUNT = "Job ID
JOB_RELEASED = "Checkbox: 'X' = True, ' ' = False
EXCEPTIONS
ERROR_OPEN_JOB = 1 ERROR_DELETING_JOB = 2 ERROR_CLOSING_JOB = 3 ERROR_ADDING_STEP = 4 CANCELED_BY_USER = 5 NO_AUTHORITY = 6
IMPORTING Parameters details for DX_RUN_BATCH_START
PROJECT -
Data type: DXRUN-PROJECTOptional: No
Call by Reference: No ( called with pass by value option)
SUBPROJECT -
Data type: DXRUN-SUBPROJECTOptional: No
Call by Reference: No ( called with pass by value option)
RUNDEF -
Data type: DXRUN-RUNDEFOptional: No
Call by Reference: No ( called with pass by value option)
RESTART - Checkbox: 'X' = True, ' ' = False
Data type: DXFIELDS-CHECKBOXOptional: No
Call by Reference: No ( called with pass by value option)
JOBNAME - Background job name
Data type: TBTCJOB-JOBNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
TARGETSERVER - Server Name
Data type: BTCTGTSRVR-SRVNAMEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DX_RUN_BATCH_START
JOBCOUNT - Job ID
Data type: TBTCJOB-JOBCOUNTOptional: No
Call by Reference: Yes
JOB_RELEASED - Checkbox: 'X' = True, ' ' = False
Data type: DXFIELDS-CHECKBOXOptional: No
Call by Reference: Yes
EXCEPTIONS details
ERROR_OPEN_JOB -
Data type:Optional: No
Call by Reference: Yes
ERROR_DELETING_JOB -
Data type:Optional: No
Call by Reference: Yes
ERROR_CLOSING_JOB -
Data type:Optional: No
Call by Reference: Yes
ERROR_ADDING_STEP -
Data type:Optional: No
Call by Reference: Yes
CANCELED_BY_USER -
Data type:Optional: No
Call by Reference: Yes
NO_AUTHORITY -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for DX_RUN_BATCH_START 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_project | TYPE DXRUN-PROJECT, " | |||
| lv_jobcount | TYPE TBTCJOB-JOBCOUNT, " | |||
| lv_error_open_job | TYPE TBTCJOB, " | |||
| lv_subproject | TYPE DXRUN-SUBPROJECT, " | |||
| lv_job_released | TYPE DXFIELDS-CHECKBOX, " | |||
| lv_error_deleting_job | TYPE DXFIELDS, " | |||
| lv_rundef | TYPE DXRUN-RUNDEF, " | |||
| lv_error_closing_job | TYPE DXRUN, " | |||
| lv_restart | TYPE DXFIELDS-CHECKBOX, " | |||
| lv_error_adding_step | TYPE DXFIELDS, " | |||
| lv_jobname | TYPE TBTCJOB-JOBNAME, " | |||
| lv_canceled_by_user | TYPE TBTCJOB, " | |||
| lv_no_authority | TYPE TBTCJOB, " | |||
| lv_targetserver | TYPE BTCTGTSRVR-SRVNAME. " |
|   CALL FUNCTION 'DX_RUN_BATCH_START' " |
| EXPORTING | ||
| PROJECT | = lv_project | |
| SUBPROJECT | = lv_subproject | |
| RUNDEF | = lv_rundef | |
| RESTART | = lv_restart | |
| JOBNAME | = lv_jobname | |
| TARGETSERVER | = lv_targetserver | |
| IMPORTING | ||
| JOBCOUNT | = lv_jobcount | |
| JOB_RELEASED | = lv_job_released | |
| EXCEPTIONS | ||
| ERROR_OPEN_JOB = 1 | ||
| ERROR_DELETING_JOB = 2 | ||
| ERROR_CLOSING_JOB = 3 | ||
| ERROR_ADDING_STEP = 4 | ||
| CANCELED_BY_USER = 5 | ||
| NO_AUTHORITY = 6 | ||
| . " DX_RUN_BATCH_START | ||
ABAP code using 7.40 inline data declarations to call FM DX_RUN_BATCH_START
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 PROJECT FROM DXRUN INTO @DATA(ld_project). | ||||
| "SELECT single JOBCOUNT FROM TBTCJOB INTO @DATA(ld_jobcount). | ||||
| "SELECT single SUBPROJECT FROM DXRUN INTO @DATA(ld_subproject). | ||||
| "SELECT single CHECKBOX FROM DXFIELDS INTO @DATA(ld_job_released). | ||||
| "SELECT single RUNDEF FROM DXRUN INTO @DATA(ld_rundef). | ||||
| "SELECT single CHECKBOX FROM DXFIELDS INTO @DATA(ld_restart). | ||||
| "SELECT single JOBNAME FROM TBTCJOB INTO @DATA(ld_jobname). | ||||
| "SELECT single SRVNAME FROM BTCTGTSRVR INTO @DATA(ld_targetserver). | ||||
Search for further information about these or an SAP related objects