MIMEPHIO_VERS SAP (Version Display: PHIO Properties) Structure details
Description: Version Display: PHIO Properties
Related tables to MIMEPHIO_VERS
Access table MIMEPHIO_VERS
Structure field list including key, data, relationships and ABAP select examples
MIMEPHIO_VERS 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 "Version Display: PHIO Properties" 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_MIMEPHIO_VERS TYPE MIMEPHIO_VERS.
The MIMEPHIO_VERS table consists of various fields, each holding specific information or linking keys about Version Display: PHIO Properties data available in SAP. These include CLASS (Document class), OBJID (ID for documents and relations), FILE_SIZE (File size (in bytes)), BINARY_FLG (Flag for binary files).. 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)
SAP MIMEPHIO_VERS 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 |
| CLASS | Document class | SDOK_CLASS | CHAR | 10 | SDOKIOCL | SDOK_CLASS | |||
| OBJID | ID for documents and relations | SDOK_DOCID | CHAR | 32 | SDOK_DOCID | ||||
| FILE_SIZE | File size (in bytes) | SDOK_FSIZE | NUMC | 12 | SDOK_FSIZE | ||||
| BINARY_FLG | Flag for binary files | SDOK_BINFL | CHAR | 1 | XFELD | ||||
| FIRST_LINE | Line number in internal table | SDOK_LINNM | NUMC | 12 | SDOK_LINNM | ||||
| LAST_LINE | Line number in internal table | SDOK_LINNM | NUMC | 12 | SDOK_LINNM | ||||
| FILE_NAME | Relative storage location of physical document | SDOK_FILNM | CHAR | 255 | SDOK_FILNM | ||||
| MIMETYPE | HTML content type | W3CONTTYPE | CHAR | 128 | W3_CONTTYP | ||||
| PROPERTY | Component attribute for the application | SDOK_COMPR | CHAR | 4 | SDOK_FORM | ||||
| KW_RELATIVE_URL | Name | SKWF_URLP | CHAR | 40 | SDOK_PRV_L | ||||
| CHNG_USER | Last changed by | SDOK_CHUSR | CHAR | 12 | USERNAME | ||||
| CHNG_TIME | Time of change (UTC) | SDOK_CHTST | NUMC | 14 | TSTLC | SDOK_TSTMP | |||
| DESCRIPTION | Title of a document | SDOK_TITEL | CHAR | 64 | TEXT64 |
| Key field | Non-key field |
How do I retrieve data from SAP structure MIMEPHIO_VERS using ABAP code?
As MIMEPHIO_VERS 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 MIMEPHIO_VERS as there is no data to select.How to access SAP table MIMEPHIO_VERS
Within an ECC or HANA version of SAP you can also view further information about MIMEPHIO_VERS 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