SAP DEQUEUE_E_OIISOCISL Function Module for Release lock on object E_OIISOCISL









DEQUEUE_E_OIISOCISL is a standard dequeue e oiisocisl 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_OIISOCISL 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 oiisocisl FM, simply by entering the name DEQUEUE_E_OIISOCISL into the relevant SAP transaction such as SE37 or SE38.

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



Function DEQUEUE_E_OIISOCISL 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_OIISOCISL'"Release lock on object E_OIISOCISL
EXPORTING
* MODE_OIISOCISL = 'E' "Lock mode for table OIISOCISL
* _SYNCHRON = ' ' "Synchonous unlock
* _COLLECT = ' ' "Initially only collect lock
* MANDT = SY-MANDT "01th enqueue argument
* WERKS = "02th enqueue argument
* LGORT = "03th enqueue argument
* SEQNR = "04th enqueue argument
* X_WERKS = ' ' "Fill argument 02 with initial value?
* X_LGORT = ' ' "Fill argument 03 with initial value?
* X_SEQNR = ' ' "Fill argument 04 with initial value?
* _SCOPE = '3' "
.



IMPORTING Parameters details for DEQUEUE_E_OIISOCISL

MODE_OIISOCISL - Lock mode for table OIISOCISL

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: OIISOCISL-MANDT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

WERKS - 02th enqueue argument

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

LGORT - 03th enqueue argument

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

SEQNR - 04th enqueue argument

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

X_WERKS - Fill argument 02 with initial value?

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

X_LGORT - Fill argument 03 with initial value?

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

X_SEQNR - 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_OIISOCISL 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_oiisocisl  TYPE ENQMODE, "   'E'
lv__synchron  TYPE ENQMODE, "   SPACE
lv__collect  TYPE DDENQCOLL, "   ' '
lv_mandt  TYPE OIISOCISL-MANDT, "   SY-MANDT
lv_werks  TYPE OIISOCISL-WERKS, "   
lv_lgort  TYPE OIISOCISL-LGORT, "   
lv_seqnr  TYPE OIISOCISL-SEQNR, "   
lv_x_werks  TYPE OIISOCISL, "   SPACE
lv_x_lgort  TYPE OIISOCISL, "   SPACE
lv_x_seqnr  TYPE OIISOCISL, "   SPACE
lv__scope  TYPE OIISOCISL. "   '3'

  CALL FUNCTION 'DEQUEUE_E_OIISOCISL'  "Release lock on object E_OIISOCISL
    EXPORTING
         MODE_OIISOCISL = lv_mode_oiisocisl
         _SYNCHRON = lv__synchron
         _COLLECT = lv__collect
         MANDT = lv_mandt
         WERKS = lv_werks
         LGORT = lv_lgort
         SEQNR = lv_seqnr
         X_WERKS = lv_x_werks
         X_LGORT = lv_x_lgort
         X_SEQNR = lv_x_seqnr
         _SCOPE = lv__scope
. " DEQUEUE_E_OIISOCISL




ABAP code using 7.40 inline data declarations to call FM DEQUEUE_E_OIISOCISL

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_oiisocisl) = 'E'.
 
DATA(ld__synchron) = ' '.
 
DATA(ld__collect) = ' '.
 
"SELECT single MANDT FROM OIISOCISL INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
"SELECT single WERKS FROM OIISOCISL INTO @DATA(ld_werks).
 
"SELECT single LGORT FROM OIISOCISL INTO @DATA(ld_lgort).
 
"SELECT single SEQNR FROM OIISOCISL INTO @DATA(ld_seqnr).
 
DATA(ld_x_werks) = ' '.
 
DATA(ld_x_lgort) = ' '.
 
DATA(ld_x_seqnr) = ' '.
 
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!