Introduction
The following features are available for in-house service since release 2025 FPS1:
- Intercompany logistics for in-house service objects
- The management of multiple serial numbers and pieces of equipment per in-house service object
- The restructuring of in-house service objects via Split and Merge
Intercompany Logistics for In-House Service Objects
Note
Intercompany Logistics for In-House Service Objects: Scenario 1
Starting situation: The in-house service document exists in the company code of the selling company. The user selects one or many in-house service objects of this in-house service and initiates a movement to a plant of another company code.
The system detects that there is no in-house service document available in the executing company which is already referring to the in-house service of the selling company. Therefore, a new one is created, considering only the in-house service objects that have been moved. There is no impact on service orders that are linked to the in-house service object of the selling company.
In-house service documents do exist now in the selling company and also in the executing company. Next, the user assigns one or multiple in-house service objects to a new intercompany service item of the service order of the selling company and releases it.
The system detects that there is already an in-house service document available in the executing company which is already referring to the related in-house service of the selling company. Therefore, the created intercompany service order is implicitly linked to the in-house service of the executing company.
When you launch the transfer of service objects to a service center within the same organization but that belongs to a different company, the system creates an intercompany in-house service in addition to the already existing in-house service.
After its creation, the linked intercompany in-house service is visualized in the Process Flow (In-House Service) of the Manage In-House Service Objects app.
Intercompany Logistics for In-House Service Objects: Scenario 2
Starting situation: an in-house service document exists in the selling company. The user assigns one or multiple in-house service objects to a new intercompany service item of the service order of the selling company and releases it.
The system detects that there is no in-house service document available in the executing company which is already referring to the relevant in-house service of the selling company. The in-house service objects are taken over to the intercompany order. Therefore, a new in-house service is created implicitly in addition to the intercompany service order, considering only the in-house service objects that have been assigned to the intercompany service item.
You can launch intercompany processes for in-house service objects (service object) in service orders in the app Manage Service Orders.
To launch the intercompany process for a service object in a service order that is not yet released, first add a service item and choose one of the available intercompany item categories (step 1 in the figure). Then, add an existing service object or insert a piece of equipment, a serialized or non-serialized product as a service object to the intercompany service item (step 2 in the figure). Next, enter the receiving sales organization in the intercompany service item (step 3 in the figure). This organization represents the performing service center. When you release the service order (step 4 in the figure), the system creates an intercompany service order and an intercompany in-house service to process the service object within the executing company.
Mapping Multiple Serial Numbers and Pieces of Equipment to a Service Object
Note
Note
The Serial Number and Equipment columns show links with the number of assigned entries. Selecting a link opens the list of serial numbers or equipment IDs.
All assigned serial numbers and equipment IDs are listed in the details of the service object. Each entry represents one actual item assigned to the service object.
Additional serial numbers or equipment IDs can be added using the Add action while the service object is open. The number of entries matches the service object quantity.
Service objects can be found using any of the assigned serial numbers or equipment IDs.
An in-house service contains fewer service objects, while users can still work with actual serial numbers or equipment IDs in the details.
The number of serial numbers and equipment IDs in the details cannot exceed the quantities maintained for the service object. Also: the quantity cannot be reduced below the assigned number of serial numbers and equipment IDs. Duplicate numbers and numbers of another product are not accepted.
Restructuring In-House Service Objects by Split and Merge: Introduction
During a service process, the way service objects need to be handled may change. Objects recorded together may require separate handling, while independent objects may need to be handled together.
Split and Merge allows the restructuring of service objects directly from within an ongoing process, instead of cancelling and recreating documents.
The system creates successor service objects which are used for continued processing. The original service objects remain in the history and become obsolete.
Split Service Object
This functionality lets you create multiple successor service objects from one original service object. The user assigns the content of the original service object to the new service objects:
- For non-serialized products, the user defines the quantities for the successor service objects. The full quantity must be assigned.
- For serialized products or pieces of equipment, each serial number or equipment ID is explicitly assigned to a successor service object.
The original service object becomes obsolete.
Merge Service Object
This functionality lets you merge multiple compatible service objects into one successor service object:
- For non-serialized products, quantities are combined in the successor service object.
- For serialized products or equipment, serial numbers and equipment IDs are combined in the successor service object.
Service objects with non-serialized products cannot be merged with service objects containing serialized products or pieces of equipment.
The original service objects become obsolete.
Further processing is performed only for the successor service objects: New follow-up activities are created only for the successor service objects.
Existing documents remain assigned to the original service objects and describe the previous/original service structure.
Obsolete service objects remain visible in the app Manage Service Objects but are not shown in the app Manage In-House Service. This allows the repair structure to be restructured during processing while keeping the document flow clear and uninterrupted.
Summary
- Since release 2025 FPS1, an in-house service can be processed in service centers of different company codes. In the process, a so-called intercompany in-house service is created in the target company code and linked with the original in-house service. Two scenario's are available:
- In the Manage In-House Services (F4025) and Manage In-House Service Objects (F7695) apps, you can launch the transfer of service objects to service centers in a different company code.
- You can launch intercompany processes for in-house service objects (service object) in service orders in the Manage Service Orders app.
- Since release 2025 FPS1, one service object in an in-house service can contain multiple serial numbers or equipment IDs. There is no need anymore to create a separate service object per item.
- Split and Merge allows the restructuring of service objects directly from within an ongoing process, instead of cancelling and recreating documents. The system creates successor service objects which are used for continued processing. The original service objects remain in the history and become obsolete.