VAKEDB SAP (Condition Tables: Update Structure) Structure details
Description: Condition Tables: Update Structure
Structure field list including key, data, relationships and ABAP select examples
VAKEDB is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Condition Tables: Update Structure" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_VAKEDB TYPE VAKEDB.
The VAKEDB table consists of various fields, each holding specific information or linking keys about Condition Tables: Update Structure data available in SAP. These include KVEWE (Usage of the condition table), KOTABNR (Condition table), KAPPL (Application), KSCHL (Condition Type).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type or numeric)
SAP VAKEDB structure fields - Full list of fields found in SAP data dictionary
Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
KVEWE | Usage of the condition table | KVEWE | CHAR | 1 | T681V | KVEWE | KVW | ||
KOTABNR | Condition table | KOTABNR | NUMC | 3 | T681 | KOTABNR | KON | ||
KAPPL | Application | KAPPL | CHAR | 2 | T681A | KAPPL | KAP | ||
KSCHL | Condition Type | KSCHL | CHAR | 4 | T685 | KSCHL | VKS | ||
VAKEY | Variable key 100 bytes | VAKEY | CHAR | 100 | VAKEY | ||||
DATBI | Validity end date of the condition record | KODATBI | DATS | 8 | DATUM | ||||
DATAB | Validity start date of the condition record | KODATAB | DATS | 8 | DATUM | ||||
KNUMH | Condition record number | KNUMH | CHAR | 10 | KNUMB | ||||
KNUMA | Agreement (various conditions grouped together) | KNUMA | CHAR | 10 | KONA | ALPHA | KNUMA | VMBO | |
VADAT | Variable Data Part | VADAT_KO | CHAR | 100 | CHAR100 | ||||
XXSTATE | Time Interval Handler (CO): Condition (included/excluded) | TTSTATE | CHAR | 1 | TTSTATE | ||||
XXGAPINDIC | Time Interval Handler (CO): Flag for Interval Gap | TTGAPIND | CHAR | 1 | X | ||||
XXCNINDEX | Time Interval Handler (CO): Index during interval join | TTCNINDEX | NUMC | 3 | TTCNINDEX | ||||
XXPROCINFO | Time Interval Handler (CO): 'Collector' during interval join | TTPROCINFO | CHAR | 1 | TTPROCINFO | ||||
XXDBACTION | Time Interval Handler (CO): Identifier for database activity | TTDBACTION | CHAR | 1 | TTDBACTION |
Key field | Non-key field |
How do I retrieve data from SAP structure VAKEDB using ABAP code?
As VAKEDB is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on VAKEDB as there is no data to select.How to access SAP table VAKEDB
Within an ECC or HANA version of SAP you can also view further information about VAKEDB and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects