Identifying New Features of In-House Service

Objective

After completing this lesson, you will be able to identify new features of in-house service processing in release 2025

New Features of In-House Service

Introduction

Two photos of workers busy with in-house service activities (undetermined what they actually do).

In this unit, you learn ...

  • … that in-house repair has been renamed to in-house service.
  • … how Joule can support processing in-house services.
  • … about additional support for retroactive quantity updates.
  • … that an intracompany transfer for in-house service objects is now supported.
  • … that enhanced shipping of in-house service objects is now supported.
  • … about the extensibility of the Manage In-House Service Objects app.

In-House Repair Renamed to In-House Service

Screenshot of the SAP Fiori launchpad with the app Manage In-House Services highlighted.

The in-house repair solution capability has been renamed to in-house service. This change affects the names of all objects containing the terms in-house repair and repair.

The reason for this change is that the solution capability can be used not only for processing repairs, but also for processing different types of product-related services. These services can be carried out at in-house service centers. The term in-house service better covers this scope.

A table is shown with an overview of all changed object names: Scope item 7GB / scenario was called Service - In-House Repair and is now called In-House Service. Service transaction type IHRP was called In-House Repair and is now called In-House Service. Item category IHRI was called In-House Repair Item / Repair Object and is now called In-House Service Object. Note: This is now abbreviated with Service Object. App F4025 was called Manage In-House Repairs and is now called Manage In-House Services. App F7695 was called Manage Repair Objects and is now called Manage In-House Service Objects. API API_INHOUSEREPAIR was called In-House Repair and is now called In-House Service. Archiving object CRMS4_REPA was called In-House Repair and is now called In-House Service.

The above slide summarizes the changed object names.

Joule: Search for In-House Service Objects and Create Follow-Up Actions

Screenshot of the search for in-house service objects and the creation of a follow-up action in Joule.

Joule enables you to search for in-house service objects. From the search results you can:

  • Display details of a service object.
  • Open a service object in the Manage In-House Service Objects app.
  • Perform follow-up actions for a service object.
  • Open a prefiltered list of service objects in the Manage In-House Service Objects app, with the search criteria that you have already applied in Joule.

For more information search for the Joule capability Processing In-House Services in the SAP Help Portal.

Note

The prerequisite for using this Joule capability is SAP S/4HANA Cloud Private Edition 2023 FPS03 (or higher).
Slide showing three use cases (UC) for a search in in‑house service. The left panel, showing use case 1 and titled UC 1: Search for In‑House Service Objects discusses a search for in‑house service objects, narrowing down your results, and accessing details or triggering next steps through a conversational approach. The top‑right panel, showing use case 2 and titled UC 2: Display Details displays two example cards for an in‑house service and an in‑house service object. The third panel, showing use case 3 and titled UC 3: Perform Follow‑Up Actions shows the creation of follow‑up transactions with guided access on how to do this. Examples are Create Returns Order, Create Service Quotation, Create Service Order, and Set Service Object to Completed.

The slide above shows three use cases (UC) for a search in in‑house service.

The left panel, showing use case 1 and titled UC 1: Search for In‑House Service Objects discusses a search for in‑house service objects, narrowing down your results, and accessing details or triggering next steps through a conversational approach.

The top‑right panel, showing use case 2 and titled UC 2: Display Details displays two example cards for an in‑house service and an in‑house service object.

The third panel, showing use case 3 and titled UC 3: Perform Follow‑Up Actions shows the creation of follow‑up transactions with guided access on how to do this. Examples are Create Returns Order, Create Service Quotation, Create Service Order, and Set Service Object to Completed.

Note

See the following video to see examples of a few use cases where Joule is used to search for in-house service objects and create follow-up actions:
Screenshots shown of the Joule user interface for 4 consecutive steps in a process workflow for triggering a follow-up action for an in-house service object. Step 1: a user prompt can trigger a follow-up action. Step 2: Joule suggests available follow-up options. Step 3: a follow-up action is chosen (Create Returns Order). Step 4: a results screen is shown indicating that the action has been performed.

In this use case, you can see four consecutive steps in a process workflow for triggering a follow-up action for an in-house service object. Step 1: a user prompt can trigger a follow-up action. Step 2: Joule suggests available follow-up options. Step 3: a follow-up action is chosen (Create Returns Order). Step 4: a results screen is shown indicating that the action has been performed.

Retroactive Quantity Updates

Screenshot of a returns order in which an order quantity change has been maintained (that is: a retrospective quantity update). And a second screenshot (of the screen Manage In-House Service Details) showing that in the details of the corresponding in-house service object, the quantity has now also been updated.

Since release 2025 FPS0, you can sync the quantity of in-house service objects actually delivered using returns orders with the quantity of these in-house service objects in in-house service processing. In returns orders, you can (retroactively) change the quantity of the in-house service object(s) that are returned. You do this if it turns out that a higher or lower number of in-house service objects than originally announced, is returned by the customer.

This ...:

  • … helps to ensure that the quantity of the returns order item matches the quantity of the in-house service object.
  • … updates the quantity in the in-house service object whenever the quantity of the related returns order item changes.

Grouping of Subordinate Service Objects

Screenshot of the screen Manage In-House Service Details with highlighted the grouping of several subservice objects directly below their main service object.

In the app Manage In-House Services and the in-house service assignment block of the apps for managing service orders and service quotations, you can enable subservice objects by default to be listed directly below their main service objects. This gives you a better overview of the higher-level service objects and their subordinate service objects.

Within the grouping, the subordinate service objects are sorted by their service object number.

Intracompany Logistics for In-House Service Objects

Process flow showing three steps: (1) Receive from Customer then (2) Transfer to Another Plant (with the indication New in 2025 FPS0) and finally (3) Send Back to Customer. For step 1, using an inbound delivery is new in 2025 FPS0. For step 2 using an outbound delivery in the sending plant to trigger an inbound delivery in the receiving plant is new in 2025 FPS0. A note states that the transfer to another plant (step 2) is, in release 2025 FPS0, only possible for plants belonging to the same company code.

The logistics capabilities of in-house service processing have been enhanced significantly.

Screenshot of the creation of an inbound delivery to receive a service object.

When receiving service objects from customers, you can now launch the logistics process by creating an inbound delivery in the Manage In-House Services (F7695) and Manage In-House Service Objects (F4025) apps. Previously, it was only possible to launch the logistics process using the integration with customer returns.

Screenshot of the Transfer (of a service object) pop-up window on the screen Manage Service Object Details.

Once the service objects have the availability Received by Service Center, you can now transfer them to another service center at which the in-house service is to be performed. You launch this logistics process in the Manage In-House Service Objects (F7695) or Manage In-House Services (F4025) app by creating an outbound delivery and subsequently, when posting the goods issue, an inbound delivery for the receiving service center.

Note

In 2025 FPS0, a transfer is only possible to plants which are assigned to the same company code (which is called an intracompany transfer).
Screenshot of the view in Customizing called Specify Settings for Returns Orders as Follow-Up and that you can choose option Customer Stock (B).

Previously, when launching the returns process for service objects in the Manage In-House Services (F7695) and Manage In-House Service Objects (F4025) apps, the incoming service objects were posted to the sales stock (special stock indicator Orders on Hand (E)). You can now post the service objects to the special stock indicator Customer Stock (B), if you've specified this in Customizing.

Screenshot of the Create Returns Order pop-up window on the screen Manage Service Object Details.

When creating a returns order for service objects in the Manage In-House Services (F7695) and Manage In-House Service Objects (F4025) apps, you can specify the plant and the storage location to which the service object is posted.

If you do not enter a plant and a storage location, the system uses the plant and storage location that have been configured for customer returns.

Screenshot of an example of the Process Flow (Logistics) screen in the app Manage In-House Service Objects.

In release 2025, in the Manage In-House Service Objects (F4025) app, a process flow has been added which is visualizing all relevant logistics documents that are related to a specific in-house service object.

The tiles contain relevant information such as the lifecycle status and the date of the goods issue or goods receipt of the deliveries. In addition, the tiles are grouped into lanes, pointing out for which process step a certain document has been created.

Other Topics in In-House Service

Screenshot of the maintenance of an alternative shipping address (and where to trigger this) on the screen Manage In-House Service Details (of the app Manage In-House Services).

In the Manage In-House Services (F4025) and Manage In-House Service Objects (F7695) apps under Shipping, you can now change the ship-to address of the ship-to party specified in in-house services and service objects.

Screenshot showing the possibility to switch between different ship-to party addresses and where to trigger this in the app Manage In-House Service Objects.

In the Manage In-House Services (F4025) and Manage In-House Service Objects (F7695) apps under Shipping, you can now switch between different ship-to party addresses which have been maintained as master data.

Screenshot of the Add: Field extensibility option in the app Manage In-House Service Objects.

You can now extend the Manage In-House Service Objects app according to your business needs.

Extensibility allows you to ...:

  • … define custom fields with custom logic.
  • … add these fields to the filter bar, result list and details screen.

You can find more information in the help portal for SAP S/4HANA Cloud Private Edition under Product AssistanceServiceService Operations and ProcessesIn-House ServiceApps Used in In-House ServiceManage In-House Service ObjectsApp Extensibility: Manage In-House Service Objects.

In context of the app extensibility, the Odata API called API_INHOUSEREPAIR has also been enabled for extensibility.

For more information see the API business documentation for in-house service under APIs for ServiceIn-House ServiceExtensibility: In-House Service.

Summary

In release 2025:

  • In-house repair has been renamed to in-house service.
  • Joule can support processing in-house services.
  • Additional support for retroactive quantity updates is available.
  • An intracompany transfer for in-house service objects is supported.
  • Enhanced shipping of in-house service objects is supported.
  • You can extend the Manage In-House Service Objects app according to your business needs.