Resources / Glossary
SAP PM Planning Glossary (Mechanical + I&E, ECC and S/4HANA)
DRAFT · unverifiedThe Planner's Bench · Version 0.2 · Oct 25, 2026 · Follows playbook DRAFT v0.2 Status: DRAFT | Unverified until owner sign-off
Built only from public sources and general industry knowledge. Sources were checked Oct 24–25, 2026. "Source-checked" means a public source was read; it does not mean owner-verified. SAP, SAP S/4HANA and SAP Fiori are trademarks of SAP SE. This glossary uses them descriptively. Adapt to your site's SAP configuration and procedures. Not affiliated with or endorsed by SAP SE.
Acronyms used in this glossary
PM = Plant Maintenance (SAP module) · I&E = Instrumentation and Electrical · ECC = SAP ERP Central Component (the predecessor of S/4HANA) · S/4HANA (S/4) = SAP's current ERP suite · Fiori = SAP's web/app user interface · GUI = SAP GUI (the classic transaction screen) · MM = Materials Management · CO = Controlling · QM = Quality Management · MRP = Material Requirements Planning · BOM = bill of material · PR = purchase requisition · GI = goods issue · TECO = technically completed · LIS = Logistics Information System · PMIS = Plant Maintenance Information System · KBA = SAP Knowledge Base Article · FPS = Feature Pack Stack (an S/4HANA update) · WCM = Work Clearance Management · WCA = work clearance application · WCD = work clearance document · PTW = Permit to Work · LOTO = lockout/tagout · OSHA = US Occupational Safety and Health Administration · SIS = safety instrumented system · SIF = safety instrumented function · SIL = safety integrity level · PFDavg = average probability of failure on demand · IEC = International Electrotechnical Commission Applicability key: Both = ECC and S/4HANA (on-prem/private cloud); S/4 = S/4HANA only. SAP Learning lessons are written for S/4HANA. Where a concept is also classic ECC PM, that comes from general product knowledge and is marked "Both [UNVERIFIED: ECC applicability]".
Source keys:
- [L-FL] https://learning.sap.com/courses/exploring-business-processes-in-sap-s-4hana-asset-management/using-functional-locations_a01c057a-df2e-4f17-8bb2-b3c7b357ad97
- [L-EQ] https://learning.sap.com/courses/exploring-business-processes-in-sap-s-4hana-asset-management/using-equipment-and-serial-numbers_edd6b2ef-0a26-4eb9-8e0b-b1f8ee03e41c
- [L-BOM] https://learning.sap.com/courses/exploring-business-processes-in-sap-s-4hana-asset-management/using-bills-of-materials-boms_ff84a992-8e6c-4c1d-9a62-27cf19d06bfc
- [L-ORG] https://learning.sap.com/courses/exploring-business-processes-in-sap-s-4hana-asset-management/explaining-organizational-levels_c86e3042-d911-40d1-9b0f-8348da6a09ce
- [L-NOT] https://learning.sap.com/courses/exploring-business-processes-in-sap-s-4hana-asset-management/creating-notifications_a37b5b9b-60c2-43c9-ab0b-07cf81ea6084
- [L-ORD] https://learning.sap.com/courses/exploring-business-processes-in-sap-s-4hana-asset-management/creating-orders_ed9d6206-5dcd-440a-a0d5-9252217d16d9
- [L-MAT] https://learning.sap.com/courses/exploring-business-processes-in-sap-s-4hana-asset-management/planning-material-and-services_aef816cb-fcb7-48e6-b9f9-da9247e433af
- [L-REL] https://learning.sap.com/courses/exploring-business-processes-in-sap-s-4hana-asset-management/checking-and-releasing-orders_e31cefac-b531-4921-880a-9d3336939d7d
- [L-CNF] https://learning.sap.com/courses/exploring-business-processes-in-sap-s-4hana-asset-management/confirming-notifications-and-orders_a770ddba-efe8-4cec-8153-085703160e68
- [L-TECO] https://learning.sap.com/courses/exploring-business-processes-in-sap-s-4hana-asset-management/completing-notifications-and-orders_c6be4198-202f-4b3d-bba7-e2069b460e70
- [L-PM] https://learning.sap.com/courses/exploring-business-processes-in-sap-s-4hana-asset-management/outlining-preventive-maintenance_e81e7c7d-2f8f-4f39-94e3-e2c9b0edae77
- [L-TL] https://learning.sap.com/courses/exploring-business-processes-in-sap-s-4hana-asset-management/using-maintenance-task-list_d763c67c-2b76-4916-9aab-4625c59c09f6
- [L-MP] https://learning.sap.com/courses/exploring-business-processes-in-sap-s-4hana-asset-management/using-maintenance-plans_ebb53721-acf1-4f60-9207-3b17091fa1d7
- [L-SCH] https://learning.sap.com/courses/exploring-business-processes-in-sap-s-4hana-asset-management/scheduling-maintenance-plans_a1924dce-60b5-496d-b81a-563df3bb9655
- [L-GI] https://learning.sap.com/courses/inventory-management-and-physical-inventory-in-sap-s-4hana/posting-a-goods-issue-with-reference
- [H-WCA] https://help.sap.com/doc/saphelp_nw70/7.0.12/ja-JP/30/12700e46b611d4a7850060087a7a74/content.htm?no_cache=true
- [C-PERM] https://community.sap.com/t5/enterprise-resource-planning-blog-posts-by-members/permits-part1/ba-p/13303675
- [C-PTW] https://community.sap.com/t5/enterprise-resource-planning-blog-posts-by-sap/asset-management-in-sap-s-4hana-cloud-private-edition-2023-fps02-release/ba-p/13894290
- [C-CM01] https://community.sap.com/t5/enterprise-resource-planning-q-a/work-center-capacities-not-reduced-in-cm01-but-pm-order-is-displayed/qaq-p/12101201
- [L-SCP] https://learning.sap.com/courses/exploring-preventive-maintenance-in-sap-s-4hana-asset-management/scheduling-a-single-cycle-plan_a3991299-f39a-4a0f-8664-5909da45e4d6
- [KBA-262] https://userapps.support.sap.com/sap/support/knowledge/en/1962261
- [C-CAL] https://community.sap.com/t5/enterprise-resource-planning-blog-posts-by-members/calibration-maintenance-order-pm-qm/ba-p/13581096
- [C-CALPC] https://community.sap.com/t5/enterprise-resource-planning-q-a/calibration-eam-checklist-in-s4hana-eam-public-cloud/qaq-p/14409871
- [IT-CAL] https://instrumentationtools.com/as-found-and-as-left-documentation-during-calibration/
- [ESC-PT] https://esc.uk.net/wp-content/uploads/2017/06/Proof-Testing-Key-Performance-Indicators.pdf
- [SC-SIS] https://safetycase.sg/wp-content/uploads/2019/10/Proof-Test-of-Safety-Instrumented-Systems-SIS-according-to-IEC-61511.pdf
- [FIORI] SAP Fiori Apps Reference Library, https://fioriappslibrary.hana.ondemand.com (S/4HANA 2025 FPS02)
Organization & master data
| Term | Definition | Applies | Source |
|---|---|---|---|
| Maintenance plant | The plant where technical objects are installed | Both [UNVERIFIED: ECC applicability] | [L-ORG] |
| Maintenance planning plant | The organizational unit where maintenance requirements are planned. It can plan for several maintenance plants. | Both [UNVERIFIED: ECC applicability] | [L-ORG] |
| Maintenance planner group | Defines the planners within a planning plant | Both [UNVERIFIED: ECC applicability] | [L-ORG] |
| Work center (maintenance) | An organizational unit that is responsible for or performs maintenance work, e.g. a mechanical or instrument craft. It is the unit of capacity in PM. | Both | [L-ORG] |
| Business partner | Mandatory S/4HANA master-data approach for persons and organizations; each personnel number has one | S/4 | [L-ORG] |
| Functional location | A hierarchical structure representing a technical system or part of one, structured by spatial, technical or functional criteria (max 40 characters Unverified: owner to confirm against [L-FL]) | Both | [L-FL] |
| Structure indicator | Edit mask plus hierarchy levels that define how functional location IDs are built | Both | [L-FL] |
| Equipment | An individual physical object maintained as an autonomous unit (pump, motor, transmitter), with its own history | Both | [L-EQ] |
| Serial number | An individual unit within a material's stock. Combining it with equipment lets the object move through inventory (e.g. a repairable spare). | Both | [L-EQ] |
| Usage list | History of where a piece of equipment was installed and dismantled | Both | [L-EQ] |
| Maintenance BOM | Bill of material containing only PM-relevant items, used for spare-parts planning. Categories: material, equipment and functional location BOM. | Both | [L-BOM] |
| Measuring point / counter | A point for recording readings (e.g. vibration, temperature, run hours). A counter is a measuring point flagged as a counter. | Both | Unverified (no SAP page fetched; [L-CNF] only mentions "measurement/counter readings") |
| Measurement document | A recorded reading for a measuring point or counter | Both | Unverified (see above) |
| Catalog / code group / code | Hierarchical coded entries (damage, cause, activity, object part) used in notifications for analysis | Both | [L-NOT] |
| Catalog profile | The selection of code groups valid for an object type, assigned to the technical object or notification type | Both | [L-NOT] |
Preventive maintenance
| Term | Definition | Applies | Source |
|---|---|---|---|
| Time-based / performance-based / condition-based maintenance | Work triggered by elapsed time, by a counter reading, or by a condition leaving a value range | Both | [L-PM] |
| Task list (general / equipment / functional location) | A standard sequence of operations with work center, time, materials and tools. A general task list is object-independent; the others are tied to one object. | Both | [L-TL] |
| Maintenance strategy | A scheduling rule made of maintenance packages plus a scheduling indicator | Both | [L-MP] |
| Maintenance package | Cycle length/unit, hierarchy, offset and buffers within a strategy (e.g. 1M, 6M) | Both | [L-MP] |
| Scheduling indicator | Scheduling type: time-based (key date), time-based (factory calendar), or performance-based | Both | [L-MP] |
| Maintenance plan | Automatically generates call objects (orders, notifications, service entry sheets) at intervals | Both | [L-MP] |
| Single-cycle plan | A plan where the same activity repeats at a fixed interval (e.g. annual inspection) | Both | [L-MP] |
| Strategy plan | A plan using a strategy so that packages with different intervals are graded | Both | [L-MP] |
| Multiple counter plan | A plan driven by several counters and/or time combined | Both | Unverified (code IP43 confirmed only on a third-party list; no definition page fetched) |
| Maintenance item | The part of a plan holding the reference object, planning data and task list | Both | [L-MP] |
| Call object | An order, notification or service entry sheet created by scheduling | Both | [L-SCH] |
| Call date vs planned date | The call date (when the order is created) precedes the planned date, leaving lead time e.g. for material procurement | Both | [L-SCH] |
| Call horizon | Maintenance plan scheduling parameter that sets when the order is generated (the call date) relative to the planned date, allowing lead time (e.g. for material or external service procurement). SAP Learning example for a 90-day cycle: 0% = immediate call; 80% = call after 72 days; 100% = call when the planned date is reached. The call horizon alone does not generate the order; the plan must also be scheduled. With Business Function LOG_EAM_CI_6 active, it can be set in days. | Both [UNVERIFIED: ECC applicability] | [L-SCP]; Unverified until owner sign-off |
| Scheduling functions | Start, New Start, Scheduling, Start in Current Cycle, Manual Call | Both | [L-SCH] |
| Deadline monitoring | Regular (usually daily background) scheduling of all active plans | Both | [L-SCH] (described as a "background job"; the name "deadline monitoring" appears in the same text) |
I&E: calibration and safety instrumented systems
| Term | Definition | Applies | Source |
|---|---|---|---|
| Calibration inspection (PM/QM) | Checks that test or measurement equipment meets specification. A maintenance plan generates the calibration order, and order release creates a QM inspection lot. | Both (on-premise/private cloud) | [C-CAL] |
| Test equipment (equipment category Q) | Equipment category used for instruments processed in calibration inspections | Both | [C-CAL] |
| Inspection lot / results recording / usage decision (QA32) | The QM object created for the calibration order: results are recorded, then a usage decision (e.g. can be used / adjustment required / cannot be used) is made before TECO | Both | [C-CAL] (community member post; usage-decision codes vary by configuration Unverified) |
| Calibration in S/4HANA Cloud Public Edition | The classic QM inspection-type calibration flow is not standard there. Calibration is modelled as planned maintenance with measuring points or documents. | S/4 Cloud Public | [C-CALPC] (community answer citing KBA 3640948) |
| As-found / as-left | As-found = instrument reading before adjustment. As-left = reading after adjustment, or "same as found" if no adjustment was made. Recording both shows drift over time. | General industry | [IT-CAL] |
| Safety instrumented system / function (SIS / SIF) | An SIS performs safety functions such as emergency shutdown. Each SIF is one safety loop from sensor to logic to final element. | General industry (IEC 61511) | [SC-SIS] |
| Safety integrity level (SIL) | A discrete level (1–4) allocated to each SIF. It is not a property of an individual component. | General industry (IEC 61511) | [SC-SIS] |
| Proof test | Per IEC 61511: a "periodic test performed to detect dangerous hidden failures in a SIS" so a repair can restore it to an "as new" condition | General industry (IEC 61511) | [ESC-PT] |
| PFDavg | Average probability of a dangerous failure on demand, the target failure measure for a low-demand SIF; it determines the SIL band | General industry (IEC 61511) | [ESC-PT] |
Craft notes (Mechanical vs I&E):
- I&E fixed-interval calibrations and proof tests typically fit a single-cycle plan. Mechanical lubrication or overhaul packages at several intervals fit a strategy plan, and run-hours work fits a counter-based plan. This is general planning practice Unverified; the plan types themselves come from [L-MP].
- Bypassing or inhibiting a SIF for testing must follow site permit and override procedures. This course does not override those procedures.
Corrective work: notifications & orders
| Term | Definition | Applies | Source |
|---|---|---|---|
| Maintenance notification | Logs a request, malfunction or activity; holds items, activities and tasks | Both | [L-NOT] |
| Malfunction report / activity report / maintenance request | Standard notification categories (IW24/IW25/IW26) | Both | [L-NOT] |
| Maintenance order | Plans and executes work and collects costs; integrated with MM and CO | Both | [L-ORD] |
| Order operation / suboperation | Steps of the work with work center, control key, work, duration and capacities | Both | [L-ORD] |
| Control key | Operation parameter controlling costing and confirmation, e.g. PM02/PM03 for external work Unverified: owner to confirm | Both | [L-ORD], [L-MAT] |
| Calculation key | Links work, duration and number of capacities (e.g. key 1: work / capacities = duration) | Both | [L-ORD] |
| Object list | The list of multiple technical objects on one order | Both | [L-ORD] |
| Settlement rule | The receiver to which order costs are settled (e.g. a cost center) | Both | [L-ORD], [L-TECO] |
| Phase model | S/4HANA phase-based processing of requests and orders (screening, planning, preparation, execution, etc.) | S/4 | [C-PTW] |
Materials
| Term | Definition | Applies | Source |
|---|---|---|---|
| Stock vs non-stock material | Stock components create a reservation. Non-stock components create a purchase requisition. | Both | [L-MAT] |
| Reservation | MRP-relevant demand for stock components on an order | Both | [L-MAT] |
| Movement type 261 | Goods issue to an order from the warehouse (planned against a reservation, or unplanned) | Both | [L-GI] |
| Movement type 262 | Reversal of 261, i.e. a return from the order to stock | Both | [KBA-262] (public preview of SAP KBA 1962261, opened; covers ECC and S/4HANA) |
| Material availability check | Checks whether order materials are available, at release or by list/background job | Both | [L-REL] |
| Lean service | S/4 Enhanced Procurement Mode for small external services added as components | S/4 | [L-MAT] |
Release, safety & permits
| Term | Definition | Applies | Source |
|---|---|---|---|
| Order release | The order is released for execution after material, capacity and permit checks; shop papers are printed | Both | [L-REL] |
| Permit (standard PM) | Assigned to technical objects or orders; can block release or technical completion until issued. Two kinds: technical permits and process-oriented permits. | Both | [C-PERM], [L-REL] |
| Work Clearance Management (WCM, classic) | PM sub-module for lockout/tagout safety. Objects include work approval, work clearance application and operational WCD. | Both (classic) | [H-WCA], [L-REL] |
| Work clearance application | WCM object representing the safety certificate, especially for lockout/tagout | Both (classic) | [H-WCA] |
| Permit to Work (PTW) | Newer WCM variant: a formal work permit with safety measures. Its Fiori apps do not cross-process classic WCM objects. | S/4 | [L-REL], [C-PTW] |
| Lockout/tagout (LOTO) | Isolating energy sources and applying locks and tags before work | General industry | [H-WCA] (SAP context). The US OSHA reference is 29 CFR 1910.147 per the course script Unverified (OSHA page not fetched this pass). |
Scheduling & capacity
| Term | Definition | Applies | Source |
|---|---|---|---|
| Capacity evaluation (CM01) | Work center load: requirements vs available capacity. Caveat: order-header blocked capacity is not shown (CM21/CM25/CM50 show it). | Both | [L-REL], [C-CM01] |
| Capacity leveling (CM25) | Planning board for leveling operations | Both | Unverified (name from a third-party list only) |
| Resource Scheduling (RSH) | S/4HANA planning/scheduling tool for maintenance | S/4 | Unverified (only seen as a lesson title in the SAP Learning course menu; lesson not read) |
Execution & completion
| Term | Definition | Applies | Source |
|---|---|---|---|
| Time confirmation | Actual time posted against an operation. Statuses PCNF (partially confirmed) / CNF (finally confirmed). Debits the order, credits the work center cost center. | Both | [L-CNF] |
| Technical confirmation | Findings (damage, cause, activities, downtime) recorded on the notification | Both | [L-CNF] |
| Technical completion (TECO) | Ends the order technically, closes reservations and capacities, and sets the TECO status. It can be reversed. | Both | [L-TECO] |
| Business completion / settlement | CO settles the costs and closes the order | Both | [L-TECO] |
| NOCO / OSTS | Notification completed / outstanding task statuses | Both | [L-TECO] |
| Maintenance history / PMIS | Completed data used for analyses. PMIS is the classic LIS-based information system (MCI* reports). | Both | [L-TECO]; PMIS naming: Unverified (no public source re-fetched) |
Verification log
- Verified by: [owner] | Date: [ ] | Notes: [ ]