TXI_VIOB02 SAP (Property master data) Structure details
Description: Property master data
Structure field list including key, data, relationships and ABAP select examples
TXI_VIOB02 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 "Property master data" 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_VIOB02 TYPE TXI_VIOB02.
The TXI_VIOB02 table consists of various fields, each holding specific information or linking keys about Property master data data available in SAP. These include MANDT (Client), BUKRS (Company Code), SWENR (Site Number), SGRNR (Property Number for BE).. 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 TXI_VIOB02 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 | |
SWENR | Site Number | SWENR | CHAR | 8 | VIOB01 | SWENR | SWENR | WEH | MCWE |
SGRNR | Property Number for BE | SGRNR | CHAR | 8 | Assigned to domain | SGRNR | SGRNR | GRS | MCGR |
XGRTXT | Text for property | XGRTXT | CHAR | 60 | XLBEZ | ||||
SGRUNDB | Land register number | SGRUNDB | NUMC | 8 | VIGBUCH | SGRUNDB | GBS | ||
RGRNART | Usage Type of Property According to Land Use Map | RGRNART | CHAR | 2 | TIVC4 | CHAR2 | |||
BDMQMB1 | Market value | BDMQMB1 | CURR | 13(2) | WRTV7 | ||||
BDMQMB2 | Purchase price | BDMQMB2 | CURR | 13(2) | WRTV7 | ||||
BDNRWERT | Land reference value for determining current market value | BDNRWERT | CURR | 13(2) | WRTV7 | ||||
BDNWERT | Land value for determining current market value | BDNWERT | CURR | 13(2) | WRTV7 | ||||
DBDNWERT | Date of land value | DBDNWERT | DATS | 8 | DDAT | ||||
RBEPLAN | Development plan | RBEPLAN | CHAR | 30 | XMBEZ | ||||
DBEPLAN | Date of development plan | DBEPLAN | DATS | 8 | DDAT | ||||
XNUTZGRU | Current usage of property | XNUTZGRU | CHAR | 30 | XMBEZ | ||||
NZGRZ | Permitted Usage: Site Occupancy Index | NZGRZ | DEC | 3(2) | DEC1_2 | ||||
NZGFZ | Permitted Usage: Floor Area Ratio | NZGFZ | DEC | 4(2) | DEC2_2 | ||||
NZBMZ | Permitted Usage: Construction Dimension Number | NZBMZ | DEC | 5(2) | DEC3_2 | ||||
NTGRZ | Actual Usage: Site Occupancy Index | NTGRZ | DEC | 3(2) | DEC1_2 | ||||
NTGFZ | Actual Usage: Floor Area Ratio | NTGFZ | DEC | 4(2) | DEC2_2 | ||||
NTBMZ | Actual Usage: Construction Dimension Number | NTBMZ | DEC | 5(2) | DEC3_2 | ||||
JVORKAUF | Preemptive right indicator | JVORKAUF | CHAR | 1 | JANEI | ||||
JAUSNAHM | Special licence indicator | JAUSNAHM | CHAR | 1 | JANEI | ||||
JGRUNDW | Ground water indicator | JGRUNDW | CHAR | 1 | JANEI | ||||
JUEBERS | Danger of flooding indicator | JUEBERS | CHAR | 1 | JANEI | ||||
RARTOPT | Option rate calculation type | RARTOPT | NUMC | 1 | RARTOPT | ||||
JLOESCH | Real Estate Deletion Indicator/Flag | JLOESCH | CHAR | 1 | JLOESCH | ||||
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 | ||||
DAKTBEST | Date active in portfolio | DAKTBEST | DATS | 8 | DATUM | ||||
ADRNR | Object number (virtual object) | SOBJNR | NUMC | 10 | SANO1 | SOBJNR | |||
RNBPLAN | Usage type according to development plan | RNBPLAN | CHAR | 4 | TIVB3 | RGRNART | |||
IMKEY | Internal Key for Real Estate Object | IMKEY | CHAR | 8 | IMKEY | ||||
KOSTL | Cost Center | KOSTL | CHAR | 10 | Assigned to domain | ALPHA | KOSTL | KOS | |
J_OBJNR | Object number | J_OBJNR | CHAR | 22 | ONR00 | J_OBJNR | ONR | ||
RFAKT | Conversion factor for fractional share of property | VVRFAKT | NUMC | 6 | VVRFAKT | ||||
SGRART | Property type | VVSGRART | NUMC | 4 | TIV56 | VVSGRART | |||
SGRQAL | Property: Quality of location | VVSGRQAL | NUMC | 3 | TIV57 | VVSGRQAL | |||
SGRFRM | Property ground type | VVSGRFRM | NUMC | 3 | TIV58 | VVSGRFRM | |||
SGRGZS | Overall condition of property | VVSGRGZS | NUMC | 3 | TIV59 | VVSGRGZS | |||
PRCTR | Profit Center | PRCTR | CHAR | 10 | CEPC | ALPHA | PRCTR | PRC | PRCTR_EMPTY |
DWIRTUB | Transfer usage / charges | VVDWIRTUB | DATS | 8 | DATUM | ||||
DVERKAUF | Sale date | VVDVERKAUF | DATS | 8 | DATUM | ||||
SUNUTZA | Main usage type | VVSUNART | CHAR | 8 | TIV36 | VVSUNART | |||
JUNUTZA | Indicator: Predominant usage type ' '-ANLKL, 'X'-TIV36 | VVJUNUTZA | CHAR | 1 | JANE | ||||
PROFL | Settlement profile for costs | VVAPROF | CHAR | 6 | TKB1A | ALPHA | APROF | ||
KOKRS | Controlling Area | KOKRS | CHAR | 4 | TKA01 | CACCD | CAC | ||
DVRKPLAN | Planned sale | VVDVRKPLAN | DATS | 8 | DATUM | ||||
INTRENO | Internal Real Estate Master Data Code | VVINTRENO | CHAR | 13 | VVINTRENO | ||||
GSBER | Business Area | GSBER | CHAR | 4 | TGSB | GSBER | GSB | ||
TXJCD | Tax Jurisdiction | TXJCD | CHAR | 15 | Assigned to domain | TXJCD | TXJ | ||
BERGRP | Authorization group | VVBERGRP | CHAR | 40 | VVBERGRP | ||||
XGEMARK | Local Subdistrict | VVGEMARK | CHAR | 12 | TIVG2 | VVGEMARK | |||
NFLURNR | Number of Tract of Land in Land Register | NFLURNR | CHAR | 6 | NFLURNR | ||||
XFLURST | Parcel of Land | XFLURST | CHAR | 10 | TEXT10 | ||||
BRFLURST | Fractional Parcel of Land | VVBRFLURST | CHAR | 4 | VVBRFLURST | ||||
JERBBAU | Heritable building right indicator | JERBBAU | CHAR | 1 | TDO9 | SOBJERBBAU | |||
GEMEINDE | Municipality key | VVGEMEINDE | CHAR | 8 | TIVG1 | VVGEMEINDE | |||
ZULBAUH | Permitted building height | VVZULBAUH | QUAN | 4 | VVZULBAUH | ||||
LEINS | Unit of length | VVLEINS | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
.INCLU--AP | 0 | ||||||||
BLOCK | Block/section/tract | HB_BLOCK | CHAR | 10 | HBS_BLOCK | ||||
FRONTAGE | Length of the Lot Facing the Street | HB_FRNTGE | QUAN | 8(2) | HBS_QUAN | ||||
DEPTH | Depth of the Lot | HB_DEPTH | QUAN | 8(2) | HBS_QUAN | ||||
LOTSIZE | Area of the Lot | HB_SIZE | QUAN | 8(2) | HBS_QUAN | ||||
REFNO | External Reference Number | HB_REFNO | CHAR | 24 | HBS_REFNO | ||||
HB_MARKER | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
PHASE | Development Phase Allocated to the Lot | HB_PPHSE | CHAR | 11 | HBSPPH | HBS_PHASE | |||
.INCLU--AP | 0 | ||||||||
VALIDFROM | Date: Object Valid From | REBDOBJVALIDFROM | DATS | 8 | RECADATEBEG | ||||
VALIDTO | Date: Object Valid To | REBDOBJVALIDTO | DATS | 8 | REDAT | RECADATEEND | |||
CREATIONTYPE | How the Object Was Created | RECACREATIONTYPE | CHAR | 1 | RECACREATIONTYPE | ||||
RESPONSIBLE | Person Responsible | RECARESPONSIBLE | CHAR | 12 | Assigned to domain | XUBNAME | USER_COMP | ||
USEREXCLUSIVE | User with Exclusive Change Authorization | RECAUSEREXCLUSIVE | CHAR | 12 | Assigned to domain | XUBNAME | USER_COMP | ||
BDMQMB1_CY | CUKY for SYST | SYCUKY | CUKY | 5 | SYCUKY | ||||
BDMQMB2_CY | CUKY for SYST | SYCUKY | CUKY | 5 | SYCUKY | ||||
BDNRWERT_CY | CUKY for SYST | SYCUKY | CUKY | 5 | SYCUKY | ||||
BDNWERT_CY | CUKY for SYST | SYCUKY | CUKY | 5 | SYCUKY | ||||
ZULBAUH_QY | Unit | UNIT | UNIT | 3 | CUNIT | EINHEIT |
Key field | Non-key field |
How do I retrieve data from SAP structure TXI_VIOB02 using ABAP code?
As TXI_VIOB02 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_VIOB02 as there is no data to select.How to access SAP table TXI_VIOB02
Within an ECC or HANA version of SAP you can also view further information about TXI_VIOB02 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