SAP TCOR_DB_DEQUEUE Function Module for Unlock the correspondence and deal
TCOR_DB_DEQUEUE is a standard tcor db dequeue SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Unlock 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 dequeue FM, simply by entering the name TCOR_DB_DEQUEUE 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_DEQUEUE 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_DEQUEUE'"Unlock the correspondence and deal.
EXPORTING
IV_CORR_OBJID = "Correspondence Object UUID
* IV_COMPANY_CODE = "Company Code
* IV_DEALNUMBER = "Financial Transaction
IMPORTING Parameters details for TCOR_DB_DEQUEUE
IV_CORR_OBJID - Correspondence Object UUID
Data type: FTR_COIDOptional: No
Call by Reference: Yes
IV_COMPANY_CODE - Company Code
Data type: BUKRSOptional: Yes
Call by Reference: Yes
IV_DEALNUMBER - Financial Transaction
Data type: TB_RFHAOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for TCOR_DB_DEQUEUE 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_iv_corr_objid | TYPE FTR_COID, " | |||
| lv_iv_company_code | TYPE BUKRS, " | |||
| lv_iv_dealnumber | TYPE TB_RFHA. " |
|   CALL FUNCTION 'TCOR_DB_DEQUEUE' "Unlock the correspondence and deal |
| EXPORTING | ||
| IV_CORR_OBJID | = lv_iv_corr_objid | |
| IV_COMPANY_CODE | = lv_iv_company_code | |
| IV_DEALNUMBER | = lv_iv_dealnumber | |
| . " TCOR_DB_DEQUEUE | ||
ABAP code using 7.40 inline data declarations to call FM TCOR_DB_DEQUEUE
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