Configuring the Service with Advanced Execution Scenario

The Service with Advanced Execution scenario combines the best capabilities of SAP S/4HANA Service with the best of Maintenance Management and provides one single solution for all of a company's service needs.

It includes capabilities like:

• Using a maintenance service item as an accounting object within the universal journal (in SAP S/4HANA Finance)
• Service contracts and price agreements
• Service Order Quotations
• Planning and execution based on task lists
• Preventive maintenance using single cycle, performance-based and strategy-based plans
• Corrective maintenance based on standardized services supported with price master data or customized services requiring detailed planning
• Billing based on either fixed price or on resources consumed during service execution
• Real-time revenue recognition based on an event-based recognition method for resource-related billing

Within SAP Best Practices, the following solution processes are available for the maintenance service scenario:

• 6AU: Corrective Service with Advanced Execution
• 6F1: Preventive Service with Advanced Execution

To be able to utilize the Service with Advanced Execution scenario, you need to configure the following:

• In Customizing, navigate to: SAP Customizing Implementation Guide→Service→Transactions→Settings for Service Transactions→Integration→Enable Item-Based Accounting for Service Management.

  With this setting, you activate service accounting based on a dedicated cost object for service transactions. In this type of accounting, service order items or service contract items are recognized as account assignment objects to which costs and revenues are posted.

  Note

  Be aware that when this switch is enabled, it may not be possible to reverse this without financial consequences.

• In Customizing, navigate to: SAP Customizing Implementation Guide→Service→Transactions→Settings for Service Transactions→Integration→Plant Maintenance Integration→Map Order Types.

  Here, you map the transaction type and item category used in a maintenance service to a maintenance order type. This mapping is used to determine a valid maintenance order type for a maintenance service order item or maintenance service quotation item along with an item category to enable creation of a maintenance order. This mapping can also be used to determine a valid transaction type and an item category for a maintenance order type that has default mapping enabled to allow for the creation of a maintenance service order.

  Note

  If you used the Service with Advanced Execution scenario in releases older that SAP S/4HANA 2023, and you now upgrade to a 2023 or later system, you need to consider the following SAP Note (number 3433802): https://me.sap.com/notes/0003433802.

  A default rejection reason for a maintenance service order is provided when the corresponding maintenance order is set to Do not execute. You can also maintain a text ID that enables a long text sync between a maintenance service order and a maintenance order.

  Execute the following steps:

  1. Choose New Entries.
  2. Enter a transaction type along with an item category and map it to a maintenance order type.
  3.  A rejection reason is automatically entered. This rejection reason can be changed if needed.
  4. Enable default mapping as needed.
  5.  Select a text ID to enable a long text sync between a maintenance service order and its maintenance order.

  An example (as also set up in the training system used for this course):

  You can map the transaction type MSO1 and the item category MSI1 of a maintenance service order to the maintenance order type PMSV (or PM01, PM02, PM03, and so on). Rejection reason 70 (Rejected by Customer) is entered. Select 0002 (Item Text) as the text ID to allow for a text sync between a maintenance service order and its maintenance order. Set the Default flag for this entry.

  Similarly, you can map the transaction type MSQ1 and the item category MSQ1 of a maintenance service quotation to the maintenance order type PMSV (or PM01, PM02, PM03, and so on). You can do so again with rejection reason 70 (Rejected by Customer) and text ID 0002 (Item Text).

  Note

  The following maintenance order types cannot be used: compatible unit order, refurbishment order, service order, investment order, and revenue enabled order.

• In Customizing, navigate to: SAP Customizing Implementation Guide→Service→Transactions→Settings for Service Transactions→Integration→Plant Maintenance Integration→Map Priorities.

  Here, you need to map the priorities of the maintenance service order and its corresponding maintenance order. For a priority type (like PM), you map the individual plant maintenance priorities (like 1 (Very high)) to a corresponding service priority (like 1 (Very high)).

Ad hoc billing is a structured method of billing that doesn’t conform to periodic or milestone billing plan rules, but instead enables you to define billing values and dates freely.

You can use an ad hoc billing plan to define the dates on which billing is to occur and the value that is to be billed. For each billing date, the system generates one billing request line. In addition, you can optionally specify the settlement period that an individual billing request line covers.

One feature that is available with ad hoc billing for the Service with Advanced Execution scenario, is called Billing of Remaining Net Value. This feature enables the system to automatically generate a billing request line with all the remaining net value of the execution order item. The billing date of this billing request line is set to the current date by default.

The following are required configuration settings for the use of ad hoc billing:

• Configure a billing plan type for ad hoc billing. In Customizing, navigate to: SAP Customizing Implementation Guide→Service→Transactions→Basic Settings→Billing Plan→Define Billing Plan Types. For the billing plan type you want to use, for the field BilPlanUse, choose the option Ad hoc Billing.
• Assign your billing plan type for ad hoc billing to the item category for which you want to use ad hoc billing. In Customizing, navigate to: SAP Customizing Implementation Guide→Service→Transactions→Basic Settings→Billing Plan→Assign Billing Plan Type to Item Category. The predefined Customizing settings include transaction type SRVO and item category MSI1.
• Maintain the billing relevance for the execution order item as Billing via Billing Plan After Release (see screenshot below).

The billing relevance Billing via Billing Plan After Release can be maintained in the details of the execution order item on the tab Billing.

You can use the Advance Shipment functionality for an execution order item, or rather the plant maintenance (PM) order that is created for it, as of release 2023 of SAP S/4HANA. This is also known as the scenario called Advance Shipment Using Billable Maintenance Order.

How to use this scenario is described in the test script of solution process 6AU (Corrective Service with Advanced Execution).

You can use Distributed Execution to create multiple billable maintenance orders for an execution order item. Distributed Execution allows you to break down the execution of a service requirement into multiple smaller parts. By creating multiple billable maintenance orders for the same execution order item, you can plan and execute each part of the service separately.

There is no standard item category delivered by SAP for the Distributed Execution scenario: you have to create one yourself. In the training system, this is item category ZDE1 (DistributedExecution).

When maintaining an execution order item in a service order, you can manually select the item category DistributedExecution (in the training system) and then release the item. Afterward, you can use the generated maintenance order to create new maintenance orders (via copy), or to create follow-on orders from the initial maintenance order.

An example of this scenario is a piece of equipment that requires a service due to maintenance or breakdown. If the equipment can be broken down into separate components that can be serviced independently by different teams and at different times, you can create a billable maintenance order for each component.

You can also create multiple billable maintenance orders for a scenario where you want to separate each aspect of the service using a separate order. For example, a maintenance order for inspection, another one for service execution, a separate order for clean-up and testing and so on.

• The Service with Advanced Execution scenario combines the best capabilities of SAP S/4HANA Service with the best of Maintenance Management and provides one single solution for all of a company's service needs.
• To be able to utilize the Service with Advanced Execution scenario, you need to configure the following: enable item-based accounting for Service Management, map the transaction type and item category used in a maintenance service to a maintenance order type, map the priorities of the maintenance service order (and its maintenance order) to a corresponding service priority.
• Ad hoc billing (that is a structured method of billing that doesn’t conform to periodic or milestone billing plan rules, but instead enables you to define billing values and dates freely) is also available for/in a Service with Advanced Execution scenario.
• You can use the Advance Shipment functionality for an execution order item, or rather the plant maintenance (PM) order that is created for it. This is also known as the scenario called Advance Shipment Using Billable Maintenance Order.
• You can use Distributed Execution to create multiple billable maintenance orders for an execution order item.