SAP MM Pricing

You are an SAP Materials Management (MM) pricing configuration expert. The user wants to configure MM pricing procedures, condition types, and schemas to control how material costs and prices are calculated in purchasing and inventory transactions.

What to check first

• Run transaction SPRO and navigate to Materials Management > Purchasing > Pricing to access the IMG customization area
• Verify your user role includes SAP_ALL or MM_CUSTOMIZING authorization for MM pricing configuration
• Check transaction OMS9 to review existing pricing schemas and determine if you're creating new ones or modifying existing procedures

Steps

1. Open transaction V/08 (Maintain Condition Types) to define custom condition types (e.g., PB00 for base price, PB01 for discounts) with calculation types (percentage, absolute, quantity-based) and rounding rules
2. In transaction OVKP, navigate to Define Price Determination Process and select your sales/purchasing organization to assign pricing procedures
3. Create or modify pricing procedure via transaction V/09 or VKOP — assign condition types in sequential order with access sequence keys that pull data from pricing tables (A900, A901, A906)
4. Configure access sequences in transaction V/12 (Maintain Access Sequences) — map source tables and field selections (e.g., Material + Customer + Date for customer-specific pricing)
5. Populate condition master data via transaction VK11 (Create Condition Records) for each condition type, specifying valid periods and organizations
6. Link pricing procedure to price list type in transaction OVKA to activate the complete pricing schema for specific business transactions
7. Execute transaction VK31 (Analyze Pricing) on a test purchase order or sales order to verify condition determination and price calculation flow
8. Run transaction MCHB (Batch Condition Maintenance) if bulk importing condition records from legacy systems or spreadsheets

Code

REPORT Z_MM_PRICING_CONFIG.

DATA: lt_condition_types TYPE TABLE OF t685t,
      lt_pricing_procedure TYPE TABLE OF komv,
      lt_access_seq TYPE TABLE OF t681t,
      lv_priceproc TYPE komkp,
      lv_cond_type TYPE koaid.

* Select existing condition types
SELECT * INTO TABLE lt_condition_types
  FROM t685t
  WHERE spras = 'E'
    AND kappl = '02'.  "Purchasing application

IF lt_condition_types IS NOT INITIAL.
  WRITE: / 'Found condition types for Purchasing'.
  LOOP AT lt_condition_types INTO DATA(wa_cond).
    WRITE: / wa_cond-ktext.
  ENDLOOP.
ENDIF.

* Read pricing procedure for material
SELECT * INTO TABLE lt_pricing_procedure
  FROM komv
  WHERE lifnr = 'VENDOR01'
    AND matnr = 'MAT-001'
    AND datab <= sy-datum

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

• Treating this skill as a one-shot solution — most workflows need iteration and verification
• Skipping the verification steps — you don't know it worked until you measure
• Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

• When a simpler manual approach would take less than 10 minutes
• On critical production systems without testing in staging first
• When you don't have permission or authorization to make these changes

How to Verify It Worked

• Run the verification steps documented above
• Compare the output against your expected baseline
• Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

• Test in staging before deploying to production
• Have a rollback plan — every change should be reversible
• Monitor the affected systems for at least 24 hours after the change