SAP Service Management Module Guide
Customer Service / After-Sales Management — Implementation Guide
June 2026
Chapter 1: Overview and Role of SAP Service
Role and Positioning of the Service Module
SAP Service (formerly known as CS, Customer Service) is the module that provides integrated management of the after-sales service operations that occur once a product has been sold. It centrally manages the entire field service cycle within SAP — from receiving service requests from customers, creating repair orders, and consuming spare parts, to recording labor hours and issuing invoices. In S/4HANA it has been redesigned as “SAP Service,” with enhanced real-time cost tracking, mobile support, and AI utilization.
Service businesses share a common characteristic: “the real business begins after the product is sold.” Guaranteeing equipment uptime, meeting SLA (Service Level Agreement) commitments, preventive maintenance, and arranging replacement parts — monetizing the service business is a management challenge for manufacturers, machinery makers, medical device companies, and IT infrastructure companies alike. SAP Service integrates these activities with Production (PP), Purchasing (MM), Finance (FI/CO), and Sales (SD), making service operations visible as a source of revenue.
| Key Business Scenarios Involving SAP Service |
|
– Service notification intake: Recording customer reports of failures, repair requests, and complaints in the system – Service order execution: Creating orders for repairs, periodic maintenance, and installation work; arranging parts and recording labor hours – Maintenance contract management: Automating fixed-price, time-and-material, and SLA-based maintenance contracts and periodic billing – Warranty management: Automatically determining whether repairs within the product warranty period are free of charge or chargeable – Resource-related billing: Billing based on actual labor hours, parts used, and travel expenses incurred – Preventive maintenance planning: Automatically generating periodic maintenance schedules based on time or usage counters |
Integration with Other Modules
| Integrated Module | Integration Content | Representative Data Flow |
| SD (Sales) | Service order billing is issued via SD sales documents. The DIP Profile (Dynamic Item Processor) converts actual costs into billing line items. | Service order → DP90 → SD billing request → VF01 invoice |
| MM (Purchasing / Inventory) | Consumption of replacement parts from a service order (goods issue). Service procurement for subcontracted repairs. | IW31 order → MIGO goods issue (movement type 261). Subcontracting → MM purchase order → goods receipt → invoice |
| PM (Plant Maintenance) | CS and PM technically share the same foundation (notifications, orders, and equipment master are shared). CS covers customer-owned equipment, while PM covers company-owned equipment. | Equipment master and functional locations are shared. The order type distinguishes CS from PM. |
| FI (Financial Accounting) | Actual costs on a service order automatically generate FI journal entries. SD invoices generate AR/revenue postings. | Parts issue → BSX/GBB postings. Invoice → accounts receivable/revenue postings |
| CO (Management Accounting) | Like an internal order, a service order is a cost-collector object, tracking actual costs (parts + labor + subcontracting) in real time. | Order-level cost report (IW39). Actual/plan comparison in KOB1/KOB2 |
| QM (Quality Management) | Recording quality data on repair outcomes and managing defect cause codes. Linkage between quality notifications and service notifications. | Linking a quality notification (M2) to a service order. Defect code / cause code systems |
Automatic Journal Entry Generation, Goods Movements, and Workflow
Each business transaction in SAP Service automatically generates goods movements and FI journal entries. “Issuing parts to a service order,” “posting subcontracting costs,” and “linking to an SD invoice” are the main posting triggers. In addition, status changes on service notifications and orders are linked to workflow, driving automatic task notifications and escalation management for the responsible parties.
| Business Step | Goods Movement Type | Automatically Generated FI Posting |
| Issuing replacement parts to a service order (MIGO / IW31 material component) | 261 (order issue) | Work in process/expense (GBB-VBR) ← Parts inventory (BSX) |
| Posting subcontracted repair costs (MIRO) | No goods movement | Subcontracting costs (posted to the order) ← Accounts payable (KBS) |
| Goods receipt for a completed repair (in-house repair) | 101 (repaired goods receipt) | Repair inventory (BSX) ← Order cost (price variance PRD) |
| DP90 resource-related billing | No goods movement | Generates an SD sales document (billing request) → in VF01, accounts receivable (FI-AR) ← revenue (FI-CO-PA) |
| Periodic billing for maintenance contracts (VA41) | No goods movement | Automatically generates SD invoices on a recurring basis. Accounts receivable ← service revenue |
| Order settlement (KO88) | No goods movement | Settles the order’s cost balance to a cost center, WBS element, or revenue account |
| Workflow: Approval Control for Service Notifications, Orders, and Contracts |
|
[Service Notification WF] – Notification creation (IW21) → automatic task assignment to the responsible person based on priority (Fiori notification) – SLA management: automatic escalation when the response time or resolution time defined in the contract is exceeded – Notification completion: after corrective action is complete, the responsible person closes the notification as “Complete” → final approval WF by the supervisor [Service Order WF] – Order creation (IW31) → automatic task assignment to the technician (field service dispatch) – Subcontract purchase order approval: when an outsourced MM purchase order is generated from the order, a purchasing approval WF is triggered – Order closure: technician completion confirmation → manager approval → WF to generate the DP90 billing request [Warranty Determination WF] – The equipment master’s warranty period is automatically checked when a notification is received – Within warranty → processed free of charge (warranty order type) – Outside warranty → automatically switched to a chargeable order (a customer quotation approval WF can be inserted) |
Chapter 2: Master Data
Equipment Master
The equipment master is the object that manages each individual piece of equipment (a serial-managed product) that is subject to service. The equipment number is linked to the serial number, and the delivery history to the customer, installation location, warranty period, and repair history are all managed at the equipment level. In manufacturing, shipped equipment is tracked via the equipment master to understand “which equipment is installed at which customer’s which site.”
| Key Fields of the Equipment Master | Content / Purpose |
| Equipment number | Internal management number (assigned by SAP, or linked 1:1 with the serial number) |
| Equipment category | Classifies the type of equipment (e.g., M = Equipment / I = Instrumentation / F = Plant Facility) |
| Serial number | The unique identification number of the product; linked to the material master for model management |
| Functional location (FLOC) | The hierarchical structure of the location (plant/building/line) where the equipment is installed |
| Customer (sold-to party) | The customer (business partner) that owns and uses the equipment |
| Warranty information | Type of product warranty, start date, and end date. Automatically checked when a notification is received |
| Usage counter | Values such as operating hours or mileage that trigger periodic maintenance |
| Acquisition price / acquisition date | Used for asset management (AA integration). Also used to manage leased equipment |
Functional Location
A functional location (FLOC) is the hierarchical structure of the physical or functional location where equipment is installed. Locations are managed in a hierarchy such as “plant – building – line – unit,” and the installation history is tracked by installing or dismantling equipment at that location. When managing multiple customer sites, the location is defined from the customer’s point of view using a hierarchy such as “customer – business location – floor – facility number.”
Service BOM and Task Lists
| Master Data | Overview | Main Use |
| Service BOM (bill of materials) | A list of parts and consumables needed for repair/maintenance, defined per equipment category or per piece of equipment | Automatically sets components on the service order. Estimating parts costs |
| Task list (general task list) | A template for standard work procedures, defining the work content, standard labor hours, and required parts | Automatically expands work content on periodic maintenance or repair orders. Managing standard values for working time |
| Warranty master | Defines the warranty type (product warranty/extended warranty/SLA) and the warranty period and scope | Automates warranty determination when creating notifications and orders |
| Service product (service material) | Manages a service as a material (an intangible item), saleable via SD, with a service unit price used as the billing basis | Used to convert resources into billing lines in DP90. Defines hourly rates and parts unit prices |
| Counter definition | Defines the equipment’s usage counter (hours/distance/count); actual values are entered periodically or captured automatically (IoT integration) | Counter-based trigger for periodic maintenance plans |
Chapter 3: Service Notification
Concept and Types of Service Notifications
A service notification (IW21/IW51) is the first point of contact for receiving inquiries, failure reports, repair requests, and complaints from customers. The processing flow differs by notification type, and urgency, SLA, and warranty determination are automatically checked at the time the notification is created. A notification may be completed on its own, but in many cases it becomes the trigger for creating a service order (to execute the repair).
| Notification Type | Purpose | Follow-up Processing |
| S1 Service activity (Service Activity) | Records planned service activities such as periodic visits, preventive inspections, and installations | Creation of a service order (SM01/SM03) |
| M1 Repair request (Malfunction Report) | A customer’s failure/repair request; reports equipment downtime or malfunction | Recording downtime; creation of a service order (SM02) |
| M2 Quality notification (CS) (Quality Notification) | Records product complaints and quality issues; linked with the QM module | 8D report, corrective action (CAPA); quality issue feedback to the vendor |
| A1 Activity report (Activity Report) | A retrospective record of a completed service activity; used like a field engineer’s daily report | Billing via DP90 (actual cost settlement); updating equipment usage records |
Service Notification Processing Flow
| Standard Flow from Notification Intake to Order Creation |
|
Step 1: Notification intake (IW21 / Fiori: Create Service Notification) – Enter the customer, equipment number, failure symptom, and priority (urgent/normal/low) – Warranty determination: automatically checks the equipment master’s warranty information → determines chargeable or free of charge – SLA check: automatically displays the response time and resolution time from the maintenance contract Step 2: Diagnosis and entry of cause codes – Records the failure code, cause code, and action code (code sets) – References past repair history for similar cases in the system Step 3: Conversion into a service order – Clicking the “Create Order” button automatically generates a service order (linking the notification and the order) – Automatically expands standard work and parts from the task list Step 4: Notification closure – After confirming order completion, the notification status is changed to “Complete” – Triggers a customer satisfaction survey (Fiori integration) |
SLA (Service Level Agreement) Management
By setting an SLA on a maintenance contract, the system automatically monitors the response time and resolution time. If the specified time is exceeded after a notification is received, an escalation notice is automatically sent, triggering a task for the service manager. SLA breaches are aggregated in service reports and used as KPIs for contract renewal negotiations and service quality improvement.
Chapter 4: Service Order
Concept and Order Types of Service Orders
A service order (IW31/IW32, or SM01) is the central document for executing service work such as repair, maintenance, and installation. The plan and actuals for the work content, assigned technician, required parts, working time, and cost are all managed under a single order number. The order also functions as a cost-collector object, linking directly to CO (management accounting).
| Order Type | Purpose / Characteristics |
| SM01 (repair request order) | Repair work based on a customer’s repair request; often generated automatically from a notification; supports both chargeable and free-of-charge repairs |
| SM02 (warranty order) | An order type dedicated to free-of-charge repairs within the warranty period; costs are posted as cost of goods sold (no customer billing); used for warranty cost analysis |
| SM03 (service activity order) | Orders for periodic inspections, preventive maintenance, and installation work; can be automatically generated from a maintenance plan (IP01) |
| SM04 (maintenance order) | Maintenance and operational support for customer-owned equipment; manages ongoing work linked to a maintenance contract |
Key Operations of the Service Order
| Operation Phase | Key Transaction / Operation Content |
| Order creation | IW31: enter the order type, equipment, notification, and work content. Operations and components are automatically expanded from the task list. Cost plan (labor hours × rate, parts unit price) is calculated automatically |
| Technician assignment / dispatch | Assigns the order’s work to a field technician. Fiori Launchpad: displayed on a map and optimally assigned via Technician Dispatching. Sent to the technician via mobile (SAP Field Service Management integration) |
| Parts consumption (goods issue) | Parts are issued via MIGO or from the order screen (movement type 261). Inventory reservation: planned parts are reserved against the order. Subcontracted parts: an MM purchase requisition is automatically raised and posted to the order after goods receipt |
| Confirmation of labor hours (recording working time) | IW41 (individual confirmation) / IW42 (collective confirmation): the technician enters working time and completed quantity. Can also be entered via Cross-Application Timesheet (CAT2). At the time of confirmation, actual costs are automatically posted to CO |
| Subcontracting | An MM purchase requisition is automatically created from the order’s subcontracting operation. Costs are posted to the order upon goods receipt and MIRO invoice verification from the subcontractor |
| Order completion / technical completion | IW32: changes the status to TECO (Technical Completion). No further costs can be posted afterward (goods issues are also blocked). Enables the creation of a DP90 billing request |
| Order settlement | KO88: settles the order’s remaining costs to a cost center or revenue account. Free-of-charge repair: costs are transferred to a warranty cost account. Chargeable repair: remaining variances are settled after DP90 billing |
Resource-Related Billing (DP90 / DIP Profile)
“Resource-Related Billing” is the mechanism that converts a service order’s actual costs (parts, labor, subcontracting, and travel expenses) into a customer invoice. The DIP Profile (Dynamic Item Processor Profile) defines, for each cost category of the order, “which SD material and billing condition it converts into.” Executing DP90 (creating a billing request) expands the order’s actual costs into line items of an SD sales document (billing request), which is then invoiced via VF01.
| Example of DP90 Resource-Related Billing Execution |
|
Actual costs for service order #1000123 (example): Parts cost: replacement filter × 3 units × 2,500 yen = 7,500 yen Labor cost: technician 4 hours × 8,000 yen/hour = 32,000 yen Travel expenses: trip expenses 1 unit = 15,000 yen Subcontracting cost: calibration work outsourced = 50,000 yen ──────────────────── Total billed amount: 104,500 yen Executing DP90 → the DIP Profile converts each cost as follows: Parts cost → converted to a unit price via SD material “SRV-PARTS” / billing condition PR00 Labor cost → SD material “SRV-LABOR” / hourly rate × actual hours Subcontracting cost → SD material “SRV-SUBCON” / pass-through of actual cost → Issues a customer invoice (F2) via VF01 → FI posting: accounts receivable 104,500 ← service revenue 104,500 |
Chapter 5: Service Contract
Types and Management of Maintenance Contracts
A service contract (an SD contract created via VA41) manages a long-term maintenance service agreement concluded with a customer within the system. It defines the contract period, covered equipment, service content, SLA, and pricing structure, and functions as the baseline for periodic billing, warranty determination, and maintenance planning.
| Contract Type | Pricing Model | Characteristics / Applicable Cases |
| Fixed-price maintenance contract (Fixed-Price Contract) | Fixed monthly/annual fee | Periodic inspection of equipment, 24-hour response guarantee. A flat fee regardless of the number of incidents. For IT equipment, medical devices, and industrial machinery |
| Time-and-material contract (Time & Material Contract) | Settlement of actual cost based on actual labor hours plus parts used | Combined with DP90 resource-related billing. Bills the customer the actual cost for each job. For spot repairs and small/medium-sized customers |
| Quantity contract (Quantity Contract) | A method of pre-purchasing service units (number of visits/hours) | E.g., 10 annual visits or 100 support hours; the contract balance is drawn down with each use |
| Maintenance contract with SLA | A contract with guaranteed response time and recovery time; manages penalties (service credits) for violations | For mission-critical facilities; automatic detection and notification of SLA breaches |
Maintenance Plan
A maintenance plan (IP01) is a mechanism that automatically generates service orders and service notifications for equipment on a periodic basis. Triggers can be set as time-based (e.g., every 3 months), counter-based (e.g., every 1,000 operating hours), or combined (whichever comes first). Running IP10 (maintenance plan scheduling) automatically generates, in a batch, the orders for maintenance work that has come due.
| Maintenance Plan Settings | Content |
| Plan type | Time-based: defines the cycle using calendar dates. Performance-based (counter-based): defines the cycle using equipment usage values |
| Cycle | The interval for performing maintenance work (e.g., every 3 months, every 10,000 km driven) |
| Scheduling timing | Setting of the early-execution tolerance period and the late-execution tolerance period (window management) |
| Generated object | Automatically generates a service order, a service notification, or a PM order |
| Task list reference | Automatically expands the maintenance work content (work procedure, standard labor hours, parts) |
| Billing settings | Linkage with the maintenance contract (whether periodic maintenance costs are included in the contract fee) |
Contract-Based Periodic Billing
Monthly billing for a fixed-price maintenance contract can be automated using the billing plan of the SD contract. At the beginning of each month, a billing request is automatically generated, and monthly invoices are issued in a batch via VF04 (billing execution). Because the billing date, billing currency, and recipient are set per customer in the contract, billing operations can be greatly automated even for companies with a large number of maintenance contracts.
Chapter 6: End-to-End Transaction Operation Guide
Scenario 1: From Customer Complaint to Repair Completion and Billing (Chargeable Repair)
| Standard Chargeable Repair Flow (Order-to-Cash for Service) |
|
Step 1: Service notification intake (IW21) → Customer “Tozai Kiki Corporation,” equipment #EQ-00045 (compressor), failure symptom: abnormal noise → Warranty check: warranty expired March 2024 (out of warranty) → confirmed as a chargeable repair → Checked whether the repair is covered under maintenance contract #SC-1234 (fixed-price contract) → not covered → billed on a per-job basis Step 2: Service order creation (IW31) → Order type SM01, automatically generated from the notification number → Task list referenced: standard repair procedure and parts list automatically set → Cost plan: parts 15,000 yen + labor 4h × 8,000 yen = 47,000 yen Step 3: Parts reservation and issue (MIGO) → Compressor bearing × 1 (goods issue) → Posting: work in process (GBB-VBR) 15,000 ← parts inventory (BSX) 15,000 Step 4: On-site work and confirmation of labor hours (IW41) → After completing the on-site repair, the technician enters actual labor hours of 4.5h via IW41 → CO: actual cost (labor cost of 36,000 yen) is automatically posted to the order Step 5: Technical completion of the order (IW32 → TECO) → After technical closure, a billing request can be created Step 6: Creating the DP90 resource-related billing request → Converts the actual costs (parts 15,000 + labor 36,000 + travel expenses 5,000) into an SD sales document line item Step 7: Invoice issuance (VF01) → Customer invoice #9000234: 56,000 yen (excl. tax) → FI posting: accounts receivable 56,000 ← service revenue 56,000 |
Scenario 2: Preventive Maintenance Based on a Maintenance Plan (Fixed-Price Contract)
| Flow: Maintenance Plan → Automatic Order Generation → Execution → Contract Billing |
|
Step 1: Execute the maintenance plan schedule (IP10) → Displays a list of equipment for which the quarterly periodic inspection is due → Running “Generate” automatically creates SM03 orders in a batch for the target equipment Step 2: Confirm the orders and assign work (IW38 order pool) → Automatically assigns the generated list of SM03 orders to field technicians → Registers the inspection date on the scheduling calendar Step 3: Perform the inspection and record the checklist (IW41) → The technician enters actual work performed and inspection results from a mobile device → Because the periodic inspection cost is included in the maintenance contract fee, there is no customer billing Step 4: Automatic fixed monthly billing → A billing request is automatically generated at the start of the month based on the maintenance contract’s billing plan (see VA41) → Invoices are issued via the VF04 batch billing run → Monthly maintenance fee 100,000 yen × 12 months = annual total 1,200,000 yen Step 5: Order settlement (KO88) → Settles the order costs (periodic inspection labor hours, consumables) to the maintenance cost account |
Chapter 7: List of Key Transactions
| Category | Transaction | Function |
| Notification | IW21 | Create a service notification |
| Notification | IW22 | Change a service notification |
| Notification | IW23 | Display a service notification |
| Notification | IW28 | Service notification list (by person responsible / priority) |
| Order | IW31 | Create a service order |
| Order | IW32 | Change a service order |
| Order | IW38 | Service order pool (list display / assignment) |
| Order | IW39 | Order cost report (plan/actual/variance) |
| Order confirmation | IW41 | Individual confirmation (labor hours, completed quantity) |
| Order confirmation | IW42 | Collective confirmation (multiple orders) |
| Billing | DP90 | Create a resource-related billing request (order → SD) |
| Billing | VF01 | Create an individual invoice |
| Billing | VF04 | Batch invoice run (monthly) |
| Contract | VA41 | Create a service contract |
| Contract | VA42 | Change a service contract |
| Maintenance plan | IP01 | Create a maintenance plan |
| Maintenance plan | IP10 | Execute the maintenance plan schedule (batch order generation) |
| Equipment | IE01 | Create an equipment master |
| Equipment | IE02 | Change an equipment master |
| Equipment | IH01 | Create a functional location |
| Report | IW70 | Service cost report (by equipment/customer) |
| Report | IW65 | Equipment list and repair history by customer |
Chapter 8: Detailed SPRO Configuration
8.1 Basic Settings
| Setting Item | SPRO Path | Content |
| Notification type definition | SM → Service Processing → Notifications → Notification Types | Defines notification types such as S1/M1/M2; assigns priority, SLA, and code group |
| Order type settings | SM → Service Processing → Orders → Order Types | Sets the cost collection, settlement, and number range for SM01/SM02/SM03/SM04 |
| DIP Profile settings | PS/CS → Billing → DIP Profile | Defines the conversion rules from cost category to SD service material (the core setting for DP90) |
| Warranty category | SM → Warranty Settings | Sets the period and scope for product warranties and extended warranties, and the chargeable/free-of-charge determination logic |
| Maintenance plan category | PM/CS → Maintenance Plan → Plan Category | Sets the cycle and tolerance window for time-based/counter-based maintenance plans |
| Code settings | SM → Notification → Codes | Defines catalogs of failure codes, cause codes, and action codes by industry and equipment type |
8.2 Billing Integration Settings (SD Integration)
To convert service order costs into a customer invoice, the account determination (VKOA) and pricing on the SD side must be linked with the DIP Profile settings on the CS side. In the DIP Profile, the “labor cost category of the CS order” is converted into the “SD service material SRV-LABOR,” and the customer’s unit price is determined by the pricing condition (PR00) of that SD service material. With this configuration, the billing amount is automatically calculated the moment a technician enters labor hours.
8.3 Field Service Integration Settings
In S/4HANA, integration with SAP Field Service Management (FSM) has been strengthened. By configuring FSM integration in SPRO, SAP Service calls (notifications and orders) are automatically linked to the FSM dispatch management screen, and work instructions are sent to the field technician’s mobile app. Content entered from the mobile device upon work completion is automatically reflected in the labor confirmation in SAP Service.
Chapter 9: Implementation Case Studies
Case 1: Industrial Machinery Manufacturer A — Monetizing After-Sales Service and Automating Billing
Company A (a machine tool manufacturer) had more than 300 service locations for its customers nationwide, and had been managing repair work using paper work reports. Because invoices were prepared manually by aggregating the reports at month-end, missed and delayed billing had become chronic. With the introduction of SAP Service, technicians now enter working time and parts used in real time via mobile, which is automatically aggregated by DP90, enabling batch monthly billing.
| Challenges Before Implementation | Effects After Implementation |
| Repair reports were managed on paper, taking a week to aggregate | Mobile technician entry → costs are finalized the same day |
| Missed billing estimated at 30 million yen per year | Automatic aggregation via DP90 eliminates missed billing |
| Equipment repair history was managed inconsistently | All repair history is centrally managed in the equipment master |
| Determination of in/out-of-warranty relied on staff memory | Automatic determination via the warranty master → immediately decides free-of-charge/chargeable |
| Maintenance contract renewal timing was overlooked | Contract expiration alerts ensure renewal opportunities are reliably captured |
Case 2: Medical Device Manufacturer B — Maintenance Contract SLA Management and GxP Compliance
Company B (a medical diagnostic equipment manufacturer) manages maintenance contracts for 500 MRI and CT units nationwide at hospitals. Because downtime of medical equipment directly affects patient diagnosis, its SLAs are strict (response within 4 hours, recovery within 24 hours). Using SAP Service, the company built automatic SLA monitoring and escalation workflows at the time of notification intake, improving its SLA compliance rate from 91% to 99%. It also digitized repair records so that repair records could be submitted to regulatory authorities with a single click.
| Requirements Specific to Medical Devices | How SAP Service Addresses Them |
| 4-hour response SLA | Countdown starts from notification intake; automatic escalation to the manager when the remaining time falls to 30 minutes or less |
| Audit evidence for repair records | The complete history of orders, confirmations, and DIP billing is stored electronically in SAP; an audit trail of equipment number, technician, date/time, and work content |
| Uptime guarantee through preventive maintenance | A counter-based maintenance plan automatically generates a preventive maintenance order and dispatches a technician every 1,000 operating hours |
| Quality traceability of replacement parts | Batch management of parts (QM integration) links the lot and manufacturer of parts used to the repair record |
Case 3: IT Infrastructure Company C — Digitizing Field Service and Visualizing Costs
Company C (a systems integrator for servers and network equipment) has 100 field engineers nationwide, but had not been able to grasp technician utilization, order progress, or profitability in real time. Through the combined implementation of SAP Service and SAP Field Service Management (FSM), technician utilization, movement, and work progress are now visualized in real time. Through analysis of service cost and profitability by customer, the company was able to review unprofitable contracts and revise pricing, improving the service business’s EBIT margin from 4% to 11%.
Chapter 10: What You Can Do with SAP Service — Key Functions and Operations
SAP Service (CS) is not merely a repair management tool; it is an integrated platform for operating after-sales service as a “revenue-generating business.” Below, we organize by function what business users can actually do with this system.
| (1) What You Can Do with Service Notification and SLA Management |
|
– Instantly receive and number a customer’s failure/repair request via IW21 or a Fiori app – Warranty master lookup: automatically displays the warranty expiration date and scope the moment the equipment number is entered – SLA timer: displays a countdown of the time remaining for response/recovery from the time the notification was received – Automatic escalation: automatically notifies the supervisor when the remaining SLA time falls below the configured value – Similar case search: instantly references past repair history for the same equipment or the same failure code – Customer portal integration (Fiori): allows customers to submit repair requests and check progress themselves via the web |
| (2) What You Can Do with Service Orders and Field Service |
|
– Automatically expand standard work procedures and parts lists from the task list (greatly reducing data entry effort) – Order assignment to field engineers: automatic assignment that takes skills, location, and availability into account – Mobile work: technicians can confirm work, record parts consumption, attach photos, and capture electronic signatures from a smartphone – Parts inventory reservation: automatically reserves the required parts from warehouse stock at the time the order is confirmed (preventing stockouts) – Subcontracting management: generate an outsourced MM purchase order from the order with one click, managed consistently through goods receipt and billing – Real-time cost tracking: automatically updates the CO order balance every time parts are issued or labor hours are confirmed |
| (3) What You Can Do with Billing and Contract Management |
|
– DP90 resource-related billing: automatically calculates the order’s actual costs (parts + labor + subcontracting + travel expenses) using customer-specific unit price conditions → converts them into an SD invoice with one click – Automatic monthly billing for fixed-price contracts: automatically generates billing requests every month based on the maintenance contract’s billing plan → issues hundreds of invoices simultaneously via a VF04 batch run – Warranty cost analysis: aggregates the cost of free-of-charge (warranty) repairs by equipment type and by supplier → used to identify product quality issues and as a basis for penalty claims against suppliers – Contract profitability analysis: monthly reports comparing revenue (fixed fees) versus cost (repair expenses) by contract → data used as the basis for repricing or reviewing the scope of unprofitable contracts |
| (4) What You Can Do with Preventive Maintenance and Equipment Management |
|
– Time-based/counter-based maintenance plans: automatically generate periodic maintenance orders at the configured cycle → achieves “zero-touch” operation all the way through automatic assignment to the responsible technician – Equipment lifecycle management: tracks acquisition → installation → repair → parts replacement → disposal under a single equipment number – Usage counter management: automatically updates counter values from on-site readings or IoT sensors → automatically schedules maintenance such as “change the oil every 1,000 operating hours” – Repair history analysis: reports on the number of repairs, repair cost, and MTBF (mean time between failures) by equipment → used for renewal investment decisions and reviewing warranty design |
End
Have a question about this article?
Ask the author directly — no sales pitch, just an answer.