Processing Repairs in SAP Plant Maintenance (Karl Liebstückel)（Z-Library）

【One-Line Pitch】 A practical, configuration-aware walkthrough of how SAP EAM/Plant Maintenance actually handles a repair—from the first notification through planning, controlling, execution, and completion—for maintenance planners, SAP PM key users, and consultants who need to run or tune the process rather than just read about it. 【Book Arc】 - **Opening (~0%–15%)**: Establishes the five-stage repair lifecycle (notification, planning, controlling, processing, completion) and drills into notifications—creation, reference objects, catalogs/profiles, partners, documents, printing, and status—so a fault is captured accurately and routed correctly. - **Early (~15%–30%)**: Moves from notification to order: creating orders directly or from notifications, order types, screen layouts, operations, responsibilities, and scheduling logic (lead-time vs. network scheduling, operation relationships). - **Middle (~30%–50%)**: Covers material and resource planning—stock vs. non-stock materials, reservations and purchase requisitions, task lists, where-used lists, and estimated/planned cost display by cost elements or value categories. - **Middle–Late (~50%–65%)**: Shifts to controlling before execution: mass change, capacity requirements planning and leveling, availability checks, order release, and shop-paper printing. - **Late (~65%–90%)**: Addresses processing and completion—confirmations and technical completion—closing the loop so work performed is documented and orders are finalized. - **Ending (~90%–100%)**: Reinforces tailoring the SAP EAM implementation to plant-specific needs so notifications, spare parts, and work orders arrive on time. (Excerpts do not cover the final pages in detail.) 【Key Takeaways】 - **Notifications are the entry point of the whole repair cycle** (Opening): they describe the technical problem, request work, and document what was done, creating a long-term analysis record rather than a one-off message. - **Screen layouts can differ by activity** (Opening): SAP lets entry and change screens look different, so a production employee gets a minimal form while maintenance staff see richer tabs—useful for adoption and data quality. - **Catalog profiles narrow code selection** (Opening): assigning profiles to equipment, functional location, and notification type limits codes to relevant ones, improving accuracy and user acceptance. - **Object information supports the repair decision** (Opening): structure data, classification characteristics, prior damage, open notifications/orders, plans, and limit warnings are pulled together to judge whether and when work is needed. - **Order creation has several valid paths** (Early): direct order creation, order-with-notification, or combining multiple notifications into one order—each fits a different maintenance scenario. - **Scheduling only makes sense with standard times** (Early): if times are missing, don't activate scheduling; use a control key without the schedule option. Lead-time and network scheduling, plus finish-start/start-start/finish-finish relationships, drive realistic dates. - **Material planning hinges on stock vs. non-stock logic** (Middle): reservations and purchase requisitions are coupled, and dependent requirements should sit at operation level to avoid inflating warehouse stock. - **Controlling is where plans become executable** (Middle–Late): mass change, capacity overviews and leveling, availability checks, release, and shop papers are the levers that make an order ready for the workshop. 【Reading Tips】 - Deep-read the notification and order-creation chapters if you are a key user; they determine data quality for everything downstream. - Skim the Customizing function names on first pass, then return to them when configuring—they are the actionable core. - Treat scheduling and material planning as the hard spots: understand control keys, relationship types, and reservation timing before changing settings. - Keep the five-stage lifecycle in mind as a checklist; use it to diagnose where a broken repair process actually fails. - Note the cross-module dependencies (CO, PP, CS, PS share order tables) before defining order types. 【Coverage Limits】 This guide is based on stratified excerpts covering the notification, planning, and controlling stages in most detail; processing and completion are represented more thinly, and the excerpts do not cover every figure or Customizing path in the full book.