Mon – Sat: 9:00 AM – 7:00 PM IST
SAP

What is SAP MM?

SAP's materials management module — purchasing, inventory and the invoice verification that closes the loop.

In short

SAP MM (Materials Management) handles purchasing, inventory management and invoice verification. It owns the material master, the purchase requisition and order, goods receipt, and the three-way match against the supplier invoice. It is where most transactional volume in an SAP system sits, and where most master-data discipline is required.

Why It Matters

Why this matters in practice

MM is the module that most directly determines whether your stock figures and your payables are trustworthy. The three-way match lives here, the valuation of inventory lives here, and the material master drives behaviour across production, sales and planning. Configuration errors in MM therefore surface as problems that look like they belong to other modules.

Owns procure-to-pay from requisition through invoice verification
Material master drives planning, valuation and production
Movement types govern how every stock transaction posts
Valuation class links material to the right GL account
How It Works

How it works in practice

1

Material master

Views by function — purchasing, accounting, MRP, storage. Each view is maintained by a different team, which is why governance matters.

2

Purchase requisition and order

Requisition captures need; the order is the commitment to a vendor, with release strategy enforcing approval.

3

Goods receipt

Stock and the GRNI liability both post here. Movement type determines the accounts touched.

4

Invoice verification

The three-way match. Within tolerance it posts; outside it blocks for review.

5

Valuation and account determination

Valuation class and movement type together decide which GL accounts a stock movement hits.

Worked example

A worked example: the release strategy that stopped working

A business configures a release strategy so purchase orders above a value threshold require director approval. It works well for two years. Then approvals start being bypassed, and nobody can explain how.

The mechanism is splitting. Buyers facing a slow approval queue began raising two orders just under the threshold instead of one above it. This was not fraud and was not hidden — it was a rational response to an approval process that took four days while suppliers held prices for two. The control was technically intact and operationally defeated.

The fixes are both procedural. Make approval fast enough that circumventing it is not worth the effort, which usually means delegating authority rather than escalating it. And monitor for the pattern — multiple orders to one supplier for similar materials within a short window — so splitting is visible rather than invisible. Controls that are slower than the business need are not controls; they are a tax on honesty.

Key terms

The vocabulary, briefly

Term What it means
Purchase requisition An internal request to buy, before any commitment to a supplier.
Purchase order The commitment to the supplier, with terms, prices and delivery dates.
Goods receipt Recording what arrived, which values stock and creates the GRNI accrual.
Invoice verification Matching the supplier invoice against order and receipt before payment.
Info record The stored relationship between a material and a supplier, carrying price and lead time.
What Goes Wrong

Common mistakes worth avoiding

Material master maintained by one team

Purchasing data entered by purchasing, accounting data by finance. One team guessing the others' fields produces systematic errors.

Release strategy that bypasses easily

If approval can be avoided by splitting an order, it will be.

Tolerances set too wide at invoice verification

A generous tolerance passes exactly the differences the match exists to catch.

Movement types created ad hoc

Custom movement types multiply and nobody remembers what posts where. Keep the set small and documented.

What to measure

Numbers worth tracking

Metric What it tells you What distorts it
Purchase orders by approval level Clustering just under a threshold is the signature of splitting.
Requisition-to-order cycle time Approval friction, which is what drives workaround behaviour.
Receipts without purchase orders Unauthorised buying, and a direct cause of unclearable accruals.
Info record price vs actual Whether stored prices reflect reality or have quietly gone stale.
FAQ

Questions we are asked about this

A three-digit key that tells SAP what kind of stock movement is happening and, critically, which accounts to post to. 101 is goods receipt against a purchase order; 601 is goods issue for delivery.
It links a material to the GL accounts used when it moves. Materials with different accounting treatment need different valuation classes, which is a design decision made with finance.
A requisition is an internal request — somebody says they need something, and no supplier is involved or committed. A purchase order is the external commitment, with legal and financial consequences. Keeping them separate matters because it puts approval before commitment rather than after it, and because it separates the question of whether to buy from the question of whom to buy from.
Characteristics of the document — value, material group, plant, purchasing group — determine which approval path applies, and the document cannot proceed until the required releases are recorded. The configuration is flexible enough to encode almost any policy, which is also the risk: strategies designed around organisational politics rather than around risk tend to produce long chains that everyone eventually routes around.
A longer-term arrangement with a supplier covering a quantity over a period, against which individual delivery schedules are released rather than separate purchase orders. It suits repetitive supply of production materials where you want a commercial framework agreed once and call-offs managed operationally. It reduces transactional overhead considerably where volumes are regular.
Directly and immediately. A goods receipt updates stock quantity and value and posts the GRNI accrual, so the liability exists before the invoice. Invoice verification clears that accrual and creates the payable. Movement types determine which accounts are hit. The practical implication is that MM configuration decisions are accounting decisions, and they should be reviewed by finance rather than left entirely to procurement.
Related

Where to read next

What is three-way matching?

Read more

The procure-to-pay process

Read more

Our SAP consulting services

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.