SAP ENQUEUE_E_BPE_DISPATCH Function Module for Request lock for object E_BPE_DISPATCH
ENQUEUE_E_BPE_DISPATCH is a standard enqueue e bpe dispatch SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Request lock for object E_BPE_DISPATCH 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 enqueue e bpe dispatch FM, simply by entering the name ENQUEUE_E_BPE_DISPATCH into the relevant SAP transaction such as SE37 or SE38.
Function Group: /1BCDWBEN/SEN0014
Program Name: /1BCDWBEN/SAPLSEN0014
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function ENQUEUE_E_BPE_DISPATCH 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 'ENQUEUE_E_BPE_DISPATCH'"Request lock for object E_BPE_DISPATCH.
EXPORTING
* MODE_SWFINB_DISPLOCK = 'E' "Lock mode for table SWFINB_DISPLOCK
* MANDT = SY-MANDT "01th enqueue argument
* TASK = "02th enqueue argument
* X_TASK = ' ' "Fill argument 02 with initial value?
* _SCOPE = '2' "
* _WAIT = ' ' "
* _COLLECT = ' ' "Initially only collect lock
EXCEPTIONS
FOREIGN_LOCK = 1 SYSTEM_FAILURE = 2
IMPORTING Parameters details for ENQUEUE_E_BPE_DISPATCH
MODE_SWFINB_DISPLOCK - Lock mode for table SWFINB_DISPLOCK
Data type: ENQMODEDefault: 'E'
Optional: Yes
Call by Reference: No ( called with pass by value option)
MANDT - 01th enqueue argument
Data type: SWFINB_DISPLOCK-MANDTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
TASK - 02th enqueue argument
Data type: SWFINB_DISPLOCK-TASKOptional: Yes
Call by Reference: No ( called with pass by value option)
X_TASK - Fill argument 02 with initial value?
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
_SCOPE -
Data type:Default: '2'
Optional: Yes
Call by Reference: No ( called with pass by value option)
_WAIT -
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
_COLLECT - Initially only collect lock
Data type: DDENQCOLLDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FOREIGN_LOCK - Object already locked
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEM_FAILURE - Internal error from enqueue server
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ENQUEUE_E_BPE_DISPATCH 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_foreign_lock | TYPE STRING, " | |||
lv_mode_swfinb_displock | TYPE ENQMODE, " 'E' | |||
lv_mandt | TYPE SWFINB_DISPLOCK-MANDT, " SY-MANDT | |||
lv_system_failure | TYPE SWFINB_DISPLOCK, " | |||
lv_task | TYPE SWFINB_DISPLOCK-TASK, " | |||
lv_x_task | TYPE SWFINB_DISPLOCK, " SPACE | |||
lv__scope | TYPE SWFINB_DISPLOCK, " '2' | |||
lv__wait | TYPE SWFINB_DISPLOCK, " SPACE | |||
lv__collect | TYPE DDENQCOLL. " ' ' |
  CALL FUNCTION 'ENQUEUE_E_BPE_DISPATCH' "Request lock for object E_BPE_DISPATCH |
EXPORTING | ||
MODE_SWFINB_DISPLOCK | = lv_mode_swfinb_displock | |
MANDT | = lv_mandt | |
TASK | = lv_task | |
X_TASK | = lv_x_task | |
_SCOPE | = lv__scope | |
_WAIT | = lv__wait | |
_COLLECT | = lv__collect | |
EXCEPTIONS | ||
FOREIGN_LOCK = 1 | ||
SYSTEM_FAILURE = 2 | ||
. " ENQUEUE_E_BPE_DISPATCH |
ABAP code using 7.40 inline data declarations to call FM ENQUEUE_E_BPE_DISPATCH
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.DATA(ld_mode_swfinb_displock) | = 'E'. | |||
"SELECT single MANDT FROM SWFINB_DISPLOCK INTO @DATA(ld_mandt). | ||||
DATA(ld_mandt) | = SY-MANDT. | |||
"SELECT single TASK FROM SWFINB_DISPLOCK INTO @DATA(ld_task). | ||||
DATA(ld_x_task) | = ' '. | |||
DATA(ld__scope) | = '2'. | |||
DATA(ld__wait) | = ' '. | |||
DATA(ld__collect) | = ' '. | |||
Search for further information about these or an SAP related objects