{"id":2172,"date":"2026-10-13T08:38:45","date_gmt":"2026-10-13T03:08:45","guid":{"rendered":"https:\/\/www.tiwaripedia.com\/index.php\/2026\/10\/13\/sap-eam-plant-maintenance-interview-questions\/"},"modified":"2026-10-13T08:40:25","modified_gmt":"2026-10-13T03:10:25","slug":"sap-eam-plant-maintenance-interview-questions","status":"publish","type":"post","link":"https:\/\/www.tiwaripedia.com\/index.php\/2026\/10\/13\/sap-eam-plant-maintenance-interview-questions\/","title":{"rendered":"SAP EAM \/ Plant Maintenance Interview Questions &#038; End-to-End Process Guide (S\/4HANA)"},"content":{"rendered":"\n<div class=\"sap-hero\"><h2>\ud83d\udee0\ufe0f SAP EAM (Plant Maintenance) interview guide<\/h2><p>Everything a PM\/EAM consultant is asked in interviews, from the basic notification-to-settlement cycle to preventive maintenance design and S\/4HANA Asset Management, with a scored test at the end.<\/p><div class=\"sap-chips\"><span>Notifications<\/span><span>Orders<\/span><span>Preventive Maintenance<\/span><span>Settlement<\/span><span>S\/4HANA<\/span><\/div><\/div><p>SAP Enterprise Asset Management (EAM), still widely called <b>Plant Maintenance (PM)<\/b>, keeps machines, vehicles, buildings and networks running. It is one of the most in-demand SAP skills in manufacturing, utilities, oil &#038; gas, mining and pharma. This guide walks you through the full process with an infographic, the master data you must know, and the questions interview panels actually ask.<\/p><p><a href=\"#test\" style=\"display:inline-block;padding:10px 18px;border-radius:12px;background:linear-gradient(90deg,#4f46e5,#7c3aed);color:#fff;font-weight:800;text-decoration:none\">\ud83d\udcdd Jump to the scored EAM (PM) test<\/a><\/p><nav class=\"sap-toc\"><b>\ud83d\udcd1 In this guide<\/b><ol><li><a href=\"#what\">What is EAM (PM)?<\/a><\/li><li><a href=\"#process\">End-to-end process<\/a><\/li><li><a href=\"#org\">Org structure &#038; master data<\/a><\/li><li><a href=\"#tcodes\">Key T-codes &#038; Fiori apps<\/a><\/li><li><a href=\"#s4\">What changed in S\/4HANA<\/a><\/li><li><a href=\"#integration\">Integration points<\/a><\/li><li><a href=\"#questions\">Interview questions &#038; answers<\/a><\/li><li><a href=\"#architect\">Solution architect view<\/a><\/li><li><a href=\"#test\">Test yourself (scored)<\/a><\/li><li><a href=\"#tips\">Interview tips<\/a><\/li><\/ol><\/nav><h2 id=\"what\">What is SAP EAM (PM)?<\/h2><p>SAP EAM manages the complete lifecycle of physical assets: recording technical objects, planning and executing maintenance work, capturing costs and history, and analysing reliability. In S\/4HANA it is delivered as <b>Asset Management<\/b>, and it works with SAP Intelligent Asset Management, SAP Asset Performance Management and the SAP Service and Asset Manager mobile app.<\/p><p>Maintenance falls into three types that you should be able to explain:<\/p><ul><li><b>Corrective (breakdown) maintenance:<\/b> something fails, a notification is raised and an order repairs it.<\/li><li><b>Preventive maintenance:<\/b> time-based or performance (counter)-based plans automatically generate orders, such as an inspection every 3 months or every 500 operating hours.<\/li><li><b>Predictive \/ condition-based maintenance:<\/b> measurement readings or IoT signals trigger work when a threshold is crossed.<\/li><\/ul><h2 id=\"process\">End-to-end process: Plan-to-Maintain (notification to settlement)<\/h2><p>Almost every EAM interview starts with &#8220;walk me through the maintenance cycle&#8221;. Use this flow and name the T-codes as you go.<\/p><figure class=\"sap-fig\" style=\"margin:18px 0 26px\"><img decoding=\"async\" src=\"https:\/\/www.tiwaripedia.com\/wp-content\/uploads\/2026\/10\/sap-eam-end-to-end-process-flow.png\" alt=\"SAP EAM: End-to-end maintenance cycle infographic\" loading=\"lazy\" style=\"width:100%;height:auto;border-radius:18px;box-shadow:0 12px 30px rgba(15,23,42,.12)\"\/><\/figure><ol class=\"sap-steps\"><li><b>Raise notification<\/b> <code style=\"background:#eef2ff;color:#4338ca;padding:1px 6px;border-radius:6px;font-size:13px\">IW21 \/ IW26 \u00b7 M1, M2<\/code><br>A user reports a malfunction (M2) or requests work (M1) against a functional location or equipment, with damage and cause codes from catalogs.<\/li><li><b>Screen &amp; approve<\/b> <code style=\"background:#eef2ff;color:#4338ca;padding:1px 6px;border-radius:6px;font-size:13px\">IW22 \/ IW28<\/code><br>The maintenance planner reviews the request, sets priority and decides whether an order is needed.<\/li><li><b>Create order<\/b> <code style=\"background:#eef2ff;color:#4338ca;padding:1px 6px;border-radius:6px;font-size:13px\">IW31 \/ IW34<\/code><br>A maintenance order is created directly or from the notification. The order type (such as PM01) controls numbering, settlement and costing.<\/li><li><b>Plan operations<\/b> <code style=\"background:#eef2ff;color:#4338ca;padding:1px 6px;border-radius:6px;font-size:13px\">Task list \u00b7 Work centre<\/code><br>Operations, work centres, durations, spare parts (components), tools and external services are planned. A task list can be copied in.<\/li><li><b>Check material &amp; costs<\/b> <code style=\"background:#eef2ff;color:#4338ca;padding:1px 6px;border-radius:6px;font-size:13px\">Availability \u00b7 Estimate<\/code><br>Stock items create reservations; non-stock items and services create purchase requisitions automatically. Planned costs are calculated.<\/li><li><b>Schedule &amp; permits<\/b> <code style=\"background:#eef2ff;color:#4338ca;padding:1px 6px;border-radius:6px;font-size:13px\">Capacity \u00b7 Permits<\/code><br>Work is scheduled against work-centre capacity. Permits and work clearance (lock-out\/tag-out) are obtained for safety.<\/li><li><b>Release order<\/b> <code style=\"background:#eef2ff;color:#4338ca;padding:1px 6px;border-radius:6px;font-size:13px\">IW32 \u00b7 Release<\/code><br>Release makes the order executable: reservations become relevant for goods issue and shop papers can be printed.<\/li><li><b>Issue spares<\/b> <code style=\"background:#eef2ff;color:#4338ca;padding:1px 6px;border-radius:6px;font-size:13px\">MIGO \u00b7 Mvt 261<\/code><br>Spare parts are issued from the store to the order, and the actual material cost is posted to the order.<\/li><li><b>Confirm work<\/b> <code style=\"background:#eef2ff;color:#4338ca;padding:1px 6px;border-radius:6px;font-size:13px\">IW41 \/ IW44 \/ CAT2<\/code><br>Technicians confirm actual hours, which posts labour cost via the activity type rate. Measurement readings are recorded.<\/li><li><b>Complete technically<\/b> <code style=\"background:#eef2ff;color:#4338ca;padding:1px 6px;border-radius:6px;font-size:13px\">TECO \u00b7 History<\/code><br>The order is technically completed. Damage, cause and activity codes are recorded on the notification for history.<\/li><li><b>Settle costs<\/b> <code style=\"background:#eef2ff;color:#4338ca;padding:1px 6px;border-radius:6px;font-size:13px\">KO88 \/ KO8G<\/code><br>Order costs are settled to the receiver in the settlement rule, such as a cost centre, asset (capitalisation) or WBS element.<\/li><li><b>Close &amp; analyse<\/b> <code style=\"background:#eef2ff;color:#4338ca;padding:1px 6px;border-radius:6px;font-size:13px\">CLSD \u00b7 Fiori analytics<\/code><br>Business completion closes the order. MTBF, MTTR, planned-vs-actual cost and PM compliance are analysed.<\/li><\/ol><h2 id=\"org\">Organizational structure &#038; master data<\/h2><figure class=\"sap-fig\" style=\"margin:18px 0 26px\"><img decoding=\"async\" src=\"https:\/\/www.tiwaripedia.com\/wp-content\/uploads\/2026\/10\/sap-eam-org-structure-master-data.png\" alt=\"SAP EAM (PM) org structure and master data\" loading=\"lazy\" style=\"width:100%;height:auto;border-radius:18px;box-shadow:0 12px 30px rgba(15,23,42,.12)\"\/><\/figure><h3>Organizational structure<\/h3><div class=\"sap-grid\"><div class=\"sap-card\"><h4>Maintenance plant<\/h4><p>The plant where technical objects are located.<\/p><\/div><div class=\"sap-card\"><h4>Maintenance planning plant<\/h4><p>The plant where maintenance is planned. It can be centralised (one planning plant serving many maintenance plants) or decentralised.<\/p><\/div><div class=\"sap-card\"><h4>Planner group<\/h4><p>The group of planners responsible for a set of objects or orders.<\/p><\/div><div class=\"sap-card\"><h4>Main work centre<\/h4><p>The default responsible work centre on the notification and order.<\/p><\/div><div class=\"sap-card\"><h4>Plant section \/ location<\/h4><p>Used for responsibility and reporting within a plant.<\/p><\/div><div class=\"sap-card\"><h4>Company code, controlling area, business area<\/h4><p>Determine where maintenance costs land in FI\/CO.<\/p><\/div><\/div><h3>Master data<\/h3><div class=\"sap-grid\"><div class=\"sap-card\"><h4>Functional location (IL01)<\/h4><p>A hierarchy defined by a structure indicator (edit mask). It represents where work is done.<\/p><\/div><div class=\"sap-card\"><h4>Equipment (IE01)<\/h4><p>Installed at or dismantled from a functional location, with full usage history. Can be serialised material.<\/p><\/div><div class=\"sap-card\"><h4>Bill of material<\/h4><ul><li>Equipment BOM (IB01)<\/li><li>Functional location BOM (IB11)<\/li><li>Material BOM used as an assembly<\/li><\/ul><\/div><div class=\"sap-card\"><h4>Task lists (IA05 \/ IA01 \/ IA11)<\/h4><ul><li>General task list (A)<\/li><li>Equipment task list (E)<\/li><li>Functional location task list (T)<\/li><\/ul><\/div><div class=\"sap-card\"><h4>Maintenance plans<\/h4><ul><li>Single cycle (IP41)<\/li><li>Strategy plan (IP42, strategy in IP11)<\/li><li>Multiple counter (IP43)<\/li><\/ul><\/div><div class=\"sap-card\"><h4>Measuring points &#038; counters (IK01 \/ IK11)<\/h4><p>Capture readings and operating hours that drive counter-based and condition-based maintenance.<\/p><\/div><div class=\"sap-card\"><h4>Catalogs &#038; catalog profile<\/h4><p>Coded damage, cause, object part and activity codes that make history analysable.<\/p><\/div><div class=\"sap-card\"><h4>Work centre (IR01)<\/h4><p>Capacity, formulas, cost centre and activity type for labour costing.<\/p><\/div><\/div><h2 id=\"tcodes\">Key T-codes &#038; Fiori apps<\/h2><p>Interviewers often ask you to name the transaction or app for a step. You do not need to memorise hundreds, but you should know these confidently.<\/p><div class=\"sap-wrap\"><table class=\"sap-tbl\"><thead><tr><th>T-code \/ App<\/th><th>What it does<\/th><\/tr><\/thead><tbody><tr><td><b>IW21 \/ IW22 \/ IW23<\/b><\/td><td>Create \/ change \/ display notification<\/td><\/tr><tr><td><b>IW28 \/ IW29<\/b><\/td><td>Notification list change \/ display<\/td><\/tr><tr><td><b>IW31 \/ IW32 \/ IW33<\/b><\/td><td>Create \/ change \/ display maintenance order<\/td><\/tr><tr><td><b>IW38 \/ IW39<\/b><\/td><td>Order list change \/ display<\/td><\/tr><tr><td><b>IW41 \/ IW44 \/ IW42<\/b><\/td><td>Individual \/ collective \/ overall completion confirmation<\/td><\/tr><tr><td><b>IL01 \/ IE01<\/b><\/td><td>Create functional location \/ equipment<\/td><\/tr><tr><td><b>IA05 \/ IA01 \/ IA11<\/b><\/td><td>General \/ equipment \/ functional location task list<\/td><\/tr><tr><td><b>IP41 \/ IP42 \/ IP43<\/b><\/td><td>Create maintenance plans (single cycle, strategy, multiple counter)<\/td><\/tr><tr><td><b>IP10 \/ IP30<\/b><\/td><td>Schedule a plan \/ deadline monitoring (batch scheduling)<\/td><\/tr><tr><td><b>IK01 \/ IK11<\/b><\/td><td>Create measuring point \/ enter measurement document<\/td><\/tr><tr><td><b>KO88 \/ KO8G<\/b><\/td><td>Individual \/ collective order settlement<\/td><\/tr><tr><td><b>Fiori: Request Maintenance, Find Maintenance Notification, Manage Maintenance Planning Buckets, Perform Maintenance Jobs<\/b><\/td><td>Modern UX for requesters, planners and technicians<\/td><\/tr><\/tbody><\/table><\/div><h2 id=\"s4\">What changed in S\/4HANA<\/h2><ul><li>Plant Maintenance is positioned as <b>S\/4HANA Asset Management<\/b>, with role-based Fiori apps for requesters, planners, supervisors and technicians.<\/li><li>Newer releases add an optional <b>phase model<\/b> for notifications and orders (initiation, screening, planning, approval, preparation, scheduling, execution, post-execution, completion), giving a clear status-driven process.<\/li><li><b>Maintenance planning buckets<\/b> and a scheduling board support capacity-aware weekly scheduling.<\/li><li>The <b>Universal Journal (ACDOCA)<\/b> means order costs are visible in real time without reconciliation between FI and CO.<\/li><li><b>Business Partner<\/b> replaces separate customer and vendor masters, and the material number field is extended to 40 characters.<\/li><li>Mobile execution moves to <b>SAP Service and Asset Manager<\/b>, and predictive use cases move to SAP Asset Performance Management on BTP.<\/li><\/ul><h2 id=\"integration\">Integration points<\/h2><div class=\"sap-wrap\"><table class=\"sap-tbl\"><thead><tr><th>With<\/th><th>How it integrates<\/th><\/tr><\/thead><tbody><tr><td><b>MM<\/b><\/td><td>Reservations for stock spares, purchase requisitions for non-stock items and external services, goods issue with movement type 261.<\/td><\/tr><tr><td><b>CO<\/b><\/td><td>Orders collect planned and actual costs, which are settled to cost centres, internal orders or WBS elements. Labour uses activity-type rates.<\/td><\/tr><tr><td><b>FI-AA<\/b><\/td><td>Capital work can be settled to an asset or asset under construction. Equipment can be linked to a fixed asset.<\/td><\/tr><tr><td><b>PS<\/b><\/td><td>Shutdowns and turnarounds are planned with WBS elements, and maintenance orders are assigned to them.<\/td><\/tr><tr><td><b>QM<\/b><\/td><td>Quality notifications, calibration of test equipment and inspection lots for calibration orders.<\/td><\/tr><tr><td><b>HCM \/ CATS<\/b><\/td><td>Technician time is recorded in CATS and transferred to order confirmations.<\/td><\/tr><tr><td><b>EHS<\/b><\/td><td>Work clearance management and permits for safe isolation.<\/td><\/tr><\/tbody><\/table><\/div><h2 id=\"questions\">Interview questions &#038; answers<\/h2><p>Tap a question to see a model answer. They are grouped from fundamentals to scenario-based questions that senior panels love.<\/p><h3>\ud83d\udfe2 Fundamentals<\/h3><details class=\"sap-qa\"><summary>What is the difference between a functional location and an equipment? <small style=\"margin-left:auto;font-size:11px;color:#6366f1;white-space:nowrap\">Beginner<\/small><\/summary><div class=\"sap-a\">A <b>functional location<\/b> is a place in the technical structure where work is done (for example &#8220;Pump station 1, line 2&#8221;). It is hierarchical and usually not moved. An <b>equipment<\/b> is an individual physical object (for example &#8220;Pump serial 12345&#8221;) that can be installed at a functional location and later dismantled and moved. Equipment keeps its own history; the functional location keeps the history of the place. Good answer line: <i>the location stays, the equipment moves.<\/i><\/div><\/details><details class=\"sap-qa\"><summary>Explain the standard notification types. <small style=\"margin-left:auto;font-size:11px;color:#6366f1;white-space:nowrap\">Beginner<\/small><\/summary><div class=\"sap-a\"><b>M1<\/b> maintenance request (planned work request), <b>M2<\/b> malfunction report (breakdown) and <b>M3<\/b> activity report (documents work already done). Notification types are configured with screen layout, catalog profile, partner determination and priority type.<\/div><\/details><details class=\"sap-qa\"><summary>What is the difference between a notification and an order? <small style=\"margin-left:auto;font-size:11px;color:#6366f1;white-space:nowrap\">Beginner<\/small><\/summary><div class=\"sap-a\">A notification <b>describes the problem<\/b> and records history (damage, cause, activities). An order <b>plans and executes the work<\/b>: operations, materials, resources, costs and settlement. One notification can lead to one order, and an order can hold several notifications through the object list.<\/div><\/details><details class=\"sap-qa\"><summary>What is TECO and how is it different from business completion (CLSD)? <small style=\"margin-left:auto;font-size:11px;color:#6366f1;white-space:nowrap\">Beginner<\/small><\/summary><div class=\"sap-a\"><b>TECO<\/b> (technically complete) means the work is finished. Open reservations and requisitions are cancelled, but costs can still be posted, for example a late invoice. <b>CLSD<\/b> (business completion) is set after settlement, and no further postings are allowed.<\/div><\/details><details class=\"sap-qa\"><summary>Which movement type issues spare parts to a maintenance order? <small style=\"margin-left:auto;font-size:11px;color:#6366f1;white-space:nowrap\">Beginner<\/small><\/summary><div class=\"sap-a\">Movement type <b>261<\/b> (goods issue for order), posted with MIGO against the order reservation. The cost is debited to the order.<\/div><\/details><details class=\"sap-qa\"><summary>What is a work centre used for in PM? <small style=\"margin-left:auto;font-size:11px;color:#6366f1;white-space:nowrap\">Beginner<\/small><\/summary><div class=\"sap-a\">It represents the people or machines who perform the work. It holds capacity, scheduling formulas, the cost centre and the <b>activity type<\/b> whose rate (KP26) values confirmed hours, so time confirmations post labour costs to the order.<\/div><\/details><details class=\"sap-qa\"><summary>What are catalogs in PM? <small style=\"margin-left:auto;font-size:11px;color:#6366f1;white-space:nowrap\">Beginner<\/small><\/summary><div class=\"sap-a\">Coded lists (catalog types such as damage, cause, object part, activity, tasks) grouped into code groups and assigned through a catalog profile. Coded history makes breakdown analysis and reliability reports possible.<\/div><\/details><h3>\ud83d\udfe1 Intermediate<\/h3><details class=\"sap-qa\"><summary>Explain the different maintenance plan types. <small style=\"margin-left:auto;font-size:11px;color:#6366f1;white-space:nowrap\">Intermediate<\/small><\/summary><div class=\"sap-a\"><b>Single cycle plan (IP41)<\/b>: one cycle, time- or performance-based. <b>Strategy plan (IP42)<\/b>: uses a maintenance strategy (IP11) with packages such as 1M, 3M and 12M, so the larger package also covers the smaller ones on the same date. <b>Multiple counter plan (IP43)<\/b>: several cycles combined with AND\/OR logic, for example every 6 months OR 1,000 hours, whichever comes first.<\/div><\/details><details class=\"sap-qa\"><summary>What scheduling parameters matter in a maintenance plan? <small style=\"margin-left:auto;font-size:11px;color:#6366f1;white-space:nowrap\">Intermediate<\/small><\/summary><div class=\"sap-a\">Call horizon (when the order is created relative to the due date), scheduling period (how far ahead calls are generated), shift factors for late and early completion, tolerances, and the cycle modification factor. Deadline monitoring <b>IP30<\/b> runs in batch to create the calls.<\/div><\/details><details class=\"sap-qa\"><summary>How is a settlement rule determined for a maintenance order? <small style=\"margin-left:auto;font-size:11px;color:#6366f1;white-space:nowrap\">Intermediate<\/small><\/summary><div class=\"sap-a\">Through the settlement profile on the order type, plus the default rule derived from the reference object, typically the cost centre from the equipment or functional location. It can be changed to an asset, WBS or internal order. Settlement runs with KO88 (individual) or KO8G (collective), usually monthly.<\/div><\/details><details class=\"sap-qa\"><summary>What is the difference between an internal and an external operation? <small style=\"margin-left:auto;font-size:11px;color:#6366f1;white-space:nowrap\">Intermediate<\/small><\/summary><div class=\"sap-a\">An internal operation is performed by your own work centre (control key PM01) and confirmed with time. An external operation (control key PM02 or PM03) is performed by a vendor; it creates a purchase requisition for the service and is completed through GR or service entry.<\/div><\/details><details class=\"sap-qa\"><summary>What is a refurbishment order? <small style=\"margin-left:auto;font-size:11px;color:#6366f1;white-space:nowrap\">Intermediate<\/small><\/summary><div class=\"sap-a\">An order to repair damaged spare parts (often split-valuated by condition, such as new, repaired or damaged). The defective part is issued to the order and the refurbished part is received back into stock at a different valuation.<\/div><\/details><details class=\"sap-qa\"><summary>How do measuring points support condition-based maintenance? <small style=\"margin-left:auto;font-size:11px;color:#6366f1;white-space:nowrap\">Intermediate<\/small><\/summary><div class=\"sap-a\">Measuring points record readings such as temperature and vibration. Counters record usage such as hours or kilometres. Counter readings drive performance-based plans, and readings outside limits can automatically create a notification.<\/div><\/details><h3>\ud83d\udd34 Scenario &#038; design<\/h3><details class=\"sap-qa\"><summary>A plant wants orders created automatically every 500 running hours or every 3 months, whichever is first. How do you design it? <small style=\"margin-left:auto;font-size:11px;color:#6366f1;white-space:nowrap\">Scenario<\/small><\/summary><div class=\"sap-a\">Create a <b>counter<\/b> measuring point for running hours, then a <b>multiple counter plan (IP43)<\/b> with two cycles (500 h and 3 months) linked with <b>OR<\/b>. Assign a task list, set the call horizon and schedule the plan with IP10. IP30 runs in batch, and operators enter readings with IK11, or readings arrive through an IoT integration.<\/div><\/details><details class=\"sap-qa\"><summary>Breakdown costs are landing on the wrong cost centre. How do you investigate? <small style=\"margin-left:auto;font-size:11px;color:#6366f1;white-space:nowrap\">Scenario<\/small><\/summary><div class=\"sap-a\">Check the settlement rule on the order (from the reference object), the cost centre on the equipment or functional location, any substitution, and the settlement profile on the order type. Correct the master data, adjust the settlement rule on open orders, and if needed reverse and re-run settlement for the period.<\/div><\/details><details class=\"sap-qa\"><summary>How would you plan an annual plant shutdown in SAP? <small style=\"margin-left:auto;font-size:11px;color:#6366f1;white-space:nowrap\">Scenario<\/small><\/summary><div class=\"sap-a\">Use a PS project or WBS for the shutdown budget and timeline. Create maintenance orders, possibly using a revision code to group them, assign them to the WBS, plan materials early so long-lead items are procured, and use capacity levelling and the scheduling board. Track progress through confirmations, then settle to the WBS for consolidated reporting.<\/div><\/details><details class=\"sap-qa\"><summary>The business wants technicians to work on mobile devices offline. What would you propose? <small style=\"margin-left:auto;font-size:11px;color:#6366f1;white-space:nowrap\">Scenario<\/small><\/summary><div class=\"sap-a\">SAP Service and Asset Manager (SSAM) on SAP BTP mobile services, with offline OData sync. Define the order types and operations that are pushed to mobile, the confirmation and measurement capture, attachments and photos, and the authorisations. Plan device management and the network sync strategy.<\/div><\/details><details class=\"sap-qa\"><summary>How do you migrate technical objects to S\/4HANA? <small style=\"margin-left:auto;font-size:11px;color:#6366f1;white-space:nowrap\">Scenario<\/small><\/summary><div class=\"sap-a\">Use the <b>S\/4HANA Migration Cockpit<\/b> objects in order: functional locations (with the structure indicator in place first), equipment, installation at functional location, BOMs, task lists, measuring points, and finally maintenance plans with their start dates. Cleanse duplicates and agree the hierarchy with the business before loading. Validate with counts and spot checks.<\/div><\/details><details class=\"sap-qa\"><summary>Which KPIs would you build for a maintenance manager? <small style=\"margin-left:auto;font-size:11px;color:#6366f1;white-space:nowrap\">Scenario<\/small><\/summary><div class=\"sap-a\">MTBF (mean time between failures), MTTR (mean time to repair), PM compliance (preventive orders completed on time), planned vs. unplanned ratio, backlog in hours, planned vs. actual cost, and schedule compliance. These come from embedded analytics and Fiori analytical apps.<\/div><\/details><details class=\"sap-qa\"><summary>When would you choose a functional location hierarchy over equipment only? <small style=\"margin-left:auto;font-size:11px;color:#6366f1;white-space:nowrap\">Scenario<\/small><\/summary><div class=\"sap-a\">When the business needs costs and history by <b>place<\/b> as well as by object, when equipment moves between positions (such as pumps swapped during repairs), or for linear and network assets. A small site with fixed assets may manage with equipment and a simple hierarchy.<\/div><\/details><h2 id=\"architect\">Solution architect view<\/h2><div class=\"sap-arch\"><p><b>Key design decisions a solution architect owns in EAM:<\/b><\/p><ul><li><b>Technical object structure:<\/b> the functional location mask and depth, the equipment categories, and which objects need their own history and cost tracking. This is the hardest thing to change later.<\/li><li><b>Planning model:<\/b> centralised or decentralised planning plants, planner groups and work-centre granularity.<\/li><li><b>Order and notification types:<\/b> keep a small, clear set (breakdown, preventive, project-related, refurbishment) with clean settlement profiles.<\/li><li><b>Costing:<\/b> activity types and rates, cost element planning and settlement receivers, agreed with Finance early.<\/li><li><b>Preventive strategy:<\/b> time, counter or condition-based plans, call horizons and batch scheduling.<\/li><li><b>Mobility and IoT:<\/b> SAP Service and Asset Manager, APM and sensor integration through BTP.<\/li><li><b>Data migration:<\/b> functional location and equipment hierarchy cleansing is usually the critical path.<\/li><\/ul><p><b>Typical deliverables:<\/b> asset hierarchy design document, business process design (BPD) for corrective, preventive and refurbishment processes, configuration rationale, integration design, and a KPI and reporting catalogue.<\/p><\/div><h2 id=\"test\">Test yourself: scored EAM (PM) quiz<\/h2><div class=\"tpq\" data-quiz=\"{&quot;id&quot;:&quot;sap-eam&quot;,&quot;title&quot;:&quot;SAP EAM (PM) Interview Test&quot;,&quot;intro&quot;:&quot;12 questions, shuffled every attempt. Submit to see your score, grade and an explanation for every answer.&quot;,&quot;questions&quot;:[{&quot;l&quot;:&quot;Beginner&quot;,&quot;q&quot;:&quot;Which notification type is used to report a breakdown?&quot;,&quot;o&quot;:[&quot;M2 Malfunction report&quot;,&quot;M1 Maintenance request&quot;,&quot;M3 Activity report&quot;,&quot;Q1 Customer complaint&quot;],&quot;a&quot;:0,&quot;e&quot;:&quot;M2 is the malfunction report used for breakdowns. M1 requests work and M3 documents work already done.&quot;},{&quot;l&quot;:&quot;Beginner&quot;,&quot;q&quot;:&quot;Which movement type issues spare parts to a maintenance order?&quot;,&quot;o&quot;:[&quot;261&quot;,&quot;101&quot;,&quot;201&quot;,&quot;311&quot;],&quot;a&quot;:0,&quot;e&quot;:&quot;261 is goods issue for an order. 201 is issue to a cost centre and 101 is goods receipt.&quot;},{&quot;l&quot;:&quot;Beginner&quot;,&quot;q&quot;:&quot;Which transaction creates a functional location?&quot;,&quot;o&quot;:[&quot;IL01&quot;,&quot;IE01&quot;,&quot;IW31&quot;,&quot;IA05&quot;],&quot;a&quot;:0,&quot;e&quot;:&quot;IL01 creates functional locations. IE01 creates equipment, IW31 creates orders and IA05 creates general task lists.&quot;},{&quot;l&quot;:&quot;Beginner&quot;,&quot;q&quot;:&quot;What happens when an order is set to TECO?&quot;,&quot;o&quot;:[&quot;Work is complete and open reservations are closed, but costs can still post&quot;,&quot;No further postings of any kind are allowed&quot;,&quot;The order is deleted&quot;,&quot;Settlement runs automatically&quot;],&quot;a&quot;:0,&quot;e&quot;:&quot;TECO means technically complete. Late costs can still post. Business completion (CLSD) blocks further postings.&quot;},{&quot;l&quot;:&quot;Intermediate&quot;,&quot;q&quot;:&quot;Which plan type handles \\&quot;every 6 months or 1,000 hours, whichever comes first\\&quot;?&quot;,&quot;o&quot;:[&quot;Multiple counter plan&quot;,&quot;Single cycle plan&quot;,&quot;Strategy plan&quot;,&quot;Maintenance item only&quot;],&quot;a&quot;:0,&quot;e&quot;:&quot;A multiple counter plan combines several cycles with OR or AND logic.&quot;},{&quot;l&quot;:&quot;Intermediate&quot;,&quot;q&quot;:&quot;Where is the maintenance strategy with packages (1M, 3M, 12M) defined?&quot;,&quot;o&quot;:[&quot;IP11&quot;,&quot;IP30&quot;,&quot;IK01&quot;,&quot;KP26&quot;],&quot;a&quot;:0,&quot;e&quot;:&quot;Strategies and their packages are maintained in IP11 and used in strategy plans (IP42).&quot;},{&quot;l&quot;:&quot;Intermediate&quot;,&quot;q&quot;:&quot;Which transaction runs deadline monitoring to create maintenance calls in batch?&quot;,&quot;o&quot;:[&quot;IP30&quot;,&quot;IP10&quot;,&quot;IW38&quot;,&quot;KO8G&quot;],&quot;a&quot;:0,&quot;e&quot;:&quot;IP30 is deadline monitoring for many plans. IP10 schedules a single plan manually.&quot;},{&quot;l&quot;:&quot;Intermediate&quot;,&quot;q&quot;:&quot;How is labour cost posted to a maintenance order?&quot;,&quot;o&quot;:[&quot;Time confirmation valued with the work centre activity type rate&quot;,&quot;Goods issue of labour material&quot;,&quot;Manual FI journal entry&quot;,&quot;It is not possible to post labour cost&quot;],&quot;a&quot;:0,&quot;e&quot;:&quot;Confirmed hours multiplied by the activity type rate (planned in KP26) debit the order.&quot;},{&quot;l&quot;:&quot;Intermediate&quot;,&quot;q&quot;:&quot;An external operation in a maintenance order typically creates\u2026&quot;,&quot;o&quot;:[&quot;A purchase requisition for the service&quot;,&quot;A sales order&quot;,&quot;A production order&quot;,&quot;A transfer posting&quot;],&quot;a&quot;:0,&quot;e&quot;:&quot;External operations generate purchase requisitions, which purchasing converts into POs for the vendor.&quot;},{&quot;l&quot;:&quot;Scenario&quot;,&quot;q&quot;:&quot;Costs for a capital overhaul must be capitalised. What should the settlement receiver be?&quot;,&quot;o&quot;:[&quot;An asset or asset under construction&quot;,&quot;The maintenance cost centre&quot;,&quot;A sales order&quot;,&quot;A G\/L account for expenses only&quot;],&quot;a&quot;:0,&quot;e&quot;:&quot;Capital work is settled to an asset or AuC so that it is capitalised rather than expensed.&quot;},{&quot;l&quot;:&quot;Scenario&quot;,&quot;q&quot;:&quot;In S\/4HANA, which mobile solution replaces older PM mobile apps for technicians?&quot;,&quot;o&quot;:[&quot;SAP Service and Asset Manager&quot;,&quot;SAP Fiori Launchpad on desktop only&quot;,&quot;SAP GUI for Java&quot;,&quot;SAP Ariba&quot;],&quot;a&quot;:0,&quot;e&quot;:&quot;SAP Service and Asset Manager is the strategic mobile app for maintenance and field service.&quot;},{&quot;l&quot;:&quot;Scenario&quot;,&quot;q&quot;:&quot;What is usually the critical path when migrating EAM to S\/4HANA?&quot;,&quot;o&quot;:[&quot;Cleansing and loading the functional location and equipment hierarchy&quot;,&quot;Creating Fiori tiles&quot;,&quot;Printing shop papers&quot;,&quot;Translating catalog texts only&quot;],&quot;a&quot;:0,&quot;e&quot;:&quot;The technical object hierarchy drives everything else (plans, BOMs, task lists), so it needs early cleansing and sign-off.&quot;}]}\"><\/div><h2 id=\"tips\">Interview tips<\/h2><div class=\"sap-tip\"><b>\ud83d\udca1 How to stand out<\/b><ul><li>Always narrate the cycle with T-codes: notification, order, planning, release, goods issue, confirmation, TECO, settlement.<\/li><li>Know the difference between corrective, preventive and predictive maintenance, with one real example of each.<\/li><li>Be ready to draw the functional location hierarchy from a plant you know.<\/li><li>Mention S\/4HANA items (Fiori apps, phase model, Service and Asset Manager) to show you are current.<\/li><li>For senior roles, talk about KPIs (MTBF, MTTR, PM compliance) and how you designed the reporting.<\/li><\/ul><\/div><p><b>Keep preparing:<\/b> <a href=\"https:\/\/www.tiwaripedia.com\/index.php\/sap-interview-preparation\/\">\ud83c\udfaf SAP Interview Prep hub &#038; combined mock test<\/a> \u00b7 <a href=\"https:\/\/www.tiwaripedia.com\/index.php\/category\/erp-software\/sap-interview-prep\/\">All SAP interview guides<\/a> \u00b7 <a href=\"https:\/\/www.tiwaripedia.com\/index.php\/category\/erp-software\/\">ERP Software<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Complete SAP EAM (Plant Maintenance) interview guide: end-to-end maintenance process infographic, org structure, master data, T-codes, S\/4HANA changes, 20+ real interview Q&#038;As and a scored mock test.<\/p>\n","protected":false},"author":1,"featured_media":2169,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"googlesitekit_rrm_CAow_YXIDA:productID":""},"categories":[348,353],"tags":[],"_links":{"self":[{"href":"https:\/\/www.tiwaripedia.com\/index.php\/wp-json\/wp\/v2\/posts\/2172"}],"collection":[{"href":"https:\/\/www.tiwaripedia.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tiwaripedia.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tiwaripedia.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tiwaripedia.com\/index.php\/wp-json\/wp\/v2\/comments?post=2172"}],"version-history":[{"count":1,"href":"https:\/\/www.tiwaripedia.com\/index.php\/wp-json\/wp\/v2\/posts\/2172\/revisions"}],"predecessor-version":[{"id":2173,"href":"https:\/\/www.tiwaripedia.com\/index.php\/wp-json\/wp\/v2\/posts\/2172\/revisions\/2173"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.tiwaripedia.com\/index.php\/wp-json\/wp\/v2\/media\/2169"}],"wp:attachment":[{"href":"https:\/\/www.tiwaripedia.com\/index.php\/wp-json\/wp\/v2\/media?parent=2172"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tiwaripedia.com\/index.php\/wp-json\/wp\/v2\/categories?post=2172"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tiwaripedia.com\/index.php\/wp-json\/wp\/v2\/tags?post=2172"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}