Lesson 1 of 6
CS in SAP S/4HANA: the 2030 clock
10 min
Listen to this lesson
Many ECC customers run their service business on Customer Service (CS), the ECC component built on Plant Maintenance objects: service notifications, service orders, service contracts in SD, and resource-related billing. A brownfield conversion carries CS into SAP S/4HANA, and it keeps working. That creates a comfortable illusion. CS is part of the SAP S/4HANA compatibility scope: functions that may be used for a limited time, after which the right to use them ends, not just maintenance. SAP's successor is SAP S/4HANA Service, with its own objects and processes.
The dates, precisely
For systems run under a cloud subscription such as RISE with SAP, use rights for all compatibility packs run longer than on-premise (check SAP Note 2269324 for the current date). For on-premise licenses, most compatibility items had to stop by May 31, 2026, but selected Customer Service items, together with LE-TRA and PP-PI items, also run to the end of 2030. SAP provides a usage check (SAP Note 2399707) to find which compatibility items a system actually uses. Two open points deserve a direct question to SAP: exactly which CS items in your system are covered, and what read access to historical CS documents will be possible after the end date; community discussions show that the latter is not obvious from the notes.
| Topic | Classic CS (compatibility scope) | SAP S/4HANA Service |
|---|---|---|
| Technical base | Plant Maintenance orders and notifications, SD contracts | Business transactions (the "one order" model) with transaction types and item categories |
| Main documents | Service notification, service order (for example order types SM01/SM02), SD service contract (WV) | Service request, service order quotation, service order, service confirmation, service contract |
| Billing | Resource-related billing with DIP profile (DP90) | Billing document requests from confirmations and contracts, then billing documents |
| User interface | SAP GUI transactions (IW51, IW31, VA41) | SAP Fiori apps such as Manage Service Orders |
| Future | Use rights end; no new development | Strategic; new functions such as advanced execution and in-house service |
Contoso's service business
Contoso's Detroit plant repairs and overhauls alternators for fleet customers. In ECC, this runs on CS: Great Lakes Fleet Services reports a failing unit, a service notification is created, a service order plans the repair, technicians confirm their time and parts, and resource-related billing invoices the customer. Fleet maintenance contracts with Great Lakes are SD service contracts. The conversion carried all of this into SAP S/4HANA unchanged, and because Contoso runs on RISE with SAP, the use rights last at least until the end of 2030 (check SAP Note 2269324 for the current date). The service manager asks the obvious question: why move before then?
- Four years shrink fast: a service redesign, data migration and two release cycles of testing take 12 to 18 months.
- New functions arrive only in SAP S/4HANA Service; CS gets none.
- The rest of the order-to-cash team already works in Fiori apps; service is the odd one out.
- A move after 2029 would compete with every other customer facing the same deadline for partners and SAP support.
Each box hides real work. The design step decides, for every CS process, whether it becomes a standard service order, an in-house service, advanced execution or a contract, and which apps people use. The migration step decides what moves: usually master data, reference objects and active contracts, with open orders finished in CS. The test cycles need production-like data, which is why mock loads come before them. And the last step, retiring CS, needs its own decision about history.
- Does the system use CS compatibility items today?Yes → run the usage check (SAP Note 2399707) and list the items · No → no CS migration needed
- Is the system on-premise or under a cloud subscription?Cloud subscription → longer for all packs (check SAP Note 2269324 for the current date) · On-premise → check which CS items run to 2030
- Are CS processes critical to revenue?Yes → plan the move as a project with its own test cycles · No → consider retiring the process
- Do processes need functions that only S/4HANA Service has?Yes → earlier move · No → plan by capacity, well before 2030
| Contoso CS object | Volume (illustrative) | Note |
|---|---|---|
| Service notifications | About 4,000 per year | Mostly from three fleet customers |
| Service orders | About 3,200 per year | Repair at Detroit and some field work at depots |
| Service contracts | 45 active | Great Lakes holds 30, including its Grand Rapids and Flint depots |
| Resource-related billing | All time-and-material orders | DIP profile for labor, parts and travel |
Contoso's CS footprint, the starting point for scoping the move.
What goes wrong in testing
- Treating the move as a technical upgrade. S/4HANA Service uses different documents, so test cases written for CS do not carry over; they must be redesigned.
- Forgetting history. Warranty and repeat-repair checks read old service orders. Test where users will find CS history after the move.
- No usage check. Teams test what they think is used; the usage check shows what the system really uses.
What would you do?
Grace's PMO proposes to leave CS untouched until 2029 "because RISE gives us until 2030." The service manager is not convinced. What is the best recommendation?
- CS is compatibility scope: use rights end, not just maintenance.
- Under a cloud subscription such as RISE, use rights for all packs run longer (check SAP Note 2269324 for the current date); on-premise, selected CS items run to 2030.
- SAP S/4HANA Service is the successor, built on business transactions and Fiori apps.
- Plan the move well before 2030; run the usage check (SAP Note 2399707) first.
Check your understanding · not graded
Lesson check
1. What ends when compatibility scope use rights for CS expire?
2. How long may a RISE with SAP customer use CS compatibility items?
3. Which SAP Note provides the usage check for compatibility items?
4. Why can CS test cases not simply be reused for SAP S/4HANA Service?