SAP OTC_CONV_DB_UPDATE_CORRES Function Module for Database Update for Correspondence Planned Records
OTC_CONV_DB_UPDATE_CORRES is a standard otc conv db update corres SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Database Update for Correspondence Planned Records 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 otc conv db update corres FM, simply by entering the name OTC_CONV_DB_UPDATE_CORRES into the relevant SAP transaction such as SE37 or SE38.
Function Group: OTC_CONVERT
Program Name: SAPLOTC_CONVERT
Main Program: SAPLOTC_CONVERT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function OTC_CONV_DB_UPDATE_CORRES 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 'OTC_CONV_DB_UPDATE_CORRES'"Database Update for Correspondence Planned Records.
EXPORTING
IM_TAB_NEW_CORRES = "Neue Korrespondenzplansätze
IMPORTING Parameters details for OTC_CONV_DB_UPDATE_CORRES
IM_TAB_NEW_CORRES - Neue Korrespondenzplansätze
Data type: TRTB_TKORESOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for OTC_CONV_DB_UPDATE_CORRES 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_im_tab_new_corres | TYPE TRTB_TKORES. " |
|   CALL FUNCTION 'OTC_CONV_DB_UPDATE_CORRES' "Database Update for Correspondence Planned Records |
| EXPORTING | ||
| IM_TAB_NEW_CORRES | = lv_im_tab_new_corres | |
| . " OTC_CONV_DB_UPDATE_CORRES | ||
ABAP code using 7.40 inline data declarations to call FM OTC_CONV_DB_UPDATE_CORRES
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