Einführung in die Serviceabwicklung in SAP S/4HANA und Lernen der zugehörigen Prozessschritte
Allgemeine Konfiguration der Serviceabwicklung kennenlernen
Konfigurieren eines Vor-Ort-Serviceprozesses
Werkstattreparatur konfigurieren
Konfigurieren von Serviceverträgen
Anhang: Verstehen der technischen Architektur und der Konfiguration der Benutzungsoberfläche

Configuring the Integration Between Service Transactions and Logistical Processing in SAP S/4HANA

Objective

After completing this lesson, you will be able to configure the integration between service transactions and logistical processing in SAP S/4HANA

Configuration of the Integration with Logistical Processing

Business Example

For service orders, there are important configuration settings present in Customizing for SAP S/4HANA Service to set up the integration with other processes within the area of logistics. Examples are the creation of reservations and the external procurement of materials and/or services. You want to learn more about these settings.

Reservations and External Procurement

Flowchart displaying the process for handling service orders. The main sequence starts with a Service Request leading to a Service Order. Two additional inputs to the Service Order are a Service Order Quotation and a Service Order Template. The Service Order then branches into three outputs: Service Confirmation, Reservation, and Purchase Requisition/External Procurement. Service Confirmation feeds into Billing Document Request, which generates a Billing Document. Reservation and Purchase Requisition/External Procurement also contribute to the Billing Document Request, forming a part of the flow leading to the Billing Document. Arrows illustrate the directional flow between the elements. Highlighted here is the following part of the process: for a service order, reservations for spare parts kept in stock can be created. And also, for externally procured parts and services, purchase requisitions can be created.

The next part of this unit introduces the configuration settings related to the creation of reservations for spare parts kept in stock, and also for externally procured spare parts and services.

Creating Reservations and Posting Material Withdrawals

In Customizing, navigate to SAP Customizing Implementation GuideServiceTransactionsSettings for Service TransactionsIntegrationLogistics IntegrationDescription of Logistics Integration for a description of some of the settings presented here.

Note

The following video discusses the concept of a logistics scenario, which is assigned to an item category of a service order:

In a standard SAP S/4HANA system, item category SRVM Service Part is available for such a spare part for a service (or repair) order and item category SVCM Service Part for that spare part for a service (or repair) confirmation.

If a reservation is being created, the system also needs to determine from which plant and storage location combination the spare part is reserved. This can be configured in Customizing, using SAP Customizing Implementation GuideServiceMaster DataOrganizational ManagementCross-Application Assignment of Organizational UnitsAssign Plant and Storage Location to Service Organizational Units.

For a combination of a service organization, a service team and a service employee, the relevant plant and storage location combination can be defined. An asterisk (*) can be used to indicate that something is valid for all entries (for example, for the Service Team field or Service Employee field).

A warehouse scene with a person operating a forklift, lifting supplies on pallets from high shelves. Another person stands next to the forklift, holding a tablet, possibly checking inventory. To the right of the image is a flowchart diagram labeled Service Confirmation (transaction type SRVC). Below are arrows and boxes indicating steps in the process: Service Part (Item Category SVCM), connected to (Service Organization + Responsible Service Org. Unit), and further down Logistics Scenario, leading to P Plant / Storage Location. This indicates that a logistics scenario can also be assigned to a transaction type of a service confirmation and the item category used (in combination with a service organization and responsible service organizational unit).

For service (and repair) confirmations, the way that material withdrawals are posted needs to be configured. These withdrawals can be posted out of plant/storage location normal stock or they can be posted out of (technician or customer) consignment stock. Again, the logistics scenario indicates what scenario is required. It is assigned to the transaction type of the service confirmation and the item category (in combination with a service organization and responsible service organizational unit).

This is configured in Customizing using SAP Customizing Implementation GuideIntegration with Other SAP ComponentsCustomer Relationship ManagementSettings for Service ProcessingLogistics IntegrationCreate and Change Logistics Scenario for Material Withdrawal.

The entry for transaction type SRVC (Service Confirmation) in combination with item category SVCM (and all service organizations and service organizational units) indicates that logistics scenario P Plant / Storage Location needs to be used. This means that the material withdrawal is posted out of plant/storage location stock, instead of out of customer or technician (that is, user) consignment stock (for which logistics scenarios are also available).

Procuring Service Parts Externally

When planning service orders in SAP S/4HANA Service, certain spare or service parts (or services themselves: see later on) might need to be procured externally before the service order can be executed. For the external procurement of these service parts, the Logistics Scenario for the Procurement of Materials and Services needs to be defined as Purchase Requisition. Using this setting, the automatic creation of a purchase requisition for a service part within a service order can be achieved.

Note

Instead of a purchase requisition, it is also possible to directly create a purchase order from a service order item. This depends on the configuration of the scenario.

The image shows a flowchart detailing the process from service order to billing document, focusing on procurement of spare parts. It starts with a blue box labeled Service Order, leading to three sub-categories: Purchase Requisition Item, Service Item, and an ellipsis. From Purchase Requisition Item, an arrow labeled Release moves to a gray box named Purchase Requisition (NB), followed by an arrow termed Convert leading to another gray box, Purchase Order (NB). From Purchase Order (NB), an arrow points to a teal box titled Goods Receipt for Purchase Order. Another pathway from Service Order leads directly to Item Category: SPRM (PurchReq ServicePart), and onward to a teal box Service Confirmation. From here, an arrow labeled Procured Spare Part moves to a teal box Procured Spare Part, linking to Goods Receipt for Purchase Order. An arrow labeled Release for Billing connects Goods Receipt for Purchase Order to a blue box named Billing Document. The process concludes with Billing Document, represented as a hierarchy of boxes with ellipses. A caption below reads: The price of the procured spare part is included in the billing document.

The process discussed here could be described as follows:

  1. A service order is created within its item list a service part. This service part has an item category that has been set up as relevant for the creation of a purchase requisition.
  2. The service order is released. Releasing the service order triggers the creation of the purchase requisition.
  3. A purchasing specialist processes the purchase requisition by creating a purchase order for it. After delivery by the supplier, a goods receipt for the purchase order is posted.
  4. After the procured service part has been received, a technician confirms its use by creating a service confirmation as a follow-up to the service order.
  5. After releasing the service confirmation for billing, a billing clerk creates a billing document, which includes the price for the procured service part.

Since release 2021 of SAP S/4HANA, when using a scenario where a service part is procured externally using a purchase requisition, standard item category SPRM (PurchReq ServicePart) is available for use in a service order. The standard item category SPRC (PurchReq ServicePart) is available for use in a service confirmation.

Note

In older releases of SAP S/4HANA (like 2020), these two item categories were not available. For information purposes, especially for SAP customers who might still be using an older version of SAP S/4HANA, the paragraph below has been added to this course, explaining the configuration behind the two mentioned item categories (SPRM and SPRC). These steps need to be replicated if you want to define the scenario discussed above in an older SAP S/4HANA system (such as release 2020).

This scenario and the two mentioned item categories (SPRM and SPRC) have been defined in the system, using the following configuration steps:

  1. The document type and the pricing procedure that need to be used for the purchase requisition are identified in Customizing.

    Navigate to SAP Customizing Implementation GuideIntegration with Other SAP ComponentsCustomer Relationship ManagementSettings for Service ProcessingLogistics IntegrationSet Purchasing Document Types for CRM Logistics Integration.

    Here, both the document type for the purchase requisition and the pricing procedure to be used in purchasing are selected. Condition type PMP0 (Manual Gross Price) (see step 3) is present in this pricing procedure.

  2. It is required to configure which texts from the service order or in-house repair order are copied to which texts in the SAP S/4HANA purchasing documents (purchase requisition and/or purchase order).

    An example: for text object CRM_ORDERI, text ID 0002 is copied into text object EBAN (Purchase requisition texts) as text ID B01 (Item text).

    In Customizing, navigate to SAP Customizing Implementation GuideIntegration with Other SAP ComponentsCustomer Relationship ManagementSettings for Service ProcessingLogistics IntegrationCopying Rules for Texts When Creating Purchasing Documents.

  3. The item category for the externally procured service part for the service order and for the externally procured service part for the service confirmation were defined: SPRM (PurchReq ServicePart) for the service order and SPRC (PurchReq ServicePart) for the service confirmation. Condition type PMP0 (Manual Gross Price) (see step 1) was maintained in the configuration of both item categories. Item category SPRM (PurchReq ServicePart) for the service order has also been marked as relevant for confirmation and relevant for costing. The item category used for the externally procured part in a service confirmation (SPRC (PurchReq ServicePart)) has also been configured as relevant for costing.

    In Customizing, navigate to: SAP Customizing Implementation GuideServiceTransactionsBasic SettingsDefine Item Categories.

  4. Item category determination for both item categories has also been defined for all required combinations of fields.

    In Customizing, navigate to SAP Customizing Implementation GuideServiceTransactionsBasic SettingsDefine Item Category Determination.

  5. Copying control has been set up for the item category SPRM (PurchReq ServicePart), which is used in the service order, similar to the settings for item category SRVM (Service Part).

    In Customizing, navigate to SAP Customizing Implementation GuideServiceTransactionsBasic SettingsCopying Control for Business TransactionsDefine Copying Control for Item Categories.

  6. Item category SPRM (PurchReq ServicePart) for the service order has been configured to lead to item category SPRC (PurchReq ServicePart) being determined in the service confirmation.

    In Customizing, navigate to SAP Customizing Implementation GuideServiceTransactionsBasic SettingsCopying Control for Business TransactionsDefine Item Category Determination when Copying.

  7. The transaction type and item category for which the purchase requisition scenario (that is, an externally procured service part) is valid must also be defined. For item category SPRM (PurchReq ServicePart) this has been set to PREQ Purchase Requisition.

    In Customizing, navigate to SAP Customizing Implementation GuideServiceTransactionsSettings for Service TransactionsIntegrationLogistics IntegrationDefine Logistics Scenario for the Procurement of Materials and Services.

  8. The item category for the service confirmation (SPRC) has also been mapped to an SAP S/4HANA Sales item category to be used in the background when creating a billing document request (BDR). A BDR is created when the confirmation is released for billing. For example, for transaction type SRVC (Service Confirmation), item category SPRC (PurchReq ServicePart) has been mapped to SAP S/4HANA Sales item category CS01 (Service Item eBDR).

    In Customizing, navigate to SAP Customizing Implementation GuideServiceBasic FunctionsBillingAssign Service Transaction Types to Billing Document Request Types.

Note

For SAP S/4HANA release 2020, SAP Note 2976374 (Goods Movement for Spare Part Items) might also need to be implemented in the system where this scenario is set up.

Procuring Services Externally Using the Lean Services Functionality in Release 2023

Note

The following video discusses the process of a service order containing a lean service:

In releases older than release 2023 of SAP S/4HANA, external procurement for a service order was only supported for standard service parts, not for services created with material type SERV. These services use the so-called lean services functionality of SAP S/4HANA. Procuring these services externally required the use of a customer enhancement. With release 2023 this changed.

Note

Currently (SAP S/4HANA 2023 FPS00) it is required to maintain a manual price in the item details. In a future feature pack stack (FPS) or release, it is intended that the system automatically determines the correct purchasing info record or purchasing contract. This is done using a special pricing routine 31 that is assigned to condition type PCO4 in the column Alt. Cndn Base Value in the standard (sales) pricing procedure for service orders (S17J01).

 For the price that needs to be entered manually, in the standard configuration, you can use pricing condition PMP0 for service orders and PCO4 (charged cost) for service quotations.

Note

For specific issues during the creation of the purchase requisition or purchase order with external services management check the following SAP Note:3085016.

Advance Shipment

The functionality Advance Shipment enables the shipment of service parts to a service technician or to a customer before the actual repair starts. An advance shipment is typically used when service parts need to be shipped to a customer location in advance, because the service part is too bulky to be carried in the van of a technician. Based on the goods receipt or the planned delivery date at the customer location, the technician can then perform a repair using the service part that was shipped in advance.

Shipment of service parts is done by using a service order with a sales order. The use of sales orders allows customer consignment stock to be created. As a result of this, parts that are actually required for the repair can be invoiced after the consumption of these parts has been posted.

Note

Advance Shipment is available as of release SAP S/4HANA 2022, feature pack stack 1 (FPS1). What exact functionality is available, depends on the release of your SAP S/4HANA system and the feature pack enabled for that release. In release 2023 FPS0, when item-based accounting is enabled, only stock material that triggers a reservation can be used. This means: the behavior of item category SRVV (see below for more details). The behavior of item category SRVU is available since SAP S/4HANA 2023 FPS1 (see below for more details). SAP Note 3330419 - This SAP Note informs you about release information and restrictions related to SAP S/4HANA Service details exactly what the various restrictions are, in terms of available functionality, for the various feature pack stacks of SAP S/4HANA 2023.
The two possible scenarios for using the Advance Shipment functionality are shown. Scenario 1 begins with a Service Order in a blue box connected by a black arrow to a Sales Order in a blue box. The Sales Order leads via a black arrow to Outbound Delivery in a light blue box, which then connects to Goods Issue to Customer Consignment in a light blue box. This leads to an optional Proforma Invoice in a dark blue box. Additionally, from Service Order, a black arrow leads to Reservation in a green box, which connects back to Outbound Delivery with a dashed line, and Goods Issue to Customer Consignment connects back to Reservation with a dashed line. Scenario 2 starts similarly with a Service Order leading to a Sales Order. A dashed black arrow with an asterisk connects Sales Order to Purchase Requisition in a green box. The asterisk refers to a note below, stating Goods receipt into sales order stock. The Purchase Requisition is connected by a solid black arrow to Purchase Order in a green box, then to Inbound Delivery in a green box, leading to Goods Receipt in a green box, and finally to Supplier Invoice in a green box. Dashed lines draw connections from Goods Receipt back to Outbound Delivery, to Supplier Invoice, and forward to Sales Order while also connecting Inbound Delivery to Outbound Delivery. Goods Issue to Customer Consignment connects to optional Proforma Invoice in a blue box, while a dashed line from Proforma Invoice also leads back to Goods Receipt.

Advance Shipment distinguishes the following two scenarios:

  • The service part is already available in stock in a warehouse.
  • The service part is not yet available in stock and must be procured from a supplier.

If the service part is already available in stock in a warehouse and the service part item in the service order is released, a reservation and a sales order are automatically created. An ATP (Available-to-Promise) check can be executed from within the service parts item list of the service order.

An outbound delivery can be created from the sales order. After picking and posting of the goods issue, the service part is transferred to customer consignment stock within the plant, and the reservation is updated during the goods issue process. The reservation is set to Completed after the final goods issue. The outbound delivery and the goods movement posting are added to the transaction history of the sales order and the service order, along with the delivery status and the quantity update.

After the service technician confirms the use of the service part with a service confirmation, the final goods issue out of the customer consignment stock to the customer is posted, including the material consumption.

Note

Details of the required service part are taken from the reservation, not from the sales order or delivery. The sales order is only used as the basis for creating the delivery. It is not ATP-relevant and does not transfer requirements. So, when the delivery is created, it is not actually known whether the parts are in stock. The final check of whether the service parts are in stock is only done when the goods issue is posted.

If this process doesn't fit your business process, it is possible to change the logistics integration Customizing so that a sales order is created without a reservation. In this case, a sales order item category that transfers requirements and is ATP-relevant can be set up and used. The result of the ATP check of the sales order isn't transferred back to the service order.

If the service part is not available in stock, it can be procured via a purchase requisition or a purchase order created from the service order item. Additionally, a sales order is created and used as the basis for creating the outbound delivery.

When the goods receipt for the purchase order is posted, the service part is received into sales order stock (special stock type E), so that no other process can use the part. The confirmation control key of the purchase order item determines whether or not an inbound delivery needs to be created.

The rest of the process is identical to the processing of a service part from stock. The procurement process documents (like the purchase order) are added to the transaction history of the service order, along with the delivery status and quantity update.

Note

If you need to create a purchase requisition from the created sales order and not directly from the service order, you can do this by configuring the Customizing for Logistics Integration so that only a sales order is created, and not a purchase requisition or a purchase order.

In this case, you have to set up the sales order item category used so that it triggers a procurement process. With this configuration, the transaction documents of the procurement process ((like the purchase order) are NOT added to the transaction history of the service order. Also: no quantity or status update of the service order is executed. To track the progress of the procurement process, the sales order apps or transaction codes need to be used.

For use in a service order (object type BUS2000146 – Service Material Item), the following item categories are available in Customizing (Menu path ServiceTransactionsBasic SettingsDefine Item Categories):

  • SRVU - Adv. Shipment of Procured Srv. Parts
  • SRVV - Adv. Shipment of Srv. Parts from Stock

For the service confirmation (object type BUS2000142 – Service Material Confirmation Item), the following item categories are available:

  • SVCU - Adv. Shipment of Procured Srv. Parts
  • SVCV - Adv. Shipment of Srv. Parts from Stock

You can use the advance shipment item categories, since they have been assigned (in the item category determination) to transaction types SRVO (service order) and SRVC (service confirmation) as manual alternative item categories (menu path: ServiceTransactionsBasic SettingsDefine Item Category Determination).

The following settings have also been maintained:

  • Define Copying Control for Item Categories (menu path: ServiceTransactionsBasic SettingsCopying Control for Business TransactionsDefine Copying Control for Item Categories).
  • Define Item Category Determination when Copying (menu path: ServiceTransactionsBasic SettingsCopying Control for Business TransactionsDefine Item Category Determination when Copying).
A table is shown with the determination of the logistics scenario(s) for the various item categories used in the service order in a service process using Advance Shipment functionality. The table displayed has six columns and two rows of data, accompanied by a note under the table. The table headers are: Transaction Type, Item Category, Service Organization, Resp. Org. Unit (Service), Logistics Scenario, and Logistics Sub Scenario. The first row contains: SRVO, SRVU, asterisk, asterisk, PREQ – Purchase Requisition asterisk, and 01 – Advance Shipment (via Sales Order). The second row contains: SRVO, SRVV, asterisk, asterisk, RSRV - Reservation, and 01 – Advance Shipment (via Sales Order). Below the table, a note reads: If instead of a purchase requisition you want to directly create a purchase order, select the Purchase Order scenario. Rows in the table are shaded in different tones of light blue.

The table shows the determination of the logistics scenario for the service order (menu path: ServiceTransactionsSettings for Service TransactionsIntegrationLogistics IntegrationOrganizational Management (Legacy)Define Logistics Scenario for the Procurement of Materials and Services).

Flowchart illustrating the process from Service Order to Billing Document along with a table showcasing transaction details. The flow progresses through stages: Service Order, Service Confirmation, Goods Issue from Customer Consignment, Billing Document Request, and finally, Billing Document. Below the flowchart, a table is shown with the determination of the logistics scenario (C - Customer Consignment) for the confirmation in a service process using Advance Shipment functionality. Two rows show setups with Transaction Type as SRVC for both. The first row has Item Category as SVCU, with Logistics Scenario as C - Customer Consignment. The second row lists Item Category as SVCV, sharing the same logistics scenario. Values marked with an asterisk are used for the determination columns Service Organization and Resp. Org. Unit (Service).

The confirmation process is the same for both scenarios. Once the repair has been completed, the service technician enters the confirmation details in the system. This is followed by the goods issue for the service part used.

From a configuration point of view, logistics scenario C - Customer Consignment is determined for an SRVC confirmation using item category SVCU. This ensures that the goods issue is posted out of customer consignment stock.

The service confirmation can only confirm a service part that has already been delivered via the outbound delivery of the sales order. If the quantity in the confirmation exceeds the delivery quantity, a warning message is triggered when the confirmation is created or changed. If the confirmation is set to Completed, an error message is issued and the status automatically resets to open.

Note

For both scenarios: the sales order must use the same number range as the service order. For this, the external number range of the sales order type must correspond to the number range of the service order. In addition, if you do not maintain the service order - sales order mapping in the IMG activity Assign Service Transaction Types to Sales Document Types, the service order ID must correspond with the sales order ID (of, for example, the SRVO sales order).

Besides the configuration options mentioned above, various configuration settings in Sales and Distribution are also necessary. An example is the configuration of sales document type SRVO. Another example is the definition of the sales item categories SRVU (Srv Part Proc&Ship) and SRVV (Srv Part Adv. Ship).

Note

For a configuration guide concerning Advance Shipment, see SAP Note 3281697 - Advance Shipment - Setup Guide.

Configuring an Available to Promise (ATP) Check for a Sales Item

The availability check can be used in SAP S/4HANA Service for sales items.

Note

To see the Customizing documentation regarding the configuration for the availability check for use in SAP S/4HANA Service, navigate to SAP Customizing Implementation GuideServiceBasic FunctionsAvailability Check and choose the Documentation icon.

The following are the required steps to configure the availability check for sales items in a service scenario:

  1. Activate the availability check for the relevant schedule line categories in Customizing for SAP S/4HANA Sales.

    In Customizing, navigate to SAP Customizing Implementation GuideSalesSales DocumentsSchedule LinesDefine Schedule Line Categories.

  2. Define a key for an ATP profile that is then assigned to the relevant service item category. The name of the ATP profile needs to be a numeric value.

    In Customizing, navigate to SAP Customizing Implementation GuideServiceBasic FunctionsAvailability CheckDefine ATP Profile and SAP Customizing Implementation GuideServiceBasic FunctionsAvailability CheckAssign ATP Profile to Item Category.

  3. Start transaction FIBF to activate the ATP check, and then follow the following menu path: SettingsIdentificationSAP Applications. In the table Application Indicator, set the application CRMATP to Active.

Stock Transfer of Service Parts to the Storage Location of an Executing Service Employee

A white van with 100% ELECTRIC written on its side is parked on grass near large solar panels and several wind turbines. In the background, there are mountains visible under a clear blue sky, portraying a scene focused on sustainable energy sources.

Since release 2023 of SAP S/4HANA, you can initiate a stock transfer from a service part item of a service order or repair order, for example from a central storage location to a van stock storage location of a service employee. When the required service parts are not available in the executing service employee's storage location, a stock transfer process can be triggered to transfer the required stock to the storage location of the service employee.

Note

If the source and target plant are different, they must belong to the same company code.

The following prerequisites and settings in Customizing for Service are relevant for this specific scenario:

  • Make sure you assign a role based on the standard SAP role SAP_BR_SHIPPING_SPECIALIST to your user(s) involved in (testing or executing) this scenario.
  • In Customizing, create a storage location representing your van via Enterprise StructureDefinitionMaterials ManagementMaintain storage location.
  • You need to map a purchase requisition or a purchase order to the logistics sub-scenario 03 Stock Transfer Item.

    If you use Organizational Management (legacy), you do this via ServiceTransactionsSettings for Service TransactionsIntegrationLogistics IntegrationOrganizational Management (Legacy)Define Logistics Scenario for Procurement of Materials and Services.

    If you use the Enterprise Organizational Model, you set this up in Customizing under: ServiceTransactionsSettings for Service TransactionsIntegrationLogistics IntegrationEnterprise Organizational ManagementDefine Logistics Scenario for Procurement of Materials and Services

  • You need to specify which purchasing document type (create a new one if needed, like ZUD StockTranspOrderDel in our training system) is to be used for a combination of service transaction type and item category for logistics sub-scenario 03 Stock Transfer Item.

    You do this via ServiceTransactionsSettings for Service TransactionsIntegrationLogistics IntegrationEnterprise Organizational ManagementSet Purchasing Document Types for Service Transaction Type and Item Category.

  • If you use the Enterprise Organizational Model, you specify the relevant employee-specific plant and storage location via ServiceTransactionsSettings for Service TransactionsIntegrationLogistics IntegrationEnterprise Organizational ManagementAssign Plant and Storage Location to Service Employee and Country/Region. You specify the relevant supplying plant and storage location via ServiceTransactionsSettings for Service TransactionsIntegrationLogistics IntegrationEnterprise Organizational ManagementAssign Plant and Storage Location to Country/Region.

    If you use Organizational Management (Legacy), you specify the supplying plant and storage location and the employee-specific plant and storage location via ServiceTransactionsSettings for Service TransactionsIntegrationLogistics IntegrationOrganizational Management (Legacy)Assign Plant and Storage Location to Service Organizational Units.

Note

SAP S/4HANA uses a predefined sequence when searching for the plant and storage location. See the SAP Help Portal for more information.

Summary

  • A logistics scenario can be assigned to an item category determined in a service order. You can use it to trigger the creation of a reservation or the external procurement of a material and/or service for an order item.
  • For service (and repair) confirmations, the way that material withdrawals are posted needs to be configured. These withdrawals can be posted out of plant/storage location normal stock or they can be posted out of (technician or customer) consignment stock. Again, the logistics scenario indicates what scenario is required. It is assigned to the transaction type of the service confirmation and the item category (in combination with a service organization and responsible service organizational unit).
  • Services (with material type SERV) are procured externally and can then be entered in the system using the lean services functionality (that is, using a service entry sheet).
  • The functionality Advance Shipment enables the shipment of service parts to a service technician or to a customer before the actual repair starts. Standard settings are available for these scenarios.
  • You can initiate a stock transfer from a service part item of a service order or repair order, for example from a central storage location to a van stock storage location of a service employee. When the required service parts are not available in the executing service employee's storage location, a stock transfer process can be triggered to transfer the required stock to the storage location of the service employee.

Optional: Configure the Integration with Logistics

Part 1 of the exercise/simulation:

Part 2 of the exercise/simulation:

Part 3 of the exercise/simulation:

Optional: Perform a Stock Transfer of a Spare Part to Van Stock Based on a Service Order

Part 1 of the exercise/simulation:

Part 2 of the exercise/simulation:

Part 3 of the exercise/simulation: