SAP FKK_VT_OBJ_READ Function Module for









FKK_VT_OBJ_READ is a standard fkk vt obj read 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 obj read FM, simply by entering the name FKK_VT_OBJ_READ into the relevant SAP transaction such as SE37 or SE38.

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



Function FKK_VT_OBJ_READ 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_OBJ_READ'"
EXPORTING
* IT_VTKEY = "
* IT_GPART = "
* IT_VKONT = "
* IT_VTALT = "
* IT_PPACC = "
* IT_TECHR = "
* IV_VALID_TIMESTAMP = "
* IV_VALID_TIMESTAMP_LOCL = "
* IX_LOCL = ' ' "

IMPORTING
ET_VT_H_READ = "
ET_VT_I_READ = "
ET_VT_D_READ = "
ET_VT_TR_READ = "

EXCEPTIONS
NOT_FOUND = 1 NOT_VALID = 2 INTERNAL_ERROR = 3
.



IMPORTING Parameters details for FKK_VT_OBJ_READ

IT_VTKEY -

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

IT_GPART -

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

IT_VKONT -

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

IT_VTALT -

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

IT_PPACC -

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

IT_TECHR -

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

IV_VALID_TIMESTAMP -

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

IV_VALID_TIMESTAMP_LOCL -

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

IX_LOCL -

Data type: BOOLE-BOOLE
Default: SPACE
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FKK_VT_OBJ_READ

ET_VT_H_READ -

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

ET_VT_I_READ -

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

ET_VT_D_READ -

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

ET_VT_TR_READ -

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

EXCEPTIONS details

NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

NOT_VALID -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FKK_VT_OBJ_READ 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_it_vtkey  TYPE FKK_RT_VTKEY, "   
lv_not_found  TYPE FKK_RT_VTKEY, "   
lv_et_vt_h_read  TYPE FKK_VT_H_READ_TAB, "   
lv_it_gpart  TYPE FKK_RT_GPART, "   
lv_not_valid  TYPE FKK_RT_GPART, "   
lv_et_vt_i_read  TYPE FKK_VT_I_READ_TAB, "   
lv_it_vkont  TYPE FKK_RT_VKONT, "   
lv_et_vt_d_read  TYPE FKK_VT_D_READ_TAB, "   
lv_internal_error  TYPE FKK_VT_D_READ_TAB, "   
lv_it_vtalt  TYPE FKK_RT_VTALT, "   
lv_et_vt_tr_read  TYPE FKK_VT_TR_READ_TAB, "   
lv_it_ppacc  TYPE FKK_RT_PPACC, "   
lv_it_techr  TYPE FKK_VT_TECHR_TAB, "   
lv_iv_valid_timestamp  TYPE TIMESTAMP, "   
lv_iv_valid_timestamp_locl  TYPE TLOCL_KK, "   
lv_ix_locl  TYPE BOOLE-BOOLE. "   SPACE

  CALL FUNCTION 'FKK_VT_OBJ_READ'  "
    EXPORTING
         IT_VTKEY = lv_it_vtkey
         IT_GPART = lv_it_gpart
         IT_VKONT = lv_it_vkont
         IT_VTALT = lv_it_vtalt
         IT_PPACC = lv_it_ppacc
         IT_TECHR = lv_it_techr
         IV_VALID_TIMESTAMP = lv_iv_valid_timestamp
         IV_VALID_TIMESTAMP_LOCL = lv_iv_valid_timestamp_locl
         IX_LOCL = lv_ix_locl
    IMPORTING
         ET_VT_H_READ = lv_et_vt_h_read
         ET_VT_I_READ = lv_et_vt_i_read
         ET_VT_D_READ = lv_et_vt_d_read
         ET_VT_TR_READ = lv_et_vt_tr_read
    EXCEPTIONS
        NOT_FOUND = 1
        NOT_VALID = 2
        INTERNAL_ERROR = 3
. " FKK_VT_OBJ_READ




ABAP code using 7.40 inline data declarations to call FM FKK_VT_OBJ_READ

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.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
"SELECT single BOOLE FROM BOOLE INTO @DATA(ld_ix_locl).
DATA(ld_ix_locl) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!