MCP_PLOBJ_ENQUEUE SAP Function module

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

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

Pattern for FM MCP_PLOBJ_ENQUEUE - MCP PLOBJ ENQUEUE

CALL FUNCTION 'MCP_PLOBJ_ENQUEUE' "
  EXPORTING
    i_aktion =                  " t445s-aktion
*   i_plobjs = SPACE            " plobjs
  IMPORTING
    collision_uname =           " seqg3-guname
    enqueue_subrc =             " sy-subrc
  EXCEPTIONS
    FOREIGN_LOCK = 1            "
    INVALID_ENQ_ACTION = 2      "
    SYSTEM_FAILURE = 3          "
    .  "  MCP_PLOBJ_ENQUEUE

ABAP code example for Function Module MCP_PLOBJ_ENQUEUE

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

DATA:
ld_collision_uname  
 
 TYPE SEQG3-GUNAME
,
ld_enqueue_subrc  
 
 TYPE SY-SUBRC
.

 

SELECT single AKTION 
  FROM T445S 
  INTO @DATA(ld_i_aktion).


DATA(ld_i_plobjs) = 'Check type of data required'.
.

CALL FUNCTION 'MCP_PLOBJ_ENQUEUE'
  EXPORTING
    i_aktion =                   ld_i_aktion
*   i_plobjs =                   ld_i_plobjs
  IMPORTING
    collision_uname =            ld_collision_uname
    enqueue_subrc =              ld_enqueue_subrc
  EXCEPTIONS
    FOREIGN_LOCK =               1
    INVALID_ENQ_ACTION =         2
    SYSTEM_FAILURE =             3
    .  "  MCP_PLOBJ_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
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_collision_uname
 
 TYPE SEQG3-GUNAME ,
ld_i_aktion
 
 TYPE T445S-AKTION ,
ld_enqueue_subrc
 
 TYPE SY-SUBRC ,
ld_i_plobjs
 
 TYPE PLOBJS .



SELECT single AKTION 
  FROM T445S 
  INTO ld_i_aktion.

ld_i_plobjs = 'Check type of data required'.