IMINF SAP (Information Model: Interface) Structure details
Description: Information Model: Interface
Structure field list including key, data, relationships and ABAP select examples
IMINF 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 "Information Model: Interface" 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_IMINF TYPE IMINF.
The IMINF table consists of various fields, each holding specific information or linking keys about Information Model: Interface data available in SAP. These include FLG_ENTRY (IM interface entry flag), SKIP_ENT_1 (IM interface skip_screen flag), SKIP_ENT_3 (IM interface skip_screen flag), SKIP_DMO_1 (IM interface skip_screen flag).. 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 IMINF 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 |
| READ_ONLY | IM interface for READ_ONLY flag | UDINFREAD | CHAR | 1 | UDCHA1 | ||||
| FLG_ENTRY | IM interface entry flag | UDINFENTR | CHAR | 4 | UDCHA4 | ||||
| SKIP_ENT_1 | IM interface skip_screen flag | UDINFSKIP | CHAR | 1 | UDCHA1 | ||||
| SKIP_ENT_3 | IM interface skip_screen flag | UDINFSKIP | CHAR | 1 | UDCHA1 | ||||
| SKIP_DMO_1 | IM interface skip_screen flag | UDINFSKIP | CHAR | 1 | UDCHA1 | ||||
| SKIP_DMO_3 | IM interface skip_screen flag | UDINFSKIP | CHAR | 1 | UDCHA1 | ||||
| SAVE_OK | IM interface SAVE_OK_CODE | UDINFOK | CHAR | 4 | UDCHA4 | ||||
| EXT_DOC | IM interface Extend_Documentation_Flag | UDEXTDOCU | CHAR | 1 | UDCHA1 | ||||
| ENTID | Entity ID | UDENTID | CHAR | 4 | UDENTID | ||||
| VERSION | Version | UDVERSION | CHAR | 2 | UDVERSION | ||||
| VARIANT | Variant | UDVARIANT | CHAR | 2 | UDCHA2 | ||||
| LANGBZ_ENT | Long name | UDLANGBEZ | CHAR | 60 | UDCHA60 | ||||
| DMOID | Data model ID | UDDMOID | CHAR | 10 | UDDMOID | ||||
| DMVERSION | Version | UDVERSION | CHAR | 2 | UDVERSION | ||||
| LANGBZ_DMO | Long name | UDLANGBEZ | CHAR | 60 | UDCHA60 | ||||
| CLUID | Identification of EDM cluster | UDCLUID | CHAR | 10 | UDCLUID | ||||
| CLVERSION | Version | UDVERSION | CHAR | 2 | UDVERSION | ||||
| LANGBZ_CL | Long name | UDLANGBEZ | CHAR | 60 | UDCHA60 | ||||
| PROF | EDM profiles | UDPROF | CHAR | 9 | CHAR9 | ||||
| TCODE | Transaction code | UDTCODE | CHAR | 4 | UDTCODE |
| Key field | Non-key field |
How do I retrieve data from SAP structure IMINF using ABAP code?
As IMINF 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 IMINF as there is no data to select.How to access SAP table IMINF
Within an ECC or HANA version of SAP you can also view further information about IMINF 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