SAP FKK_VT_CHECK_EXISTENCE Function Module for
FKK_VT_CHECK_EXISTENCE is a standard fkk vt check existence SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 fkk vt check existence FM, simply by entering the name FKK_VT_CHECK_EXISTENCE into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKK_VT_CHECK
Program Name: SAPLFKK_VT_CHECK
Main Program: SAPLFKK_VT_CHECK
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FKK_VT_CHECK_EXISTENCE 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 'FKK_VT_CHECK_EXISTENCE'".
EXPORTING
IV_VTKEY = "
* IV_GPART = "
* IV_VTPOS = "
* IV_VKONT = "
IMPORTING
ES_VT_H = "
ET_VT_I = "
ET_VT_TR = "
ET_VT_D = "
EXCEPTIONS
VTKEY_NOT_VALID = 1 GPART_NOT_VALID = 2 VTPOS_NOT_VALID = 3 VTPOS_CANCELLED = 4 VKONT_NOT_VALID = 5
IMPORTING Parameters details for FKK_VT_CHECK_EXISTENCE
IV_VTKEY -
Data type: VTKEY_KKOptional: No
Call by Reference: No ( called with pass by value option)
IV_GPART -
Data type: GPART_KKOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_VTPOS -
Data type: VTPOS_KKOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_VKONT -
Data type: VKONT_KKOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FKK_VT_CHECK_EXISTENCE
ES_VT_H -
Data type: DFKK_VT_HOptional: No
Call by Reference: Yes
ET_VT_I -
Data type: FKK_VT_I_TABOptional: No
Call by Reference: Yes
ET_VT_TR -
Data type: FKK_VT_TR_TABOptional: No
Call by Reference: Yes
ET_VT_D -
Data type: FKK_VT_D_TABOptional: No
Call by Reference: Yes
EXCEPTIONS details
VTKEY_NOT_VALID -
Data type:Optional: No
Call by Reference: Yes
GPART_NOT_VALID -
Data type:Optional: No
Call by Reference: Yes
VTPOS_NOT_VALID -
Data type:Optional: No
Call by Reference: Yes
VTPOS_CANCELLED -
Data type:Optional: No
Call by Reference: Yes
VKONT_NOT_VALID -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FKK_VT_CHECK_EXISTENCE 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_es_vt_h | TYPE DFKK_VT_H, " | |||
| lv_iv_vtkey | TYPE VTKEY_KK, " | |||
| lv_vtkey_not_valid | TYPE VTKEY_KK, " | |||
| lv_et_vt_i | TYPE FKK_VT_I_TAB, " | |||
| lv_iv_gpart | TYPE GPART_KK, " | |||
| lv_gpart_not_valid | TYPE GPART_KK, " | |||
| lv_et_vt_tr | TYPE FKK_VT_TR_TAB, " | |||
| lv_iv_vtpos | TYPE VTPOS_KK, " | |||
| lv_vtpos_not_valid | TYPE VTPOS_KK, " | |||
| lv_et_vt_d | TYPE FKK_VT_D_TAB, " | |||
| lv_iv_vkont | TYPE VKONT_KK, " | |||
| lv_vtpos_cancelled | TYPE VKONT_KK, " | |||
| lv_vkont_not_valid | TYPE VKONT_KK. " |
|   CALL FUNCTION 'FKK_VT_CHECK_EXISTENCE' " |
| EXPORTING | ||
| IV_VTKEY | = lv_iv_vtkey | |
| IV_GPART | = lv_iv_gpart | |
| IV_VTPOS | = lv_iv_vtpos | |
| IV_VKONT | = lv_iv_vkont | |
| IMPORTING | ||
| ES_VT_H | = lv_es_vt_h | |
| ET_VT_I | = lv_et_vt_i | |
| ET_VT_TR | = lv_et_vt_tr | |
| ET_VT_D | = lv_et_vt_d | |
| EXCEPTIONS | ||
| VTKEY_NOT_VALID = 1 | ||
| GPART_NOT_VALID = 2 | ||
| VTPOS_NOT_VALID = 3 | ||
| VTPOS_CANCELLED = 4 | ||
| VKONT_NOT_VALID = 5 | ||
| . " FKK_VT_CHECK_EXISTENCE | ||
ABAP code using 7.40 inline data declarations to call FM FKK_VT_CHECK_EXISTENCE
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