ENQUEUE_E_ADRCITY SAP Function module - Request lock for object E_ADRCITY

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

Associated Function Group: DWBEN/SAPLSEN0001
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM ENQUEUE_E_ADRCITY - ENQUEUE E ADRCITY

CALL FUNCTION 'ENQUEUE_E_ADRCITY' "Request lock for object E_ADRCITY
* EXPORTING
*   mode_adrcity = 'E'          " enqmode       Lock mode for table ADRCITY
*   mode_adrcityt = 'E'         " enqmode       Lock mode for table ADRCITYT
*   client = SY-MANDT           " adrcity-client  01th enqueue argument
*   country =                   " adrcity-country  02th enqueue argument
*   city_code =                 " adrcity-city_code  03th enqueue argument
*   langu =                     " adrcityt-langu  04th enqueue argument
*   x_country = SPACE           " ddenqxpar     Fill argument 02 with initial value?
*   x_city_code = SPACE         " ddenqxpar     Fill argument 03 with initial value?
*   x_langu = SPACE             " ddenqxpar     Fill argument 04 with initial value?
*   _scope = '2'                " ddenqscope
*   _wait = SPACE               " ddenqwait
*   _collect = ' '              " ddenqcoll     Initially only collect lock
  EXCEPTIONS
    FOREIGN_LOCK = 1            "               Object already locked
    SYSTEM_FAILURE = 2          "               Internal error from enqueue server
    .  "  ENQUEUE_E_ADRCITY

ABAP code example for Function Module ENQUEUE_E_ADRCITY

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

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

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

 

SELECT single COUNTRY 
  FROM ADRCITY 
  INTO @DATA(ld_country).

 

SELECT single CITY_CODE 
  FROM ADRCITY 
  INTO @DATA(ld_city_code).

 

SELECT single LANGU 
  FROM ADRCITYT 
  INTO @DATA(ld_langu).


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

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

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

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

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

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

CALL FUNCTION 'ENQUEUE_E_ADRCITY'
* EXPORTING
*   mode_adrcity =               ld_mode_adrcity
*   mode_adrcityt =              ld_mode_adrcityt
*   client =                     ld_client
*   country =                    ld_country
*   city_code =                  ld_city_code
*   langu =                      ld_langu
*   x_country =                  ld_x_country
*   x_city_code =                ld_x_city_code
*   x_langu =                    ld_x_langu
*   _scope =                     ld__scope
*   _wait =                      ld__wait
*   _collect =                   ld__collect
  EXCEPTIONS
    FOREIGN_LOCK =               1
    SYSTEM_FAILURE =             2
    .  "  ENQUEUE_E_ADRCITY

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_adrcity
 
 TYPE ENQMODE ,
ld_mode_adrcityt
 
 TYPE ENQMODE ,
ld_client
 
 TYPE ADRCITY-CLIENT ,
ld_country
 
 TYPE ADRCITY-COUNTRY ,
ld_city_code
 
 TYPE ADRCITY-CITY_CODE ,
ld_langu
 
 TYPE ADRCITYT-LANGU ,
ld_x_country
 
 TYPE DDENQXPAR ,
ld_x_city_code
 
 TYPE DDENQXPAR ,
ld_x_langu
 
 TYPE DDENQXPAR ,
ld__scope
 
 TYPE DDENQSCOPE ,
ld__wait
 
 TYPE DDENQWAIT ,
ld__collect
 
 TYPE DDENQCOLL .


ld_mode_adrcity = 'Check type of data required'.
ld_mode_adrcityt = 'Check type of data required'.

SELECT single CLIENT 
  FROM ADRCITY 
  INTO ld_client.


SELECT single COUNTRY 
  FROM ADRCITY 
  INTO ld_country.


SELECT single CITY_CODE 
  FROM ADRCITY 
  INTO ld_city_code.


SELECT single LANGU 
  FROM ADRCITYT 
  INTO ld_langu.

ld_x_country = 'Check type of data required'.
ld_x_city_code = 'Check type of data required'.
ld_x_langu = 'Check type of data required'.
ld__scope = 'Check type of data required'.
ld__wait = 'Check type of data required'.
ld__collect = 'Check type of data required'.