MCIEQUI SAP (PMIS: PM equipment master) Structure details
Description: PMIS: PM equipment master
Structure field list including key, data, relationships and ABAP select examples
MCIEQUI 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 "PMIS: PM equipment master" 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_MCIEQUI TYPE MCIEQUI.
The MCIEQUI table consists of various fields, each holding specific information or linking keys about PMIS: PM equipment master data available in SAP. These include BEGRU (PMIS: Authorization group for equipment), EQTYP (Equipment category), EQART (Type of Technical Object), INVNR (Inventory number).. 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 MCIEQUI 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 |
EQUNR | Equipment Number | EQUNR | CHAR | 18 | EQUI | ALPHA | EQUNR | EQN | EQUI |
BEGRU | PMIS: Authorization group for equipment | EAUTG | CHAR | 4 | T370B | IAUTG | |||
EQTYP | Equipment category | EQTYP | CHAR | 1 | T370T | EQTYP | EQT | ||
EQART | Type of Technical Object | EQART | CHAR | 10 | T370K | EQART | |||
INVNR | Inventory number | INVNR | CHAR | 25 | INVNR_ANLA | ||||
ANSDT | Acquisition date | ANDTI | DATS | 8 | DATUM | ||||
ELIEF | Vendor number | ELIEF | CHAR | 10 | LFA1 | ALPHA | LIFNR | ||
HERST | Manufacturer of asset | HERST | CHAR | 30 | TEXT30 | ||||
SERGE | Manufacturer serial number | SERGE | CHAR | 30 | CHAR30 | ||||
TYPBZ | Manufacturer model number | TYPBZ | CHAR | 20 | TYPBZ | ||||
GERNR | Serial Number | GERNR | CHAR | 18 | GERNR | GERNR | SER | ||
EQLFN | Consecutive numbering of EquipUsagePeriods on same day | EQLFN | NUMC | 3 | NUM03 | EQL | |||
BAUJJ | Year of construction | BAUJJ | CHAR | 4 | GJAHR | CJAHR | |||
SDATE | Date | DATUM | DATS | 8 | DATUM | ||||
.INCLU--AP | 0 | ||||||||
CUOBJ | Configuration (internal object number) | CUOBJ | NUMC | 18 | CUOBJ | CUX | |||
SERNR | Serial Number | GERNR | CHAR | 18 | GERNR | GERNR | SER | ||
KMATN | Configurable Material | KMATN | CHAR | 18 | Assigned to domain | MATN1 | MATNR | MAT1 | |
.INCLU--AP | 0 | ||||||||
J_3GEIGNER | Owner | J_3GEIGNER | CHAR | 12 | Assigned to domain | J_3GEIGVER | J_3GEE | ||
J_3GVERWAL | Administrator | J_3GVERWAL | CHAR | 12 | Assigned to domain | J_3GEIGVER | J_3GEV | ||
J_3GKONDE | Material Pricing Group | KONDM | CHAR | 2 | T178 | KONDM | VKM | ||
J_3GEIFR | Indicator for Own/External Equipment | J_3GEIFR | CHAR | 1 | J_3GEIFR | ||||
J_3GEQART | Procurement Type for External Equipment | J_3GEQART | CHAR | 10 | J_3GEQART |
Key field | Non-key field |
How do I retrieve data from SAP structure MCIEQUI using ABAP code?
As MCIEQUI 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 MCIEQUI as there is no data to select.How to access SAP table MCIEQUI
Within an ECC or HANA version of SAP you can also view further information about MCIEQUI 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