Identifying New Features of the APIs for Service Orders

Regarding the SOAP APIs for service orders: The following features are supported since release 2025:

• Warranty information:

  • Service Transaction Item Is Under Warranty (header): Indicates if the service transaction is covered by a warranty.
  • Under Warranty (item): Indicates if a warranty is valid for the item.
  • Master Warranty (item): The ID of the warranty valid for the item.
  • Warranty End Date (item): The end date of the warranty assigned to the item.
• In Process Status: The status In Process is a life cycle status, indicating that a service order has not yet been released or that at least one item has the status In Process.
• Execution Status: The field is used in the integration with SAP Field Service Management (SAP FSM) and in the Service with Advanced Execution scenario.

The following features are also supported since release 2025:

The following new fields related to change indicators are now supported on header and item level:

• Created By: User who created the transaction
• Created At: Timestamp when the transaction was created
• Changed By: User who last changed the transaction
• Changed At: Timestamp when the transaction was last changed

The warranty information consists of four fields: one on header level and three on item level. The Under Warranty field can be set to false to indicate that the warranty is invalidated, for example, if the customer intentionally damages the equipment.

In Process is the second life cycle status. It indicates that the service order is being worked on and has not yet been released, or that there are still unreleased items.

The Execution Status is currently used to provide more detailed information about the execution of the service, when an item has the status Released.

The change indicators Created At, Created By, Changed At, and Changed By are important for identifying who created the transaction and when, as well as who, made the last changes to the transaction. Both on header and on item level.

These indicators are especially useful for integration scenarios involving several external systems (for example SAP Field Service Management). When the service order is changed in different systems, you can compare the data of the external system with the data provided by the change indicators to analyze if the service order was changed during reading and changing from the external system.

The OData V2 API for service orders has been deprecated as of release 2025 because a new V4 API has been released with release 2025.

However, the following basic fields were added as a final enhancement to the V2 API due to a high request for them:

• Gross Value (header and item):

  The gross value of a service transaction and its items

• Net Value (header and item):

  The net value of the header and items of the transaction

• Tax Amount:

  The tax amount of the header and items of a transaction

• Open (Status):

  The initial life cycle status when a service order is created

• In Process (Status):

  The In Process status is a life cycle status indicating that a service order has not yet been released or that at least one item has the status In Process.

The three display fields Gross Value, Net Value, and Tax Amount are all basic information fields available at both header and item level.

Support of the Open and In Process statuses includes the ability of the OData V2 API to read and search for all life cycle statuses.

Starting with SAP S/4HANA Cloud Private Edition 2025, the ODATA V4 API OP_SERVICEORDER_0001 is provided. It is the successor of the ODATA V2 API API_SERVICE_ORDER_SRV. It also enables you to integrate external applications with service order processing.

Advantages of the ODATA V4 API for service orders include:

• The ODATA V4 API is more consistent, concise, and follows modern OData and SAP guidelines:

  • Boolean status fields everywhere, carefully typed fields
  • Strong containment and composition for navigation
  • Rich annotations for UI, validation, error, and documentation
  • Generally more "read-only" (less direct update/delete on supporting entities)
  • Some field names and lengths have changed; status fields often migrated from string to type-safe booleans.
  • Entity set and property names are more standard/OData native; navigation is much easier for composition.
• The V4 API follows an optimized protocol which makes the service faster than the V2 API.
• Error Handling: V4’s SAP_Messages field enables native SAP message returns per entity instance.
• Performance: The V4 protocol uses JSON formats and better supports "delta responses" which make the V4 ODATA APIs lighter and usually faster.
• Deletions, actions: The V4 API has more precise delete restrictions and can expose bound actions (for example the ReleaseForBilling action).
• Batch: The V4 API improves batch request handling (with fewer server round trips).

The ODATA V4 API for service orders supports all entities and fields which the V2 ODATA API supported and more. The model is slightly different, so replacing ODATA V2 API calls might need to be adapted.

One example is reading the transaction history; in the ODATA V2 API for service orders, all predecessor or successor transactions are provided together. In the ODATA V4 API, there are different entities for each type of predecessor and successor transaction.

Additional differences between the ODATA V4 model and the ODATA V2 model are:

• Several technical fields have been removed:

  ServiceOrderUUID, ServiceObjectType (is always BUS2000116), ServiceDocumentTemplateType

• Fields have been renamed:

  ReferenceServiceOrder used to be called SrvcOrdExtReference.

• Fields have been added:

  ServiceOrderStatus, ServiceOrderHasError (in ServiceOrder), and SrvcOrdItemQuantityUnitISOCode (in ServiceOrderItem) have been added.

You can get detailed information about the V4 API service from the SAP Help Portal and the Business Accelerator Hub.

• The following features are supported in the SOAP APIs for service orders since release 2025: warranty information, In Process status, Execution Status, and also change indicators.
• The OData V2 API for service orders has been deprecated as of release 2025 because a new V4 API has been released with release 2025. However, some basic fields were added as a final enhancement to the V2 API.
• The ODATA V4 API OP_SERVICEORDER_0001 is provided as a successor to the ODATA V2 API API_SERVICE_ORDER_SRV. The V4 API has many advantages and differences when compared with the V2 API.