<aside> <img src="notion://custom_emoji/7f3a86c4-0e4f-8193-9274-00038d571f22/294a86c4-0e4f-8053-a481-007af138f2db" alt="notion://custom_emoji/7f3a86c4-0e4f-8193-9274-00038d571f22/294a86c4-0e4f-8053-a481-007af138f2db" width="40px" />

This page explains Pricing Procedure Determination in S4HANA for anyone working with Sales and Distribution. In short, it decides which pricing logic applies to a sales document based on Sales Area, Customer Pricing Group and Document Type. It matters because SAP cannot calculate a single penny of pricing without it. Use it when you want predictable commercial behaviour and avoid ignoring it unless you enjoy orders with blank price fields and a rising sense of dread.

</aside>


Pricing Procedure Determination is SAP’s way of selecting which pricing recipe to use for a specific sales scenario. You may have ten pricing procedures in your system, but only one of them should fire for a given order.

SAP picks the right one by checking:

Put those together and SAP knows exactly which discounts, surcharges, taxes, freight and conditions apply.

Forget this assignment and SAP refuses to calculate pricing at all.


The Principle

A Pricing Procedure is a structured list of condition types.

Pricing Procedure Determination decides which list SAP should use in which situation.

It is the link between commercial logic and transactional behaviour.

It prevents hardware pricing being applied to subscriptions, prevents wholesale discounts appearing on retail orders and prevents service fees being calculated for products that don’t require them.

In plain English:

SAP will not guess your pricing logic.

You need to tell it.