Lesson 2 of 6
The SAP S/4HANA Service object model
10 min
Listen to this lesson
SAP S/4HANA Service is built on business transactions, a document model that came from SAP CRM and now lives inside SAP S/4HANA. Every service document is a business transaction with a header and items. Its transaction type decides what kind of document it is and how it behaves; each item has an item category that decides what the line does, such as a service performed, a part used or an expense. Understanding this model is the key to mapping CS processes and to designing tests.
The main documents
| Document | Standard transaction type | Purpose |
|---|---|---|
| Service request | SRVR | Records the customer's demand or problem; can be copied to a quotation, an order or a confirmation |
| Service order quotation | SRVQ | Offers the service and price; accepted quotations become service orders |
| Service order | SRVO | Plans and manages one-off service work; also used as repair order |
| Service confirmation | SRVC | Records actual time, parts and expenses; feeds billing and costing |
| Service contract | Contract transaction type (check your system) | Long-term agreement with prices, services and periodic billing |
| In-house service (in-house repair) | IHRP | Repair of objects that the customer sends in; renamed "in-house service" in release 2025 |
Main SAP S/4HANA Service documents and standard transaction types, from SAP Learning's customizing course. Confirm in Customizing under Service > Transactions > Basic Settings > Define Transaction Types.
| Item category (order / quotation) | Meaning |
|---|---|
| SRVP / SRQP | Service item: work performed, usually priced by time or fixed price |
| SRVM / SRQM | Service part: material used in the service |
| SRVE / SRQE | Expense item: travel and similar costs |
| SRVS / SRQS | Sales item: a product sold with the service |
Standard item categories for service orders (SRVO) and service order quotations (SRVQ).
Reference objects and organization
Service documents point to reference objects, such as equipment and functional locations from asset management, so the history of a serviced unit can be followed. For Contoso, each fleet alternator under contract is equipment with a serial number, installed at the Great Lakes depot that runs the truck. Documents also carry organizational data: a service organization for the people doing the work, and a sales area (Contoso uses 1710 / 10 / 00) for pricing and billing. Partners on the documents include the sold-to (Great Lakes Fleet Services, 17100001), the ship-to depot where work happens (for example 17100007 Flint), and the employee responsible.
Accounting on the item
SAP S/4HANA Service uses item-based accounting: service transaction items act as account assignment objects for costs and revenues. When a technician confirms work, the actual cost lands on the service order item, and the revenue from billing lands there as well, so profitability can be analyzed per item and flows to margin analysis. This is a real change from CS, where the service order (a PM order) collected costs and settled them.
Statuses and partners
Business transactions carry system statuses on the header and on each item, and many customers add user statuses through a status profile. Item-level status matters: a service order can have one item released and another still open, and only the released one can be confirmed. Partner determination procedures decide which partners a document needs, for example sold-to, ship-to, bill-to, payer and the employee responsible, and which are copied from the customer master or a contract. For tests, treat the partner determination procedure and the status profile as configuration to be covered, just like pricing: a missing payer or a status that never sets blocks billing at the end of the chain.
Mapping CS to SAP S/4HANA Service
| CS (ECC) | SAP S/4HANA Service | Key difference |
|---|---|---|
| Service notification (IW51) | Service request (SRVR) | A business transaction instead of a PM notification |
| Service order (IW31, SM01/SM02) | Service order (SRVO), or service with advanced execution | Commercial order with items; advanced execution adds a maintenance order for complex work |
| Order confirmation (IW41) | Service confirmation (SRVC) | Its own document with items for time, parts and expenses |
| SD service contract (VA41, WV) | Service contract | A business transaction with items, price agreements and billing |
| Resource-related billing (DP90) | Billing document requests from confirmations and contracts | Billing follows confirmations; DIP remains for advanced execution |
| Repair order (RMA in SD) | In-house service (IHRP) | A dedicated repair process with in-house service objects |
How Contoso's CS objects map to SAP S/4HANA Service.
What goes wrong in testing
| Pitfall | Consequence | Prevention |
|---|---|---|
| Mapping only document types | Item behavior (parts, expenses) untested | Test each item category in orders and confirmations |
| Reference objects not migrated | History and contract determination fail | Load equipment and installations before service tests |
| Old settlement assumptions | Finance expects CS settlement, finds item accounting | Agree margin reporting expectations with Dan first |
Typical object-model test failures.
What would you do?
During design, the service manager asks whether Contoso's CS service order types can simply be renamed to SRVO in the converted system. What is the right answer?
- Service documents are business transactions with transaction types and item categories.
- Standard types: SRVR request, SRVQ quotation, SRVO order, SRVC confirmation, IHRP in-house service.
- Items act as account assignment objects for costs and revenues.
- Every CS object has a successor, but each one behaves differently; redesign, do not rename.
Check your understanding · not graded
Lesson check
1. What is the standard transaction type for a service confirmation?
2. Which item category is a service part in a service order?
3. What does item-based accounting mean in SAP S/4HANA Service?
4. Which CS object maps to the service request SRVR?