In this blog we identify the most important SAP Plant Maintenance (PM) tables for users of:
These tables cover the full maintain-to-settle cycle, including maintenance orders, notifications, equipment master, functional locations, task lists, maintenance plans and measurement documents. Analytics such as mean time to repair (MTTR), mean time between failures (MTBF), work order backlog and asset maintenance cost all depend on joining these tables correctly, so understanding how they fit together is essential for any reliable PM reporting. SAP Plant Maintenance tables are found in the following SAP systems:
Note that the PM order tables (AUFK, AFKO, AFVC, AFVV, AFRU and RESB) are shared with SAP Production Planning (PP), and the notification tables (QMEL, QMIH and QMFE) are shared with SAP Quality Management (QM). When working with these tables you will need to filter by order type or notification type to isolate PM records. SAP Plant Maintenance (PM) Transaction TablesPM transaction data is split between two document types: the maintenance order, which captures the work performed and the costs incurred, and the notification, which captures the event, fault or request that triggered the work. Several of the underlying tables are shared with Production Planning and Quality Management, so filtering by order type or notification type is essential when isolating PM records. Maintenance Order TablesMaintenance orders are stored across a combination of shared order tables and PM-specific extensions. The shared tables (AUFK, AFKO, AFVC, AFVV, AFRU and RESB) also hold Production Planning orders, so you will need to filter on order category or order type to isolate PM data. The key Maintenance Order tables are: AUFK - Order Master Data. Contains the general header record for every internal order, including maintenance, production and project orders. Key field is order number (AUFNR). Other important fields are order type (AUART), company code (BUKRS), plant (WERKS) and the object number (OBJNR), which is used to join to cost and settlement data. This table is shared with PP, PS and CO, so filter by order category or order type to isolate PM orders. AFIH - Maintenance Order Header. Contains the PM-specific header data that extends AUFK for maintenance orders only. Key field is AUFNR. Important fields include equipment number (EQUNR), functional location (TPLNR), PM activity type (ILART) and the linked notification number (QMNUM). Join to AUFK on AUFNR. This table is the anchor point for any PM-only order analysis. AFKO - Order Header Data for PP Orders. Contains scheduling and quantity data at order header level for both maintenance and production orders. Key field is AUFNR. Holds fields such as basic start date, basic finish date and the routing number for operations (AUFPL). Join to AUFK on AUFNR. Shared with PP. AFPO - Order Item. Contains item-level data for each order, including the material to be produced or the maintenance bill of material item. Join to AFKO on AUFNR. Less central for PM than for PP, but useful where maintenance orders have material items. AFVC - Operations within an Order. Contains one row per operation on each order, including the work centre, control key and operation short text. Key fields are routing number (AUFPL) and operation counter (APLZL). Join to AFKO on AUFPL to bring in the order number. Essential for any operation-level analysis such as scheduled versus actual hours. AFVV - Quantities, Dates and Values in the Operation. Contains the planned and actual quantities, dates and durations for each operation. Key fields are AUFPL and APLZL. Join to AFVC on AUFPL and APLZL to enrich operation data with scheduling and effort figures. Shared with PP. AFRU - Order Confirmations. Contains the time and quantity confirmations posted against each operation, including confirmed work hours, personnel number and posting date. Join to AFVC on AUFPL and APLZL. This is the primary source for actual labour hours on maintenance orders. RESB - Reservation/Dependent Requirements. Contains the component reservations for each order, including material number, reservation quantity and withdrawal quantity. Join to AFKO on RSNUM (reservation number) or directly via AUFNR. Essential for spare parts consumption and material cost analysis on maintenance orders. Notification TablesNotifications capture the events that trigger maintenance activity, such as malfunctions, maintenance requests and planned activity reports. The notification tables are shared with Quality Management, so filter by notification type (QMART) to isolate PM notifications. The key Notification tables are: QMEL - Quality Notification. Contains the header record for every notification in the system, covering both QM and PM. Key field is notification number (QMNUM). For PM, filter on notification type (QMART) where values M1 (malfunction report), M2 (maintenance request) and M3 (activity report) identify maintenance notifications. The equipment number (EQUNR) and functional location (TPLNR) identify the asset affected. QMIH - Maintenance Data Excerpt for Quality Notification. Contains the PM-specific item data that extends QMEL for maintenance notifications. Key field is QMNUM. Important fields include equipment number (EQUNR), functional location (TPLNR) and PM activity type (ILART). Join to QMEL on QMNUM to enrich notification headers with maintenance-specific context. QMFE - Quality Notification: Items. Contains the individual cause, damage and fault entries recorded against each notification. Key fields are notification number (QMNUM) and item number (FENUM). Holds the fault code (FECOD) and object part (OTEIL). Join to QMEL on QMNUM. This is the primary source for failure mode and damage code analysis, and is central to MTTR and MTBF calculations. SAP Plant Maintenance (PM) Master Data TablesPM master data describes the assets you maintain and the plans and procedures used to maintain them. Together these tables give you a complete view of the physical estate, the planned maintenance cycle and the performance data captured against each asset. Equipment TablesEQUI - Equipment Master. Contains one row per piece of equipment. Key field is equipment number (EQUNR). Other important fields include equipment category (EQTYP), inventory number (INVNR), serial number (SERNR) and acquisition value (ANSWT). This is the primary asset dimension table for any PM analysis. EQKT - Equipment Short Texts. Contains the language-specific descriptions for each equipment record. Key fields are language (SPRAS) and EQUNR. Join to EQUI on EQUNR and filter by SPRAS to get readable equipment names. EQUZ - Equipment Time Segment. Contains the time-dependent attributes of each equipment record, such as the planning plant, maintenance planner group, work centre and ABC indicator. Key fields are EQUNR and the validity-to date (DATBI). Join to EQUI on EQUNR. Important when analysing changes to equipment responsibility or location over time. Functional Location TablesIFLOT - Functional Location. Contains one row per functional location in the technical hierarchy. Key field is functional location (TPLNR). Important fields include functional location category (FLTYP), maintenance planning plant (IWERK) and start-up date (INBDT). This is the primary table for the physical or process hierarchy used to structure your PM reporting. IFLOTX - Functional Location: Short Texts. Contains the language-specific descriptions for each functional location. Key fields are SPRAS and TPLNR. Join to IFLOT on TPLNR and filter by SPRAS to get readable location names. ILOA - Location and Account Assignment for PM Reference Objects. Contains the location, cost centre, WBS element and asset number assignments used by both equipment and functional locations. Key field is ILOAN (the location/account assignment number referenced from EQUI and IFLOT). Join this table to EQUI or IFLOT via the ILOAN field to pull in cost centre and asset accounting details for your PM objects. Maintenance Plan and Task List TablesMPLA - Maintenance Plan. Contains the header record for each maintenance plan, including plan category, cycle and scheduling parameters. Key field is maintenance plan number (WARPL). This is the starting point for analysing preventive and scheduled maintenance coverage. MPOS - Maintenance Item. Contains one row per maintenance item, representing the object to be maintained by the plan. Key field is maintenance item (WAPOS). Important fields include equipment number (EQUNR), functional location (TPLNR) and PM activity type (ILART). Join to MPLA on WARPL to build a complete maintenance plan dataset. PLKO - Task List: Header. Contains the header record for each task list used by maintenance plans and orders. Key fields are task list type (PLNTY), group number (PLNNR) and group counter (PLNAL). Shared with PP, so filter by task list type to isolate PM task lists (typically types A, E and T). PLPO - Task List: Operation. Contains the individual operations on each task list, including work centre, standard times and operation short text. Key fields are PLNTY, PLNNR and node number (PLNKN). Join to PLKO on PLNTY and PLNNR to build the full task list with operations. Measuring Point and Document TablesIMPT - Measuring Points. Contains the header record for each measuring point, counter or characteristic defined against a piece of equipment or functional location. Key field is POINT (measuring point number). Important fields include measurement range unit (MRNGU) and the target object (OBJID) that the measuring point is assigned to. This is the dimension table for all condition monitoring and counter-based planning. IMRG - Measurement Document. Contains the individual readings captured against each measuring point. Key fields are POINT and measurement document number (MDOCM). Holds the measurement value, counter reading and posting date. Join to IMPT on POINT. This is the primary source for counter-based maintenance triggers and condition trend analysis. SAP Plant Maintenance (PM) Configuration TablesConfiguration tables (also known as customising tables) contain the settings and descriptions that define how your SAP PM module behaves. These are small, slowly changing tables that are useful for decoding the values stored in transaction and master data tables. The configuration tables listed below apply to both SAP ECC and SAP S/4HANA. T001W - Plants / Branches. Contains the list of plants defined in your system. Key field is plant (WERKS). Useful for filtering and grouping PM data by maintenance plant or planning plant in multi-site reports. T352R - Priorities for Maintenance and Service Orders. Contains the PM priority codes and their validity. Key fields are priority type qualifier (QUALF), priority type (ARTPR) and priority (PRIOK). Join to QMEL or AFIH using the priority field to decode priority keys in your reports. T370 - Characteristics of Measurement Types. Contains the measurement type definitions used by measuring points and documents. Key field is measurement type (MPTYP). Join to IMPT to decode measurement types in condition monitoring reports. TPMY - Maintenance Plan Categories. Contains the maintenance plan type definitions that control scheduling behaviour. Key field is MPTYP. Join to MPLA to decode maintenance plan categories in preventive maintenance reporting. Explore SAP PM Tables with a DVW ConnectorThe fastest way to explore SAP PM tables is to connect directly to your SAP system from your preferred analytics platform. DVW Connectors let you browse available tables, preview fields and extract data without writing any ABAP code. All DVW products support both SAP ECC and SAP S/4HANA. To see how all 27 tables in this blog connect to each other, visit our SAP PM Table Relationships page for an interactive data model diagram with join keys and ECC vs S/4HANA compatibility. All DVW products include a 30-day free trial with full functionality, so you can start working with these tables right away. Visit our Free Trial page to get started, or explore our Help Centre for detailed documentation on connecting to SAP PM tables. Next StepsSee these SAP PM tables in action. Register for a 30-day free trial and start extracting maintenance, equipment and notification data from your SAP system today. Comments are closed.
|
Categories
All
Archives
May 2026
|
RSS Feed