SAP DEQUEUE_E_WSOPE Function Module for Release lock on object E_WSOPE









DEQUEUE_E_WSOPE is a standard dequeue e wsope SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Release lock on object E_WSOPE 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 dequeue e wsope FM, simply by entering the name DEQUEUE_E_WSOPE into the relevant SAP transaction such as SE37 or SE38.

Function Group: /1BCDWBEN/WEN0004
Program Name: /1BCDWBEN/SAPLWEN0004
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function DEQUEUE_E_WSOPE 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 'DEQUEUE_E_WSOPE'"Release lock on object E_WSOPE
  EXPORTING
*  MODE_WSOP = 'E' "Lock mode for table WSOP
*  _SYNCHRON = ' ' "Synchonous unlock
*  _COLLECT = ' ' "Initially only collect lock
*  MANDT = SY-MANDT "01th enqueue argument
*  SKOPF =  "02th enqueue argument
*  SPOSI =  "03th enqueue argument
*  DATUB =  "04th enqueue argument
*  X_SKOPF = ' ' "Fill argument 02 with initial value?
*  X_SPOSI = ' ' "Fill argument 03 with initial value?
*  X_DATUB = ' ' "Fill argument 04 with initial value?
*  _SCOPE = '3' "
.



IMPORTING Parameters details for DEQUEUE_E_WSOPE

MODE_WSOP - Lock mode for table WSOP

Data type: ENQMODE
Default: 'E'
Optional: Yes
Call by Reference: No ( called with pass by value option)

_SYNCHRON - Synchonous unlock

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

_COLLECT - Initially only collect lock

Data type: DDENQCOLL
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

MANDT - 01th enqueue argument

Data type: WSOP-MANDT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

SKOPF - 02th enqueue argument

Data type: WSOP-SKOPF
Optional: Yes
Call by Reference: No ( called with pass by value option)

SPOSI - 03th enqueue argument

Data type: WSOP-SPOSI
Optional: Yes
Call by Reference: No ( called with pass by value option)

DATUB - 04th enqueue argument

Data type: WSOP-DATUB
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_SKOPF - Fill argument 02 with initial value?

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_SPOSI - Fill argument 03 with initial value?

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_DATUB - Fill argument 04 with initial value?

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

_SCOPE -

Data type:
Default: '3'
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for DEQUEUE_E_WSOPE 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_mode_wsop  TYPE ENQMODE, "   'E'
lv__synchron  TYPE ENQMODE, "   SPACE
lv__collect  TYPE DDENQCOLL, "   ' '
lv_mandt  TYPE WSOP-MANDT, "   SY-MANDT
lv_skopf  TYPE WSOP-SKOPF, "   
lv_sposi  TYPE WSOP-SPOSI, "   
lv_datub  TYPE WSOP-DATUB, "   
lv_x_skopf  TYPE WSOP, "   SPACE
lv_x_sposi  TYPE WSOP, "   SPACE
lv_x_datub  TYPE WSOP, "   SPACE
lv__scope  TYPE WSOP. "   '3'

  CALL FUNCTION 'DEQUEUE_E_WSOPE'  "Release lock on object E_WSOPE
    EXPORTING
         MODE_WSOP = lv_mode_wsop
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
         MANDT = lv_mandt
         SKOPF = lv_skopf
         SPOSI = lv_sposi
         DATUB = lv_datub
         X_SKOPF = lv_x_skopf
         X_SPOSI = lv_x_sposi
         X_DATUB = lv_x_datub
         _SCOPE = lv__scope
. " DEQUEUE_E_WSOPE




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_E_WSOPE

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_wsop) = 'E'.
 
DATA(ld__synchron) = ' '.
 
DATA(ld__collect) = ' '.
 
"SELECT single MANDT FROM WSOP INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
"SELECT single SKOPF FROM WSOP INTO @DATA(ld_skopf).
 
"SELECT single SPOSI FROM WSOP INTO @DATA(ld_sposi).
 
"SELECT single DATUB FROM WSOP INTO @DATA(ld_datub).
 
DATA(ld_x_skopf) = ' '.
 
DATA(ld_x_sposi) = ' '.
 
DATA(ld_x_datub) = ' '.
 
DATA(ld__scope) = '3'.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!