SAPFree referencePDF, Excel, Word exportSAP ECC / S/4HANA

SAP PM Database Tables Reference (AUFK, AFIH, QMEL, EQUI and More)

When a maintenance KPI report, data migration or interface needs data that standard transactions do not show, you end up in SE16N or an ABAP select. This reference lists the tables that matter in SAP plant maintenance, with key fields and what each one holds.

Download:

Table	Description	Key fields	Area	Typical use
AUFK	Order master data	AUFNR	Orders	Order type, plant, texts, status object number OBJNR
AFIH	Maintenance order header (PM specific)	AUFNR	Orders	Equipment, functional location, planner group, notification link
AFKO	Order header data (scheduling)	AUFNR	Orders	Basic and scheduled start and finish dates
AFVC	Operation within an order	AUFPL, APLZL	Orders	Operation number, work center, control key
AFVV	Quantities, values and dates of the operation	AUFPL, APLZL	Orders	Planned work and duration per operation
AFRU	Order completion confirmations	RUECK, RMZHL	Orders	Actual hours, confirmation text, final confirmation flag
RESB	Reservation and dependent requirements	RSNUM, RSPOS, RSART	Orders	Planned spare parts per order
MSEG	Document segment: material	MBLNR, MJAHR, ZEILE	Orders	Goods issues posted to orders
T003O	Order types	AUART	Customizing	Order type configuration
QMEL	Quality notification header	QMNUM	Notifications	Notification type, dates, reporter, priority
QMIH	Quality message: PM specific data	QMNUM	Notifications	Equipment, functional location, breakdown indicator
QMFE	Quality notification items	QMNUM, FENUM	Notifications	Damage and object part codes
QMUR	Quality notification causes	QMNUM, FENUM, URNUM	Notifications	Cause codes for failure analysis
QMMA	Quality notification activities	QMNUM, MANUM	Notifications	Activity codes recorded on a notification
QMSM	Quality notification tasks	QMNUM, MANUM	Notifications	Planned tasks on a notification
EQUI	Equipment master data	EQUNR	Technical objects	Equipment category, manufacturer, serial number
EQUZ	Equipment time segment	EQUNR, DATBI, EQLFN	Technical objects	Installation data and link to ILOA via ILOAN
EQKT	Equipment short texts	EQUNR, SPRAS	Technical objects	Equipment description by language
IFLOT	Functional location	TPLNR	Technical objects	Functional location master and category
IFLOTX	Functional location short texts	TPLNR, SPRAS	Technical objects	Functional location description by language
ILOA	PM object location and account assignment	ILOAN	Technical objects	Maintenance plant, cost center, location, TPLNR
IHPA	Plant maintenance partners	OBJNR, PARVW, COUNTER	Technical objects	Partner roles on orders and notifications
T370	Equipment categories	EQTYP	Customizing	Equipment category configuration
T370F	Functional location categories	FLTYP	Customizing	Functional location category configuration
T024I	Maintenance planner groups	IWERK, INGRP	Customizing	Planner group per planning plant
MPLA	Maintenance plan header	WARPL	Preventive maintenance	Plan category, strategy, scheduling parameters
MPOS	Maintenance item	WAPOS	Preventive maintenance	Link of plan to object and task list
MHIS	Maintenance plan history	WARPL, ZAEHL	Preventive maintenance	Planned and completion dates per call
MHIO	Maintenance call object	WARPL, ZAEHL	Preventive maintenance	Call objects generated from plan
T351	Maintenance strategies	STRAT	Customizing	Strategy definitions and scheduling indicators
T351P	Maintenance packages	STRAT, ZAEHL	Customizing	Packages (cycles) within a strategy
PLKO	Task list header	PLNTY, PLNNR, PLNAL	Task lists	Task list type, group and group counter
PLPO	Task list operation	PLNTY, PLNNR, PLNKN	Task lists	Operations, work center, text
MAPL	Assignment of task lists to materials	MATNR, WERKS, PLNTY, PLNNR	Task lists	Find the task list behind an object
DIIMPT	Measuring points	POINT	Condition monitoring	Measuring point master
IMRG	Measurement documents	MDOCM	Condition monitoring	Counter and measurement readings
JEST	Individual object status	OBJNR, STAT	Status	Active system and user statuses
JSTO	Status object information	OBJNR	Status	Status profile assigned to the object
TJ02T	System status texts	ISTAT, SPRAS	Status	Translate I-codes into REL, TECO, CLSD
CRHD	Work center header	OBJTY, OBJID	Master data	Work center, plant and category
KLAH	Class header data	CLINT	Classification	Class definition for equipment classes
AUSP	Characteristic values	OBJEK, ATINN, ATZHL	Classification	Classification values of technical objects

Table and field names are stable across ECC and S/4HANA for the on-premise PM data model, but verify in SE11 for your release. Several joins need OBJNR, ILOAN or AUFPL, which are internal numbers rather than the numbers users see.

PM data extract review

Optional: send us a report you maintain by hand and we will tell you how it could be answered directly from SAP data.

Optional. The tool and every export work without this. No spam.

How to use the table list

Type a table name, a topic such as notification or equipment, or a field name into the search box. Use the Area column to narrow to orders, notifications, technical objects, preventive maintenance, task lists, status or customizing. The Key fields column tells you how to join: for example orders and notifications connect through AFIH-QMNUM, and equipment connects to location data through EQUZ-ILOAN and ILOA-ILOAN. Export the filtered list to Excel to keep a project data dictionary.

Search by table, description or typical use
Filter to one area to see a single process end to end
Export to Excel for migration mapping documents

The joins that cause the most confusion

Four joins explain most PM reports. First, AUFK to AFIH by AUFNR gives order header plus PM data. Second, AFIH to AFVC goes through AFKO-AUFPL, because operations hang off the routing number and not the order number. Third, any status question goes through OBJNR into JEST, then TJ02T for the readable status code. Fourth, equipment and functional location both pull location and cost center from ILOA through ILOAN. Learn these four and the rest follows.

Reading and cautions

Reading from tables is safe, writing to them is not. Never update PM tables directly with SE16N edit or custom SQL, because status, change documents and dependent objects will go out of sync. Use BAPIs or standard transactions for changes. Also remember that EQUZ and several others are time segmented, so filter DATBI to the open-ended date to get the current record. On S/4HANA, some legacy tables still exist but are served as compatibility views, so check the data model for your release.

Frequently Asked Questions

Which table holds SAP maintenance order data?

The order master sits in AUFK, with PM specific fields such as equipment, functional location and planner group in AFIH. Dates are in AFKO, operations in AFVC, and confirmations in AFRU. Join them by AUFNR, and by AUFPL for operations.

How do I link a notification to its order?

The notification number is stored in the order header table AFIH in field QMNUM. Join QMEL or QMIH on QMNUM to get the notification data. In reverse, the order number is stored in the notification header as AUFNR.

Where is the current status of an order stored?

Status lives in JEST, keyed by the object number OBJNR from AUFK. Active rows have INACT blank. Translate the internal status code into text such as REL or TECO using TJ02T. User statuses use the status profile from JSTO and texts in TJ30T.

Does this list change in S/4HANA?

Core PM tables are largely retained in S/4HANA on-premise, though some fields and views have been simplified, and Fiori apps read from CDS views. Always confirm table structure in SE11 on your system before building a report or migration.

If your maintenance team still builds PM reports by hand from these tables, we can set up a read-only natural language layer over your SAP data that shows the query it ran.

Talk to an Expert Explore More Free Tools