SAP ENQUEUE_ECMS_OBJECT_SKY Function Module for Request lock for object ECMS_OBJECT_SKY









ENQUEUE_ECMS_OBJECT_SKY is a standard enqueue ecms object sky 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 ECMS_OBJECT_SKY 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 ecms object sky FM, simply by entering the name ENQUEUE_ECMS_OBJECT_SKY into the relevant SAP transaction such as SE37 or SE38.

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



Function ENQUEUE_ECMS_OBJECT_SKY 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_ECMS_OBJECT_SKY'"Request lock for object ECMS_OBJECT_SKY
EXPORTING
* MODE_CMS_STR_LOCK_SKY = 'E' "Lock mode for table CMS_STR_LOCK_SKY
* _COLLECT = ' ' "Initially only collect lock
* CATEGORY = "01th enqueue argument
* TYPE = "02th enqueue argument
* ID = "03th enqueue argument
* X_CATEGORY = ' ' "Fill argument 01 with initial value?
* X_TYPE = ' ' "Fill argument 02 with initial value?
* X_ID = ' ' "Fill argument 03 with initial value?
* _SCOPE = '2' "
* _WAIT = ' ' "

EXCEPTIONS
FOREIGN_LOCK = 1 SYSTEM_FAILURE = 2
.



IMPORTING Parameters details for ENQUEUE_ECMS_OBJECT_SKY

MODE_CMS_STR_LOCK_SKY - Lock mode for table CMS_STR_LOCK_SKY

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)

CATEGORY - 01th enqueue argument

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

TYPE - 02th enqueue argument

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

ID - 03th enqueue argument

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

X_CATEGORY - Fill argument 01 with initial value?

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

X_TYPE - Fill argument 02 with initial value?

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

X_ID - 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_ECMS_OBJECT_SKY 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_foreign_lock  TYPE STRING, "   
lv_mode_cms_str_lock_sky  TYPE ENQMODE, "   'E'
lv__collect  TYPE DDENQCOLL, "   ' '
lv_category  TYPE CMS_STR_LOCK_SKY-CATEGORY, "   
lv_system_failure  TYPE CMS_STR_LOCK_SKY, "   
lv_type  TYPE CMS_STR_LOCK_SKY-TYPE, "   
lv_id  TYPE CMS_STR_LOCK_SKY-ID, "   
lv_x_category  TYPE CMS_STR_LOCK_SKY, "   SPACE
lv_x_type  TYPE CMS_STR_LOCK_SKY, "   SPACE
lv_x_id  TYPE CMS_STR_LOCK_SKY, "   SPACE
lv__scope  TYPE CMS_STR_LOCK_SKY, "   '2'
lv__wait  TYPE CMS_STR_LOCK_SKY. "   SPACE

  CALL FUNCTION 'ENQUEUE_ECMS_OBJECT_SKY'  "Request lock for object ECMS_OBJECT_SKY
    EXPORTING
         MODE_CMS_STR_LOCK_SKY = lv_mode_cms_str_lock_sky
         _COLLECT = lv__collect
         CATEGORY = lv_category
         TYPE = lv_type
         ID = lv_id
         X_CATEGORY = lv_x_category
         X_TYPE = lv_x_type
         X_ID = lv_x_id
         _SCOPE = lv__scope
         _WAIT = lv__wait
    EXCEPTIONS
        FOREIGN_LOCK = 1
        SYSTEM_FAILURE = 2
. " ENQUEUE_ECMS_OBJECT_SKY




ABAP code using 7.40 inline data declarations to call FM ENQUEUE_ECMS_OBJECT_SKY

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_cms_str_lock_sky) = 'E'.
 
DATA(ld__collect) = ' '.
 
"SELECT single CATEGORY FROM CMS_STR_LOCK_SKY INTO @DATA(ld_category).
 
 
"SELECT single TYPE FROM CMS_STR_LOCK_SKY INTO @DATA(ld_type).
 
"SELECT single ID FROM CMS_STR_LOCK_SKY INTO @DATA(ld_id).
 
DATA(ld_x_category) = ' '.
 
DATA(ld_x_type) = ' '.
 
DATA(ld_x_id) = ' '.
 
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!