The 2608 release reinforces SAP's commitment to making Solution Order Management a more flexible, efficient, and configurable foundation for complex solution selling. Whether you are looking to extend billing flexibility, improve revenue recognition accuracy, or reduce the configuration overhead of adapting processes to your business — this release has meaningful improvements across all of these dimensions. In this blog post, you'll find a brief summary of key new features to ensure you're up to date on the latest scope of solution orders in SAP S/4HANA Cloud Public Edition.
New Configuration Activities for Solution Orders
Our first 2608 feature delivers on a long-standing customer request for greater process configurability in Solution Business and Service Management. The current design of transactional processing in Solution Business and Service Management has lacked the flexibility for customers to adjust process configuration through item category determination settings across business objects such as solution orders, service contracts, service orders, and service confirmations. In addition, it has not been possible to maintain and assign number ranges to these service objects.
With this release, two new configuration activities are introduced that give key users and administrators significantly more flexibility to adapt solution orders — and related service transactions — to specific business requirements. These enhancements reduce time to value by allowing customers to tailor solution-order and service-management processes to their adopted scenarios without requiring manual overrides on individual transactions. The new configuration activities are:
- Define Number Ranges for Solution Orders (ID: 107300) — allows key users to define custom number range intervals for solution orders, which are then assigned to transaction types via the companion activity Assign Number Range Intervals for Service (ID: 107299). This enables unique and business-specific order numbering without relying on SAP defaults.
Change Item Category Determination (ID: 107306) — allows adjustment of SAP's pre-delivered item category determination for solution orders and other service transactions. Key users can change the sequence of determined item categories, remove existing assignments, or add new ones, giving teams the ability to align the system's default behaviour with their adopted process variants without manual overrides on every transaction.
These activities are findable via the configuration environment search and require upgrading to the latest reference content version.
Enabling Order Reasons in Solution Orders
Understanding the “why” behind every order is crucial for strategic analysis and operational efficiency. This enhancement allows you to capture the specific reason for a solution order directly at the source, providing valuable context that flows through the entire process. This improves your search capabilities, reduces operational costs through better resource planning, and provides a richer dataset for sales analysis, helping you refine your strategies and better understand customer motivations.
Technically, you can now select an order reason at the solution order header level, both through the Manage Solution Orders Fiori app and programmatically via the BusinessSolutionOrderReason field in the Business Solution Order OData V4 API. These reasons are configurable using a dedicated self-service configuration UI (SSCUI). The system automatically replicates the order reason to follow-up sales orders, ensuring consistency, and you can use it as a filter criterion in the Manage Solution Orders app for targeted searches and reporting.
Ad Hoc Billing for One-Time Services
One of the headline additions in 2608 is the extension of ad hoc billing to one-time service items in solution orders. Previously limited to service bundles and fixed-price service bundles, ad hoc billing can now be applied to a broader set of item categories — including service items, external service items, spare parts, expense items, and non-stock service part items.
This matters most when businesses need to bill partially before a service is completed. Rather than waiting for full delivery, solution order specialists can now freely define billing values and dates for individual service items, giving significantly more flexibility in how and when revenue is collected. These item categories can also be used as subitems within bundle items, further extending the scenarios they support.
Manage Solution Orders App: UI and Usability Improvements
This release also brings a series of targeted UI enhancements to the Manage Solution Orders app, closing gaps that existed between solution orders and downstream service transactions.
Key improvements include:
- One-time service items now show serial number, product ID, product description, and reference product columns in the item detail page, bringing the solution order view in line with what is already available in follow-up service transactions.
- Service contract items gain a serial number column in the object list section of the item detail page.
- For sales items, the flag for changed follow-up documents has been moved to the sales items view for easier access.
- The transaction history links for sales orders now navigate directly to the Manage Sales Orders – Version 2 app, replacing the legacy app link.
These changes are quality-of-life improvements that reduce the need to switch between applications and ensure a more consistent experience across the solution-to-service process.
Cost-Based Percentage of Completion for Service Contract Items
A significant new capability arrives for businesses using revenue recognition on service contracts: the cost-based Percentage of Completion (POC) method is now supported for service contract items within solution orders.
Two new item categories have been introduced — SOC1 (POC service contract item for price adaptation) and SOC2 (POC service contract item for ad hoc billing) — which can be assigned to service items, expense items, and service part items through service contract determination. When these items are released, the system creates follow-up service orders with the cost-based POC method applied, meaning revenue is recognised progressively based on costs incurred from the relevant service orders.
This is a new feature (not a change to existing behaviour) and must be explicitly activated in the configuration activity Activate Features using feature CRMS4_POC_REV_REC. Products used in these items must be assigned to item category group SCNP in the product master.
Billing Block Updates for Released and Completed Sales Items
Operational efficiency gets a boost with the ability to set and reset billing blocks on sales items that have already reached released or completed status — directly within the Manage Solution Orders app.
When solution orders generate follow-up sales orders, billing blocks are commonly used to hold invoicing until a service is fully completed — ensuring a single, consolidated invoice can be raised once all obligations are fulfilled. Previously, once a sales item progressed beyond the open or in-process status, users had no way to update the billing block from within the solution order. Instead, they were required to navigate away from the solution order and make changes directly in the follow-up sales order — a separate, manual step that added friction, especially for specialists managing high volumes of orders daily.
In the Manage Solution Orders app, you can now set and reset billing block reasons on sales items that have reached the released or completed status — directly within the solution order, without needing to open or modify the follow-up sales order separately. This restores and extends a key piece of operational flexibility, allowing billing issues to be corrected later in the process without reopening documents.
The billing block is specified by selecting a billing block reason code on the relevant sales item. This keeps the entire action within a single application, significantly reducing context-switching for solution order specialists and improving the speed and accuracy of the billing workflow.
Milestone Billing for Third-Party Sales Items with Variant Configuration
The final enhancement in this release extends milestone billing support to third-party sales items with variant configuration. Two new item categories have been introduced:
Item Category Description
SOMB | Third-Party VC Sales Item with Shipping Notification – Milestone Billing Plan |
SOMC | Third-Party VC Sales Item without Shipping Notification – Milestone Billing Plan |
These item categories inherit their definitions and customising attributes from their respective reference item categories and map to the corresponding milestone billing item categories on the follow-up sales order when the solution order is orchestrated. This completes a gap for customers selling configurable products through third-party channels who need milestone-based billing tied to delivery events.
Output Management Enhancements for Solution Orders
Imagine generating an order confirmation that automatically includes the delivery status from a follow-up transaction, creating a single, consistent communication for your customer without any extra effort. This feature makes that a reality, allowing you to create seamless and comprehensive external documents. It eliminates the need for redundant data storage and ensures a consistent view for the customer across various fulfilment touchpoints, from order confirmation to delivery notification.
This is enabled through two new Business Add-Ins (BAdIs) for key user extensibility — one for the header and one for the item level. Using these BAdIs, you can implement custom logic to read data from downstream or related transactions, based on published CDS views, and enrich the output of your solution order and service transactions. The data is retrieved on-the-fly, ensuring your documents are always up-to-date without storing duplicate information.
Complementing this is a new capability for controlling when outputs are sent. In some business scenarios, an order is not considered complete until all follow-up processes — such as downstream sales orders or service orders — have been successfully created. You can now use events from those follow-up documents to update a custom field on the solution order, and then use output determination rules to decide whether to send or hold back the order acknowledgement accordingly. This ensures customer communications only go out when the entire fulfilment process is truly complete.
Together, these enhancements give solution order specialists full control over both the content and timing of customer-facing outputs — with no additional manual effort or redundant data management.
API-Driven Simulation for Configurable Products and Solution Bundles
For sales representatives working in an external quoting system, the ability to simulate a complex solution in real time is a game-changer — accurate quotes on the first try, fewer revisions, and a faster sales cycle. This enhancement makes that possible by enabling seamless, touchless integration between your quoting platform and SAP S/4HANA Cloud, whether you are running a third-party tool or SAP Sales Cloud.
The OData V4 RAP-based CRUD and Simulation API for solution orders now fully supports Advanced Variant Configuration (AVC). Consuming applications can pass characteristic value assignments directly through the API for standalone configurable products, solution bundles, and service bundles within a solution bundle. Since configuration choices directly influence pricing, this ensures that simulations return a precise, reliable price — giving sales teams the confidence to quote accurately without switching between systems.
Key capabilities include creating, reading, updating, and deleting solution orders with configurable sales and service contract items, passing characteristic values at order creation or simulation, and combining physical products, one-time services, and recurring services in a single integrated solution.
Header-Level Pricing and Discounts via Solution Order APIs
In many integrated landscapes, sales teams need to apply overall discounts at the quote level to close a deal. This feature extends our new API to support this critical commercial requirement, ensuring your quoting process is both flexible and accurate. Now, sales representatives using an external quoting application can not only simulate a configured solution but also pass header-level pricing conditions, such as a percentage discount, directly into the simulation. This ensures the final estimated price they see is completely accurate, reflecting all negotiated terms from the start.
Technically, the OData V4 Simulation API for Solution Orders can now accept header-level pricing conditions. The system applies this condition (e.g., a discount) to all relevant items and returns the calculated net value, giving the sales rep a final, trustworthy price to present to the customer. To ensure end-to-end consistency from quote to order, this same functionality is enabled for the CRUD API. This allows the final solution order to be created with the header discount automatically included, perfectly mirroring the approved quote and eliminating manual entry errors.
We are constantly innovating to help you run your business better. The 2608 release and our forward-looking roadmap demonstrate our commitment to delivering a world-class cloud ERP that is intelligent, flexible, and built for your success.
Source link