GMAVC_SET_GLOBAL_ENQUEUE SAP Function module - Global Enqueues for Control Ledgers

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

Associated Function Group: GMAVC_RECONSTRUCT
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM GMAVC_SET_GLOBAL_ENQUEUE - GMAVC SET GLOBAL ENQUEUE

CALL FUNCTION 'GMAVC_SET_GLOBAL_ENQUEUE' "Global Enqueues for Control Ledgers
  EXPORTING
    i_company_code =            " bukrs         Company Code
    i_fiscyear =                " gjahr         Fiscal Year
    i_aldnr =                   " buavc_aldnr   Availability Control Ledger
    i_arcty =                   " buavc_arcty   Record Type of an Availability Control Ledger
    i_flg_collect =             " ddenqcoll     Flag whether locks should only be collected first
  EXCEPTIONS
    ENQUEUE_ERROR = 1           "               Error on enqueue request
    .  "  GMAVC_SET_GLOBAL_ENQUEUE

ABAP code example for Function Module GMAVC_SET_GLOBAL_ENQUEUE

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

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

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

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

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

CALL FUNCTION 'GMAVC_SET_GLOBAL_ENQUEUE'
  EXPORTING
    i_company_code =             ld_i_company_code
    i_fiscyear =                 ld_i_fiscyear
    i_aldnr =                    ld_i_aldnr
    i_arcty =                    ld_i_arcty
    i_flg_collect =              ld_i_flg_collect
  EXCEPTIONS
    ENQUEUE_ERROR =              1
    .  "  GMAVC_SET_GLOBAL_ENQUEUE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "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_i_company_code
 
 TYPE BUKRS ,
ld_i_fiscyear
 
 TYPE GJAHR ,
ld_i_aldnr
 
 TYPE BUAVC_ALDNR ,
ld_i_arcty
 
 TYPE BUAVC_ARCTY ,
ld_i_flg_collect
 
 TYPE DDENQCOLL .


ld_i_company_code = 'Check type of data required'.
ld_i_fiscyear = 'Check type of data required'.
ld_i_aldnr = 'Check type of data required'.
ld_i_arcty = 'Check type of data required'.
ld_i_flg_collect = 'Check type of data required'.