SAP UPC_DATA_ENQ_DEQ Function Module for Locking Transaction Data
UPC_DATA_ENQ_DEQ is a standard upc data enq deq SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Locking Transaction Data 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 upc data enq deq FM, simply by entering the name UPC_DATA_ENQ_DEQ into the relevant SAP transaction such as SE37 or SE38.
Function Group: UPC1
Program Name: SAPLUPC1
Main Program: SAPLUPC1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UPC_DATA_ENQ_DEQ 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 'UPC_DATA_ENQ_DEQ'"Locking Transaction Data.
EXPORTING
I_AREA = "Planning Area
ITO_CHASEL = "Characteristic Selection
I_ACTION = "Single-Character Indicator
I_ENQMODE = "Lock Mode
* IS_LOCK_INFO = "Context Information on Lock Request
EXCEPTIONS
FOREIGN_LOCK = 1 RFC_ERROR = 2
IMPORTING Parameters details for UPC_DATA_ENQ_DEQ
I_AREA - Planning Area
Data type: UPC_Y_AREAOptional: No
Call by Reference: Yes
ITO_CHASEL - Characteristic Selection
Data type: UPC_YTO_CHASELOptional: No
Call by Reference: Yes
I_ACTION - Single-Character Indicator
Data type: CHAR1Optional: No
Call by Reference: Yes
I_ENQMODE - Lock Mode
Data type: ENQMODEOptional: No
Call by Reference: Yes
IS_LOCK_INFO - Context Information on Lock Request
Data type: UPC_YS_LOCK_INFOOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
FOREIGN_LOCK - Lock
Data type:Optional: No
Call by Reference: Yes
RFC_ERROR - Error During RFC Call
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for UPC_DATA_ENQ_DEQ 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_i_area | TYPE UPC_Y_AREA, " | |||
| lv_foreign_lock | TYPE UPC_Y_AREA, " | |||
| lv_rfc_error | TYPE UPC_Y_AREA, " | |||
| lv_ito_chasel | TYPE UPC_YTO_CHASEL, " | |||
| lv_i_action | TYPE CHAR1, " | |||
| lv_i_enqmode | TYPE ENQMODE, " | |||
| lv_is_lock_info | TYPE UPC_YS_LOCK_INFO. " |
|   CALL FUNCTION 'UPC_DATA_ENQ_DEQ' "Locking Transaction Data |
| EXPORTING | ||
| I_AREA | = lv_i_area | |
| ITO_CHASEL | = lv_ito_chasel | |
| I_ACTION | = lv_i_action | |
| I_ENQMODE | = lv_i_enqmode | |
| IS_LOCK_INFO | = lv_is_lock_info | |
| EXCEPTIONS | ||
| FOREIGN_LOCK = 1 | ||
| RFC_ERROR = 2 | ||
| . " UPC_DATA_ENQ_DEQ | ||
ABAP code using 7.40 inline data declarations to call FM UPC_DATA_ENQ_DEQ
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.Search for further information about these or an SAP related objects