VVIOB39 SAP (Change document structure; generated by RSSCD000) Structure details
Description: Change document structure; generated by RSSCD000
Structure field list including key, data, relationships and ABAP select examples
VVIOB39 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; generated by RSSCD000" 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_VVIOB39 TYPE VVIOB39.
The VVIOB39 table consists of various fields, each holding specific information or linking keys about Change document structure; generated by RSSCD000 data available in SAP. These include MANDT (Client), INTRENO (Internal Real Estate Master Data Code), TPLNR (Functional Location), ROART (Real estate object types).. 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 VVIOB39 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 | |||
| INTRENO | Internal Real Estate Master Data Code | VVINTRENO | CHAR | 13 | VVINTRENO | ||||
| TPLNR | Functional Location | TPLNR | CHAR | 30 | IFLOT | TPLNR | TPLNR | IFL | IFLM |
| ROART | Real estate object types | VVROART | NUMC | 2 | VVROART | ||||
| 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 | VIOB02 | SGRNR | SGRNR | GRS | MCGR |
| SGENR | Building Number | SGENR | CHAR | 8 | VIOB03 | SGENR | SGENR | GEB | MCGE |
| SMENR | Number of Rental Unit | SMENR | CHAR | 8 | VIMI01 | SMENR | SMENR | MEH | MCME |
| FLAG_GENERATED | Functional location generated from RE | VVFLAG_GENERATED | CHAR | 1 | JANE | ||||
| .INCLU--AP | 0 | ||||||||
| FLID | VIGWASPID | CHAR | 13 | VIGWFFLID | FLNAS | ||||
| SRAUMEXT | VIGWRAUMEXT | CHAR | 13 | VIGWRAUMEXT | RAU | ||||
| VMFLID | Rental Space | VIGWFFLID | CHAR | 13 | VIGWUFLID | FLN | |||
| KZ | Change Type (U, I, S, D) | CDCHNGIND | CHAR | 1 | CDCHNGIND |
| Key field | Non-key field |
How do I retrieve data from SAP structure VVIOB39 using ABAP code?
As VVIOB39 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 VVIOB39 as there is no data to select.How to access SAP table VVIOB39
Within an ECC or HANA version of SAP you can also view further information about VVIOB39 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