SAPFree worksheetPDF, Excel, Word exportSAP ECC / S/4HANA

SAP Pricing Procedure Design Worksheet: Steps, Condition Types and Net Value

A pricing procedure is the ordered list of condition types that SAP walks through to calculate a net price. Designing it on paper first saves a lot of rework, because step order, subtotals and account keys all depend on each other.

Download:

Step	Cond type	Description	Class	Calc type	Base value	Rate %	Fixed amount	Condition value
								$1,000
								-$50
								-$20
								$25
								$172

Net value plus tax

$1,127

Average condition value

$225

Quick sanity figure across all lines.

Condition types shown are common SAP standard examples. In the real procedure, the base for each step comes from the From and To columns and the subtotal. This sheet keeps the base as an input so you can test the arithmetic before configuring.

Pricing procedure walkthrough

Optional: send us an exported pricing procedure and we will return a plain-language explanation of each step and a list of risky spots.

Optional. The tool and every export work without this. No spam.

How to use the worksheet

Start from your pricing requirements: list base price, customer and material discounts, surcharges, freight and tax in the order they should apply. Enter each as a row, set the class and calculation type, and type a test base and rate. The condition value column computes the amount, and the total gives a quick check of the final value. Export the sheet to Excel and attach it to the functional specification.

One row per step in the pricing procedure
Use negative rates for discounts in this sheet
Test tax on the discounted base, not the list price
Add statistical rows for cost and margin if needed

The condition technique behind it

SAP pricing uses the condition technique. A condition type, for example PR00 for price, is found through an access sequence, which lists condition tables in priority order such as customer and material, then price list and material, then material only. The pricing procedure, assigned in OBYZ and found by sales area, customer pricing procedure and document pricing procedure, controls the step, from and to levels, subtotals, requirements and account keys used for FI posting.

Condition type holds calculation type and plus or minus sign
Access sequence picks the first valid condition record
Pricing procedure defines order and subtotals
Account keys link conditions to revenue and discount GL accounts

Worked example

A list price of 1,000 gets a customer discount of 5 percent and a material discount of 2 percent, both calculated on the list price, giving 950 less 20, or 930. Add a freight surcharge of 25 and the taxable net is 955. Tax at 18 percent on that base is 171.90, so the document total is 1,126.90. If you compute the second discount on the already discounted value, the result changes, which is why the from step column matters.

Common design mistakes

Teams often leave out subtotals, which makes statistics and tax basis hard to read later. Another common problem is forgetting the manual flag on conditions users must override. Copying RVAA01 and adding conditions without a requirement routine can also fire pricing in documents where it is not valid. Always test the procedure in VK13 and in a real order, including a case with no condition record, to see the pricing error message behavior.

Frequently Asked Questions

How is a pricing procedure determined for a sales document?

SAP combines the sales area, the customer pricing procedure from the customer master, and the document pricing procedure from the sales document type. That combination points to one pricing procedure in the assignment table maintained in OBYZ or SPRO.

What is the difference between a condition type and a condition record?

A condition type is the configured definition, such as PR00 or K007, with its calculation type and rules. A condition record is the actual data, such as price 100 per unit for customer X and material Y valid from a date, created in VK11.

What do the From and To columns do?

They define the range of steps SAP sums to get the base value for the line. For a percentage discount, From and To normally point at the gross price step. For tax they usually point at a net subtotal line.

Can I use this for S/4HANA?

Yes for the design thinking. S/4HANA keeps the condition technique and pricing procedures, though it adds a new pricing engine and some changed condition tables. Check your release notes for the exact tables and transactions before building.

If your pricing procedures have grown over years and nobody can explain them any more, we can build a read-only agent that explains the procedure for any order line in plain language.

Talk to an Expert Explore More Free Tools

Related Tools

SAP

More SAP tools

See all

Back to All Tools