π§° SAP Service Management interview guide
S/4HANA Service and classic Customer Service (CS), from request and entitlement to confirmation, billing and profitability. Includes field service integration and a scored test.
Service OrdersContracts & SLAConfirmationsWarrantyRRB / DIP
SAP Service Management runs after-sales and field service: repairs, installations, maintenance contracts, warranty claims and in-house repairs. Today there are two flavours you must be able to compare in interviews: classic Customer Service (CS), built on the PM objects, and SAP S/4HANA Service, which brings the CRM one-order service model natively into S/4HANA. Both follow a Service-to-Cash cycle.
π Jump to the scored Service Mgmt test
What is SAP Service Mgmt?
Classic CS uses service notifications (S1, S2, S3), service orders (such as SM01 and SM02) on PM technology, service contracts in SD (VA41), warranty and resource-related billing (DIP profile, DP90).
SAP S/4HANA Service uses business transactions (service requests, quotations, service orders, service confirmations, service contracts, in-house repair and solution orders), service products, SLAs and entitlement, with Fiori apps and standard integration to SAP Field Service Management (FSM).
Service types to know: field service, in-house (depot) repair, contract-based preventive service, warranty service and bundled solutions combining products, services and subscriptions.
End-to-end process: Service-to-Cash
Walk the panel through the cycle and, at each step, say how it works in S/4HANA Service and in classic CS. This comparison is a favourite senior-level question.
- Customer request
Service request Β· IW51
The customer reports an issue through phone, portal or email. S/4HANA Service creates a service request; classic CS creates a service notification (S1, S2 or S3). - Identify object & entitlement
Equipment Β· Contract Β· Warranty
Identify the technical object (equipment and serial number) and check entitlement: service contract, warranty and SLA response times. - Quote (optional)
Service quotation
Prepare a quotation for chargeable work with service products, spare parts and expenses. Customer acceptance converts it to an order. - Create service order
Service order Β· IW31
The order holds service items, spare part items and expense items. In CS, the order type (such as SM02) carries revenue planning. - Price & set SLA dates
Pricing Β· Service profile
Pricing applies contract or price agreement conditions. SLA dates (first response, solution) are calculated from service and response profiles. - Plan & dispatch
FSM Β· Dispatching
Assign the technician by skills, location and availability, often in SAP Field Service Management with replication from S/4HANA. - Provide spare parts
Reservation Β· Delivery
Spare parts are issued from the warehouse or van stock, or procured through PRs for non-stock parts. - Execute on site
Mobile Β· FSM / SSAM
The technician performs the job, records time, parts, expenses and checklists, and captures the customer signature on mobile. - Confirm service
Service confirmation Β· IW41
The confirmation posts actual time, materials and expenses, with costs flowing to the controlling object. - Bill the customer
Billing Β· DP90 / VF01
Billing is based on confirmations (S/4HANA Service billing) or resource-related billing with a DIP profile (CS). Warranty work is not charged. - Costs & profitability
Settlement Β· Margin analysis
Revenues and costs land in CO-PA / margin analysis. Classic CS settles the order with KO88; S/4HANA Service posts in real time. - Analyse & renew
SLA KPIs Β· Contract renewal
Track first-time fix rate, SLA compliance and contract profitability, then renew or upsell service contracts.
Organizational structure & master data
Organizational structure
Sales area
Sales org, distribution channel and division used for pricing, billing and contracts in both CS and S/4HANA Service.
Service organisation (S/4HANA Service)
Maintained in the organisational model with the service function and determined in transactions through org determination rules.
Maintenance planning plant and work centres (classic CS)
CS orders are planned in a planning plant with work centres and activity types for labour costing.
Company code & controlling area
Determine where service revenue and costs are posted.
Service teams and territories
Used for responsibility, routing and dispatch, often managed in FSM.
Master data
Business Partner
Customer roles plus contact person and employee (technician) roles.
Service products (SERV)
Services with service-specific attributes, duration and unit of measure. Product categories for S/4HANA Service.
Technical objects
- Equipment (IE01) with serial number (IQ01)
- Functional locations for site-based service
- Installed base / object hierarchies
Contracts & warranty
- Service contracts with SLA and price agreements
- Warranty master (BGM1) assigned to equipment
- Service and response profiles
Pricing
Condition records for service products, labour rates, contract discounts and expenses.
DIP profile (classic CS)
Controls resource-related billing: which costs (by cost element) become which billable material and how they are summarised.
Key T-codes & Fiori apps
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.
| T-code / App | What it does |
|---|---|
| IW51 / IW52 / IW53 | Create / change / display service notification (CS) |
| IW31 / IW32 / IW33 | Create / change / display service order (CS order types like SM01, SM02) |
| IW72 / IW73 | Service order list change / display |
| IW41 | Order confirmation |
| DP90 / DP91 | Resource-related billing for service order / sales order |
| ODP1 | Maintain DIP profile |
| VA41 / VA42 | Create / change service contract (CS, SD contract) |
| BGM1 | Create master warranty |
| IE01 / IQ01 | Create equipment / serial number |
| KO88 | Settle service order |
| Fiori (S/4HANA Service): Manage Service Orders, Manage Service Contracts, Manage Service Confirmations, Manage In-House Repairs, Manage Service Quotations | S/4HANA Service business transactions |
What changed in S/4HANA
- SAP S/4HANA Service brings CRM-based service processes (one-order model) into the S/4HANA core, with business transactions for service requests, quotations, orders, confirmations, contracts, in-house repair and solution orders.
- No separate CRM system or middleware replication is needed: master data (BP, products, technical objects) is shared in one system.
- Classic CS remains available in S/4HANA, so many customers run CS processes and adopt S/4HANA Service gradually.
- Real-time financials: service transactions post costs and revenues through the Universal Journal, and event-based revenue recognition supports service orders and contracts.
- Standard integration with SAP Field Service Management for scheduling and mobile execution, and with SAP Service Cloud for customer engagement.
- Solution quotations and solution orders combine products, services and subscriptions, with BRIM for usage-based and recurring billing.
Integration points
| With | How it integrates |
|---|---|
| SD | Sales area, pricing, contracts (classic CS) and billing documents. Spare parts sales via sales orders. |
| PM / EAM | Classic CS reuses PM technical objects, notifications, orders, task lists and maintenance plans for contract-based preventive service. |
| MM / EWM | Spare parts reservations, van stock, procurement of non-stock parts and returns of defective parts. |
| FI / CO | Costs and revenues post to the service order or controlling object, then to margin analysis. RRB uses cost elements mapped in the DIP profile. |
| SAP FSM | Service orders and technician assignments replicate to FSM. Confirmations, time and parts come back to S/4HANA. |
| SAP Service Cloud / CX | Customer tickets and case management flow into S/4HANA service orders. |
| BRIM / Subscription | Recurring and usage-based charges for service contracts and bundled solutions. |
Interview questions & answers
Tap a question to see a model answer. They are grouped from fundamentals to scenario-based questions that senior panels love.
π’ Fundamentals
What is the difference between classic CS and S/4HANA Service? Beginner
Classic CS is built on PM objects (notifications, orders with order types such as SM01/SM02, work centres) with SD contracts and DIP-based billing. S/4HANA Service uses the CRM one-order model with business transactions (service request, quotation, order, confirmation, contract), service products, SLAs and Fiori, integrated natively in S/4HANA. Both are available in S/4HANA.
What are the service notification types in classic CS? Beginner
S1 problem notification (customer complaint), S2 activity report (service already performed) and S3 service request.
Explain the difference between service order types SM01 and SM02. Beginner
SM01 is a service order without revenue planning, typically for internal or warranty work. SM02 is a service order with revenue planning, used for chargeable work billed to the customer, often through resource-related billing.
What is resource-related billing (RRB)? Beginner
Billing based on the actual resources consumed (labour hours, materials, expenses) on a service order or sales order. The DIP profile defines how costs by cost element map to billable materials. DP90 creates a billing request, which is then billed in SD.
What is a service contract? Beginner
An agreement to provide services over a period, with covered objects, prices or price agreements, SLAs, and billing plans (periodic billing). In CS it is an SD contract (VA41, type WV); in S/4HANA Service it is a service contract business transaction.
What is warranty in SAP service? Beginner
A master warranty (BGM1) defines what is covered for how long. It is assigned to equipment or serial numbers, with customer and vendor warranty dates. The warranty check in notifications and orders decides whether work is billable.
π‘ Intermediate
How are SLAs handled in S/4HANA Service? Intermediate
Through service profiles (service availability windows) and response profiles (response and resolution times by priority), assigned via contracts or products. The system calculates SLA dates such as first response by and solution by, and monitors breaches.
What item types does a service order in S/4HANA Service have? Intermediate
Service items (labour), service parts items (spare parts) and expense items (travel, accommodation). Item categories determine pricing, billing relevance, logistics (reservation or delivery) and controlling.
How does billing work in S/4HANA Service? Intermediate
Confirmed items (or order items, depending on configuration) become billing-relevant and create billing request items. The billing document is created in SD billing, and accounting posts revenue. Contract billing uses billing plans for periodic charges.
What is in-house repair? Intermediate
A depot repair process: the customer sends the device, a repair order is created, the device is received and inspected, a quotation may be prepared, the repair is executed and confirmed, and the device is shipped back and billed. S/4HANA Service has a dedicated in-house repair transaction and Fiori apps.
How does contract-based preventive service work in classic CS? Intermediate
A maintenance plan referencing the service contract item and the customer equipment generates SM orders automatically. Costs are captured on the order, and billing follows the contract (fixed price) or RRB.
How do costs and revenues flow in service management? Intermediate
Labour (activity type rates), spare parts and expenses debit the service order or controlling object. Revenue comes from billing. In classic CS, the order is settled (KO88) to CO-PA or a sales order. S/4HANA Service posts to margin analysis in real time, with EBRR as an option.
π΄ Scenario & design
A customer wants technicians to use a modern mobile app with smart scheduling. What do you propose? Scenario
Integrate S/4HANA Service (or CS) with SAP Field Service Management: service orders replicate as service calls and activities, the dispatcher uses the planning board with skills and location-based scheduling, technicians use the FSM mobile app offline, and confirmations, time, parts and expenses flow back to S/4HANA through the standard integration.
A customer is on SAP CRM Service and ECC CS. What is your S/4HANA roadmap? Scenario
Assess whether to move to S/4HANA Service (successor to CRM Service) for the one-order processes, or keep CS processes initially. Map CRM transaction types to S/4HANA Service transaction types, migrate BP, products, technical objects and contracts, plan the FSM and Service Cloud integration, and phase the cutover by service line.
Billing amounts on a service order are wrong after RRB. How do you troubleshoot? Scenario
Check the DIP profile (ODP1): source characteristics, cost element to material mapping, quantity and value determination and summarisation. Review the dynamic items in DP90 simulation, the pricing for the billing materials, already billed items, and whether confirmations and goods issues are complete.
How would you design warranty claims against the original manufacturer? Scenario
Use warranty claim processing: the claim is created from the service order or notification, checked against vendor warranty, submitted to the manufacturer, and credited. Track parts returned to the vendor and reconcile credit notes. Use analytics for claim recovery rates.
How do you handle a service contract with quarterly fixed fees plus chargeable extra visits? Scenario
A service contract item with a periodic billing plan for the quarterly fee, and coverage definitions (entitled objects and services). Extra visits create service orders where contract determination applies the price agreement or discount, and billing runs from confirmations as chargeable items.
Which KPIs matter for a service business? Scenario
First-time fix rate, mean time to respond and resolve, SLA compliance, technician utilisation, parts availability, contract renewal rate, service revenue and margin per contract, and warranty cost as a percentage of sales.
How would you handle spare parts for field technicians? Scenario
Van stock as storage locations or special stock per technician, replenishment through stock transfer orders, parts consumption from confirmations, and returns of defective parts for repair or vendor claims. Integrate with FSM for parts visibility on mobile.
Solution architect view
Key Service Management design decisions:
- Platform choice: S/4HANA Service, classic CS, or a phased coexistence. Base it on process needs (SLA, contracts, solution orders), CRM history and roadmap.
- Service portfolio: service products, item categories and transaction types for field service, in-house repair, contract and warranty work.
- Entitlement model: contracts, warranties, SLA profiles and price agreements, and how they are determined automatically.
- Field execution: SAP Field Service Management or SAP Service and Asset Manager for scheduling and mobile.
- Commercials: fixed price, time and material (RRB), periodic contract billing, and subscription/usage billing with BRIM.
- Finance: controlling objects, margin analysis and event-based revenue recognition.
- Front office: SAP Service Cloud integration for case management and the customer portal.
Typical deliverables: Service-to-Cash process design, transaction type and item category matrix, SLA and entitlement design, FSM integration specification, and the billing and revenue recognition design.
Test yourself: scored Service Mgmt quiz
Interview tips
π‘ How to stand out
- Always compare classic CS and S/4HANA Service. Panels love this question.
- Explain RRB and the DIP profile with a concrete example (labour hours and parts on one invoice).
- Know entitlement: contracts, warranty, SLA profiles, and how they are determined.
- Talk about field service integration with SAP FSM and mobile execution.
- For senior roles, cover commercial models (fixed, T&M, subscription) and revenue recognition.
Keep preparing: π― SAP Interview Prep hub & combined mock test Β· All SAP interview guides Β· ERP Software
