SAP UPC_CHASEL_ENQUEUE_RFC Function Module for Lock Management









UPC_CHASEL_ENQUEUE_RFC is a standard upc chasel enqueue rfc SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Lock Management 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 chasel enqueue rfc FM, simply by entering the name UPC_CHASEL_ENQUEUE_RFC into the relevant SAP transaction such as SE37 or SE38.

Function Group: UPC_SERVICES
Program Name: SAPLUPC_SERVICES
Main Program: SAPLUPC_SERVICES
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function UPC_CHASEL_ENQUEUE_RFC 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_CHASEL_ENQUEUE_RFC'"Lock Management
  EXPORTING
   I_INFOPROV =  "InfoProvider
   I_AREA =  "Planning Area
   ITO_CHASEL =  "Characteristic Selection
   I_ACTION =  "Single-Character Flag
   I_ENQMODE =  "Lock Mode
*  IS_LOCK_INFO =  "Context Information on Lock Request

 IMPORTING
   E_SUBRC =  "Return Value, Return Value After ABAP Statements
   ES_MESG =  "Message Structure
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLUPC_SERVICES_001 Enhancement for checking characteristic value combinations
EXIT_SAPLUPC_SERVICES_002 Enhancement for characteristic derivation

IMPORTING Parameters details for UPC_CHASEL_ENQUEUE_RFC

I_INFOPROV - InfoProvider

Data type: RSINFOPROV
Optional: No
Call by Reference: No ( called with pass by value option)

I_AREA - Planning Area

Data type: UPC_Y_AREA
Optional: No
Call by Reference: No ( called with pass by value option)

ITO_CHASEL - Characteristic Selection

Data type: UPC_YTO_CHASEL
Optional: No
Call by Reference: No ( called with pass by value option)

I_ACTION - Single-Character Flag

Data type: CHAR1
Optional: No
Call by Reference: No ( called with pass by value option)

I_ENQMODE - Lock Mode

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

IS_LOCK_INFO - Context Information on Lock Request

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

EXPORTING Parameters details for UPC_CHASEL_ENQUEUE_RFC

E_SUBRC - Return Value, Return Value After ABAP Statements

Data type: SYSUBRC
Optional: No
Call by Reference: No ( called with pass by value option)

ES_MESG - Message Structure

Data type: UPC_YS_MESG
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for UPC_CHASEL_ENQUEUE_RFC 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_e_subrc  TYPE SYSUBRC, "   
lv_i_infoprov  TYPE RSINFOPROV, "   
lv_i_area  TYPE UPC_Y_AREA, "   
lv_es_mesg  TYPE UPC_YS_MESG, "   
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_CHASEL_ENQUEUE_RFC'  "Lock Management
    EXPORTING
         I_INFOPROV = lv_i_infoprov
         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
    IMPORTING
         E_SUBRC = lv_e_subrc
         ES_MESG = lv_es_mesg
. " UPC_CHASEL_ENQUEUE_RFC




ABAP code using 7.40 inline data declarations to call FM UPC_CHASEL_ENQUEUE_RFC

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



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!