AVIMI26 SAP (Change Document Structure for VIMI26) Structure details
Description: Change Document Structure for VIMI26
Structure field list including key, data, relationships and ABAP select examples
AVIMI26 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 "Change Document Structure for VIMI26" 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_AVIMI26 TYPE AVIMI26.
The AVIMI26 table consists of various fields, each holding specific information or linking keys about Change Document Structure for VIMI26 data available in SAP. These include MANDT (Client), BUKRS (Company Code), SMIVE (Lease-Out Number), SWENR (Site Number).. 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: Not classified
SAP AVIMI26 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 | Assigned to domain | MANDT | |||
| BUKRS | Company Code | BUKRS | CHAR | 4 | T001 | BUKRS | BUK | C_T001 | |
| SMIVE | Lease-Out Number | SMIVE | CHAR | 13 | ALPHA | VVSMIVE | MIV | MRTA | |
| SWENR | Site Number | SWENR | CHAR | 8 | Assigned to domain | SWENR | SWENR | WEH | MCWE |
| SMENR | Number of Rental Unit | SMENR | CHAR | 8 | Assigned to domain | SMENR | SMENR | MEH | MCME |
| DKUEZU | Contract Notice Per | DKUZU | DATS | 8 | DDAT | ||||
| DEINKUE | Date of receipt of notice | DEKUE | DATS | 8 | DDAT | ||||
| SKUEART | Notice Type | SKUAR | CHAR | 1 | SKUAR | ||||
| RKUEGRU | Reason for notice | RKUEGRU | NUMC | 2 | TIV39 | RKUEGRU | |||
| RABLGRU | Reason for rejection | RABLGRU | NUMC | 2 | TIV41 | RABLGRU | |||
| DKUZUG | Date notice approved | VVDKUZUG | DATS | 8 | DDAT | ||||
| DKUABG | Date notice rejected | VVDKUABG | DATS | 8 | DDAT | ||||
| DAKTKU | Activation date | VVDAKTKU | DATS | 8 | DDAT | ||||
| DSTKU | Reversal date | VVDSTKU | DATS | 8 | DDAT | ||||
| DDRKU | Date of written notice printout | VVDDRKU | DATS | 8 | DDAT | ||||
| DWIKU | Date of objection to notice | VVDWIKU | DATS | 8 | DDAT | ||||
| DKREUEB | Date notice submitted to legal department | VVDKREUEB | DATS | 8 | DDAT | ||||
| DKUERCK | Date of withdrawal of notice | DKUERCK | DATS | 8 | DATUM | ||||
| RERF | Entered by | RERF | CHAR | 12 | SYCHAR12 | ||||
| DERF | First Entered on | DERF | DATS | 8 | DATUM | ||||
| TERF | Time of Initial Entry | TERF | TIMS | 6 | TIMES | ||||
| REHER | Source of initial entry | REHER | CHAR | 10 | CHAR10 | ||||
| RBEAR | Employee ID | RBEAR | CHAR | 12 | SYCHAR12 | ||||
| DBEAR | Last Edited on | DBEAR | DATS | 8 | DATUM | ||||
| TBEAR | Last Edited at | TBEAR | TIMS | 6 | TIMES | ||||
| RBHER | Editing Source | RBHER | CHAR | 10 | CHAR10 | ||||
| DKUEWU | Tenant's notice request date | VVDKUEWU | DATS | 8 | DDAT | ||||
| DKGSTZL | Date of (calculated) notice | VVDKGSTZL | DATS | 8 | DATUM | ||||
| LEERGD | Vacancy reason | VVLEERGD | NUMC | 2 | Assigned to domain | VVLEERGD | SHLEERGD | ||
| DFAENACH | Due date for follow-up postings | VVDFAENACH | DATS | 8 | DATUM | ||||
| KZ | Change Type (U, I, S, D) | CDCHNGIND | CHAR | 1 | CDCHNGIND |
| Key field | Non-key field |
How do I retrieve data from SAP structure AVIMI26 using ABAP code?
As AVIMI26 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 AVIMI26 as there is no data to select.How to access SAP table AVIMI26
Within an ECC or HANA version of SAP you can also view further information about AVIMI26 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