Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
cancel
Showing results for 
Search instead for 
Did you mean: 
MarceGiovanetti
Product and Topic Expert
Product and Topic Expert

286873_GettyImages-938516428_small.jpg

 

Agility and flexibility to adopt innovations are great values that businesses must have. Using SAP S/4HANA tools to design business processes ensures the company assumes quick innovations.

This blog summarizes for you the tools for SAP S/4HANA Sales Price management that allow faster software deployment and easier adoption of SAP innovations and new business requirements.

We can start with the usual customer requirements regarding managing sales Prices:

  • Transparency, simplicity, and agility to maintain sales prices
  • Approval for release prices
  • Integration with other systems
  • Initial Price Migration.
  • Customs fields
  • Events
  • Analytical reports
  • Authorizations

Let's review the tools that SAP S/4HANA offers to us to cover each requirement.

 

Transparency, simplicity, and agility to maintain sales prices.

Available since the S/4HANA 2020 release, the SAP Fiori app. Manage Prices – Sales (ID F4111) enables the following actions:

  • Search for existing condition records with filter criteria.
  • Create one or more condition records simultaneously.
  • Define pricing scales for condition records.
  • Send one or more condition records for approval.
  • Copy selected condition records to new ones.
  • Edit condition records.
  • Import condition records.
  • View import history.
  • Delete selected condition records.

You can see more detail in these videos:           

Available since the SAP S/4HANA Cloud Private Edition release 2023 FPS1 release, SAP Fiori app. Manage Tax Rates - Sales  ( F6972 ) can be used to manage sales taxes.

 

Approval for release prices

As of the SAP S/4HANA 2022 release, you can design custom workflow processes. This include defining preconditions under which a price must be approved and selecting approvers who will receive the approval request for the price in the SAP Fiori app—my Inbox (ID F0862). All approval request notifications are accessible in the SAP Fiori Launchpad.

The workflow is easy, flexible, and intuitive to configure, the business owner have the master key to modify it according to their needs of the moment (for example, change of approvers or prerequisites).

For more detail please, see in How to manage Workflows for Sales Price in SAP S/4HANA ? | SAP Blogs

Additionally, you can route requests to teams instead of specific individuals, this allows you to have independency between the workflow configuration and the Teams configuration. For more details on this topic, you can see in:    Flexible Workflow using Responsibility Management in SAP S/4HANA

 

Integration with other systems.

Best practices for integrating with other system is through SAP delivered standard Integrations on standard APIs (OData and SOAP). For Sales Prices Master Data, you have these APIs:

API

Technical Name

Description

Condition Record for Pricing in Sales

API_SLSPRICINGCONDITIONRECORD_SRV

This synchronous inbound service enables you to create, read, update, and delete condition records for pricing that are used in Sales.

Condition Record for Pricing in Sales - Replicate

CO_SDCM_ESR_SALES_PRICING_COND_SPRX

This asynchronous outbound service enables you to replicate condition records for pricing that are used in Sales to external systems.

 

For more details regarding APIs for Sales Prices, you can review APIs for Sales | SAP Help Portal

 

Initial Price Migration.

SAP S/4HANA customers can take advantage of reliable migration approaches built into SAP S/4HANA using the SAP S/4HANA Migration Cockpit together with a set of predefined data migration objects. You can see the migration object available for Sales Prices in SAP S/4HANA  here: Condition record for pricing (general template) | SAP Help Portal

As I shared with you, in the Fiori app SAP Fiori app. Manage Prices – Sales ( ID F4111 )you can import condition records from Excel. You can use this feature to facilitate initial migration data loads.  Please note that the recommended maximum file size using this load option is limited to 3 MB.

 

Customs fields

You can create your own custom fields and enhancement implementations to customize applications and their UIs, reports, e-mail templates, and form templates.  For Sales Prices case, you can create a custom field and use it as a field in the condition records.

For example, I had created this field to use in a condition record:

MarceGiovanetti_0-1710266796318.png

In my case, I need the field in the “Manage Prices app.” and “Tax Rates – Sales app.” I also want to use them in the template for importing condition records, so I enabled them like this:

MarceGiovanetti_1-1710266796325.png

After these settings, you will find the custom field in the Catalog for Pricing in Sales:

MarceGiovanetti_2-1710266796328.png

 

MarceGiovanetti_3-1710266796330.png

And here, used by a custom condition table:

MarceGiovanetti_4-1710266796332.png

 

Events

A business event is a message sent to notify a system consumer that an SAP Object Type has changed. That message will be manipulated by a middleware ( for example CPI or Event Mesh in BTP ) and from there an action is generated on an other platform.

Sales Pricing Condition Record Events has the business object Sales Pricing Condition Record Events and can trigger the following events:

Created / Changed / Deleted When a condition record is created/changed/deleted, the event is raised and informs the Condition record, condition type, and other condition records for which the validity period is altered due to an overlap with the condition record for which the event was raised.

ValdtyPerdChanged This event is raised when the validity period of a condition record is changed. Inform Condition record, condition type, the valid-to-date of the condition record and the valid-from date of the condition record.

AmountChanged This event is raised when the condition amount of a condition record is changed. Inform the Condition record, condition type, the condition amount of the condition record and the currency key for the condition amount.

RatioChanged This event is raised when the condition percentage of a condition record is changed. Inform the Condition record, condition type, the condition percentage of the condition record and a percent sign.

For more information about business events: Business Events on SAP Business Accelerator Hub.

 

Analytical reports.

The SAP Fiori Pricing Elements - Flexible Analysis app. helps the Pricing Specialist to review the uses of the condition records in sales documents. The app allows the user to focus on their specific analytic needs.

In this example, we want to review Discounts given to customers in the last 400 days in billing documents:

MarceGiovanetti_5-1710266796337.png

At the top right, you have filters to use. In our test case, we need only the last 400 days. You can also configure dimensions in the app on the left side and rows and columns for your analysis.

In our test case, we want to include ( drag and drop ) as rows: Sales Organization, condition type, condition category (to filter only discounts), and condition document (to filter only invoices).

As measure: The condition value.

MarceGiovanetti_6-1710266796346.png

The CDS views (either released by SAP or customized) are used to expose business data - stored in database tables - in a format that is based on business semantics making it easy for the users to consume.  A custom analytical app may be used in some case cases to provide a custom view of this data. For more details regarding CDS views you can see CDS Views for Sales

 

Authorizations.

As of version S/4HANA 2023 Cloud Private Edition, you can configure the appropriate role and authorization to access the information in the price element area of the respective documents. So, you can define authorization objects that can display and change condition records across sales documents.

For example you can, in order to restrict the ability of Sales Representative to change customer discounts in sales orders. You may alternatively grant the Sales Manager the necessary permissions to change customer discounts in sales orders.  The resulting views for each role when changing a sales orders will be the following:

Sales Manager                                                                     

MarceGiovanetti_7-1710266796349.png

 

 

 

 

 

 

 

 

 

 

 

 

Sales Representative

MarceGiovanetti_8-1710266796352.png

 

 

 

 

 

 

 

 

 

 

 

 

 

 

For more detail, you can see an example here: Example for Setting Up Role-Based Access | SAP Help Portal

 

We have reached the end of the blog post and I hope it was helpful for you!

I'm looking forward to your feedback and thoughts or clarification questions you may have in the comment section below.

Thank you,

Brought to you by the SAP S/4HANA RIG team.