Sales in SAP S/4HANA Cloud Public Edition 2408

[Chr_Vogler]

Using easy-to-use tools and interfaces to create and control intelligent scenarios can assist in tackling difficulties associated with complexity and data accuracy. This approach can lead to improved understanding and suggestions, especially with the new Recommendation-Assisted Sales Order Completion, resulting in higher customer satisfaction and business growth. Learn more about how the innovative Auto-Activation of Intelligent Scenario enhances automation in my most recent blog post.

Additionally, I will walk you through my selected key highlights for Sales:

To name just a few highlights:

• Auto-Activation of Intelligent Scenario for Input Recommendations for Sales Orders,
• New SAP Fiori app to Display the Change Log for Sales Documents,
• Improvement of Flexible Default Item Category Determination in Sales Documents,
• Enhanced SAP Fiori app “Manage Customer Returns – Version 2”,
• … and more.

In case you do not need all the information below and just briefly want to get an overview of the release highlights, please watch this video with the top three key innovations:

Release video: SAP S/4HANA Cloud Public Edition 2408 for Sales: Top 3 key innovations.

Auto-Activation of Intelligent Scenario for Input Recommendations for Sales Orders

Business Background

Sales teams receive many sales orders from various channels and APIs daily. Unfortunately, some of these orders are missing important information, making them unable to be handled further. Fixing these errors requires a significant amount of manual work in data management.

With the last release, we delivered the first feature concerning the Sales Order Auto-Completion and it’s about Recommendation-Assisted Sales Order Completion. Over the use of historical data and machine learning, the system can now offer proposals for filling in empty fields in an incomplete sales order.

Implementing intelligent scenarios often requires a deep understanding of prediction models, data analytics, and model training techniques. With SAP S/4HANA Cloud Public Edition 2408 release, we introduce the Auto-Activation of Intelligent Scenario feature via Turnkey AI, aligning with the broader goal of leveraging technology to drive digital transformation and improve business performance.

Key Feature

To enable the Recommendation-Assisted Sales Order Completion functionality and display recommendations in the sales orders user interface, customers typically have to undertake several manual setup procedures.

Below you find some challenges on the customer side:

• Create the connection between SAP S/4HANA Cloud Public Edition and the SAP BTP Platform or train the model on historical sales order data.
• The activation of a Machine-Learning (ML) scenario is time-consuming and requires many manual steps,
• Data Science knowledge is required to enable the ML scenarios,
• Process knowledge is required.

 Picture 1: Automatic set-up, training, and activation of intelligent scenario for input recommendations for sales order completion.

Turnkey AI addresses these challenges by enabling SAP S4/HANA ML scenarios to be activated automatically without user intervention.

The turnkey feature enables you to automate all ML operations of an intelligent scenario. This means, that once turnkey is enabled for an intelligent scenario, all the operations, such as pre-requisites check, train, deployment, and activation are run automatically. By automating the ML operations, the turnkey feature significantly reduces manual effort during the initial activation of an SAP S/4HANA ML scenario and throughout its lifecycle management. You can schedule turnkey and monitor the schedule in the Turnkey tab. Further details about the schedule and runs are provided in the Turnkey Schedule and Turnkey Runs tabs.

 Demo 1: Fast activation of intelligent scenario for sales order recommendations.

Remark 1:

The turnkey option is available in the “Intelligent Scenario Management” app only. You can select the intelligent scenario that supports the turnkey and switch it on. Once switched on, you can continue with the predefined schedule for turnkey. Otherwise, modify the schedule details and create a new turnkey schedule as needed.

Remark 2:

Turnkey AI for Sales Order Auto-Completion is automatically enabled by activating the scope item (73P).

For more information, see Turnkey and Monitor Recommendations for Sales Document Completion.

New SAP Fiori app to Display the Change Log for Sales Documents

Business Background

Many industries have strict regulatory requirements that necessitate tracking and documenting changes made to sales documents for auditing and compliance purposes. An application that displays a log of changes helps to ensure compliance with these regulations.

In the same way, in case of disputes or legal issues, a detailed change log can serve as evidence to support or defend business decisions related to sales documents. It offers legal protection and clarity in such situations.

Key Features

With this release, we introduce a new SAP Fiori app “Display Change Logs - Sales Documents”, in which you as a sales manager or an internal sales representative can display change logs for sales documents.

In this app, a change log contains changes to a sales document. Each log entry stores information about a change to the document header, a document item, or a schedule line, and the change is logged on the field or table level:

• The system logs a change on the table level when an entry is created in or deleted from a table. For example, when a sales order item is created, the system logs this change on the table level because a new entry is generated in the item table.
• The system logs a change on the field level when the value of a field is altered (for example, when order reason "001" is changed to "002" or removed). You can view the old and new values of the field in this app.

Change Type

The changes to sales documents can be classified into three types:

• Insert: A table entry is created (for example, a sales order item created in the item table).
• Delete: A table entry is deleted (for example, a sales order item is deleted from the item table).
• Change: A field value is altered (for example, the order reason field is altered).

 Demo 2: Enhanced Transparency by tracking all modifications made to sales documents, promoting transparency in the sales process.

In summary, the key features are:

• Display changes to multiple types of sales documents, including sales orders, sales contracts, sales quotations, credit memo requests, and return orders in one list
• Search changes using flexible criteria such as changed by changed on, sales document type, or the field that was changed.

For more information, see Display Change Logs - Sales Documents.

Improvement of Flexible Default Item Category Determination in Sales Documents

Business Background

An Item Category identifies different types of items (for example, free-of-charge items and text items) and determines how the system processes the item. Item Category is determined by SSCUI Assign Item Category.

By enabling flexible item category determination, businesses gain increased control over how item categories are assigned. This feature allows for a more accurate mapping of items to relevant categories based on factors like material type, sales organization, or distribution channel. For instance, the system can be configured to suggest the CBAO item category for sales order items when specific business criteria are fulfilled, leading to the automatic activation of the billing plan.

Key Features

With the last 2402 release, we have introduced the possibility, of creating business rules in the Business Rule Framework plus (BRFplus) so that the system determines the item categories for items in sales quotations, orders, and orders without charges.

Instead of proposing the item category configured in the configuration activity Assign Item Categories, the system can now, by default, propose an item category according to the business rules that you specified in the Business Rule Framework plus.

 Demo 3: Provide more flexibility to define business rules to determine the default item category.

Now with this new 2408 release, we made improvements in business rules in Business Rule Framework plus (BRFplus) to determine the default item category with the following additional fields:

• Custom fields on the sales document header,
• Plant,
• Payment terms.

Effects on Configuration

As a key user for configuration, you create and assign BRFplus applications, functions, and expressions in the configuration activity Create BRFplus Objects for Sales Document Categories. After that, you navigate to the “Simplified BRFplus Workbench” app to define your business rules.

For more information, see Flexible Item Category Determination.

Enhanced SAP Fiori app “Manage Customer Returns – Version 2”

Business Background

A customer return is a process that involves the return of goods from a customer to a company location. With customer returns processing, you can handle all returns scenarios, such as returns made at the counter, returns that involve a shipment to the warehouse (including the subsequent reverse logistics of the goods), and direct shipments from a customer to a supplier.

Key Features

With this 2408 release, we made enhancements to the “Manage Customer Returns - Version 2” app, you can now do the following:

• Create individual returns order items with a reference,
• Select a different item category from the alternative options defined for the returns order,
• Track the returns processing for a returns order item in the returns overview.

Create individual returns order items with a reference:

At the returns order item level, you can create single items concerning a sales order, an invoice, or a sales order without charge. The system then copies the relevant data from the reference document item to your returns order item. You can change the copied data and add additional information. For the same returns order, you can create items that reference different document categories. For example, in a returns order, you can create one item concerning a sales order and another concerning an invoice.

Select a different item category from the alternative options defined for the returns order:

Item category classifies different types of items, such as standard items and free-of-charge items. It determines how the system processes the item. When you enter a product in a returns order, the system automatically determines an item category. If alternative item categories are defined for the same product, you can now select a different item category from the alternative options for the returns order. Previously, the item category for the returns order item was read-only.

Track the returns processing for a returns order item in the returns overview:

With the returns overview, you can have an overview of all the steps required to complete the customer return process for a returns order item. By checking the processing status of each step, you can see whether a step is open, in process, complete, or contains errors. You can resolve the errors by navigating to the respective document in the step. You can monitor whether the subsequent documents related to the customer return have been successfully generated.

 Demo 4: Empower the returns and refund clerk with more functionalities in return order processing.

For more information, see Customer Returns Processing.

Creating External Billing Document Requests (EBDR) with Custom Fields by Importing Billing Data in Spreadsheet Format

Business Background

In previous releases, billing clerks could utilize the Create function within the “Manage Billing Document Requests” app to generate EBDRs by importing billing data from Microsoft® Excel® files. However, the importing of values for custom header and item fields added to EBDRs through the extensibility business contexts Sales: Billing Document and Sales: Billing Document Item was not supported.

Key Features

With the SAP S/4HANA Cloud Public Edition 2408 update, any custom field that has been activated for the mentioned business contexts (and is consequently part of all EBDRs at the header or item level) can now be populated through the import of billing data from Microsoft® Excel® files when creating EBDRs.

This functionality is achieved by incorporating the custom fields as extra columns in the template file being imported.

 Picture 2: Entry of custom field data and other billing data into the Microsoft® Excel® template file.

For more information, see Creating External Billing Document Requests via Spreadsheet Import.

SAP Fiori app “Manage Debit Memo Requests - Version 2”: Item Creation with Reference, Preview of Billing Documents

Business Background

A Debit Memo Request in sales process management is a document used to request a credit or refund from a customer. It is typically issued by a seller to notify the buyer that a credit will be applied to their account, or a refund will be issued due to an overcharge, damaged goods, returned items, or any other situation where the buyer is owed money.

Key Features

The “Manage Debit Memo Requests - Version 2” app has been enhanced with the following features:

• You can now create invoice increase requests (document type CBII) concerning an invoice. An invoice increase request can be used when the amount on the invoice needs to be increased. An invoice increase request is a type of debit memo request, but in contrast to standard debit memo requests, you cannot create an invoice increase request concerning a sales order or without a reference. You can only create an invoice increase request concerning an invoice or without reference. For more information about invoice increase requests, see Invoice Increase Request: Definition.
• You can now display a preview of the billing document for the debit memo requests in this app. To preview the billing document, select a debit memo request in the list, and choose Preview Billing Document. The preview is displayed in a new window.
• You can now add debit memo request items by referencing a sales order or an invoice. You can do so by selecting the Create with Reference button above the item table. For more information, see the Items Table.
• You can now create, change, or display manual debit memo requests (document type DMR4) in this app. You can create them concerning a billing document, or without reference. Manual debit memo requests can only be used within the project-based services scenario.

 Picture 3: Empower internal sales representatives through increased functionalities in debit memo request processing.

For more information, see Manage Debit Memo Requests - Version 2.

SAP Fiori app “Manage Credit Memo Requests - Version 2”: Item Creation with Reference, Preview of Billing Documents

Business Background

A Credit Memo Request is a document used in sales process management to ask for a credit or adjustment to a customer's account. It is usually given by a seller to show that a credit will be given to the customer's account because of reasons like returned items, differences in pricing, or any other situation where the customer is owed a credit.

Key Features

The “Manage Credit Memo Requests - Version 2” app has been enhanced with the following features:

• You can now display a preview of the billing document for the credit memo requests in this app. To preview the billing document, select a credit memo request from the list, and choose Preview Billing Document. The preview is displayed in a new window.
• You can now add credit memo request items by referencing a sales order or an invoice. You can do so by selecting the Create with Reference button above the item table. For more information, see the Items Table.
• You can now create, change, or display manual credit memo requests (document type CMR4) in this app. You can create them with reference to a billing document, or without reference. Manual credit memo requests can only be used within the project-based services scenario.

 Picture 4: Empower the internal sales representative with more functionalities in credit memo request processing.

For more information, see Manage Credit Memo Requests - Version 2.

Integration

Business Background

Integrating SAP S/4HANA Cloud Public Edition with external systems via new APIs based on RAP and OData V4 offers compelling advantages for modern applications:

• RAP (Rapid Application Development): Simplifies development, allowing faster implementation of business logic.
• OData V4: Widely adopted for RESTful APIs, offering improved support for complex data structures and enhanced security.
• Interoperability: Easily consumed by various clients and platforms, promoting integration of different systems.
• Scalability and Performance: Designed for large-scale applications with efficient data handling and clustering support.
• Developer Productivity: Provides UI controls, model-driven development, and flexible data retrieval, enhancing productivity.

Key Features

With this 2408 release for SAP S/4HANA Cloud Public Edition, we deliver the basic scope for the following interface:

Sales Contracts OData V4 API

• Provide the initial version of the sales contract OData V4 API to create, update, read, and delete the sales contract and its entities, including:
• Sales contract header, Sales contract item
• Price elements (sales contract header and item)
• Text (sales contract header and item)
• Use the sales contract OData V4 API together with existing sales contract APIs to fulfill different integration use cases to operate sales contracts in SAP S/4HANA Cloud Public Edition.

For more information, see Sales Contract (A2X, OData V4).

Preliminary Billing Document OData v4 API

This OData V4 API, which offers both synchronous and asynchronous processing, makes the data of preliminary billing documents available through its header, item, partner, and text entities. You can extend it with custom fields via key user extensibility.

With this new 2408 release, we deliver the basic scope of the preliminary billing document OData v4 API for managing preliminary billing documents:

• Operations: read and update
• Actions: CreateFromSDDocument, reject, SetStatusToFinalized, SetStatusToInProgress, and WithdrawFromApproval
• Entities: header, item, partner, and text
• Custom field extensibility 

For more information, see APIs for Preliminary Billing Document.

Billing Document Request OData v4 API

This SOAP-based web service enables external consumers to create billing document requests by sending billing data into your SAP S/4HANA Cloud system. Once the data is persisted in the form of billing document requests, it can be converged with billing data from other internal and external sources to create combined customer invoices. These can be used to invoice customers for a variety of products and services within a single document.

Whit this new 2408 release, we deliver the basic scope of the billing document request OData v4 API for managing billing document requests:

• Operations: read and delete
• Actions: CreateFromExternalData and reject
• Entities: header, item, partner, and text 

For more information, see APIs for Billing Document Request.

Billing document OData v4 API

Billing documents collectively refer to customer invoices, credit memos, debit memos, pro forma invoices, and related cancellation documents. This inbound OData v4 service makes billing document data in your system available through its header, item, and partner entities.

With this new 2408 release, we deliver the basic scope of the billing document OData v4 API to operate billing documents, including basic billing document entities:

• Operations: read and update
• Actions: CreateFromSDDocument, CreateCancellationDocument, and PostToAccounting
• Entities: header, item, partner, and text
• Custom field extensibility 

For more information, see APIs for Billing Document.

Returns Order OData v4 API

You can use the OData V4 API Customer Return (A2X) to manage standard customer returns by creating, reading, and updating returns orders for order type CBAR from external systems. In addition, you can delete single entities (such as items) in return orders.

You can choose whether you want to process your requests in synchronous or asynchronous mode.

With this new 2408 release, we deliver the basic scope of the Returns Order OData v4 API to operate returns orders, including basic returns order entities:

• Returns order header,
• Returns order items,
• Pricing elements (header and item),
• Partner entities (header and item),
• Text (header and item).

For more information, see Customer Return (A2X, OData V4).

 Picture 5: Leverage the new features offered in the ABAP RESTful application programming model framework.

Remark

Stay tuned on the progress of this function as in future releases, SAP will continuously add more features and enhancements here.

Early Adopter Care Service

SAP offers a range of programs that allow customers to influence SAP software development decisions and adopt innovations early on.

And here we are searching for customers who want to evaluate the Assisted Object Creation of Customer Return.

Here you can test the following new features and give your feedback to SAP, which allows you to influence the features for customer returns.

The new features for evaluating the Assisted Object Creation of Customer Returns are:

You can create return orders with the aid of input recommendations.

• Based on the data you’ve entered in the returns order; the system provides input recommendations for related fields.
• For example, when you enter a sold-to party, the system automatically recommends the best-matched returns order reason.
• When you enter the product, the system recommends the return reason, supplier, refund data, and other related information.

 Picture 6: Register and experience the latest AI features in SAP S/4HANA Cloud Public Edition and influence upcoming AI developments.

For more information, see Get Involved Early and Customer Returns Influence Program.

Remark

Beta testing provides you with early access to SAP software to test and see how it fits your business requirements. Beta shipments are provided under a Test and Evaluation Agreement (TEA) and can be used for testing purposes only. Productive usage is not allowed and is not supported under the maintenance and support agreement.

Don’t hesitate to leave a comment and check out our community page to ask your questions and engage with the experts. Follow the PSCC_Enablement tag to stay up to date with our latest blog posts.

For more information about Sales, please see the Link Collection for Sales here

Follow us on @SAP and #S4HANA, and myself on LinkedIn and X.

📽️ Watch the Replays of Our SAP S/4HANA Cloud Public Edition 2408 Early Release Series!

From July 8 to July 12, we hosted a series of 20 compelling live sessions to highlight the exciting innovations shipped with the SAP S/4HANA Cloud Public Edition 2408 release. Did you miss the live sessions? We've got you covered! Take advantage of the entire series or pick and choose the sessions most relevant to you. You will find a 50-minute-long recording and a presentation for Sales as well as 19 other topics of interest. Don't miss this chance and watch them on demand–anywhere, anytime.

🔎Find All of Our Assets

SAP S/4HANA Cloud is the foundation of the intelligent, sustainable enterprise and is an innovative, robust, and scalable ERP. We at Cloud ERP Product Success and Cloud Co-Innovation offer a service as versatile as our product itself. Check out the numerous offerings our team has created for you below: