SAP MM Pricing Procedure Configuration (Calculation Schema, M/08)
sap mm pricing procedure configuration
Also searched as
- sap mm pricing procedure tcode
- sap mm calculation schema
- pricing procedure in sap s4 hana
- sap mm price condition tcode
Short answer
In MM the pricing procedure is called a calculation schema. Configure it by defining condition types, an access sequence, the calculation schema (M/08), schema groups for vendor and purchasing organization, and the schema determination; then create condition records with MEK1 and map accounting keys in OBYC. The standard schema is RM0000.
Applies to: SAP ECC 6.0 and SAP S/4HANA on-premise (purchasing price determination)
Configure MM pricing end to end
- 1Define condition types in SPRO > Materials Management > Purchasing > Conditions > Define Price Determination Process. Copy a standard type such as PB00 (gross price) or FRB1 (freight) instead of changing it.
- 2Define or reuse the access sequence and condition tables that decide how a condition record is found (for example vendor and material).
- 3Open the calculation schema (M/08), copy the standard RM0000 to a customer schema, and add condition types as steps with step number, counter, from/to, subtotal, requirement and account key.
- 4Define schema groups: one for vendors (assigned in the vendor master purchasing data) and one for purchasing organizations.
- 5Define schema determination: assign the calculation schema to the combination of purchasing organization schema group and vendor schema group.
- 6Create condition records with MEK1 (change MEK2, display MEK3) or in the info record (ME11) or contract.
- 7Create a test PO in ME21N and check the Conditions tab shows the expected steps and values. Map accrual and freight account keys in OBYC.
How the pieces fit together
The condition technique in MM works like pricing in sales. A condition type represents a price element (gross price, discount, freight, surcharge). An access sequence lists the condition tables to search for a record. The calculation schema orders the condition types into a calculation, giving net price and effective price.
The schema is chosen per purchase document from the schema groups of the purchasing organization and the vendor. This is the usual way to have different pricing logic for domestic and import vendors, for example with customs duty steps.
Condition records hold the actual values and validity. They can sit at several levels: plant and material, vendor and material, info record, or contract.
M/08 Define calculation schema (purchasing)
MEK1 Create condition records
MEK2 Change condition records
MEK3 Display condition records
OBYC Automatic postings: account keys (FR1, FR2, FR3, and so on)
ME21N Create purchase order (check Conditions tab)
Designing the schema
Start with the standard RM0000 and adjust. Typical additions are freight, insurance, customs duty and handling, each with a condition type and a step in the schema. Subtotals separate the gross and net parts so that later steps (such as freight on net value) refer to the right base.
The account key on a schema step connects the condition to financial postings. For delivery costs that should be capitalized into inventory or posted to a separate account, the account key is mapped in OBYC. A wrong key sends cost to the wrong GL account at invoice receipt or goods receipt.
Requirement routines and alternative calculation types give you conditional steps, for example a surcharge only when an import indicator is set. Use them sparingly, as they are ABAP and need maintenance.
S/4HANA notes and troubleshooting
In S/4HANA the principle is the same, with the calculation schema and condition technique still applied to purchasing. Check the simplification list for your release and for the use of the newer pricing elements in the sales side, as these may not apply to MM.
If a condition does not appear in a PO, check that the type is in the schema, the access sequence finds a record, the validity is right, and the schema determination chose the schema you edited. The pricing analysis in the PO's conditions tab shows the reason.
If values are right but the posting is wrong, the cause is the account key mapping. Check OBYC for the key, chart of accounts and valuation class.
Try it here, free
SAP Pricing Procedure Design Worksheet
An editable worksheet to lay out a pricing procedure step by step, test the net value with example numbers and export it to Excel for the blueprint.
Common pitfalls
- !Changing the standard RM0000 instead of copying it.
- !Adding a condition type to the schema but not to the access sequence, so no record is found.
- !Forgetting to assign schema groups to vendors and purchasing organizations.
- !Mapping the wrong account key in OBYC, so freight posts to the wrong account.
- !Testing with a PO whose vendor has a different schema group.
How an ERP-grounded AI assistant handles this
Procurement pricing problems are almost always a trace: which schema did this PO get, which step is missing, which record was found. A grounded assistant can read the PO conditions, the schema and the record and explain the gap in plain language, saving the consultant the pricing analysis clicks. Netray can run this read-only against your SAP data on your own infrastructure.
Frequently asked questions
What is the tcode for the MM pricing procedure?
M/08 defines the calculation schema for purchasing. Condition records are maintained with MEK1, MEK2 and MEK3. Related IMG nodes sit under Materials Management > Purchasing > Conditions.
What is the difference between a pricing procedure and a calculation schema?
They are the same concept under different names. SD calls it a pricing procedure, MM calls it a calculation schema. Both order condition types into a calculation.
Which standard calculation schema does MM use?
RM0000 is the standard purchasing schema in most systems. Copy it into a customer schema before making changes.
Why is my condition not picked up in the PO?
Check that the condition type is in the schema, the access sequence has the table that holds your record, the record is valid on the document date, and the schema determination assigned your schema.
Related
SAP Pricing Error: Condition Record Missing for PR00 in a Sales Order
The error means the pricing procedure expected a price condition such as PR00, found no valid record for the key, and the condition was flagged mandatory. Use the pricing analysis in the order item to see which access failed, then create the record with VK11, or fix the pricing procedure determination if the wrong procedure was selected.
How-toSAP GR/IR clearing account balance: reconcile with MB5S and clear with MR11
The GR/IR clearing account holds the value of goods received but not yet invoiced, and invoices not yet matched with receipts. It should trend to zero per PO item. Reconcile it with MB5S, find the PO items that are stuck, and clear true differences with MR11 or automatic clearing in F.13, after correcting the cause.
How-toSAP ME21N: why the release strategy is not determined on a purchase order
When a purchase order saves without a release strategy, no strategy in the release group matched the PO's characteristic values. Compare the PO header values (value, document type, purchasing group, plant) against the value ranges in the strategy classification (CL24N), and check that the release group and code are active for the PO document type.
Error fixSAP M7 021: Deficit of SL Stock Quantity
M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.
Error fixSAP IDoc Status 51: Application Document Not Posted
Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.
Error fixSAP Short Dump TIME_OUT: Maximum Runtime Exceeded
A TIME_OUT runtime error means a dialog (or RFC) work process ran longer than the maximum allowed runtime, controlled by profile parameter rdisp/max_wprun_time (600 seconds by default). The fix is almost always to move the long-running work to background processing or tune the underlying program, not to raise the timeout.
AI for ERPAI for SAP S/4HANA, Running On-Prem or in Your Private Cloud
Run AI on SAP S/4HANA without sending ERP data to a public API. On-prem and private-cloud architecture, CDS views, OData, and honest deployment trade-offs.
Stuck on SAP S/4HANA and ECC?
Talk to engineers who work inside SAP S/4HANA and ECC every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- SAP Pricing Procedure Design WorksheetAn editable worksheet to lay out a pricing procedure step by step, test the net value with example numbers and export it to Excel for the blueprint.
- SAP SD Pricing Condition Price CalculatorWalk a sales order line through a typical SD pricing procedure and see net value, invoice total and margin. Sweep the customer discount to see margin erosion.
- SAP Variant Condition Pricing WorksheetPlan variant condition surcharges per characteristic value before you load them into SAP pricing, and total the configured price for test cases.
ERP fixes and how-tos
- Pricing Procedure in SAP MM, with a Worked PO ExampleHow the SAP MM purchasing pricing procedure works: condition types, calculation schema, schema determination, a worked PO and how freight is captured.
- SAP MM price determination: pricing procedure, condition types and fixing wrong PO pricesHow SAP MM determines purchase prices: the RM0000 calculation schema, condition types like PB00, schema determination, and how to fix a wrong price in ME21N.
- Freight Cost in SAP MM: Planned and Unplanned Delivery CostsHow to handle inbound freight in SAP MM: planned delivery costs on the PO, freight condition types, unplanned costs in MIRO, and the GR/IR and stock impact.