SAP TCOR_DB_ENQUEUE Function Module for Lock the correspondence and deal

Search SAP Function Modules

TCOR_DB_ENQUEUE is a standard tcor db enqueue 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 the correspondence and deal 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 tcor db enqueue FM, simply by entering the name TCOR_DB_ENQUEUE into the relevant SAP transaction such as SE37 or SE38.

Function Group: TCOR_DB
Program Name: SAPLTCOR_DB
Main Program: SAPLTCOR_DB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function TCOR_DB_ENQUEUE 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 'TCOR_DB_ENQUEUE'"Lock the correspondence and deal
  EXPORTING
   IV_CORR_OBJID =  "Correspondence Object UUID
*  IV_COMPANY_CODE =  "Company Code
*  IV_DEALNUMBER =  "Financial Transaction
*  IV_LOCK_DEAL =  "Flag for locking the deal data

 IMPORTING
   OV_LOCK_SUCCESS =  "Deal data is locked

EXCEPTIONS
   NO_DEAL_DATA = 1    LOCK_FAILURE = 2 

.

IMPORTING Parameters details for TCOR_DB_ENQUEUE

IV_CORR_OBJID - Correspondence Object UUID

Data type: FTR_COID
Optional: No
Call by Reference: Yes

IV_COMPANY_CODE - Company Code

Data type: BUKRS
Optional: Yes
Call by Reference: Yes

IV_DEALNUMBER - Financial Transaction

Data type: TB_RFHA
Optional: Yes
Call by Reference: Yes

IV_LOCK_DEAL - Flag for locking the deal data

Data type: FLAG
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for TCOR_DB_ENQUEUE

OV_LOCK_SUCCESS - Deal data is locked

Data type: FLAG
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_DEAL_DATA -

Data type:
Optional: No
Call by Reference: Yes

LOCK_FAILURE -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for TCOR_DB_ENQUEUE 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.

ABAP code using 7.40 inline data declarations to call FM TCOR_DB_ENQUEUE

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