ISU_DM_MR_COVER_P_S_DEV_LOC SAP (Device Location) Structure details
Description: Device Location
Related tables to ISU_DM_MR_COVER_P_S_DEV_LOC
Access table ISU_DM_MR_COVER_P_S_DEV_LOC
Structure field list including key, data, relationships and ABAP select examples
ISU_DM_MR_COVER_P_S_DEV_LOC 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_ISU_DM_MR_COVER_P_S_DEV_LOC TYPE ISU_DM_MR_COVER_P_S_DEV_LOC.
The ISU_DM_MR_COVER_P_S_DEV_LOC 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 (Deep)
SAP ISU_DM_MR_COVER_P_S_DEV_LOC 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 |
| WA_DEV_LOC | 0 | ||||||||
| MANDT | Client | MANDT | CLNT | 3 | MANDT | ||||
| DEVLOC | Device Location | DEVLOC | CHAR | 30 | TPLNR | TPLNR | GEP | EGPL | |
| SPRAS | Language Key | SPRAS | LANG | 1 | 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 | TPLKZ | ISR | |||
| FLTYP | Functional location category | FLTYP | CHAR | 1 | FLTYP | IFT | |||
| HAUS | Connection Object | HAUS | CHAR | 30 | TPLNR | TPLNR | HAU | EHAU | |
| DATAB | Valid-From Date | DATAB | DATS | 8 | DATUM | ||||
| BEGRU | Technical object authorization group | IAUTG | CHAR | 4 | IAUTG | ||||
| EINZLI | Data origin for authorization group field | INH_BEGRUI | CHAR | 1 | INHER | ||||
| IWERK | Maintenance Planning Plant | IWERK | CHAR | 4 | 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 | ALPHA | VSTELLE | VBS | EVBS | |
| SWERK | Maintenance plant | SWERK | CHAR | 4 | WERKS | SWK | |||
| SWERKI | Data origin for maintenance plant field | INH_SWERKI | CHAR | 1 | INHER | ||||
| BUKRS | Company Code | BUKRS | CHAR | 4 | BUKRS | BUK | C_T001 | ||
| BUKRSI | Data origin for company code field | INH_BUKRSI | CHAR | 1 | INHER | ||||
| ADRNR | Address number | AD_ADDRNUM | CHAR | 10 | ALPHA | AD_ADDRNUM | ADR | ||
| ADRNRI | Data origin for address field | INH_ADRNRI | CHAR | 1 | INHER | ||||
| STORT | Location of maintenance object | PMLOC | CHAR | 10 | 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 | ILOAN | ||||
| OBJNR | Object number | J_OBJNR | CHAR | 22 | 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 | ||||
| WA_LOCATION_T | 0 | ||||||||
| MANDT | Client | MANDT | CLNT | 3 | MANDT | ||||
| WERKS | Plant | WERKS_D | CHAR | 4 | WERKS | WRK | H_T001W_C | ||
| STAND | Location | STORT_T499S | CHAR | 10 | AP_STAND | ||||
| KTEXT | Text, 40 Characters Long | TEXT40 | CHAR | 40 | TEXT40 | ||||
| ADDRNUM | Address number | AD_ADDRNUM | CHAR | 10 | ALPHA | AD_ADDRNUM | ADR | ||
| T_DEVICE | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure ISU_DM_MR_COVER_P_S_DEV_LOC using ABAP code?
As ISU_DM_MR_COVER_P_S_DEV_LOC 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 ISU_DM_MR_COVER_P_S_DEV_LOC as there is no data to select.How to access SAP table ISU_DM_MR_COVER_P_S_DEV_LOC
Within an ECC or HANA version of SAP you can also view further information about ISU_DM_MR_COVER_P_S_DEV_LOC 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