SAP ENQUEUE_E_FQM_GFK Function Module for Request lock for object E_FQM_GFK
ENQUEUE_E_FQM_GFK is a standard enqueue e fqm gfk 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 E_FQM_GFK 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 e fqm gfk FM, simply by entering the name ENQUEUE_E_FQM_GFK into the relevant SAP transaction such as SE37 or SE38.
Function Group: /1BCDWBEN/FEN0017
Program Name: /1BCDWBEN/SAPLFEN0017
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ENQUEUE_E_FQM_GFK 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_E_FQM_GFK'"Request lock for object E_FQM_GFK.
EXPORTING
* MODE_FQM_AIF_SER_INT = 'E' "Lock mode for table FQM_AIF_SER_INT
* ORIGIN_SYSTEM = "01th enqueue argument
* GENERIC_KEY = "02th enqueue argument
* X_ORIGIN_SYSTEM = ' ' "Fill argument 01 with initial value?
* X_GENERIC_KEY = ' ' "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_E_FQM_GFK
MODE_FQM_AIF_SER_INT - Lock mode for table FQM_AIF_SER_INT
Data type: ENQMODEDefault: 'E'
Optional: Yes
Call by Reference: No ( called with pass by value option)
ORIGIN_SYSTEM - 01th enqueue argument
Data type: FQM_AIF_SER_INT-ORIGIN_SYSTEMOptional: Yes
Call by Reference: No ( called with pass by value option)
GENERIC_KEY - 02th enqueue argument
Data type: FQM_AIF_SER_INT-GENERIC_KEYOptional: Yes
Call by Reference: No ( called with pass by value option)
X_ORIGIN_SYSTEM - Fill argument 01 with initial value?
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
X_GENERIC_KEY - 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: DDENQCOLLDefault: ' '
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_E_FQM_GFK 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_fqm_aif_ser_int | TYPE ENQMODE, " 'E' | |||
| lv_origin_system | TYPE FQM_AIF_SER_INT-ORIGIN_SYSTEM, " | |||
| lv_system_failure | TYPE FQM_AIF_SER_INT, " | |||
| lv_generic_key | TYPE FQM_AIF_SER_INT-GENERIC_KEY, " | |||
| lv_x_origin_system | TYPE FQM_AIF_SER_INT, " SPACE | |||
| lv_x_generic_key | TYPE FQM_AIF_SER_INT, " SPACE | |||
| lv__scope | TYPE FQM_AIF_SER_INT, " '2' | |||
| lv__wait | TYPE FQM_AIF_SER_INT, " SPACE | |||
| lv__collect | TYPE DDENQCOLL. " ' ' |
|   CALL FUNCTION 'ENQUEUE_E_FQM_GFK' "Request lock for object E_FQM_GFK |
| EXPORTING | ||
| MODE_FQM_AIF_SER_INT | = lv_mode_fqm_aif_ser_int | |
| ORIGIN_SYSTEM | = lv_origin_system | |
| GENERIC_KEY | = lv_generic_key | |
| X_ORIGIN_SYSTEM | = lv_x_origin_system | |
| X_GENERIC_KEY | = lv_x_generic_key | |
| _SCOPE | = lv__scope | |
| _WAIT | = lv__wait | |
| _COLLECT | = lv__collect | |
| EXCEPTIONS | ||
| FOREIGN_LOCK = 1 | ||
| SYSTEM_FAILURE = 2 | ||
| . " ENQUEUE_E_FQM_GFK | ||
ABAP code using 7.40 inline data declarations to call FM ENQUEUE_E_FQM_GFK
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_fqm_aif_ser_int) | = 'E'. | |||
| "SELECT single ORIGIN_SYSTEM FROM FQM_AIF_SER_INT INTO @DATA(ld_origin_system). | ||||
| "SELECT single GENERIC_KEY FROM FQM_AIF_SER_INT INTO @DATA(ld_generic_key). | ||||
| DATA(ld_x_origin_system) | = ' '. | |||
| DATA(ld_x_generic_key) | = ' '. | |||
| DATA(ld__scope) | = '2'. | |||
| DATA(ld__wait) | = ' '. | |||
| DATA(ld__collect) | = ' '. | |||
Search for further information about these or an SAP related objects