SAP ENQUEUE_E_CGPL_MAPPING Function Module for Request lock for object E_CGPL_MAPPING
ENQUEUE_E_CGPL_MAPPING is a standard enqueue e cgpl mapping 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_CGPL_MAPPING 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 cgpl mapping FM, simply by entering the name ENQUEUE_E_CGPL_MAPPING into the relevant SAP transaction such as SE37 or SE38.
Function Group: /1BCDWBEN/CEN0005
Program Name: /1BCDWBEN/SAPLCEN0005
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function ENQUEUE_E_CGPL_MAPPING 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_CGPL_MAPPING'"Request lock for object E_CGPL_MAPPING.
EXPORTING
* MODE_CGPL_MAPPING = 'E' "Lock mode for table CGPL_MAPPING
* CLIENT = SY-MANDT "01th enqueue argument
* APPLICATION = "02th enqueue argument
* ALTERNATIVE = "03th enqueue argument
* X_APPLICATION = ' ' "Fill argument 02 with initial value?
* X_ALTERNATIVE = ' ' "Fill argument 03 with initial value?
* _SCOPE = '2' "
* _WAIT = ' ' "
* _COLLECT = ' ' "Initially only collect lock
EXCEPTIONS
FOREIGN_LOCK = 1 SYSTEM_FAILURE = 2
IMPORTING Parameters details for ENQUEUE_E_CGPL_MAPPING
MODE_CGPL_MAPPING - Lock mode for table CGPL_MAPPING
Data type: ENQMODEDefault: 'E'
Optional: Yes
Call by Reference: No ( called with pass by value option)
CLIENT - 01th enqueue argument
Data type: CGPL_MAPPING-CLIENTDefault: SY-MANDT
Optional: Yes
Call by Reference: No ( called with pass by value option)
APPLICATION - 02th enqueue argument
Data type: CGPL_MAPPING-APPLICATIONOptional: Yes
Call by Reference: No ( called with pass by value option)
ALTERNATIVE - 03th enqueue argument
Data type: CGPL_MAPPING-ALTERNATIVEOptional: Yes
Call by Reference: No ( called with pass by value option)
X_APPLICATION - Fill argument 02 with initial value?
Data type:Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
X_ALTERNATIVE - Fill argument 03 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_CGPL_MAPPING 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_cgpl_mapping | TYPE ENQMODE, " 'E' | |||
lv_client | TYPE CGPL_MAPPING-CLIENT, " SY-MANDT | |||
lv_system_failure | TYPE CGPL_MAPPING, " | |||
lv_application | TYPE CGPL_MAPPING-APPLICATION, " | |||
lv_alternative | TYPE CGPL_MAPPING-ALTERNATIVE, " | |||
lv_x_application | TYPE CGPL_MAPPING, " SPACE | |||
lv_x_alternative | TYPE CGPL_MAPPING, " SPACE | |||
lv__scope | TYPE CGPL_MAPPING, " '2' | |||
lv__wait | TYPE CGPL_MAPPING, " SPACE | |||
lv__collect | TYPE DDENQCOLL. " ' ' |
  CALL FUNCTION 'ENQUEUE_E_CGPL_MAPPING' "Request lock for object E_CGPL_MAPPING |
EXPORTING | ||
MODE_CGPL_MAPPING | = lv_mode_cgpl_mapping | |
CLIENT | = lv_client | |
APPLICATION | = lv_application | |
ALTERNATIVE | = lv_alternative | |
X_APPLICATION | = lv_x_application | |
X_ALTERNATIVE | = lv_x_alternative | |
_SCOPE | = lv__scope | |
_WAIT | = lv__wait | |
_COLLECT | = lv__collect | |
EXCEPTIONS | ||
FOREIGN_LOCK = 1 | ||
SYSTEM_FAILURE = 2 | ||
. " ENQUEUE_E_CGPL_MAPPING |
ABAP code using 7.40 inline data declarations to call FM ENQUEUE_E_CGPL_MAPPING
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_cgpl_mapping) | = 'E'. | |||
"SELECT single CLIENT FROM CGPL_MAPPING INTO @DATA(ld_client). | ||||
DATA(ld_client) | = SY-MANDT. | |||
"SELECT single APPLICATION FROM CGPL_MAPPING INTO @DATA(ld_application). | ||||
"SELECT single ALTERNATIVE FROM CGPL_MAPPING INTO @DATA(ld_alternative). | ||||
DATA(ld_x_application) | = ' '. | |||
DATA(ld_x_alternative) | = ' '. | |||
DATA(ld__scope) | = '2'. | |||
DATA(ld__wait) | = ' '. | |||
DATA(ld__collect) | = ' '. | |||
Search for further information about these or an SAP related objects