DEQUEUE_EFAGL_FCVDELTA SAP Function module - Release lock on object EFAGL_FCVDELTA

DEQUEUE_EFAGL_FCVDELTA 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 DEQUEUE_EFAGL_FCVDELTA into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM DEQUEUE_EFAGL_FCVDELTA - DEQUEUE EFAGL FCVDELTA

CALL FUNCTION 'DEQUEUE_EFAGL_FCVDELTA' "Release lock on object EFAGL_FCVDELTA
* EXPORTING
*   mode_fagl_fcv_e_delta = 'E'  " enqmode      Lock mode for table FAGL_FCV_E_DELTA
*   mandt = SY-MANDT            " fagl_fcv_e_delta-mandt  01th enqueue argument
*   ccode =                     " fagl_fcv_e_delta-ccode  02th enqueue argument
*   val_area =                  " fagl_fcv_e_delta-val_area  03th enqueue argument
*   x_ccode = SPACE             "               Fill argument 02 with initial value?
*   x_val_area = SPACE          "               Fill argument 03 with initial value?
*   _scope = '3'                "
*   _synchron = SPACE           "               Synchonous unlock
*   _collect = ' '              " ddenqcoll     Initially only collect lock
    .  "  DEQUEUE_EFAGL_FCVDELTA

ABAP code example for Function Module DEQUEUE_EFAGL_FCVDELTA

The ABAP code below is a full code listing to execute function module DEQUEUE_EFAGL_FCVDELTA 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_fagl_fcv_e_delta) = 'Check type of data required'.


DATA(ld_mandt) = Check type of data required


DATA(ld_ccode) = some text here


DATA(ld_val_area) = some text here

DATA(ld_x_ccode) = 'some text here'.

DATA(ld_x_val_area) = 'some text here'.

DATA(ld__scope) = 'some text here'.

DATA(ld__synchron) = 'some text here'.

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

CALL FUNCTION 'DEQUEUE_EFAGL_FCVDELTA'
* EXPORTING
*   mode_fagl_fcv_e_delta =      ld_mode_fagl_fcv_e_delta
*   mandt =                      ld_mandt
*   ccode =                      ld_ccode
*   val_area =                   ld_val_area
*   x_ccode =                    ld_x_ccode
*   x_val_area =                 ld_x_val_area
*   _scope =                     ld__scope
*   _synchron =                  ld__synchron
*   _collect =                   ld__collect
    .  "  DEQUEUE_EFAGL_FCVDELTA

IF SY-SUBRC EQ 0.
  "All OK
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_fagl_fcv_e_delta
 
 TYPE ENQMODE ,
ld_mandt
 
 TYPE FAGL_FCV_E_DELTA-MANDT ,
ld_ccode
 
 TYPE FAGL_FCV_E_DELTA-CCODE ,
ld_val_area
 
 TYPE FAGL_FCV_E_DELTA-VAL_AREA ,
ld_x_ccode
 
 TYPE STRING ,
ld_x_val_area
 
 TYPE STRING ,
ld__scope
 
 TYPE STRING ,
ld__synchron
 
 TYPE STRING ,
ld__collect
 
 TYPE DDENQCOLL .


ld_mode_fagl_fcv_e_delta = 'Check type of data required'.

ld_mandt = Check type of data required

ld_ccode = some text here

ld_val_area = some text here
ld_x_ccode = 'some text here'.
ld_x_val_area = 'some text here'.
ld__scope = 'some text here'.
ld__synchron = 'some text here'.
ld__collect = 'Check type of data required'.