Sales in SAP S/4HANA Cloud 2202.1

In late 2021 and continuing into 2022, SAP will significantly accelerate the delivery of new business innovations. Coming from a quarterly release cycle, we will implement continuous feature delivery through monthly updates. With this approach, our customers have the option to access new capabilities in a nondisruptive manner every month.

Twice a year, we will provide the usual system upgrades – entailing the latest, and more substantial developments.

SAP S/4HANA Cloud customers have received 2202.1 – the first update based on the current 2202 release. This blog provides you with delta information on new, changed, or deleted features, as well as legal changes for SAP S/4HANA Cloud 2202.1 for Sales.

To name just a few highlights:

  • Sales Order Management and Processing: Type-Ahead Improvements for Fields
  • Cloud BAdIs for Sales Order/Returns Order Inbound EDI Processing
  • Message Monitoring for Sales Scheduling Agreements
  • Manual Completion of Imports and Import Items in Sales Document Import apps
  • … and more.

Picture 1: SAP S/4HANA Cloud: Release and Update Cycle.
This is the current state of planning and may be changed by SAP at any time without notice.

For more information, see:

  • SAP S/4HANA Cloud 2202: Release Information Note: 3108326
  • SAP S/4HANA Cloud 2202: Release Restriction Note: 3109182

In SAP S/4HANA Cloud, you are able to represent the presales business processes using sales inquiries and sales quotations.

  • Sales inquiries are requests from customers for information about the purchasing conditions (such as price and availability) for certain goods or services.
  • Sales quotations, in turn, are the responses to sales inquiries and represent legally binding offers to customers for the supply of goods or the provision of services under specific conditions.

And at the end, the customers can respond to a sales quotation with a purchase order, which in turn triggers a sales order.

Now with SAP S/4HANA Cloud 2202.1, in the Manage Sales Quotations app, you can now use view settings to add the order reason field as an additional column in the sales quotation list. This field can also be used as an additional filter by adapting the filter bar and selecting it from the filter list.

Picture 2: Order reason field as an additional filter.

With the SAP S/4HANA Cloud 2005 release, we improved the sales orders process with a new option to create sales orders by uploading spreadsheets with the required data. You can use this process when creating sales orders as a result of mass upload capabilities.

New with SAP S/4HANA Cloud 2202 is the possibility to also import Sales Scheduling Agreements.

For more information, see my post blog with a demo here.

With SAP S/4HANA Cloud 2202.1, you can now do the following:

  • You can enable custom fields for this app. If key users have enabled custom fields for this app, you can see these fields in the field list of the import template. For more information, see App Extensibility: Import Sales Scheduling Agreements.
  • If a sales scheduling agreement contains multiple items, you now only need to enter header data for the first item in your spreadsheet file. Previously, you needed to enter the same header data for each item.

In the Message Monitoring app, you can use filters to search for messages that are received from the Delivery Schedule of Sales Scheduling Agreement – Receive, Update (B2B) service (SchedgAgrmtDlivSchedule_In).

With this 2022.1 release, you can use the following new filters:

  • Delivery Schedule (PurchasingDeliveryScheduleID at header level)
  • Release Type (SchedulingAgreementReleaseType)

Delivery Schedule of Sales Scheduling Agreement – Receive, Update (B2B)

This asynchronous inbound service enables you as the supplier using SAP S/4HANA Cloud to automatically create and update delivery schedules of sales scheduling agreements. It’s based on the SOAP protocol with namespace http://sap.com/xi/EDI/Supplier.

This service is published on the SAP API Business Hub. For more information about APIs, see APIs on SAP API Business Hub.

Some filter fields in the Manage Sales Orders app and some fields in the Process Sales Orders app now offer improved search-as-you-type functionality to give you more accurate proposals.

This improvement affects the following fields:

Filter fields in the Manage Sales Orders app and header fields in the Process Sales Orders app:

  • Sales group
  • Sales office

Item fields in the Process Sales Orders app:

  • Shipping point
  • Storage location
  • WBS element
  • Plant
  • Payment method
  • Item category

Picture 3: With the Manage Sales Orders app, you can search for sales orders according to your filter criteria and display them in a list.

With SAP S/4HANA Cloud 2105 release, we introduced the mass changes for sales documents. With SAP S/4HANA Cloud 2202 release you can use the Mass Change of Sales Documents SAP Fiori app to access and make changes across all types of sales documents in one step. For example, you can make changes to multiple sales orders and sales quotations at the same time.

Remark: You find here a demo concerning the ability to trigger mass changes at a header and item level across multiple sales document categories (including audio).

With SAP S/4HANA Cloud 2202.1, the filter field for partner function in the Mass Change of Sales Documents app now has improved search-as-you-type functionality. As you type a value in the filter field, the system proposes search values. Now the characters or digits identical to your input are highlighted in bold.

Picture 4: Improved search-as-you-type functionality.

With this app, you as an internal sales representative can create sales orders from an XLSX spreadsheet file.

You can now perform a corrective import in the following apps:

  • Import Sales Orders
  • Import Sales Scheduling Agreements

When an import contains errors (indicating that document creation has failed or partially failed), you can revise your file data and perform a corrective import on the object page of the import. The corrective import targets previously failed records only.

Picture 5: Create sales scheduling agreements by uploading spreadsheets with the required data using the SAP Fiori app Import Sales Orders.

Effects on System Administration

The corrective import will not automatically be available in your system as of SAP S/4HANA Cloud 2202.1 but requires that you activate the feature Corrective Import for Failed Import Items (CORRECT_UPLOAD_IMPORT_DOCUMENTS).

For more details on the activation of features, see Activate New Features.

You can now set imports or import items as completed in the following apps:

  • Import Sales Documents
  • Import Sales Orders
  • Import Sales Scheduling Agreements

When an import contains errors (indicating that document creation has failed or partially failed) but you don’t want to continue with further processing, you can manually complete the import or any failed import item.

Picture 6: Set as Complete the import or any failed import item.

Effects on System Administration

The manual completion of imports and imports items will not automatically be available in your system as of SAP S/4HANA Cloud 2202.1 but requires that you activate the feature Manual Completion of Imports and Import Items (SD_SLS_DOC_IMPORT_MANUALLY_COMPLETE).

For more details on the activation of features, see Activate New Features.

With this asynchronous outbound SOAP service, you can replicate sales orders in bulk to external systems.

Sales orders consist of a header that contains data that is relevant for all sales order items (for example, the billing company code) and one or more items. You can apply any of the filters provided or replicate all existing data.

The replication logic is handled by the data replication framework (DRF).

Now with SAP S/4HANA Cloud 2202.1, you can use specific replication mode parameters in the Communication Arrangements app. For the pricing element replication, you can now choose to replicate price conditions, subtotals, and specific field properties. These field properties tell you if you can delete or change the pricing element node or specific fields in it.

In the context of the integration with external buyers, this inbound service enables you as the supplier using SAP S/4HANA Cloud to automatically create, update, and cancel sales orders and customer returns. If there are errors, business users can make manual changes before reprocessing the message.

This service is published on the SAP API Business Hub. For more information about APIs, see APIs on SAP API Business Hub.

Previously, if you received multiple texts of the same text ID and language, the processing of the EDI message was stopped with an error. With this feature, the error-handling behavior is different. If you receive multiple texts of the same type and language, or of different types but mapped to the same ID, these texts will be merged into one text containing several paragraphs in the sales order or return order (see the example below). This feature ensures there is no missing information from buyer to supplier.

For related information about the text, see SAP Help Portal here.

The Sales Order business object has been enabled with the following new events on header and item level:

  • OvrlSDProcStsChgd: This event is raised when the overall processing status of a sales order is changed.
  • ItmSDProcStsChgd: This event is raised when the overall processing status of a sales order item is changed.

These events will be available on the SAP API Business Hub with SAP S/4HANA Cloud 2208.

For related information about events, see SAP Help Portal here.

As a key user, you can extend the SOAP service Sales Order/Customer Return – Create, Update, Cancel according to your business needs.

Previously, you can only define text mapping with the limited standard text types. With the Business Add-Ins (BAdIs) Mapping of Text Types for Header Texts in EDI Inbound Processing (EDI_SD_INB_ORDER_TEXT_HEADER) and Mapping of Text Types for Item Texts in EDI Inbound Processing (EDI_SD_INB_ORDER_TEXT_ITEM), you can now implement your own custom logic to define the mapping between text types and text IDs for the header and item texts that you receive via the API OrderRequest_In. This offers more flexibility for suppliers to manage their texts on sales orders and returns orders

Additional Details

In the Custom Logic app, you can implement custom logic for the BAdIs in business contexts Sales: Sales Document and Sales: Sales Document Item. For more information, see the example logic and BAdI documentation in the Custom Logic app.

You use follow-up activities to specify the next step in the logistical processing of a returns order item. While you are editing a returns order, you can select a follow-up activity for the different items. Depending on the follow-up activity you select, you may have to specify additional information, such as the supplier. The system then automatically creates the relevant follow-up documents, based on the activity that you have specified.

You can now use the follow-up activity In-House Repair (Service) (0026) if you choose the Follow-Up Activities button in a returns order by using the Manage Customer Returns app.

In previous releases, this follow-up activity is only available when you navigate to the Create Customer Return app or the Change Customer Return app from the returns order list in the Manage Customer Returns app. If you select this follow-up activity for a returns order, the system triggers the creation of an in-house repair in Service.

Picture 7: Trigger an in-house repair in Service for the returned goods.

Additional Detail.

In-House Repair (Service) (0026): The in-house repair contains the repair objects that correspond to the individual returned materials (represented by a serial number).

Optionally, you can configure an automatic goods movement from the returns stock to the stock for in-house repairs in the configuration activity Specify Storage Locations for Follow-Up Activities in your configuration environment.

The system creates the delivery of a return, posts the receipt of the goods, and creates the inspection document that contains the logistical follow-up activity. In addition, the system creates an in-house repair and posts the goods movement if the storage location for in-house repairs has been configured.

For more information about creating in-house repairs as a follow-up activity for customer returns, see Create In-House Repairs in Customer Returns.

You can use this app to gain an understanding of the monthly sales volume.

Key Features

  • You can view the key figures as a graphic or a table on a monthly basis.
  • You can drill down to view detailed information for selected sales organizations, sold-to parties, bill-to parties, and so on.
  • You can analyze aggregated values and quantities according to product hierarchy levels.
  • You can filter the items according to various criteria, such as year/month, sales organization, sold-to party, and bill-to party.
  • You can change the displayed ID or description.
  • You can save your selection as a variant.

The following fields are now available in the Sales Volume – Flexible Analysis app:

  • Higher-level item
  • Pricing reference material of the main item

These fields are useful for analyzing sales data related to bills of material (BOM).

Picture 8: Gain an understanding of the monthly sales volume.

The scope item Automation of Order-to-Invoice with Ariba Network (4A1) seamlessly connects SAP S/4HANA Cloud with Ariba Network for suppliers and automates the sales processing from creating sales orders to sending customer invoices.

When a purchase order is generated for you as a supplier in Ariba Network, a sales order is created or updated in SAP S/4HANA Cloud. Your SAP S/4HANA Cloud system also sends order confirmations, advanced shipping notifications, and customer invoices to Ariba Network in electronic forms when you complete the preceding steps.

All data is routed through SAP Ariba Cloud Integration Gateway.

For additional information, see SAP Help Portal here.

With this SAP S/4HANA Cloud 2202.1 release, the batch information in the advanced shipping notification in your SAP S/4HANA Cloud can be transferred to your Ariba Network system.

Picture 9: Automation of Order-to-Invoice with Ariba Network.

Additional Details

You use the Outbound Delivery – Notify (B2B) service (DeliveryRequest_Out) to send outbound messages for advanced shipping notifications. In this service, the following fields in node DeliveryItem can now be transferred to Ariba Network:

Field Description
Batch Batch number
BatchBySupplier Batch number which belongs to supplier
ManufactureDate Date of manufacture
ShelfLifeExpirationDate Shelf life expiration or best-before date

Thanks for reading this blog post. Stay tuned!

If you want to learn more and actively engage with SAP subject matter experts on SAP S/4HANA Cloud, join our SAP S/4HANA Cloud Customer Community. This platform which is available to SAP S/4HANA Cloud customers and partners has a clear mission: deliver an interactive community to engage with one another about best practices and product solutions.

Please stay tuned – we are about to release a community landing page on continuous delivery under the topic page of SAP S/4HANA Cloud. See here.

For more information on SAP S/4HANA Cloud, check out the following links:

  • SAP S/4HANA Cloud release info here
  • The Link Collection for Sales here
  • Latest SAP S/4HANA Cloud Release Blog Posts here and previous release highlights here
  • Product videos on our SAP S/4HANA Cloud and SAP S/4HANA YouTube playlist
  • SAP S/4HANA PSCC Digital Enablement Wheel here
  • Early Release Webinar Series here
  • Inside SAP S/4HANA Podcast here
  • openSAP Microlearnings for SAP S/4HANA here
  • Best practices for SAP S/4HANA Cloud here
  • SAP S/4HANA Cloud Community: here
  • Feature Scope Description for Sales here
  • What’s New here
  • Help Portal Product Page here
  • Implementation Portal here

Follow us via @SAP and #S4HANA, or myself via @VoglerChrist and LinkedIn