SAP ISCD_BROK_POST_START Function Module for Broker Report: Start Job
ISCD_BROK_POST_START is a standard iscd brok post start SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Broker Report: Start Job 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 iscd brok post start FM, simply by entering the name ISCD_BROK_POST_START into the relevant SAP transaction such as SE37 or SE38.
Function Group: IBR08
Program Name: SAPLIBR08
Main Program: SAPLIBR08
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISCD_BROK_POST_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 'ISCD_BROK_POST_START'"Broker Report: Start Job.
EXPORTING
I_LAUFD = "
* EXTRA_PARAMS = "
I_LAUFI = "
* I_XSIMU = ' ' "
* I_XCOPY = ' ' "
* I_COPYD = "
* I_COPYI = "
* I_XSTRF = 'X' "Start Now
* I_STRDT = SY-DATUM "
* I_STRZT = "
IMPORTING
E_RES = "
EXCEPTIONS
NO_SUCCESS = 1
IMPORTING Parameters details for ISCD_BROK_POST_START
I_LAUFD -
Data type: DFK_JC_CNTR_PROD-LAUFDOptional: No
Call by Reference: No ( called with pass by value option)
EXTRA_PARAMS -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
I_LAUFI -
Data type: DFK_JC_CNTR_PROD-LAUFIOptional: No
Call by Reference: No ( called with pass by value option)
I_XSIMU -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_XCOPY -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_COPYD -
Data type: DFK_JC_CNTR_PROD-LAUFDOptional: Yes
Call by Reference: No ( called with pass by value option)
I_COPYI -
Data type: DFK_JC_CNTR_PROD-LAUFIOptional: Yes
Call by Reference: No ( called with pass by value option)
I_XSTRF - Start Now
Data type: CDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_STRDT -
Data type: SY-DATUMDefault: SY-DATUM
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_STRZT -
Data type: SY-UZEITOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for ISCD_BROK_POST_START
E_RES -
Data type: COptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_SUCCESS -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISCD_BROK_POST_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_e_res | TYPE C, " | |||
| lv_i_laufd | TYPE DFK_JC_CNTR_PROD-LAUFD, " | |||
| lv_no_success | TYPE DFK_JC_CNTR_PROD, " | |||
| lv_extra_params | TYPE DFK_JC_CNTR_PROD, " | |||
| lv_i_laufi | TYPE DFK_JC_CNTR_PROD-LAUFI, " | |||
| lv_i_xsimu | TYPE C, " SPACE | |||
| lv_i_xcopy | TYPE C, " SPACE | |||
| lv_i_copyd | TYPE DFK_JC_CNTR_PROD-LAUFD, " | |||
| lv_i_copyi | TYPE DFK_JC_CNTR_PROD-LAUFI, " | |||
| lv_i_xstrf | TYPE C, " 'X' | |||
| lv_i_strdt | TYPE SY-DATUM, " SY-DATUM | |||
| lv_i_strzt | TYPE SY-UZEIT. " |
|   CALL FUNCTION 'ISCD_BROK_POST_START' "Broker Report: Start Job |
| EXPORTING | ||
| I_LAUFD | = lv_i_laufd | |
| EXTRA_PARAMS | = lv_extra_params | |
| I_LAUFI | = lv_i_laufi | |
| I_XSIMU | = lv_i_xsimu | |
| I_XCOPY | = lv_i_xcopy | |
| I_COPYD | = lv_i_copyd | |
| I_COPYI | = lv_i_copyi | |
| I_XSTRF | = lv_i_xstrf | |
| I_STRDT | = lv_i_strdt | |
| I_STRZT | = lv_i_strzt | |
| IMPORTING | ||
| E_RES | = lv_e_res | |
| EXCEPTIONS | ||
| NO_SUCCESS = 1 | ||
| . " ISCD_BROK_POST_START | ||
ABAP code using 7.40 inline data declarations to call FM ISCD_BROK_POST_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 LAUFD FROM DFK_JC_CNTR_PROD INTO @DATA(ld_i_laufd). | ||||
| "SELECT single LAUFI FROM DFK_JC_CNTR_PROD INTO @DATA(ld_i_laufi). | ||||
| DATA(ld_i_xsimu) | = ' '. | |||
| DATA(ld_i_xcopy) | = ' '. | |||
| "SELECT single LAUFD FROM DFK_JC_CNTR_PROD INTO @DATA(ld_i_copyd). | ||||
| "SELECT single LAUFI FROM DFK_JC_CNTR_PROD INTO @DATA(ld_i_copyi). | ||||
| DATA(ld_i_xstrf) | = 'X'. | |||
| "SELECT single DATUM FROM SY INTO @DATA(ld_i_strdt). | ||||
| DATA(ld_i_strdt) | = SY-DATUM. | |||
| "SELECT single UZEIT FROM SY INTO @DATA(ld_i_strzt). | ||||
Search for further information about these or an SAP related objects