SAP ENQUEUE_CATU Function Module for Request lock for object CATU









ENQUEUE_CATU is a standard enqueue catu SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Request lock for object CATU processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for enqueue catu FM, simply by entering the name ENQUEUE_CATU into the relevant SAP transaction such as SE37 or SE38.

Function Group: /1BCDWBEN/SEN0018
Program Name: /1BCDWBEN/SAPLSEN0018
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ENQUEUE_CATU pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'ENQUEUE_CATU'"Request lock for object CATU
  EXPORTING
*  MODE_CATU = 'E' "Lock mode for table CATU
*  _COLLECT = ' ' "Initially only collect lock
*  ABLNR =  "01th enqueue argument
*  VARNT =  "02th enqueue argument
*  PARNR =  "03th enqueue argument
*  X_ABLNR = ' ' "Fill argument 01 with initial value?
*  X_VARNT = ' ' "Fill argument 02 with initial value?
*  X_PARNR = ' ' "Fill argument 03 with initial value?
*  _SCOPE = '2' "
*  _WAIT = ' ' "

EXCEPTIONS
   FOREIGN_LOCK = 1    SYSTEM_FAILURE = 2
.



IMPORTING Parameters details for ENQUEUE_CATU

MODE_CATU - Lock mode for table CATU

Data type: ENQMODE
Default: 'E'
Optional: Yes
Call by Reference: No ( called with pass by value option)

_COLLECT - Initially only collect lock

Data type: DDENQCOLL
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

ABLNR - 01th enqueue argument

Data type: CATU-ABLNR
Optional: Yes
Call by Reference: No ( called with pass by value option)

VARNT - 02th enqueue argument

Data type: CATU-VARNT
Optional: Yes
Call by Reference: No ( called with pass by value option)

PARNR - 03th enqueue argument

Data type: CATU-PARNR
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_ABLNR - Fill argument 01 with initial value?

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_VARNT - Fill argument 02 with initial value?

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_PARNR - Fill argument 03 with initial value?

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

_SCOPE -

Data type:
Default: '2'
Optional: Yes
Call by Reference: No ( called with pass by value option)

_WAIT -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

FOREIGN_LOCK - Object already locked

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

SYSTEM_FAILURE - Internal error from enqueue server

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ENQUEUE_CATU Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_mode_catu  TYPE ENQMODE, "   'E'
lv_foreign_lock  TYPE ENQMODE, "   
lv__collect  TYPE DDENQCOLL, "   ' '
lv_ablnr  TYPE CATU-ABLNR, "   
lv_system_failure  TYPE CATU, "   
lv_varnt  TYPE CATU-VARNT, "   
lv_parnr  TYPE CATU-PARNR, "   
lv_x_ablnr  TYPE CATU, "   SPACE
lv_x_varnt  TYPE CATU, "   SPACE
lv_x_parnr  TYPE CATU, "   SPACE
lv__scope  TYPE CATU, "   '2'
lv__wait  TYPE CATU. "   SPACE

  CALL FUNCTION 'ENQUEUE_CATU'  "Request lock for object CATU
    EXPORTING
         MODE_CATU = lv_mode_catu
         _COLLECT = lv__collect
         ABLNR = lv_ablnr
         VARNT = lv_varnt
         PARNR = lv_parnr
         X_ABLNR = lv_x_ablnr
         X_VARNT = lv_x_varnt
         X_PARNR = lv_x_parnr
         _SCOPE = lv__scope
         _WAIT = lv__wait
    EXCEPTIONS
        FOREIGN_LOCK = 1
        SYSTEM_FAILURE = 2
. " ENQUEUE_CATU




ABAP code using 7.40 inline data declarations to call FM ENQUEUE_CATU

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

DATA(ld_mode_catu) = 'E'.
 
 
DATA(ld__collect) = ' '.
 
"SELECT single ABLNR FROM CATU INTO @DATA(ld_ablnr).
 
 
"SELECT single VARNT FROM CATU INTO @DATA(ld_varnt).
 
"SELECT single PARNR FROM CATU INTO @DATA(ld_parnr).
 
DATA(ld_x_ablnr) = ' '.
 
DATA(ld_x_varnt) = ' '.
 
DATA(ld_x_parnr) = ' '.
 
DATA(ld__scope) = '2'.
 
DATA(ld__wait) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!