You sit down to create a purchase order for a vendor you’ve used many times. Most of the time it is simple. The price is added automatically, discounts are applied and you’re done in no time. But today, something doesn’t look right. The price is off. The discount isn’t showing. Freight hasn’t been added. Now you’re stuck going back and checking vendor data, condition records, and system settings just to figure out what went wrong.
If you’ve spent any time working in SAP MM, this probably sounds familiar. And in most cases, the root of the problem is how the SAP MM pricing procedure has been configured. . If you’re new to SAP, our guide on SAP for non-technical beginners fits perfectly before diving deeper into SAP MM.
That’s why we need to understand how SAP actually determines pricing behind the scenes. If you know what’s going on in the background, it’s a lot easier to identify problems and keep everything on track.
In this blog, we’ll walk through the SAP MM Condition Technique, explain it in simple terms, go step by step through how pricing is calculated, and look at a real example to tie everything together.
What is SAP MM Pricing Procedure?
Every purchase order in SAP goes through a pricing step before it’s finalized. When you are buying raw materials, office supplies or equipment, SAP has to calculate the proper pricing according to a number of rules. Here, the SAP MM pricing procedure will be used.
This creates consistency of pricing between vendors and documents. It also saves time and avoids the mistakes that might be made when computations are done by hand.
SAP’s own documentation describes this the same way: the calculation schema in purchasing exists specifically to define the order in which condition types and subtotals are processed to arrive at a net value, see SAP Help Portal: Pricing Procedures. Every standard SAP install ships with predefined procedures and condition types out of the box, which you can use as-is, adapt, or replace entirely depending on your business needs. If you’ve spent any time working in SAP MM or are planning to enroll in SAP MM training in Bangalore, this scenario probably sounds familiar.
Where Is It Used?
SAP MM pricing procedure is used in each step of the purchase process.
Request for Quotation (RFQ)
During RFQs vendors send their quotes. SAP assists in comparing them using the same price rationale. This makes it easier to judge which offer is best.
Purchase Orders
This is where you’ll use them most, for setting prices. The buyer first chooses a seller and a material. Then SAP gets the proper price criteria and calculates the total value.
Contracts
For long-term contracts, prices are usually pre-negotiated. The pricing procedure ensures those agreed prices are applied whenever a PO is created with reference to the contract.
Scheduling Agreements
If a company regularly buys the same materials, scheduling agreements are used. The pricing procedure makes sure each release order follows the agreed pricing without needing manual updates every time.
Why Organizations Use Pricing Procedures
Procurement today isn’t just about buying things. It covers vendor agreements, logistics costs, taxes and changing prices. The pricing procedure helps to:
- Increase accuracy.
- Reducing manual effort.
- Vendor specific pricing support.
- Ensuring the implementation of corporate policies.
- Simple sustainable price over time.
Buyers would have to figure it all out manually, which would be time-consuming and prone to error.
Understanding the SAP MM Condition Technique
The SAP MM Condition Technique is really the motor driving the price procedure. It tells SAP where to find pricing information, what to pick and how to calculate the final amount.
Think of it like a chain. Each part has a part. If any one piece is missing or not adjusted correctly, pricing will not operate as anticipated. The five basic ingredients are:
- Condition Tables
- Access Sequences
- Condition Types
- Pricing schema in SAP
- Schema Determination
Condition Tables
Condition tables define where SAP should look for pricing data. They specify the pricing search fields. SAP, for example, checks:
- Vendor
- Material
- Purchasing Organization
- Plant
- Material Group
These fields act as search criteria.
So for example, if Vendor XYZ is supplying Material A to Purchasing Org 1000, then SAP uses that combination to retrieve the proper pricing data.
SAP provides standard tables, but you can also create custom ones if needed.
Access Sequences
Condition tables alone aren’t enough. SAP also needs to know the order in which to search them. That’s where an access sequence sap comes in. It works like a search path.
For example:
- First, SAP checks Vendor + Material.
- If nothing is found, it checks Vendor + Material Group.
- Then Vendor only.
- And finally, a general record.
This way, SAP tries to find the most specific price first and falls back to more general ones if needed.
There’s also something called the Exclusive Indicator. If it’s turned on, SAP stops searching once it finds a valid record. If not, it keeps checking other tables.
Condition Types
While condition tables and access sequences help find the data, condition types MM define what that data actually means. Some common ones are:
Condition Type | Purpose |
PB00 | Gross purchase price |
PBXX | Manual price |
RA01 | Discount |
FRA1 | Freight charges |
MWST | Tax |
Pricing Procedure (Schema)
Everything is tied together by the pricing schema in SAP. This controls the order of processing of the condition kinds and how the final price is determined. For example SAP could:
- Apply the base price.
- Apply discounts.
- Add freight.
- Calculate taxes.
- Arrive at the final value.
It also controls things like requirements, subtotals, and calculation methods. SAP’s documentation on the condition technique in Purchasing notes that in the standard system, calculation schema RM0000 is the one used to determine purchase price in purchasing documents, worth knowing if you’re ever tracing a pricing issue back to its source.
Schema Determination
Once the pricing procedure is set up, SAP still needs to know which one to use. That’s handled through schema determination.
SAP looks at things like:
- Vendor Schema Group
- Purchasing Organization Schema Group
Based on these, it automatically picks the right pricing procedure for the transaction. Developing expertise in SAP MM pricing procedures can also positively influence your SAP MM consultant salary as you progress in your career.
Expert Insight: Most ‘pricing procedure not found’ errors we see in support tickets aren’t actually configuration bugs; they’re schema determination mismatches that were never re-tested after a vendor or purchasing org was reassigned. Teams that build a habit of re-running the Health Check after any org-structure change save themselves the 2 a.m. debugging sessions.
Step-by-Step SAP MM Pricing Procedure Using the Condition Technique
Ok, now that we’ve got the basics down, let’s tie it all together and see how it actually plays out in real life.
Step 1: Create the Condition Table
First you need a condition table.
Here is where SAP determines what it wants to search for in a pricing search. For example you can tell SAP to check at Vendor, Material and Purchasing Organization.
So every time someone makes a purchase order SAP will check to see whether there is a matched record based on those fields.
Step 2: Create the Access Sequence
Once your condition table is ready, you connect it to an access sequence.
This basically tells SAP how to search. For example:
- First, try Vendor + Material.
- If nothing is found, try Vendor + Material Group.
- Still nothing? Try Vendor just.
So in this approach SAP always tries to get the most particular price first and then falls back to something more general.
Step 3: Configure the Condition Type
Here you define the type of pricing element you are working with e.g. base price, discount, freight, etc.
Also here you link the access sequence so that SAP knows where it should obtain the data from.
Step 4: Define the Pricing Procedure
This is where you list all your condition types in the order they should be applied. And yes, the order really matters. A basic example is:
- Base price (PB00)
- Discount (RAO1)
- Freight (FRA1).
- Tax (VAT)
SAP processes them one by one in this order.
Step 5: Configure Schema Determination
At this point, SAP still needs to know which pricing procedure to use. That’s where schema determination comes in. You assign:
- Vendor Schema Group.
- Purchasing Organization Schema Group.
Based on these, SAP automatically picks the right pricing procedure when a purchase order is created.
Step 6: Maintain Condition Records
Now comes the part people often forget: condition records. All your configuration won’t do anything unless you actually maintain the pricing data. These records hold things like:
- Vendor price
- Discounts
- Freight charges
- Taxes
- Validity dates
And yes, these need to be updated regularly as prices change.
Step 7: Create a Purchase Order
Now imagine a buyer creates a purchase order. They enter the vendor and material, and that’s it. SAP takes over from there:
- It checks the condition tables.
- Follow the access sequence.
- Find the right condition records.
- And it applies to everything based on the pricing procedure.
Step 8: Check Automatic Price Determination
SAP displays the total price for the purchase order. The buyer can see the:
- Base price
- Discounts
- Freight
- Tax
- Final amount
Real SAP MM Pricing Procedure Example
Let’s get more real with a simple example. ABC Electronics wishes to purchase 50 laptops from Vendor XYZ.
Pricing Element | Value |
PB00 (Base Price) | ₹80,000 |
Quantity | 50 |
Gross Value | ₹40,00,000 |
RA01 (Discount) | 5% |
FRA1 (Freight) | ₹15,000 |
MWST (GST) | 18% |
Here’s how SAP works through it.
First it takes the seller and material from the purchase order and searches for condition records that match.
It finds the base price: ₹80,000 per laptop.
So:
₹80,000 × 50 = ₹40,00,000
Next, it applies the 5% discount:
₹2,00,000 discount
New Value: ₹3,80,00,000
It adds freight then:
₹38,00,000 + ₹15,000 = ₹38,15,000
Finally, the GST is decided by the tax status.
And like that SAP shows the complete breakdown in the purchase order.
How Does SAP Calculate Prices Using the Condition Technique?
Even though all of this happens in seconds, there’s a clear flow behind it.
Vendor + Material
↓
Condition Table
↓
Access Sequence
↓
Condition Record
↓
Condition Type (PB00)
↓
Pricing Procedure
↓
Discount
↓
Freight
↓
Tax
↓
Final Purchase Order Price
Each step has a role.
- Condition table → where to look.
- Access sequence → how to search.
- Condition record → actual values.
- Condition type → what the value means.
- Pricing procedure → how everything is combined. For practical exposure, consider exploring the top SAP internship providers in South India to gain hands-on experience with real SAP projects.
Common SAP MM Condition Types Used in the SAP MM Pricing Procedure
Here are some condition types you’ll see almost everywhere:
Condition Type | Purpose | Manual/Automatic | Business Use |
PB00 | Gross Price | Automatic | Base purchase price |
PBXX | Manual Price | Manual | User-entered price |
RA01 | Discount | Automatic | Vendor discount |
FRA1 | Freight | Automatic | Transportation charges |
MWST | Tax | Automatic | GST or VAT calculation. |
NAVS | Non-deductible Tax | Automatic | Tax adjustments |
GST 2.0 and Your SAP MM Pricing Procedure - What Changed in 2026
Most SAP consultants today are in the middle of a configuration cycle, right in the midst of the huge change in India’s GST structure. The GST Council changed the existing five slab structure (0%, 5%, 12%, 18%, 28%) into a simple structure principally of 5% and 18% with a 40% rate for luxury and sin items with effect from 22nd September 2025.
This is relevant for SAP MM teams for MWST condition records and not only for accounting. If the active condition records are referencing the old 12% or 28% slabs, then TAXINN and TAXINJ purchase orders will calculate the improper tax. Instead of error, you will ‘successfully’ find a stale record in your access sequence.
SAP MM consultants and buyers agenda for 2026:
- Audit FV11/FV12 tax code allocations linked to condition categories like JOCG, JOSG OR MWST for HSN codes that have shifted between slabs.
- Re-validate access sequences don’t recover 12%/28% of the system records.
- Coordinate with FI/CO teams as GST rate changes affect tax procedure OBYZ settings and not only MM condition data.
- The re-test schema is to be determined for any purchase order issued under long term contracts or scheduling agreements prior to September 2025.
Always check current slab classifications against the official government source before changing condition records. Directly refer to the Central Board of Indirect Taxes and Customs (CBIC) and the official GST portal.
Common Pricing Procedure Errors and Troubleshooting
One common issue is: “Pricing Procedure Not Found”
- This usually means schema determination isn’t set up correctly. Double-check your vendor and purchasing organization assignments.
- Another issue is missing condition records. If SAP can’t find a valid price, it simply won’t calculate anything.
- Sometimes the access sequence is wrong, so SAP looks in the wrong place. Fixing the search order usually solves it.
- And if freight or tax isn’t showing up, it’s often because the condition record is missing or inactive, not necessarily a configuration issue. In our training practice, we run every client system through what we call a Pricing Procedure Health Check, an 8-point audit covering schema documentation, access sequence logic, and condition record hygiene, before we even look at the error message. Nine times out of ten, the root cause was introduced weeks earlier by an unrelated org-structure change, not by the transaction.
Mastering The SAP MM Pricing Procedure with DigitalERPS
If you’ve ever worked with SAP MM, you know pricing can feel confusing at first. It’s not always evident how the system arrives at a final purchase price, and it can seem as if everything is happening behind the scenes. But as you start to understand how condition tables, access sequences, condition types and pricing methods fit together, it starts to make a lot more sense.
If you want to understand SAP MM effectively or want to become more confident at areas like pricing, DigitalERPS offers training that focuses on practical, real-world use. It’s an excellent method to develop a solid foundation so that everyday work in SAP doesn’t seem daunting.
Disclaimer: This article is provided for general educational and informational purposes only and reflects publicly available SAP documentation, official investor and support disclosures, and government rate notifications. It does not constitute official SAP guidance, tax advice, legal advice, or a substitute for your organization’s own SAP Basis, functional, or finance teams.
Ready to master SAP MM?
Discover more from Digital ERP Solutions
Subscribe to get the latest posts sent to your email.
