SAP ENQUEUE_EFIVIMIME Function Module for Request lock for object EFIVIMIME









ENQUEUE_EFIVIMIME is a standard enqueue efivimime 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 EFIVIMIME 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 efivimime FM, simply by entering the name ENQUEUE_EFIVIMIME into the relevant SAP transaction such as SE37 or SE38.

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



Function ENQUEUE_EFIVIMIME 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_EFIVIMIME'"Request lock for object EFIVIMIME
  EXPORTING
*  MODE_VIMIMEHEAD = 'E' "Lock mode for table VIMIMEHEAD
*  MODE_VIMIMELINE = 'E' "Lock mode for table VIMIMELINE
*  MANDT = SY-MANDT "01th enqueue argument
*  SMIMEID =  "02th enqueue argument
*  X_SMIMEID = ' ' "Fill argument 02 with initial value?
*  _SCOPE = '2' "
*  _WAIT = ' ' "
*  _COLLECT = ' ' "Initially only collect lock

EXCEPTIONS
   FOREIGN_LOCK = 1    SYSTEM_FAILURE = 2
.



IMPORTING Parameters details for ENQUEUE_EFIVIMIME

MODE_VIMIMEHEAD - Lock mode for table VIMIMEHEAD

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

MODE_VIMIMELINE - Lock mode for table VIMIMELINE

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

MANDT - 01th enqueue argument

Data type: VIMIMEHEAD-MANDT
Default: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)

SMIMEID - 02th enqueue argument

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

X_SMIMEID - Fill argument 02 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)

_COLLECT - Initially only collect lock

Data type: DDENQCOLL
Default: ' '
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_EFIVIMIME 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_vimimehead  TYPE ENQMODE, "   'E'
lv_system_failure  TYPE ENQMODE, "   
lv_mode_vimimeline  TYPE ENQMODE, "   'E'
lv_mandt  TYPE VIMIMEHEAD-MANDT, "   SY-MANDT
lv_smimeid  TYPE VIMIMEHEAD-SMIMEID, "   
lv_x_smimeid  TYPE VIMIMEHEAD, "   SPACE
lv__scope  TYPE VIMIMEHEAD, "   '2'
lv__wait  TYPE VIMIMEHEAD, "   SPACE
lv__collect  TYPE DDENQCOLL. "   ' '

  CALL FUNCTION 'ENQUEUE_EFIVIMIME'  "Request lock for object EFIVIMIME
    EXPORTING
         MODE_VIMIMEHEAD = lv_mode_vimimehead
         MODE_VIMIMELINE = lv_mode_vimimeline
         MANDT = lv_mandt
         SMIMEID = lv_smimeid
         X_SMIMEID = lv_x_smimeid
         _SCOPE = lv__scope
         _WAIT = lv__wait
         _COLLECT = lv__collect
    EXCEPTIONS
        FOREIGN_LOCK = 1
        SYSTEM_FAILURE = 2
. " ENQUEUE_EFIVIMIME




ABAP code using 7.40 inline data declarations to call FM ENQUEUE_EFIVIMIME

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_vimimehead) = 'E'.
 
 
DATA(ld_mode_vimimeline) = 'E'.
 
"SELECT single MANDT FROM VIMIMEHEAD INTO @DATA(ld_mandt).
DATA(ld_mandt) = SY-MANDT.
 
"SELECT single SMIMEID FROM VIMIMEHEAD INTO @DATA(ld_smimeid).
 
DATA(ld_x_smimeid) = ' '.
 
DATA(ld__scope) = '2'.
 
DATA(ld__wait) = ' '.
 
DATA(ld__collect) = ' '.
 


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!