Overview on Maintenance Service
Service Processes in SAP S/4HANA 2021 OP
The following two options have been available to map service processes up to SAP S/4HANA 2021 OP:
- SAP S/4HANA Service 2021 OP
- SAP S/4HANA CS Compatibility pack 2030
SAP S/4HANA Service 2021
The design of SAP S/4HANA Service eliminates functional redundancies and data replication. It unifies CRM and S/4HANA objects, so that unified objects share the same database representation, thus require no middleware. Furthermore, it identifies functional redundancies and is optimized by using the most suitable object / engine / process.
SAP S/4HANA CS Compatibility pack 2030
In order to help customers get the highest business value from their SAP S/4HANA systems, SAP has decided to align the usage rights for Customer Service as well as for Transport and Production Planning for Process Industries with the SAP Business Suite maintenance timeline. SAP is extending the usage rights exclusively for Customer Service, Transport, and Production Planning for Process Industries until the end of 2030.
Obviously, there are two almost independent options to map service processes as of SAP S/4HANA 2021 OP. This interim stage has been optimized and harmonized as you will find out now.
Maintenance Service in SAP S/4HANA Service 2022 OP
![](/service/media/topic/bd8fec4a-99c2-4d75-91e3-409f40658b9d/S47000_23_en-US_media/S47000_23_en-US_images/Maintenance Service03.png)
Maintenance Service is a service scenario built around the integration between SAP S/4HANA Service and maintenance management. With Maintenance Service, you can use asset management capabilities like maintenance planning and execution, along with commercial aspects of service like contract management, price agreements, credit check and so on.
The maintenance service order (MSO) and maintenance order (MO) are the core business transactions used in the maintenance service process. A maintenance service order can consist of a single or multiple maintenance service items. When a maintenance service item is released, a corresponding maintenance order is created.
Information that is relevant for both service and maintenance components, for example partner, planning plant, priority, reference objects, is shared between the maintenance service order and maintenance order. This allows the user to carry over the information from service into maintenance planning and execution.
Integrated Process Flow: Maintenance Management
A maintenance service plan is used to schedule periodic maintenance service orders, thereby facilitating preventive maintenance. The maintenance service process also supports the use of task lists. That is, a sequence of individual maintenance activities that must be repeatedly performed. Technical objects are managed in the master data of the SAP system as functional locations and pieces of equipment. A functional location represents the place at which a maintenance activity is to be performed. A piece of equipment is an individual, physical object that is to be maintained as an autonomous unit.
Integrated Process Flow: SAP S/4HANA Service
Service contracts are used to determine the terms of the service. A maintenance service quotation is used to provide a cost estimate for a requested service and a maintenance service order is used to manage a service that has been agreed upon by a service provider and a recipient. A maintenance service quotation or order can have multiple maintenance items.
The maintenance order that is created when the maintenance service item is released is used to plan and execute the service. The current status of the corresponding maintenance order is displayed by the execution status field in the service order.
Integrated Process Flow: Billing
After service completion, the billing process is carried out through the Dynamic Item Processor (DIP). A debit memo request is used to generate an invoice. The entire process works on item-based accounting. In this type of accounting, service transaction items are recognized as account assignment objects to which costs and revenues are posted.