Friday 15 March 2024

Effectively adopting Recurring Service process from S/4 HANA Service Management into your business

Regular maintenance aids in maintaining a customer's assets at their best performance levels while reducing the likelihood of breakdowns and the costs associated with repairs.

Our preventive maintenance solution, designed to sustain customer assets, facilitates consistent production by mitigating unexpected breakdowns. This solution creates and executes orders at specified intervals/usage, drastically improving asset production efficiency and minimizing breakdowns. Notably, this solution also reduces maintenance costs and contributes to recurring service revenues for customers. It adeptly manages both commercial aspects through service orders, as per the service contract, and technical aspects through execution orders.

There are different types of Maintenance Plans, namely: Single cycle plans based on time or performance, strategy plans, or multiple counter maintenance plans that are implemented on need basis . Once you create a maintenance plan, you can schedule the plan to generate call objects when the system is due for maintenance.

The normal recurring service is the process that is more straightforward and is suitable for simple servicing scenarios and is inclusive of commercial aspects in the same document. The Service with Advanced Execution is a process that combines commercial aspects of service with maintenance management for tasks that require detailed planning and execution. Maintenance task lists help in planning and organizing maintenance work efficiently, saving time during scheduling. They're especially useful for frequent tasks requiring the same materials, and for recurring and one-time tasks. The service part handles the customer's needs, pricing, satisfaction, and profit, while the maintenance management part focuses on planning, understanding equipment technicalities, and carrying out the service. The process creates Execution Order Items, which can be part of a service order or a maintenance plan. These items generate a maintenance order, enabling the service's planning and execution.

The information below explains how to differentiate between the two.

Effectively adopting Recurring Service process from S/4 HANA Service Management into your business
Image 1 : Apps related to Recurring Service

Effectively adopting Recurring Service process from S/4 HANA Service Management into your business
Image 2: Recurring Service with Advanced Execution

S.I No  Category Recurring Service

Recurring Service with Advanced Execution 

1 Scenarios Classic Recurring Service Preventive Maintenance

ABAP Call Type Technical code

Maintenance Service Call Type '5'  Maintenance Service Call Type '6' 
3 Types of MPLAN supported  Single Cycle (Time or Performance), Multiple-Counter  Single Cycle (Time or Performance), Multiple-Counter, Strategy Time Based. Strategy Performance Based 
4 Preceding Document  Service Template  Service Contract
5 Mandatory Inputs for Scheduling  Service Template
Either Technical Object OR Service Contract
Call Object Type (Service Order or Service Quotation) 
Service Contract
Work Centre
Planning Plant
Call Object Type (Service Order) 
6 Output  Service Order or Service Quotation 

Service Order with Execution Order


7 Source of Service Transaction Items  Service Order Template  Service Contract Items
8 Task List  Table OISD (Service Product with Task List)  Directly from Maintenance Item, else from table OISD. 
9 Supported Service Document Types  Service Order and Service Quotation

Service Order

10 Applications support and GUI support 

Supports on Fiori Apps

GUI (TCODES: IP01/02/03 and IP10, etc) and Fiori Apps

The ABAP code flow for simple recurring service is as follows:

PERFORM service_order_create ->
PERFORM service_order_post_mhio (calling CRM_ORDER_SAVE).

The ABAP code flow for recurring service with execution order item ( Advanced Execution ) is as follows:

FAELLIGE_MHIS_ORDER (FM) ->PERFORM create_srvo_pmo->
SERVICE ORDER CREATION: PERFORM service_order_create ->
CRM_ORDER_MAINTAIN->(call back to PERFORM create_srvo_pmo )->
PERFORM order_create_f13 -> (call back to FAELLIGE_MHIS_ORDER)->
PERFORM update_srvo_pmo->
PERFORM order_update_f13->( call back to PERFORM update_srvo_pmo )->
(Logic for Creation of the DOCFLOW between Plant Maintenance Order and Service Order and vice versa).

In conclusion, the distinction between normal Recurring service and Service with Advanced Execution lies in their complexity and scope. The decision to select one over the other depends on the specific needs and requirements of the business.

No comments:

Post a Comment