SAP FKK_VT_DATA_MAINTAIN_BDT Function Module for
FKK_VT_DATA_MAINTAIN_BDT is a standard fkk vt data maintain bdt 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 data maintain bdt FM, simply by entering the name FKK_VT_DATA_MAINTAIN_BDT into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKK_VT_DATA
Program Name: SAPLFKK_VT_DATA
Main Program: SAPLFKK_VT_DATA
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FKK_VT_DATA_MAINTAIN_BDT 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_DATA_MAINTAIN_BDT'".
EXPORTING
IV_AKTYP = "
* IX_INIT = 'X' "
* IX_SAVE = 'X' "
* IV_APPLI = "
* IX_UPDTASK = 'X' "
* IV_SICHT_START = ' ' "
IMPORTING
EV_STATE = "
EV_STATE_FCODE = "
TABLES
* T_RLTYP = "
* T_RLTGR = "
* T_FLDVL = "
* T_SCRSEL = "
IMPORTING Parameters details for FKK_VT_DATA_MAINTAIN_BDT
IV_AKTYP -
Data type: BU_AKTYPOptional: No
Call by Reference: Yes
IX_INIT -
Data type: BUS000FLDS-CHAR1Default: 'X'
Optional: Yes
Call by Reference: Yes
IX_SAVE -
Data type: BUS000FLDS-XSAVEDefault: 'X'
Optional: Yes
Call by Reference: Yes
IV_APPLI -
Data type: TBZ0A-APPLIOptional: Yes
Call by Reference: Yes
IX_UPDTASK -
Data type: XFELDDefault: 'X'
Optional: Yes
Call by Reference: Yes
IV_SICHT_START -
Data type: BU_SICHTDefault: SPACE
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FKK_VT_DATA_MAINTAIN_BDT
EV_STATE -
Data type: BUS000FLDS-CHAR1Optional: No
Call by Reference: Yes
EV_STATE_FCODE -
Data type: BUS000FLDS-CHAR1Optional: No
Call by Reference: Yes
TABLES Parameters details for FKK_VT_DATA_MAINTAIN_BDT
T_RLTYP -
Data type: BUS0RLTYPOptional: Yes
Call by Reference: Yes
T_RLTGR -
Data type: BUS0RLTGROptional: Yes
Call by Reference: Yes
T_FLDVL -
Data type: BUS0FLDVALOptional: Yes
Call by Reference: Yes
T_SCRSEL -
Data type: BUS0SCRSELOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for FKK_VT_DATA_MAINTAIN_BDT 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: | ||||
| lt_t_rltyp | TYPE STANDARD TABLE OF BUS0RLTYP, " | |||
| lv_ev_state | TYPE BUS000FLDS-CHAR1, " | |||
| lv_iv_aktyp | TYPE BU_AKTYP, " | |||
| lv_ix_init | TYPE BUS000FLDS-CHAR1, " 'X' | |||
| lt_t_rltgr | TYPE STANDARD TABLE OF BUS0RLTGR, " | |||
| lv_ev_state_fcode | TYPE BUS000FLDS-CHAR1, " | |||
| lv_ix_save | TYPE BUS000FLDS-XSAVE, " 'X' | |||
| lt_t_fldvl | TYPE STANDARD TABLE OF BUS0FLDVAL, " | |||
| lv_iv_appli | TYPE TBZ0A-APPLI, " | |||
| lt_t_scrsel | TYPE STANDARD TABLE OF BUS0SCRSEL, " | |||
| lv_ix_updtask | TYPE XFELD, " 'X' | |||
| lv_iv_sicht_start | TYPE BU_SICHT. " SPACE |
|   CALL FUNCTION 'FKK_VT_DATA_MAINTAIN_BDT' " |
| EXPORTING | ||
| IV_AKTYP | = lv_iv_aktyp | |
| IX_INIT | = lv_ix_init | |
| IX_SAVE | = lv_ix_save | |
| IV_APPLI | = lv_iv_appli | |
| IX_UPDTASK | = lv_ix_updtask | |
| IV_SICHT_START | = lv_iv_sicht_start | |
| IMPORTING | ||
| EV_STATE | = lv_ev_state | |
| EV_STATE_FCODE | = lv_ev_state_fcode | |
| TABLES | ||
| T_RLTYP | = lt_t_rltyp | |
| T_RLTGR | = lt_t_rltgr | |
| T_FLDVL | = lt_t_fldvl | |
| T_SCRSEL | = lt_t_scrsel | |
| . " FKK_VT_DATA_MAINTAIN_BDT | ||
ABAP code using 7.40 inline data declarations to call FM FKK_VT_DATA_MAINTAIN_BDT
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 CHAR1 FROM BUS000FLDS INTO @DATA(ld_ev_state). | ||||
| "SELECT single CHAR1 FROM BUS000FLDS INTO @DATA(ld_ix_init). | ||||
| DATA(ld_ix_init) | = 'X'. | |||
| "SELECT single CHAR1 FROM BUS000FLDS INTO @DATA(ld_ev_state_fcode). | ||||
| "SELECT single XSAVE FROM BUS000FLDS INTO @DATA(ld_ix_save). | ||||
| DATA(ld_ix_save) | = 'X'. | |||
| "SELECT single APPLI FROM TBZ0A INTO @DATA(ld_iv_appli). | ||||
| DATA(ld_ix_updtask) | = 'X'. | |||
| DATA(ld_iv_sicht_start) | = ' '. | |||
Search for further information about these or an SAP related objects