SAP MM Procurement Analytics: Supplier Performance, Delays and Spend Visibility

Read supplier performance as a business question

A procurement report becomes useful when a buyer can explain the population behind it and decide what to investigate. A high delay percentage may describe a supplier problem, a small sample, a changed delivery agreement or an internal posting delay. Start with the decision: which overdue items need attention today, and which repeated issues deserve a supplier review?

Keep those two questions separate. An operational exception list supports immediate follow-up; a historical scorecard supports a longer discussion. This guide uses a small fictional dataset to show why the metric definition and source reconciliation matter before drawing either conclusion.

Core concepts to learn

Build a practice scenario

1. Step 1: Choose three purchase-order items and record their quantities, due dates and receipt dates.
2. Step 2: Calculate both item-based completion and quantity received by the due date; label their different denominators.
3. Step 3: Reconcile one item’s ordered value independently and check whether joins repeat it.
4. Step 4: Write one supported finding, an uncertainty and a named role responsible for investigating.

Use sample, authorised or fictional data. Do not publish credentials, business data, account numbers or customer information in a portfolio. If a task has financial, security or production impact, include a review or approval step before any change.

What good work looks like

Define the metric before comparing suppliers

A purchasing dashboard needs a written measurement rule. “Late delivery” could mean the first receipt arrived late, the complete quantity arrived late, or a receipt missed the statistical delivery date. Those definitions answer different questions. SAP’s supplier-evaluation guidance describes time, quantity, price and quality measures; its time-variance example compares the statistical delivery date with the actual goods receipt date. Calendar treatment and included purchasing documents depend on configuration.

For your own practice report, record the date field, unit of analysis, reporting cutoff, exclusions and handling of partial receipts. Label it a custom exercise measure rather than an exact reproduction of an SAP standard score. Keep the source document numbers beside the summary so every percentage can be investigated.

Worked example: three deliveries, two different answers

Use three fictional purchase-order items due on 10 October. Item A requires 100 units: 80 arrive on 10 October and 20 on 12 October. Item B requires 50 units and all 50 arrive on 10 October. Item C requires 200 units and all arrive on 13 October. For this example, define “on time and complete” as receiving the full ordered quantity by the due date, with no tolerance.

Only B passes that definition, giving one successful item out of three, or 33.3%. A different measure, quantity received by the due date, gives 130 units out of 350, or 37.1%. Neither result is inherently wrong. They use different denominators and reveal different aspects of service. State explicitly which measure appears in the headline.

Now move the reporting cutoff to the evening of 10 October. Do not exclude A and C merely because they remain open: doing so would leave only B and create a misleading 100% result. Preserve the due population and show the outstanding quantities. Later receipts change completion status, while the original due-date result remains part of the historical record.

Keep spend and delivery analysis at compatible levels

Suppose A has an agreed net unit price of ₹500, B ₹800 and C ₹100. Their illustrative ordered values are ₹50,000, ₹40,000 and ₹20,000, totalling ₹110,000 before tax or additional charges. This is ordered value, not automatically invoiced spend, paid spend or receipt value. Name the measure and reconcile it to the corresponding source before presenting a saving.

A frequent spreadsheet error appears when one order item is joined directly to several receipts and several invoices. Two receipt rows and two invoice rows can produce four joined combinations, repeating the order value. Aggregate each transaction set to the intended item level first, or retain separate measures with a clearly defined relationship. Test one item manually before trusting the grand total.

Also check currency, price unit and quantity unit. A price per 100 pieces cannot be multiplied as though it were a price per piece. Comparing suppliers across different material mixes can exaggerate a performance gap; show the mix or compare a consistent group before recommending a change.

Turn an exception into a documented action

For item A, ask whether the split delivery was agreed, whether the remaining quantity affected production and whether the recorded receipt dates match the receiving evidence. For C, separate supplier delay from a late internal receipt posting. Record what is known, what remains uncertain and who should investigate. An analytics result supports the conversation; it does not establish fault by itself.

A useful action log contains the supplier, item, observed variance, supporting document, owner, target review date and resolution evidence. At the next review, check whether the action happened and whether the same issue recurred. Do not hide difficult cases by changing the metric definition between reporting periods.

Keep the report reproducible

Save the extraction date, selected plants, supplier list and calculation version with the exercise. Ask another learner to reproduce the three-item result without looking at your final percentage. If they obtain a different answer, compare assumptions before checking arithmetic. This small handover test reveals missing definitions and makes the analysis easier to review when source data changes.

Analytics troubleshooting questions

Why does my dashboard disagree with an SAP report?

Compare the reporting period, organisational filters, currency basis, cancellations, partial receipts and document status first. Reconcile a single item, then expand to a supplier and the full population. If definitions differ, explain the difference rather than forcing totals to match.

Can I rank a supplier with one delivery?

You can describe that delivery, but show the small sample prominently. One late order is weak evidence of a persistent pattern. Keep the number of evaluated items beside the score and avoid treating a low-volume supplier as directly comparable with a supplier handling hundreds of items.

Official SAP references

• SAP Learning: Explain Supplier Evaluation

Frequently asked question

What should a beginner practise after learning SAP MM procurement analytics?

Build one small, documented exercise that uses the concepts safely, validate the result, and explain the decisions and limitations. Repeating this cycle makes learning more reliable than collecting disconnected tutorials.