# SAP MM Pricing Procedure Configuration (Calculation Schema, M/08) > Source: https://netray.co/erp-help/sap-mm-pricing-procedure-calculation-schema-m08-how-to > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## 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. ## Kind how-to ## System sap ## Erp SAP S/4HANA and ECC ## Module Materials Management (MM) / Purchasing Conditions ## Query sap mm pricing procedure configuration ## Alternate Queries - sap mm pricing procedure tcode - sap mm calculation schema - pricing procedure in sap s4 hana - sap mm price condition tcode ## Applies To SAP ECC 6.0 and SAP S/4HANA on-premise (purchasing price determination) ## Steps ### Configure MM pricing end to end **Items:** - Define 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. - Define or reuse the access sequence and condition tables that decide how a condition record is found (for example vendor and material). - Open 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. - Define schema groups: one for vendors (assigned in the vendor master purchasing data) and one for purchasing organizations. - Define schema determination: assign the calculation schema to the combination of purchasing organization schema group and vendor schema group. - Create condition records with MEK1 (change MEK2, display MEK3) or in the info record (ME11) or contract. - Create a test PO in ME21N and check the Conditions tab shows the expected steps and values. Map accrual and freight account keys in OBYC. ## Sections ### How the pieces fit together **Body:** 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. **Code:** - 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 **Body:** 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 **Body:** 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. ## 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. ## Ai Angle 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. ## Faq ### What is the tcode for the MM pricing procedure? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms sap mm pricing procedure configuration, sap mm pricing procedure tcode, sap mm price condition tcode, pricing procedure in sap s4 hana, sap mm calculation schema, sap m/08 calculation schema, sap rm0000 calculation schema, sap mek1 condition record, sap purchasing condition types --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json