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

Function ISCD_BROK_STM_BAPI_ENQUEUE 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_STM_BAPI_ENQUEUE'"Lock on Broker Report Header.
EXPORTING
I_IDENT = "Broker Report Identification
* I_ENQMODE = 'S' "Lock Mode
EXCEPTIONS
ENQUEUE_FAILED = 1
IMPORTING Parameters details for ISCD_BROK_STM_BAPI_ENQUEUE
I_IDENT - Broker Report Identification
Data type: IBROSTMH-IDENTOptional: No
Call by Reference: No ( called with pass by value option)
I_ENQMODE - Lock Mode
Data type: DD26E-ENQMODEDefault: 'S'
Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ENQUEUE_FAILED - Lock failed
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for ISCD_BROK_STM_BAPI_ENQUEUE 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_i_ident | TYPE IBROSTMH-IDENT, " | |||
| lv_enqueue_failed | TYPE IBROSTMH, " | |||
| lv_i_enqmode | TYPE DD26E-ENQMODE. " 'S' |
|   CALL FUNCTION 'ISCD_BROK_STM_BAPI_ENQUEUE' "Lock on Broker Report Header |
| EXPORTING | ||
| I_IDENT | = lv_i_ident | |
| I_ENQMODE | = lv_i_enqmode | |
| EXCEPTIONS | ||
| ENQUEUE_FAILED = 1 | ||
| . " ISCD_BROK_STM_BAPI_ENQUEUE | ||
ABAP code using 7.40 inline data declarations to call FM ISCD_BROK_STM_BAPI_ENQUEUE
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 IDENT FROM IBROSTMH INTO @DATA(ld_i_ident). | ||||
| "SELECT single ENQMODE FROM DD26E INTO @DATA(ld_i_enqmode). | ||||
| DATA(ld_i_enqmode) | = 'S'. | |||
Search for further information about these or an SAP related objects