SAP CJDW_ENQUEUE Function Module for NOTRANSL: Sperren Projekt (Fkts.doku beachten!!!)
CJDW_ENQUEUE is a standard cjdw enqueue SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Sperren Projekt (Fkts.doku beachten!!!) 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 cjdw enqueue FM, simply by entering the name CJDW_ENQUEUE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CJDW
Program Name: SAPLCJDW
Main Program: SAPLCJDW
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CJDW_ENQUEUE 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 'CJDW_ENQUEUE'"NOTRANSL: Sperren Projekt (Fkts.doku beachten!!!).
EXPORTING
* OBJECT_ID = ' ' "Key (project or WBS element number)
* VSNMR = ' ' "Version Number
* OTYPE = 'P' "
* SHARED = ' ' "X = block shared
* WAIT = ' ' "Waiting During Lock
* SCOPE = '2' "
EXCEPTIONS
FOREIGN_LOCK = 1 INVALID_TYPE = 2 MISSING_PARAMETER = 3 SYSTEM_FAILURE = 4
IMPORTING Parameters details for CJDW_ENQUEUE
OBJECT_ID - Key (project or WBS element number)
Data type: PROJ-PSPIDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
VSNMR - Version Number
Data type: VSKOPF-VSNMRDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
OTYPE -
Data type: PROJ_ENQ-TYPDefault: 'P'
Optional: Yes
Call by Reference: No ( called with pass by value option)
SHARED - X = block shared
Data type: PROJ_ENQ-TYPDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
WAIT - Waiting During Lock
Data type: PROJ_ENQ-TYPDefault: 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)
EXCEPTIONS details
FOREIGN_LOCK - Object already being processed
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_TYPE - Invalid object type
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
MISSING_PARAMETER - Parameter is missing (object or element list)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SYSTEM_FAILURE - Error has occurred in lock routine
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CJDW_ENQUEUE 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_object_id | TYPE PROJ-PSPID, " SPACE | |||
| lv_foreign_lock | TYPE PROJ, " | |||
| lv_vsnmr | TYPE VSKOPF-VSNMR, " SPACE | |||
| lv_invalid_type | TYPE VSKOPF, " | |||
| lv_otype | TYPE PROJ_ENQ-TYP, " 'P' | |||
| lv_missing_parameter | TYPE PROJ_ENQ, " | |||
| lv_shared | TYPE PROJ_ENQ-TYP, " SPACE | |||
| lv_system_failure | TYPE PROJ_ENQ, " | |||
| lv_wait | TYPE PROJ_ENQ-TYP, " SPACE | |||
| lv_scope | TYPE PROJ_ENQ. " '2' |
|   CALL FUNCTION 'CJDW_ENQUEUE' "NOTRANSL: Sperren Projekt (Fkts.doku beachten!!!) |
| EXPORTING | ||
| OBJECT_ID | = lv_object_id | |
| VSNMR | = lv_vsnmr | |
| OTYPE | = lv_otype | |
| SHARED | = lv_shared | |
| WAIT | = lv_wait | |
| SCOPE | = lv_scope | |
| EXCEPTIONS | ||
| FOREIGN_LOCK = 1 | ||
| INVALID_TYPE = 2 | ||
| MISSING_PARAMETER = 3 | ||
| SYSTEM_FAILURE = 4 | ||
| . " CJDW_ENQUEUE | ||
ABAP code using 7.40 inline data declarations to call FM CJDW_ENQUEUE
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.| "SELECT single PSPID FROM PROJ INTO @DATA(ld_object_id). | ||||
| DATA(ld_object_id) | = ' '. | |||
| "SELECT single VSNMR FROM VSKOPF INTO @DATA(ld_vsnmr). | ||||
| DATA(ld_vsnmr) | = ' '. | |||
| "SELECT single TYP FROM PROJ_ENQ INTO @DATA(ld_otype). | ||||
| DATA(ld_otype) | = 'P'. | |||
| "SELECT single TYP FROM PROJ_ENQ INTO @DATA(ld_shared). | ||||
| DATA(ld_shared) | = ' '. | |||
| "SELECT single TYP FROM PROJ_ENQ INTO @DATA(ld_wait). | ||||
| DATA(ld_wait) | = ' '. | |||
| DATA(ld_scope) | = '2'. | |||
Search for further information about these or an SAP related objects