EGPL SAP (Device Location) Structure details
Dictionary Type: Structure
Description: Device Location
Description: Device Location
Structure field list including key, data, relationships and ABAP select examples
EGPL 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 "Device Location" 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_EGPL TYPE EGPL.
The EGPL table consists of various fields, each holding specific information or linking keys about Device Location data available in SAP. These include MANDT (Client), DEVLOC (Device Location), SPRAS (Language Key), PLTXT (Description of 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 (character-type or numeric)
SAP EGPL 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 | Assigned to domain | MANDT | |||
| DEVLOC | Device Location | DEVLOC | CHAR | 30 | Assigned to domain | TPLNR | TPLNR | GEP | EGPL |
| SPRAS | Language Key | SPRAS | LANG | 1 | Assigned to domain | ISOLA | SPRAS | SPR | H_T002 |
| PLTXT | Description of functional location | PLTXT | CHAR | 40 | TEXT40 | ||||
| KZLTX | Indicator: More long text exists | KZLTX | CHAR | 1 | XFELD | ||||
| TPLKZ | Functional location structure indicator | TPLKZ | CHAR | 5 | Assigned to domain | TPLKZ | ISR | ||
| FLTYP | Functional location category | FLTYP | CHAR | 1 | Assigned to domain | FLTYP | IFT | ||
| HAUS | Connection Object | HAUS | CHAR | 30 | Assigned to domain | TPLNR | TPLNR | HAU | EHAU |
| DATAB | Valid-From Date | DATAB | DATS | 8 | DATUM | ||||
| BEGRU | Technical object authorization group | IAUTG | CHAR | 4 | Assigned to domain | IAUTG | |||
| EINZLI | Data origin for authorization group field | INH_BEGRUI | CHAR | 1 | INHER | ||||
| IWERK | Maintenance Planning Plant | IWERK | CHAR | 4 | Assigned to domain | WERKS | IWK | ||
| IWERKI | Data origin for planning plant field | INH_IWERKI | CHAR | 1 | INHER | ||||
| POSNR | Position in superior technical object | ILOM_POSNR | CHAR | 4 | CHAR4 | ||||
| ISTYP | Object category for Industry Solutions (IS) | ILOM_ISTYP | CHAR | 1 | ILOM_ISTYP | ||||
| VSTELLE | Premise | VSTELLE | CHAR | 10 | Assigned to domain | ALPHA | VSTELLE | VBS | EVBS |
| SWERK | Maintenance plant | SWERK | CHAR | 4 | Assigned to domain | WERKS | SWK | ||
| SWERKI | Data origin for maintenance plant field | INH_SWERKI | CHAR | 1 | INHER | ||||
| BUKRS | Company Code | BUKRS | CHAR | 4 | Assigned to domain | BUKRS | BUK | C_T001 | |
| BUKRSI | Data origin for company code field | INH_BUKRSI | CHAR | 1 | INHER | ||||
| ADRNR | Address number | AD_ADDRNUM | CHAR | 10 | Assigned to domain | ALPHA | AD_ADDRNUM | ADR | |
| ADRNRI | Data origin for address field | INH_ADRNRI | CHAR | 1 | INHER | ||||
| STORT | Location of maintenance object | PMLOC | CHAR | 10 | T499S | AP_STAND | |||
| STORTI | Data origin for location field | INH_STORTI | CHAR | 1 | INHER | ||||
| STORTZUS | Addition to device location | STORTZUS | CHAR | 30 | TEXT30 | ||||
| ILOAN | Location and account assignment for technical object | ILOAN | CHAR | 12 | Assigned to domain | ILOAN | |||
| OBJNR | Object number | J_OBJNR | CHAR | 22 | Assigned to domain | J_OBJNR | ONR | ||
| IEQUI | Installation of equipment allowed at the functional location | IEQUI | CHAR | 1 | X | ||||
| IEQUII | Data origin for equip. inst. allowed field | INH_IEQUII | CHAR | 1 | INHER | ||||
| ERDAT | Date on which the object was created | ICRDT | DATS | 8 | DATUM | ||||
| ERNAM | Name of User Who Created the Object | ICRNA | CHAR | 12 | USNAM | ||||
| AEDAT | Date on which the object was last changed | IUPDT | DATS | 8 | DATUM | ||||
| AENAM | Name of the user who last changed the object | IUPNA | CHAR | 12 | USNAM | ||||
| STRNO | Device Location Identification | GP_STRNO | CHAR | 40 | ILOM_STRNO |
| Key field | Non-key field |
How do I retrieve data from SAP structure EGPL using ABAP code?
As EGPL 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 EGPL as there is no data to select.How to access SAP table EGPL
Within an ECC or HANA version of SAP you can also view further information about EGPL 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