TXI_VIMI11 SAP (Applications - Real Estate Management) Structure details
Description: Applications - Real Estate Management
Structure field list including key, data, relationships and ABAP select examples
TXI_VIMI11 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 "Applications - Real Estate Management" 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_TXI_VIMI11 TYPE TXI_VIMI11.
The TXI_VIMI11 table consists of various fields, each holding specific information or linking keys about Applications - Real Estate Management data available in SAP. These include MANDT (Client), SBWNR (Application number), SBWSTA (Applicant status), VADRNR (Business Partner 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 TXI_VIMI11 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 | T000 | MANDT | |||
SBWNR | Application number | SBWNR | NUMC | 7 | Assigned to domain | SBWNR | OWK | ||
SBWSTA | Applicant status | SBWSTA | CHAR | 1 | SBWSTAT | ||||
VADRNR | Business Partner Number | BP_PARTNR | CHAR | 10 | BP000 | ALPHA | BP_PARTNR | BPN | |
SBWTYP | Applicant category | SBWTYP | CHAR | 1 | SBWTYP | OWT | |||
XANSPRP | Contact person | XANSPRP | CHAR | 30 | XMBEZ | ||||
XSTAAT | Nationality | XSTAAT | CHAR | 3 | T005 | LAND1 | |||
XPASSNR | Passport number | XPASSNR | CHAR | 18 | CHAR18 | ||||
DPASSV | Date of submission of passport | DPASSV | DATS | 8 | DDAT | ||||
XARBSTR | Employer street | XARBSTR | CHAR | 35 | XCHA35 | ||||
XARBORT | Employer postcode/city | XARBORT | CHAR | 35 | XCHA35 | ||||
XAVERM | Current landlord | XAVERM | CHAR | 50 | XCH50 | ||||
XAVSTR | Landlord street | XAVSTR | CHAR | 35 | XCHA35 | ||||
XAORT | Postal code/city current landlord | XAORT | CHAR | 35 | XCHA35 | ||||
XREFEREN | Applicant reference data | XREFEREN | CHAR | 35 | XCHA35 | ||||
SBONI | Credit standing application | SBONI | NUMC | 2 | TIV62 | SBONI | |||
XWBONI | Reason for credit standing | XWBONI | CHAR | 50 | XTEXT50 | ||||
XALTSEX | Age/sex of children | XALTSEX | CHAR | 35 | XCHA35 | ||||
APERS | Number of persons | APERS | DEC | 3 | DEC3 | ||||
SBUEADR | Guarantor address | SBUEADR | CHAR | 10 | SPRT1 | SPARTNR | |||
XTIER1 | Domestic animal description | XTIERE | CHAR | 35 | XCHA35 | ||||
XABSAGE | Reason for rejection | XABSAGE | CHAR | 60 | XLBEZ | ||||
DABSAGE | Rejection date | DABSAGE | DATS | 8 | DDAT | ||||
XSITZ | Company head office | XSITZ | CHAR | 35 | XCHA35 | ||||
JOPTIO | Opting approved | JOPTIO | CHAR | 1 | JANEI | ||||
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 | ||||
DEINB | Date application was received | DEINB | DATS | 8 | DDAT | ||||
JLOESCH | Real Estate Deletion Indicator/Flag | JLOESCH | CHAR | 1 | JLOESCH | ||||
IMKEY | Internal Key for Real Estate Object | IMKEY | CHAR | 8 | IMKEY | ||||
INTRENO | Internal Real Estate Master Data Code | VVINTRENO | CHAR | 13 | VVINTRENO | ||||
RBELBIND1 | Occupancy obligation key | RBELBIND | CHAR | 4 | Assigned to domain | RBELBIND | |||
RBELBIND2 | Occupancy obligation key | RBELBIND | CHAR | 4 | Assigned to domain | RBELBIND | |||
RBELBIND3 | Occupancy obligation key | RBELBIND | CHAR | 4 | Assigned to domain | RBELBIND | |||
RBELBIND4 | Occupancy obligation key | RBELBIND | CHAR | 4 | Assigned to domain | RBELBIND | |||
DENDB | Application valid to | VVDENDB | DATS | 8 | DDAT | ||||
BEARKZ | Processing Indicator for Rental Request | VVIBEARKZ | CHAR | 4 | TIVC1 | CHAR4 | |||
VORMKZ | Preselection Indicator for Rental Request | VVIVORMKZ | CHAR | 4 | TIVC2 | CHAR4 | |||
BSTAT | Rental Request Processing Status | VVIBSTAT | CHAR | 4 | TIVC3 | CHAR4 | |||
BERGRP | Authorization group | VVBERGRP | CHAR | 40 | VVBERGRP | ||||
PARTFROM | Source of Prospect | VVIPARTFROM | CHAR | 4 | TIVP1 | CHAR4 | |||
PARTWHY | Reason for Acquisition | VVIPARTWHY | CHAR | 4 | TIVP2 | CHAR4 | |||
PARTWAY | Enquiry method | VVIWAY | CHAR | 4 | TIVP3 | CHAR4 |
Key field | Non-key field |
How do I retrieve data from SAP structure TXI_VIMI11 using ABAP code?
As TXI_VIMI11 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 TXI_VIMI11 as there is no data to select.How to access SAP table TXI_VIMI11
Within an ECC or HANA version of SAP you can also view further information about TXI_VIMI11 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