FI_CUST_ENQUEUE_CHECK SAP Function module - Lock all relevant tables

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

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

Pattern for FM FI_CUST_ENQUEUE_CHECK - FI CUST ENQUEUE CHECK

CALL FUNCTION 'FI_CUST_ENQUEUE_CHECK' "Lock all relevant tables
  EXPORTING
*   i_genkey = 'N'              "               Generic key
*   i_genkey = 'N'              "               Generic key
*   i_nocli = 'N'               "               Lock without clients
*   i_nocli = 'N'               "               Lock without clients
    i_okcod =                   "
    i_okcod =                   "               OK code
    i_okcod_to_change_aktyp =   "               OK code to change from displaying
    i_tables =                  "               Tables to be blocked
    i_tables =                  "               Tables to be blocked
  IMPORTING
    e_uname =                   " sy-uname
    e_uname =                   " sy-uname      Name of the blocking user
  EXCEPTIONS
    FOREIGN_LOCK = 1            "               Table already in process
    FOREIGN_LOCK = 1            "               Table already in process
    FOREIGN_LOCK_NOW_DISPLAY = 2  "             System error when blocking
    SYSTEM_FAILURE = 3          "               Table in process, change to displa
    .  "  FI_CUST_ENQUEUE_CHECK

ABAP code example for Function Module FI_CUST_ENQUEUE_CHECK

The ABAP code below is a full code listing to execute function module FI_CUST_ENQUEUE_CHECK 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_e_uname  
 
 TYPE SY-UNAME
,
ld_e_uname  
 
 TYPE SY-UNAME
.


DATA(ld_i_genkey) = 'some text here'.

DATA(ld_i_genkey) = 'some text here'.

DATA(ld_i_nocli) = 'some text here'.

DATA(ld_i_nocli) = 'some text here'.

DATA(ld_i_okcod) = 'some text here'.

DATA(ld_i_okcod) = 'some text here'.

DATA(ld_i_okcod_to_change_aktyp) = 'some text here'.

DATA(ld_i_tables) = 'some text here'.

DATA(ld_i_tables) = 'some text here'.
.

CALL FUNCTION 'FI_CUST_ENQUEUE_CHECK'
  EXPORTING
*   i_genkey =                   ld_i_genkey
*   i_genkey =                   ld_i_genkey
*   i_nocli =                    ld_i_nocli
*   i_nocli =                    ld_i_nocli
    i_okcod =                    ld_i_okcod
    i_okcod =                    ld_i_okcod
    i_okcod_to_change_aktyp =    ld_i_okcod_to_change_aktyp
    i_tables =                   ld_i_tables
    i_tables =                   ld_i_tables
  IMPORTING
    e_uname =                    ld_e_uname
    e_uname =                    ld_e_uname
  EXCEPTIONS
    FOREIGN_LOCK =               1
    FOREIGN_LOCK =               1
    FOREIGN_LOCK_NOW_DISPLAY =    2
    SYSTEM_FAILURE =             3
    .  "  FI_CUST_ENQUEUE_CHECK

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "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_e_uname
 
 TYPE SY-UNAME ,
ld_e_uname
 
 TYPE SY-UNAME ,
ld_i_genkey
 
 TYPE STRING ,
ld_i_genkey
 
 TYPE STRING ,
ld_i_nocli
 
 TYPE STRING ,
ld_i_nocli
 
 TYPE STRING ,
ld_i_okcod
 
 TYPE STRING ,
ld_i_okcod
 
 TYPE STRING ,
ld_i_okcod_to_change_aktyp
 
 TYPE STRING ,
ld_i_tables
 
 TYPE STRING ,
ld_i_tables
 
 TYPE STRING .


ld_i_genkey = 'some text here'.
ld_i_genkey = 'some text here'.
ld_i_nocli = 'some text here'.
ld_i_nocli = 'some text here'.
ld_i_okcod = 'some text here'.
ld_i_okcod = 'some text here'.
ld_i_okcod_to_change_aktyp = 'some text here'.
ld_i_tables = 'some text here'.
ld_i_tables = 'some text here'.