CJDW_ENQUEUE SAP Function module

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

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

Pattern for FM CJDW_ENQUEUE - CJDW ENQUEUE

CALL FUNCTION 'CJDW_ENQUEUE' "
* EXPORTING
*   object_id = SPACE           " proj-pspid    Key (project or WBS element number)
*   vsnmr = SPACE               " vskopf-vsnmr  Version Number
*   otype = 'P'                 " proj_enq-typ
*   shared = SPACE              " proj_enq-typ  X = block shared
*   wait = SPACE                " proj_enq-typ  Waiting During Lock
*   scope = '2'                 "
  EXCEPTIONS
    FOREIGN_LOCK = 1            "               Object already being processed
    INVALID_TYPE = 2            "               Invalid object type
    MISSING_PARAMETER = 3       "               Parameter is missing (object or element list)
    SYSTEM_FAILURE = 4          "               Error has occurred in lock routine
    .  "  CJDW_ENQUEUE

ABAP code example for Function Module CJDW_ENQUEUE

The ABAP code below is a full code listing to execute function module CJDW_ENQUEUE 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).

 

SELECT single PSPID 
  FROM PROJ 
  INTO @DATA(ld_object_id).

 

SELECT single VSNMR 
  FROM VSKOPF 
  INTO @DATA(ld_vsnmr).



DATA(ld_otype) = some text here


DATA(ld_shared) = some text here


DATA(ld_wait) = some text here

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

CALL FUNCTION 'CJDW_ENQUEUE'
* EXPORTING
*   object_id =                  ld_object_id
*   vsnmr =                      ld_vsnmr
*   otype =                      ld_otype
*   shared =                     ld_shared
*   wait =                       ld_wait
*   scope =                      ld_scope
  EXCEPTIONS
    FOREIGN_LOCK =               1
    INVALID_TYPE =               2
    MISSING_PARAMETER =          3
    SYSTEM_FAILURE =             4
    .  "  CJDW_ENQUEUE

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
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "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_object_id
 
 TYPE PROJ-PSPID ,
ld_vsnmr
 
 TYPE VSKOPF-VSNMR ,
ld_otype
 
 TYPE PROJ_ENQ-TYP ,
ld_shared
 
 TYPE PROJ_ENQ-TYP ,
ld_wait
 
 TYPE PROJ_ENQ-TYP ,
ld_scope
 
 TYPE STRING .



SELECT single PSPID 
  FROM PROJ 
  INTO ld_object_id.


SELECT single VSNMR 
  FROM VSKOPF 
  INTO ld_vsnmr.


ld_otype = some text here

ld_shared = some text here

ld_wait = some text here
ld_scope = 'some text here'.