VIBDAO_TAB SAP (Architectural Object: Attributes) Structure details
Description: Architectural Object: Attributes
Structure field list including key, data, relationships and ABAP select examples
VIBDAO_TAB 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 "Architectural Object: Attributes" 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_VIBDAO_TAB TYPE VIBDAO_TAB.
The VIBDAO_TAB table consists of various fields, each holding specific information or linking keys about Architectural Object: Attributes data available in SAP. These include AOTYPE (Architectural Object Type), AONR (Number of Architectural Object), VALIDFROM (Date: Object Valid From), VALIDTO (Date: Object Valid To).. 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 VIBDAO_TAB 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 |
AOTYPE | Architectural Object Type | REBDAOTYPE | CHAR | 4 | TIVBDAROBJTYPE | REBDAOTYPE | REBDAOTYPE | REBDAOTYPE | |
AONR | Number of Architectural Object | REBDAONR | CHAR | 13 | REBDAONR | REBDAONR | REBDAONR | ||
VALIDFROM | Date: Object Valid From | REBDOBJVALIDFROM | DATS | 8 | RECADATEBEG | ||||
VALIDTO | Date: Object Valid To | REBDOBJVALIDTO | DATS | 8 | REDAT | RECADATEEND | |||
PARTSEPARATOR | AOID Code: Separator | REBDPARTSEPARATOR | CHAR | 10 | REBDPARTSEPARATOR | ||||
PARTAOID | AOID Code | REBDPARTAOID | CHAR | 30 | REBDPARTAOID | REBDPARTAOID | |||
XAO | Name of Architectural Object | REBDXAO | CHAR | 60 | RECAXLDESCRIPTION | ||||
AOFUNCTION | Function of Architectural Object | REBDAOFUNCTION | CHAR | 4 | TIVBDARFUNC | ALPHA | REBDAOFUNCTION | ||
USAGECOMMON | Common Usage | REBDUSCOMMON | CHAR | 1 | REBDUSCOMMON | ||||
OBJNR | Object Number | RECAOBJNR | CHAR | 22 | Assigned to domain | J_OBJNR | ONR | ||
AUTHGRP | Authorization Group | RECAAUTHGRP | CHAR | 40 | RECAAUTHGRP | ||||
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 | ||||
RESPONSIBLE | Person Responsible | RECARESPONSIBLE | CHAR | 12 | USR02 | XUBNAME | USER_COMP | ||
USEREXCLUSIVE | User with Exclusive Change Authorization | RECAUSEREXCLUSIVE | CHAR | 12 | USR02 | XUBNAME | USER_COMP | ||
LASTRENO | Date of last redecoration | DRENOV | DATS | 8 | DATUM | ||||
MEASSTRC | Measurement Structure | REBDMEASSTRC | CHAR | 4 | TIVBDMEASSTRC | REBDMEASSTRC | |||
DOORPLT | Short description | REBDDOORPLT | CHAR | 15 | REBDDOORPLT | ||||
RSAREA | Reservation Area | REORRSAREA | CHAR | 10 | TIVORRSAREA | REORRSAREA | |||
SINSTBEZ | Maintenance district | SINSTBEZ | NUMC | 5 | TIV16 | SINSTBEZ | |||
SVERKEHR | Transport Connections of Business Entity | SVERKEHR | CHAR | 1 | TIV44 | SVERKEHR | |||
SLAGEWE | Business entity location number | SLAGEWE | NUMC | 4 | TIV10 | SLAGEWE | |||
SOBJLAGE | Indicator: District Location of Object | RESOBJLAGE | NUMC | 2 | TIV45 | RESOBJLAGE | |||
RGRNART | Usage Type of Property According to Land Use Map | RGRNART | CHAR | 2 | TIVC4 | CHAR2 | |||
RBEPLAN | Development plan | RBEPLAN | CHAR | 30 | XMBEZ | ||||
DBEPLAN | Date of development plan | DBEPLAN | DATS | 8 | DDAT | ||||
RNBPLAN | Usage type according to development plan | RNBPLAN | CHAR | 4 | TIVB3 | RGRNART | |||
XNUTZGRU | Current usage of property | XNUTZGRU | CHAR | 30 | XMBEZ | ||||
SUNUTZA | Main usage type | VVSUNART | CHAR | 8 | TIV36 | VVSUNART | |||
JUNUTZA | Indicator: Predominant usage type ' '-ANLKL, 'X'-TIV36 | VVJUNUTZA | CHAR | 1 | JANE | ||||
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 | ||||
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 | |||
JERBBAU | Heritable building right indicator | JERBBAU | CHAR | 1 | TDO9 | SOBJERBBAU | |||
ZULBAUH | Allowed Building Height (as Integer) | REBDALLOWEDHEIGHT | INT2 | 5 | REBDALLOWEDHEIGHT | ||||
RGEBART | Type of building | RGEBART | NUMC | 2 | TIV5A | SOBJART | |||
RGEBZUST | General condition of building | RGEBZUST | NUMC | 2 | TIV83 | VVRZUSTAND | |||
YBAUJAHR | ConstYr | VVYBAUJAHR | DATS | 8 | DATUM | ||||
JNURJAHR | Indicator: Only regard construction date in terms of years | VVJNURJ | CHAR | 1 | JANE | ||||
YMODERN | Year of modernization | VVYMODERN | DATS | 8 | DATUM | ||||
YAUFBAU | Year of reconstruction | VVYAUFBAU | DATS | 8 | DATUM | ||||
DBAUBEGI | Construction start date | DBAUBEGI | DATS | 8 | DDAT | ||||
DBAUVOR | Date of planning inquiry | DBAUVOR | DATS | 8 | DDAT | ||||
DVORBES | Date of prior notice | DVORBES | DATS | 8 | DDAT | ||||
DANTBAU | Application for building permit | DANTBAU | DATS | 8 | DATUM | ||||
DBAUGENE | Building permit | DBAUGENE | DATS | 8 | DDAT | ||||
XBAUGENE | Note on building permit | XBAUGENE | CHAR | 30 | XMBEZ | ||||
DFERTIG | Completion | DFERTIG | DATS | 8 | DDAT | ||||
DSCHLUSS | Final Inspection | DSCHLUSS | DATS | 8 | DDAT | ||||
DBEZUGSF | Ready for occupancy | DBEZUGSF | DATS | 8 | DDAT | ||||
RDAZUST | Dummy: No Longer Used | RECADUMMYN2 | NUMC | 2 | NUMC2 | ||||
RFAZUST | Dummy: No Longer Used | RECADUMMYN2 | NUMC | 2 | NUMC2 | ||||
JDENKMAL | Protection of Historical Sites | JDENKMAL | CHAR | 1 | JANE | ||||
DFRDVON | Public funding from | VVDFRDVON | DATS | 8 | DATUM | ||||
DFRDBIS | Public funding to | VVDFRDBIS | DATS | 8 | DATUM | ||||
BANZGE | Number of floors | VVBANZGE | DEC | 4(1) | DEC3_1 | ||||
AUGESCH | Number of basements | AUGESCH | DEC | 2 | DEC2 | ||||
SSTCKBIS | Uppermost Floor of a Building | VVSTCKBIS | NUMC | 3 | TIV37 | VVSSTOCKW | |||
SLIFTBIS | Elevator to Floor in Building | VVLIFTBIS | NUMC | 3 | TIV37 | VVSSTOCKW | |||
NSTCKLFT | Number of highest floor reached by elevator | VVNSTCKLFT | NUMC | 3 | NUMC3 |
Key field | Non-key field |
How do I retrieve data from SAP structure VIBDAO_TAB using ABAP code?
As VIBDAO_TAB 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 VIBDAO_TAB as there is no data to select.How to access SAP table VIBDAO_TAB
Within an ECC or HANA version of SAP you can also view further information about VIBDAO_TAB 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