SAP FKK_VT_OBJ_OPEN Function Module for
FKK_VT_OBJ_OPEN is a standard fkk vt obj open 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 open FM, simply by entering the name FKK_VT_OBJ_OPEN 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_OPEN 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_OPEN'".
EXPORTING
IV_VTKEY = "
* IX_TEST = ' ' "
* IX_DB_SELECT = 'X' "
* IS_VT_H = "
* IV_VTCAT = "
IV_AKTYP = "
* IV_VALID_TIMESTAMP = ' ' "
* IV_RUN_TIMESTAMP = ' ' "
* IX_SET_ENQUEUE = ' ' "
* IX_CHECK_AUTHORITY = 'X' "
* IX_DINP = ' ' "
* IX_UPDTASK = ' ' "
* IX_CHDOC = 'X' "
IMPORTING
ES_VT = "
ES_VT_OLD = "
EXCEPTIONS
AKTYP_NOT_SUPPORTED = 1 KEYFIELD_NOT_FILLED = 2 NO_AUTHORITY = 3 ENQUEUE_LOCK = 4 NOT_FOUND = 5 ALREADY_EXISTS = 6 ERROR_LOCK = 7
IMPORTING Parameters details for FKK_VT_OBJ_OPEN
IV_VTKEY -
Data type: VTKEY_KKOptional: No
Call by Reference: No ( called with pass by value option)
IX_TEST -
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IX_DB_SELECT -
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IS_VT_H -
Data type: DFKK_VT_HOptional: Yes
Call by Reference: Yes
IV_VTCAT -
Data type: VTCAT_KKOptional: Yes
Call by Reference: No ( called with pass by value option)
IV_AKTYP -
Data type: BU_AKTYPOptional: No
Call by Reference: No ( called with pass by value option)
IV_VALID_TIMESTAMP -
Data type: VALID_FROM_KKDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_RUN_TIMESTAMP -
Data type: RUN_TSTMP_KKDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IX_SET_ENQUEUE -
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IX_CHECK_AUTHORITY -
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IX_DINP -
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IX_UPDTASK -
Data type: XFELDDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
IX_CHDOC -
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FKK_VT_OBJ_OPEN
ES_VT -
Data type: FKK_VT_DATAOptional: No
Call by Reference: Yes
ES_VT_OLD -
Data type: FKK_VT_DATAOptional: No
Call by Reference: Yes
EXCEPTIONS details
AKTYP_NOT_SUPPORTED -
Data type:Optional: No
Call by Reference: Yes
KEYFIELD_NOT_FILLED -
Data type:Optional: No
Call by Reference: Yes
NO_AUTHORITY -
Data type:Optional: No
Call by Reference: Yes
ENQUEUE_LOCK -
Data type:Optional: No
Call by Reference: Yes
NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
ALREADY_EXISTS -
Data type:Optional: No
Call by Reference: Yes
ERROR_LOCK -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FKK_VT_OBJ_OPEN 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 | TYPE FKK_VT_DATA, " | |||
| lv_iv_vtkey | TYPE VTKEY_KK, " | |||
| lv_aktyp_not_supported | TYPE VTKEY_KK, " | |||
| lv_ix_test | TYPE XFELD, " SPACE | |||
| lv_ix_db_select | TYPE XFELD, " 'X' | |||
| lv_is_vt_h | TYPE DFKK_VT_H, " | |||
| lv_iv_vtcat | TYPE VTCAT_KK, " | |||
| lv_iv_aktyp | TYPE BU_AKTYP, " | |||
| lv_es_vt_old | TYPE FKK_VT_DATA, " | |||
| lv_keyfield_not_filled | TYPE FKK_VT_DATA, " | |||
| lv_no_authority | TYPE FKK_VT_DATA, " | |||
| lv_iv_valid_timestamp | TYPE VALID_FROM_KK, " SPACE | |||
| lv_enqueue_lock | TYPE VALID_FROM_KK, " | |||
| lv_iv_run_timestamp | TYPE RUN_TSTMP_KK, " SPACE | |||
| lv_not_found | TYPE RUN_TSTMP_KK, " | |||
| lv_ix_set_enqueue | TYPE XFELD, " SPACE | |||
| lv_already_exists | TYPE XFELD, " | |||
| lv_ix_check_authority | TYPE XFELD, " 'X' | |||
| lv_ix_dinp | TYPE XFELD, " SPACE | |||
| lv_error_lock | TYPE XFELD, " | |||
| lv_ix_updtask | TYPE XFELD, " SPACE | |||
| lv_ix_chdoc | TYPE XFELD. " 'X' |
|   CALL FUNCTION 'FKK_VT_OBJ_OPEN' " |
| EXPORTING | ||
| IV_VTKEY | = lv_iv_vtkey | |
| IX_TEST | = lv_ix_test | |
| IX_DB_SELECT | = lv_ix_db_select | |
| IS_VT_H | = lv_is_vt_h | |
| IV_VTCAT | = lv_iv_vtcat | |
| IV_AKTYP | = lv_iv_aktyp | |
| IV_VALID_TIMESTAMP | = lv_iv_valid_timestamp | |
| IV_RUN_TIMESTAMP | = lv_iv_run_timestamp | |
| IX_SET_ENQUEUE | = lv_ix_set_enqueue | |
| IX_CHECK_AUTHORITY | = lv_ix_check_authority | |
| IX_DINP | = lv_ix_dinp | |
| IX_UPDTASK | = lv_ix_updtask | |
| IX_CHDOC | = lv_ix_chdoc | |
| IMPORTING | ||
| ES_VT | = lv_es_vt | |
| ES_VT_OLD | = lv_es_vt_old | |
| EXCEPTIONS | ||
| AKTYP_NOT_SUPPORTED = 1 | ||
| KEYFIELD_NOT_FILLED = 2 | ||
| NO_AUTHORITY = 3 | ||
| ENQUEUE_LOCK = 4 | ||
| NOT_FOUND = 5 | ||
| ALREADY_EXISTS = 6 | ||
| ERROR_LOCK = 7 | ||
| . " FKK_VT_OBJ_OPEN | ||
ABAP code using 7.40 inline data declarations to call FM FKK_VT_OBJ_OPEN
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_ix_test) | = ' '. | |||
| DATA(ld_ix_db_select) | = 'X'. | |||
| DATA(ld_iv_valid_timestamp) | = ' '. | |||
| DATA(ld_iv_run_timestamp) | = ' '. | |||
| DATA(ld_ix_set_enqueue) | = ' '. | |||
| DATA(ld_ix_check_authority) | = 'X'. | |||
| DATA(ld_ix_dinp) | = ' '. | |||
| DATA(ld_ix_updtask) | = ' '. | |||
| DATA(ld_ix_chdoc) | = 'X'. | |||
Search for further information about these or an SAP related objects