ESO_S_INET SAP (Enterprise Search: Object Link) Structure details
Description: Enterprise Search: Object Link
Structure field list including key, data, relationships and ABAP select examples
ESO_S_INET 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 "Enterprise Search: Object Link" 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_ESO_S_INET TYPE ESO_S_INET.
The ESO_S_INET table consists of various fields, each holding specific information or linking keys about Enterprise Search: Object Link data available in SAP. These include MLANG (Primary language for object texts), NETID (Network identification), KANTYP (Link category), TPVON (Link from functional location).. 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 (Deep)
SAP ESO_S_INET 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 |
KANTE | Number of the link between two technical objects | KANTE | CHAR | 18 | Assigned to domain | ALPHA | KANTE | INE | |
MLANG | Primary language for object texts | MLANG | LANG | 1 | Assigned to domain | ISOLA | SPRAS | ||
NETID | Network identification | NETID | CHAR | 8 | Assigned to domain | NETID | |||
KANTYP | Link category | KANTYP | CHAR | 1 | KANTYP | ||||
TPVON | Link from functional location | TPVON | CHAR | 30 | Assigned to domain | TPLNR | TPLNR | IFLM | |
EQVON | Link from equipment | EQVON | CHAR | 18 | Assigned to domain | ALPHA | EQUNR | ||
TPNACH | Link to functional location | TPNACH | CHAR | 30 | Assigned to domain | TPLNR | TPLNR | IFLM | |
EQNACH | Link to equipment | EQNACH | CHAR | 18 | Assigned to domain | ALPHA | EQUNR | ||
LFDKNR | Number for parallel links between objects | LFDKNR | NUMC | 4 | LFDKNR | ||||
DATVA | Date from which the link created is valid | DATVA | DATS | 8 | DATUM | ||||
ZEITVA | Time from which the link created is valid | DZEITVA | TIMS | 6 | UZEIT | ||||
DATVB | Date to which the link created is valid | DATVB | DATS | 8 | DATUM | ||||
ZEITVB | Time until which the link created is valid | DZEITVB | TIMS | 6 | UZEIT | ||||
STATUS | Object number | J_OBJNR | CHAR | 22 | Assigned to domain | J_OBJNR | ONR | ||
TPKANT | Link object is a functional location | TPKANT | CHAR | 30 | Assigned to domain | TPLNR | TPLNR | IFLM | |
EQKANT | Link object is a piece of equipment | EQKANT | CHAR | 18 | Assigned to domain | ALPHA | EQUNR | ||
MEDIU | Medium | MEDIU | CHAR | 6 | Assigned to domain | MEDIU | |||
BEZARP | Relationship type possible | BEZARP | CHAR | 1 | BEZARP | ||||
BEZARL | Relationship type used | BEZARL | CHAR | 1 | BEZARL | ||||
ERDAT | Date on which the object was created | ICRDT | DATS | 8 | DATUM | ||||
ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
AEDAT | Date on which the object was last changed | IUPDT | DATS | 8 | DATUM | ||||
AENAM | Name of Person Who Changed Object | AENAM | CHAR | 12 | USNAM | ||||
BEGRU | Technical object authorization group | IAUTG | CHAR | 4 | Assigned to domain | IAUTG | |||
LVORM | Deletion Indicator | LVORM | CHAR | 1 | XFELD | ||||
NETYP | Link category | NETYP | CHAR | 1 | Assigned to domain | NETYP | ILT | ||
KANTE_EXT | Number of the link between two technical objects | KANTE | CHAR | 18 | Assigned to domain | ALPHA | KANTE | INE | |
TPVON_EXT | Link from functional location | TPVON_STRNO | CHAR | 40 | ILOM_STRNO | ||||
EQVON_EXT | Link from equipment | EQVON | CHAR | 18 | Assigned to domain | ALPHA | EQUNR | ||
TPNACH_EXT | Link to functional location | TPNACH_STRNO | CHAR | 40 | ILOM_STRNO | ||||
EQNACH_EXT | Link to equipment | EQNACH | CHAR | 18 | Assigned to domain | ALPHA | EQUNR | ||
DOCLINK_DOKOB | Linked SAP Object | DOKOB | CHAR | 10 | Assigned to domain | DOKOB | |||
DOCLINK_OBJKY | Document management object key | OBJKY | CHAR | 50 | CHAR50 | ||||
TPKANT_EXT | Link object is a functional location | TPKANT_STRNO | CHAR | 40 | ILOM_STRNO | ||||
EQKANT_EXT | Link object is a piece of equipment | EQKANT | CHAR | 18 | Assigned to domain | ALPHA | EQUNR |
Key field | Non-key field |
How do I retrieve data from SAP structure ESO_S_INET using ABAP code?
As ESO_S_INET 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 ESO_S_INET as there is no data to select.How to access SAP table ESO_S_INET
Within an ECC or HANA version of SAP you can also view further information about ESO_S_INET 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