Lesson 3 of 6
Service orders and confirmations
10 min
Listen to this lesson
The service order is the working document of SAP S/4HANA Service. It records what the customer ordered, which services, parts and expenses are planned, who does the work and when, and how it will be billed. The confirmation records what actually happened. Billing follows the confirmation for time-and-material work, or the order for fixed-price work. This lesson walks through Contoso's most common case: a field repair for Great Lakes Fleet Services at its Flint depot.
Walkthrough: a field repair
- 1. Create the orderIn Manage Service Orders, create an order of type SRVO for sold-to 17100001, ship-to 17100007 (Flint depot), reference object: the customer's alternator equipment
- 2. Add itemsA service item (SRVP) for diagnosis and repair labor, a service part item (SRVM) for a replacement rotor kit, an expense item (SRVE) for travel
- 3. Check contract and priceThe system determines Great Lakes' service contract, which sets agreed labor rates and response terms
- 4. ReleaseSet the items to released; only released items can be confirmed
- 5. ExecuteThe technician travels, diagnoses and repairs; the part is issued from stock
- 6. ConfirmIn Manage Service Confirmations, create a confirmation (SRVC) with 3.5 hours of labor, the part used and the travel expense, then complete it
- 7. BillCompletion creates billing document requests; billing creates the invoice
Confirmations
A service confirmation records actual working time, materials and expenses. It feeds time recording, stock updates for service parts, billing and cost accounting. Confirmations can only be created for released orders and items. The confirmation itself goes through statuses: while it is in process, it can be changed or cancelled; when it is completed, its follow-on postings happen. In SAP Learning's description of the process, actual costs arise when the confirmation is completed, and actual revenue when the billing document is created.
| Confirmation item | Follow-on effect | What to check |
|---|---|---|
| Service (labor) 3.5 h | Actual cost on the order item at the technician's rate; billing quantity 3.5 h | Cost and billing quantity match the time confirmed |
| Service part (rotor kit) | Goods issue from stock; cost of the part on the item | Material document posted; stock reduced in the right plant and storage location |
| Expense (travel) | Expense cost on the item; billable if agreed | Expense billed only if the contract allows it |
| Unplanned extra part | Added in the confirmation, not in the order | Billing and cost include it; approval rules if any |
What a confirmation posts and what testers verify for each item.
From confirmation to invoice
In SAP S/4HANA, service billing uses billing document requests (BDRs) through the external billing document request function. The BDR has its own billing type; in the standard system, SAP Learning names Cust. Mgmt Service Conf. BDR (SVCB) for confirmations. BDRs appear in the billing due list of the Create Billing Documents app and can be billed alone or combined with other due items, which lets Maria's billing team invoice service and product sales together for Great Lakes if the copy control allows. That is a real improvement over separate resource-related billing runs in CS.
Service parts
Parts reach a service order in two ways. Stock parts are reserved and issued from a plant and storage location, so Contoso's warehouse picks them like any other goods issue. Non-stock parts are procured: the service part item can trigger a purchase requisition, which follows the approval rules from procurement (requisitions over $10,000 need release at Contoso). Test both, and check that the cost of a procured part ends up on the service item, not on a cost center. For field work, also test the case where the technician uses a part from van stock that was not planned in the order: the confirmation must still issue it and bill it if billable.
Fixed price or time and material
| Billing method | Billed from | Typical use at Contoso |
|---|---|---|
| Time and material | The completed confirmation: hours, parts and expenses actually used | Field repairs and diagnostics |
| Fixed price | The service order item price, regardless of actual effort | Standard overhaul packages |
| Not billable | No billing; costs stay on the item | Warranty and goodwill repairs |
What goes wrong in testing
| Symptom | Real cause | Lesson |
|---|---|---|
| Confirmation cannot be created | Order item not released | Release is a test step, not a precondition taken for granted |
| Part billed but stock unchanged | Service part item not set to post goods movements | Check the material document for every part |
| Nothing in the billing due list | Confirmation not completed, or BDR generation not run | Complete the confirmation and check the BDR |
| Travel billed under a contract that excludes it | Contract expense rule not applied | Test expenses with and without contract coverage |
Typical order and confirmation test failures.
What would you do?
In CMQ, Maria's team confirms a Great Lakes repair, but nothing appears in the billing due list the next morning. The confirmation shows status "in process". What should the tester do first?
- Service orders (SRVO) hold service, part, expense and sales items; items must be released before confirmation.
- Confirmations (SRVC) record actuals; completion creates costs and billing document requests.
- BDRs (standard billing type SVCB for confirmations) appear in the billing due list of Create Billing Documents.
- Test time and material, fixed price and non-billable cases separately.
Check your understanding · not graded
Lesson check
1. What must happen before a service confirmation can be created for an order item?
2. When do actual costs arise for confirmed service work?
3. Where do service billing document requests appear for invoicing?
4. Which billing method ignores the actual hours confirmed?