SAP FVD_IF_COT_GET_ENTRY_TEXT Function Module for Table VDCOT: Read Text for Entry with Primary Key
FVD_IF_COT_GET_ENTRY_TEXT is a standard fvd if cot get entry text SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Table VDCOT: Read Text for Entry with Primary Key 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 fvd if cot get entry text FM, simply by entering the name FVD_IF_COT_GET_ENTRY_TEXT into the relevant SAP transaction such as SE37 or SE38.
Function Group: FVD_FICO_INTERFACE_CONTAB
Program Name: SAPLFVD_FICO_INTERFACE_CONTAB
Main Program: SAPLFVD_FICO_INTERFACE_CONTAB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FVD_IF_COT_GET_ENTRY_TEXT 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 'FVD_IF_COT_GET_ENTRY_TEXT'"Table VDCOT: Read Text for Entry with Primary Key.
EXPORTING
* I_LAYER_BUFFER = 'B' "Control Layer for Read Access
* I_LANGU = SY-LANGU "Language Key of Current Text Environment
* I_RANTYP = '1' "Contract Type
I_SKOGRP = "Condition Group
I_O_CONTAB = "Condition Table Number
I_LOG_HANDLE = "Application Log: Log Handle
IMPORTING
E_STR_COTT = "Texts for Condition Table
EXCEPTIONS
COND_TAB_TXT_NOT_FOUND = 1 UNEXPECTED_EXCEPTION = 2
IMPORTING Parameters details for FVD_IF_COT_GET_ENTRY_TEXT
I_LAYER_BUFFER - Control Layer for Read Access
Data type: TB_S_LAYER_BUFFER_FOR_READDefault: 'B'
Optional: No
Call by Reference: Yes
I_LANGU - Language Key of Current Text Environment
Data type: SYLANGUDefault: SY-LANGU
Optional: No
Call by Reference: Yes
I_RANTYP - Contract Type
Data type: RANTYPDefault: '1'
Optional: No
Call by Reference: Yes
I_SKOGRP - Condition Group
Data type: SKOGRPOptional: No
Call by Reference: Yes
I_O_CONTAB - Condition Table Number
Data type: TB_FICO_CONTABOptional: No
Call by Reference: Yes
I_LOG_HANDLE - Application Log: Log Handle
Data type: BALLOGHNDLOptional: No
Call by Reference: Yes
EXPORTING Parameters details for FVD_IF_COT_GET_ENTRY_TEXT
E_STR_COTT - Texts for Condition Table
Data type: VDCOTTOptional: No
Call by Reference: Yes
EXCEPTIONS details
COND_TAB_TXT_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
UNEXPECTED_EXCEPTION -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FVD_IF_COT_GET_ENTRY_TEXT 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_str_cott | TYPE VDCOTT, " | |||
| lv_i_layer_buffer | TYPE TB_S_LAYER_BUFFER_FOR_READ, " 'B' | |||
| lv_cond_tab_txt_not_found | TYPE TB_S_LAYER_BUFFER_FOR_READ, " | |||
| lv_i_langu | TYPE SYLANGU, " SY-LANGU | |||
| lv_unexpected_exception | TYPE SYLANGU, " | |||
| lv_i_rantyp | TYPE RANTYP, " '1' | |||
| lv_i_skogrp | TYPE SKOGRP, " | |||
| lv_i_o_contab | TYPE TB_FICO_CONTAB, " | |||
| lv_i_log_handle | TYPE BALLOGHNDL. " |
|   CALL FUNCTION 'FVD_IF_COT_GET_ENTRY_TEXT' "Table VDCOT: Read Text for Entry with Primary Key |
| EXPORTING | ||
| I_LAYER_BUFFER | = lv_i_layer_buffer | |
| I_LANGU | = lv_i_langu | |
| I_RANTYP | = lv_i_rantyp | |
| I_SKOGRP | = lv_i_skogrp | |
| I_O_CONTAB | = lv_i_o_contab | |
| I_LOG_HANDLE | = lv_i_log_handle | |
| IMPORTING | ||
| E_STR_COTT | = lv_e_str_cott | |
| EXCEPTIONS | ||
| COND_TAB_TXT_NOT_FOUND = 1 | ||
| UNEXPECTED_EXCEPTION = 2 | ||
| . " FVD_IF_COT_GET_ENTRY_TEXT | ||
ABAP code using 7.40 inline data declarations to call FM FVD_IF_COT_GET_ENTRY_TEXT
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.| DATA(ld_i_layer_buffer) | = 'B'. | |||
| DATA(ld_i_langu) | = SY-LANGU. | |||
| DATA(ld_i_rantyp) | = '1'. | |||
Search for further information about these or an SAP related objects