This blog shares highlights on Service in SAP S/4HANA Cloud Public Edition 2608 release.
Watch my video to get a glimpse of the new features:
Key User Extensibility for In-House Repair
Organisations running In-House Repair (IHR) can now extend the application to match their own business practices — without writing custom code and without disrupting the standard process. Using the standard SAP extensibility framework, business experts can create custom fields, adjust user interface layouts, relabel fields, and expose additional data via API — all from within the Fiori ‘Adapt UI' tooling they already know. The five core IHR applications are covered: Manage In-House Repairs, Process Repair Quotations, Plan Repairs, Perform Repairs, and Prepare for Billing.
What makes this particularly practical is consistency: any custom field added through extensibility travels with the repair object throughout its entire lifecycle — from the initial intake through planning, execution, and billing — so data entered at one stage is always available at the next. The underlying CDS views I_InhouseRepair and I_InhouseRepairItem are released at C0/C1, making them available for reporting and external API integration. Extensions are also upgrade-safe, meaning they survive future releases without rework — a key concern for cloud customers who want to customize without taking on long-term maintenance overhead.
Enhanced Output Management for Service and Repair Documents
Four significant improvements to output management arrive in 2608, closing gaps that previously forced service teams into manual workarounds. First, the output control assignment block — which governs dispatch time, output type, form template, and recipient email — is now editable on Service Quotations, Service Orders, and Repair Quotations. Until this release, output control was only editable on Repair Orders, leaving service coordinators unable to make last-minute corrections before sending.
Second, output can now be routed to any partner function configured on the document, not just the sold-to party, contact person, and employee responsible. This means roles such as the bill-to party, payer, and ship-to party can all be configured as valid output recipients — a significant step forward for organisations with multi-party service agreements. Third, the XML data source used to design form templates has been substantially extended: unit prices, sold-to and ship-to addresses, sales office, contact details, pricing condition quantities, and custom fields are now available to form designers, enabling the production of legally compliant, customer-ready documents across markets. Finally, output can now be routed to an external output management system via the EXTOM channel, supporting organizations that manage document output outside of SAP.
Watch this demo to have a complete view of the feature.
Service Order and Quotation: Additional Capabilities
Several targeted improvements across the service quotation and order process arrive together in 2608. The most impactful is the ability to create a requote from a previously rejected service quotation. Until now, rejection ended the quotation's lifecycle entirely — the content was unrecoverable and teams had to start from scratch. The new ‘Requote' action lets a service planner select which rejected items to carry forward as open items in the revised quotation, preserving scope that was discussed and negotiated in the original round. When the requote is accepted, all newly accepted items flow to the follow-up service order automatically.
Watch this demo to have a complete view of the feature.
Service Order Templates can now be used to create both service quotations and service orders as follow-up documents — previously only service order creation was supported. This means a single template can serve both the quoting and execution phases of a service engagement, reducing template maintenance overhead and improving consistency between what was quoted and what is delivered. When a fixed-price template is used, the resulting quotation inherits the fixed-price type automatically.
Watch this demo to have a complete view of the feature.
On the localization front, country-specific legal text types required in Italy (CIG and CUP reference codes) and Spain (EDSI electronic invoice identifier) can now be entered directly on Service Orders, Repair Orders, and their confirmations. These text types flow through the document chain to billing document requests and invoices, covering both confirmation-based billing and fixed-price billing scenarios — eliminating manual re-entry of legal reference codes at the invoicing step. Alongside this, a dedicated ‘Delivery Text' type is now available in the notes section of procurement items on Service Orders and Repair Orders; the text flows automatically to the purchase requisition and purchase order, ensuring vendors receive the correct delivery instructions without any manual intervention in the procurement process.
Customer and Product Hierarchy Pricing: Complete Coverage Across Service Transactions
Customer hierarchy and product hierarchy support for pricing was introduced in release 2602, enabling condition-based discounts and pricing rules based on a customer's position in a hierarchy or a product's classification. That initial release covered service contracts, service quotations, service orders, and service confirmations — but with two notable gaps: unplanned items added during a service confirmation, and in-house repair transactions. Release 2608 closes both gaps.
For service confirmations, when a technician adds an unplanned item — such as an extra spare part discovered on site — that item now automatically inherits the product hierarchy and customer hierarchy configured in the system. Pricing conditions, including hierarchy-based discounts, are applied without any manual correction. This prevents revenue leakage and over-billing in field execution scenarios where unplanned consumption is common.
For in-house repair, both customer hierarchy and product hierarchy are now fully active on Repair Quotations, Repair Orders, and Repair Confirmations. Price conditions and hierarchy assignments flow from repair documents all the way to billing, ensuring that customers receive invoices that reflect their negotiated pricing — with no manual lookups or corrections required in the repair workflow.
Watch this demo to have a complete view of the feature.
Service Order Integration with SAP Concur Solutions
The integration between service orders and SAP Concur solutions — first delivered in release 2602.2 — connects fixed-price expense items on service orders with the Concur expense management workflow. Supported scenarios include fixed-price and non-billable expense items, ad hoc expenses, fixed-price bundles containing expense items, and time-and-materials bundles with fixed-price expense items. Technicians can book expenses with detailed categorisation directly through the integrated workflow, removing the need to duplicate entries across systems.
The business benefits span both the individual and the organization: technicians gain faster, more accurate expense booking with improved compliance to corporate travel policies, while finance teams benefit from streamlined approval workflows, better financial control, faster reimbursements, and more accurate allocation of costs to specific service orders.
Watch this demo to have a complete view of the feature.
Updating Purchase Order Numbers During Manual Service Contract Renewal
When a service contract is renewed, customers frequently issue a new purchase order number — and that number needs to appear on the service contract so invoices can be matched correctly, accelerating payment. Until 2608, capturing the new PO number during the manual renewal process required a separate correction step after the renewal was saved. This release removes that extra step: the purchase order number, stored in the External Reference field, can now be updated directly within the manual renewal workflow, for both header-level and item-level renewals.
The change is available in both the Fiori user interface and via the API for the manual service contract change process, ensuring automated renewal workflows can benefit equally. This builds on a prior enhancement that enabled PO number capture at item level; 2608 specifically extends that capability to the manual renewal flow, closing the last remaining gap in the contract renewal process.
Watch this demo to have a complete view of the feature.
Typeahead Value Help for Service Contract Partner Functions
Creating or editing a service contract now benefits from typeahead value help for key partner functions — Sold-to Party, Contact Person, and Employee Responsible. As a user begins typing a name or ID in any of these fields, the system instantly returns matching results from the database alongside recently used values, enabling fast and accurate selection without navigating to a separate search screen. The feature was driven by a long-standing customer request in the SAP Customer Influence Program, and it addresses a friction point that slows down high-volume contract processing.
The improvement is intentionally designed to extend further: the same typeahead behaviour is planned for the Product ID field in an upcoming release. In the same area, 2608 also introduces a separate number range configuration for service contract templates, allowing administrators to assign templates to a different number range from live contracts — making it easier to distinguish between the two in background jobs, reports, and system monitoring.
Watch this demo to have a complete view of the feature.
In-House Repair: Rejecting Repairs and Adding Objects After Confirmation
Two long-requested capabilities arrive for In-House Repair in 2608, giving repair centre managers greater control and cleaner operational data. The first is the ability to formally reject an IHR at header level or at the level of individual repair objects. A dedicated Reject button now appears on the IHR header; rejection requires a mandatory rejection reason, which is captured and retained on the document. This matters for reporting: previously, cancelled repairs had to be set to ‘Complete' status — making it impossible for analytics and KPI systems to distinguish a genuinely finished repair from an abandoned one. Individual repair objects can also be rejected independently, with status controls governing the exact point at which rejection is permitted.
The second capability removes a restriction that blocked new repair objects from being added once an IHR had been confirmed. From 2608, repair objects can be added throughout the IHR process regardless of confirmation status — reflecting the reality of repair workflows where new items frequently arrive mid-process. Together with the reject capabilities, this gives repair teams the flexibility to manage complex, multi-device repair scenarios without workarounds.
A further usability improvement in the same area: the ship-to party search help on IHR creation now filters available ship-to parties based on the sold-to party already entered, rather than listing all business partner master records. This reduces selection errors and speeds up data entry — particularly valuable in environments with large numbers of business partners.
VAT Tax Fields Across All Service Transactions
VAT tax fields are now available and consistently applied across all service transaction types, providing uniform tax determination and visibility throughout the service management process. This improvement, delivered progressively from release 2604 through 2608, ensures that tax data is present and handled correctly at every stage of a service engagement — from quotation and order through confirmation and billing — removing the inconsistencies that previously required manual tax adjustments on certain transaction types.
Percentage-of-Completion Revenue Recognition for Service Orders
Service orders now support percentage-of-completion (POC) revenue recognition, enabling revenue to be posted progressively as a service order advances toward completion rather than being deferred entirely to the point of full billing. This is particularly relevant for long-running service engagements — maintenance contracts, complex field service projects, and multi-milestone service agreements — where matching revenue to the period in which work is performed is both a financial accuracy requirement and, in many jurisdictions, a compliance obligation.
It is important to note that general availability for this feature has been moved to release 2702 (the February release). The reason is that the ability to customise additional item categories for POC revenue recognition is not yet complete, and SAP chose not to introduce new item category defaults that could affect existing customers prematurely. That said, organisations that want to start testing early can activate the feature in 2608 via a customer feature toggle. Those who do so will need to switch to the official customising flag when 2702 is released. SAP plans to dedicate a demo session — in the Early Read Series or Product Expert Training program — to this feature once it reaches general availability.
UX Improvements 3.0: Faster, Cleaner Service Management Apps
Service management users benefit from a third wave of targeted usability improvements across more than 20 Fiori applications in 2608, including better column header menus, improved table column width handling, and enhanced information density on object pages. The changes span the most frequently used service apps — Manage Service Orders, Process Service Order, and Manage Service Quotation among them — and are designed to reduce the number of clicks required to complete routine tasks in high-volume service processing environments.
Small as they may appear individually, these incremental usability gains compound significantly for service processors who spend their working day in these applications. Improved column resizing, better at-a-glance readability, and smoother navigation between records all contribute to reduced time-on-task — and, over time, to measurable improvements in service team productivity.
Non-Billable Item Categories for Repair Orders and Service Templates
The ability to mark individual service items as non-billable has been significantly extended in 2608. Service orders already supported non-billable item categories; this release brings the same capability to service order templates, repair quotations, repair orders, and repair confirmations. Non-billable items carry a net value of zero, are excluded from billing and revenue recognition, and route their costs to profit and loss — making it straightforward to handle warranty, goodwill, and maintenance contract scenarios within the standard process without custom order types.
For service order templates, non-billable item categories set on the template are automatically copied to the corresponding item categories when an order is created from the template, with built-in validations ensuring financial consistency. The supported non-billable categories span the full range of repair-relevant item types: expense, service part, stock service part, external service, and service bundle. Non-chargeable work is properly tracked and excluded from billing and revenue recognition throughout, maintaining financial accuracy and eliminating the need for workaround order types in warranty and goodwill scenarios.
Service Confirmation: Executing Employee No Longer Mandatory
Creating and completing a service confirmation no longer requires an Executing Service Employee partner function when the item category does not call for one. Previously, this field was mandatory for all confirmation types — including external service procurement scenarios where the work is performed by a third-party contractor and assigning an internal service employee simply does not apply. The result was a blocking validation error that forced workarounds, such as assigning a placeholder employee, just to save the document.
From 2608, the field is controlled at item category level: it remains required where the business process demands it, but is no longer enforced in scenarios where it is genuinely not applicable. This is a targeted but impactful change for service organisations that rely heavily on external service providers and subcontractors, removing friction from one of the most common daily transactions in field service operations.
Event-Based Integration for Service Orders and Confirmations
Real-time, event-driven integration between SAP service management and external systems takes a significant step forward in 2608. Business events were previously available at header level only; this release adds item-level events for both Service Orders and Service Confirmations. Organisations can now subscribe to Created, Changed, Rejected, Released, and Deleted events at service order item level, and to Completed, Changed, Created, and Deleted events at service confirmation item level — in addition to all existing header-level events.
These events are the building blocks of modern service integration architectures. A field service platform can listen for a ‘Service Order Released' event to trigger automatic technician scheduling; a CRM system can subscribe to ‘Service Confirmation Completed' to update the customer's service history in real time; an analytics platform can consume change events to maintain a live view of in-progress work — all without custom middleware or polling loops. Standard events can be extended by deriving new events with custom payload attributes, tailoring the data published to exactly what each downstream system needs. Full payload documentation, event listings, and instructions for creating derived events are published on the SAP Business Accelerator Hub.
Pricing Attributes: Equipment ID, Reference Product, and Material Group
Three new attributes — Equipment ID, Reference Product, and Material Group (MATKL) — are now available in the Service Pricing BAdI field catalog, enabling condition-based pricing logic that can reference data already present on the service transaction. This opens up a class of pricing automation that was previously difficult or impossible to implement cleanly within standard configuration.
The most direct application is warranty automation: a pricing rule can now check whether the equipment ID on a service order falls within a valid warranty period and automatically apply a full warranty discount — removing the need for technicians to manually enter or request discount values. Beyond warranty, the same mechanism supports repair cost limit rules driven by Reference Product, product group surcharges driven by Material Group, and other complex pricing scenarios that depend on equipment or product classification data. The attributes are available in both the Pricing Field Catalog and the BAdI implementation, giving pricing architects full flexibility in how they use them.
Customizable Item Category Determination for Service Transactions
Item category determination in service transactions — long a source of errors when the system defaulted to a category that did not match the business scenario — is now configurable via SSCUI. Administrators can change the main item category assigned to a determination combination, add item categories not previously available, and crucially, remove item categories that are not relevant to their process. If an organisation never uses the ad-hoc item category, for example, it can be removed from the determination entirely, eliminating it from the user interface and preventing selection errors.
In the SSCUI configuration table, both the main item category and each of the alternate item categories can be adjusted per combination — so if only three alternatives are relevant for a given transaction type, the unused alternatives can be removed rather than left as noise. The change applies across service orders, solution orders, and other service management transaction types. One area still under active development is the alignment of item categories for third-party shipment scenarios (CBOR/CBNA), which requires coordination with Sales module item category logic before it can be opened up.
The topic page SAP S/4HANA Cloud Public Edition Service collects most relevant blogs and documents on Service.
Watch on demand: Our SAP S/4HANA Cloud Public Edition 2608 Early Release Series!
Between July 13-17 2026, we hosted a series of 24 expert-led live sessions to highlight the exciting innovations shipped with the SAP S/4HANA Cloud Public Edition 2608 release. On our landing page you can watch on demand for the entire series or pick the sessions most relevant to you.
Find all our assets
The release 2608 showcases more than 130 innovation highlights across the portfolio. Check out our release document for all the details!
Source link