VEKABVB SAP (Posting structure for table VEKAB) Structure details
Description: Posting structure for table VEKAB
Structure field list including key, data, relationships and ABAP select examples
VEKABVB 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 "Posting structure for table VEKAB" 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_VEKABVB TYPE VEKABVB.
The VEKABVB table consists of various fields, each holding specific information or linking keys about Posting structure for table VEKAB data available in SAP. These include MANDT (Client), NUMMBUKRS (Company Code), DATUMJAHR (Reporting year of declaration to authorities), DATUMMONA (Reporting month of declaration to authorities).. 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)
SAP VEKABVB 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 |
| MANDT | Client | MANDT | CLNT | 3 | MANDT | ||||
| NUMMBUKRS | Company Code | BUKRS | CHAR | 4 | BUKRS | BUK | C_T001 | ||
| DATUMJAHR | Reporting year of declaration to authorities | DATUMJAHR | NUMC | 4 | GJAHR | GJAHR | GJR | ||
| DATUMMONA | Reporting month of declaration to authorities | DATUMMONA | NUMC | 2 | MONAT | ||||
| ARRIVDEPA | Indicator: Goods direction for declarations to authorities | VEREI | NUMC | 1 | VEREI | ||||
| LFDNRVEKA | Sequential number for Kobra decl.master record (B record) | LFDNRVEKA | NUMC | 5 | NUMC5 | ||||
| FIRMNUMME | Company number assigned by authorities | FIRMNUMME | CHAR | 7 | CHAR7 | ||||
| AUSFUZOLL | Customs number of exporter | AUSFUZOLL | NUMC | 7 | FIRMENNUM | ||||
| AUSFUNAME | Exporter name | AUSFUNAME | CHAR | 75 | CHAR75 | ||||
| AUSFUSTRA | Street of exporter | AUSFUSTRA | CHAR | 25 | CHAR25 | ||||
| AUSFUNATI | Nationality ID of exporter | AUSFUNATI | CHAR | 3 | CHAR3 | ||||
| AUSFUPOST | Postal code of exporter | AUSFUPOST | CHAR | 6 | CHAR06 | ||||
| AUSFUORTE | City of exporter | AUSFUORTE | CHAR | 20 | CHAR20 | ||||
| EMPFEZOLL | Recipient customs number | EMPFEZOLL | NUMC | 7 | FIRMENNUM | ||||
| EMPFENAME | Name of recipient | EMPFENAME | CHAR | 75 | CHAR75 | ||||
| EMPFESTRA | Street of recipient | EMPFESTRA | CHAR | 25 | CHAR25 | ||||
| EMPFENATI | Country ID of recipient | EMPFENATI | CHAR | 3 | CHAR3 | ||||
| EMPFEPOST | Postal code of recipient | EMPFEPOST | CHAR | 6 | CHAR06 | ||||
| EMPFEORTE | City of recipient | EMPFEORTE | CHAR | 20 | CHAR20 | ||||
| HANDELAND | Trading country | HANDELAND | CHAR | 3 | LAND1 | LND | |||
| BESTILAND | Country of destination of material | BESTILAND | CHAR | 3 | LAND1 | LND | |||
| BEFIABGAN | Means of transport at departure | BEFIABGAN | CHAR | 14 | CHAR14 | ||||
| BEFIGRENZ | Means of transport at border | BEFIGRENZ | CHAR | 14 | CHAR14 | ||||
| ARTGESCHA | Business Transaction Type for Foreign Trade | EXART | CHAR | 2 | EXART | EXA | |||
| EINLADFGH | Customs Office: Office of Exit/Entry for Foreign Trade | DZOLLS | CHAR | 6 | ZOLLS | ||||
| UNIXKENNZ | ID to define whether record exists on a UNIX file | UNIXKENNZ | CHAR | 1 | CHAR01 | ||||
| FLAGEUROC | Declarations to the authorities: Ind. for decl. crcy = Euro | FTEUR | CHAR | 1 | XFELD | ||||
| UPDKZ | Update indicator | UPDKZ_D | CHAR | 1 | UPDKZ |
| Key field | Non-key field |
How do I retrieve data from SAP structure VEKABVB using ABAP code?
As VEKABVB 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 VEKABVB as there is no data to select.How to access SAP table VEKABVB
Within an ECC or HANA version of SAP you can also view further information about VEKABVB 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