ENQUEUE_E_OIKVD SAP Function module - Request lock for object E_OIKVD

ENQUEUE_E_OIKVD is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name ENQUEUE_E_OIKVD into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: DWBEN/SAPLOEN0003
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM ENQUEUE_E_OIKVD - ENQUEUE E OIKVD

CALL FUNCTION 'ENQUEUE_E_OIKVD' "Request lock for object E_OIKVD
* EXPORTING
*   mode_oikvd = 'E'            " enqmode       Lock mode for table OIKVD
*   client = SY-MANDT           " oikvd-client  01th enqueue argument
*   loaddate =                  " oikvd-loaddate  02th enqueue argument
*   shift =                     " oikvd-shift   03th enqueue argument
*   drivercode =                " oikvd-drivercode  04th enqueue argument
*   vehicle =                   " oikvd-vehicle  05th enqueue argument
*   x_loaddate = SPACE          "               Fill argument 02 with initial value?
*   x_shift = SPACE             "               Fill argument 03 with initial value?
*   x_drivercode = SPACE        "               Fill argument 04 with initial value?
*   x_vehicle = SPACE           "               Fill argument 05 with initial value?
*   _scope = '2'                "
*   _wait = SPACE               "
*   _collect = ' '              " ddenqcoll     Initially only collect lock
  EXCEPTIONS
    FOREIGN_LOCK = 1            "               Object already locked
    SYSTEM_FAILURE = 2          "               Internal error from enqueue server
    .  "  ENQUEUE_E_OIKVD

ABAP code example for Function Module ENQUEUE_E_OIKVD

The ABAP code below is a full code listing to execute function module ENQUEUE_E_OIKVD including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA(ld_mode_oikvd) = 'Check type of data required'.
 

SELECT single CLIENT 
  FROM OIKVD 
  INTO @DATA(ld_client).

 

SELECT single LOADDATE 
  FROM OIKVD 
  INTO @DATA(ld_loaddate).

 

SELECT single SHIFT 
  FROM OIKVD 
  INTO @DATA(ld_shift).

 

SELECT single DRIVERCODE 
  FROM OIKVD 
  INTO @DATA(ld_drivercode).

 

SELECT single VEHICLE 
  FROM OIKVD 
  INTO @DATA(ld_vehicle).


DATA(ld_x_loaddate) = 'some text here'.

DATA(ld_x_shift) = 'some text here'.

DATA(ld_x_drivercode) = 'some text here'.

DATA(ld_x_vehicle) = 'some text here'.

DATA(ld__scope) = 'some text here'.

DATA(ld__wait) = 'some text here'.

DATA(ld__collect) = 'Check type of data required'.
.

CALL FUNCTION 'ENQUEUE_E_OIKVD'
* EXPORTING
*   mode_oikvd =                 ld_mode_oikvd
*   client =                     ld_client
*   loaddate =                   ld_loaddate
*   shift =                      ld_shift
*   drivercode =                 ld_drivercode
*   vehicle =                    ld_vehicle
*   x_loaddate =                 ld_x_loaddate
*   x_shift =                    ld_x_shift
*   x_drivercode =               ld_x_drivercode
*   x_vehicle =                  ld_x_vehicle
*   _scope =                     ld__scope
*   _wait =                      ld__wait
*   _collect =                   ld__collect
  EXCEPTIONS
    FOREIGN_LOCK =               1
    SYSTEM_FAILURE =             2
    .  "  ENQUEUE_E_OIKVD

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_mode_oikvd
 
 TYPE ENQMODE ,
ld_client
 
 TYPE OIKVD-CLIENT ,
ld_loaddate
 
 TYPE OIKVD-LOADDATE ,
ld_shift
 
 TYPE OIKVD-SHIFT ,
ld_drivercode
 
 TYPE OIKVD-DRIVERCODE ,
ld_vehicle
 
 TYPE OIKVD-VEHICLE ,
ld_x_loaddate
 
 TYPE STRING ,
ld_x_shift
 
 TYPE STRING ,
ld_x_drivercode
 
 TYPE STRING ,
ld_x_vehicle
 
 TYPE STRING ,
ld__scope
 
 TYPE STRING ,
ld__wait
 
 TYPE STRING ,
ld__collect
 
 TYPE DDENQCOLL .


ld_mode_oikvd = 'Check type of data required'.

SELECT single CLIENT 
  FROM OIKVD 
  INTO ld_client.


SELECT single LOADDATE 
  FROM OIKVD 
  INTO ld_loaddate.


SELECT single SHIFT 
  FROM OIKVD 
  INTO ld_shift.


SELECT single DRIVERCODE 
  FROM OIKVD 
  INTO ld_drivercode.


SELECT single VEHICLE 
  FROM OIKVD 
  INTO ld_vehicle.

ld_x_loaddate = 'some text here'.
ld_x_shift = 'some text here'.
ld_x_drivercode = 'some text here'.
ld_x_vehicle = 'some text here'.
ld__scope = 'some text here'.
ld__wait = 'some text here'.
ld__collect = 'Check type of data required'.