Ask someone outside SAP what an MM consultant does, and you'll usually get a vague answer: "something with purchasing." Ask someone who's actually worked a production support rotation, and you'll get a very different, very specific list — tickets, troubleshooting, master data fixes, and a lot of explaining to business users why something isn't working the way they expect. This article breaks down 15 real, concrete activities an SAP MM consultant handles on an actual project, each with a practical scenario showing what it looks like in practice.
1. Resolving Purchase Order Creation Failures
What it is: Investigating and fixing cases where a buyer tries to create a PO and the system blocks it or throws an error.
Scenario: A procurement user reports they can't create a PO for a specific material at a specific plant. The consultant checks the material master's plant-specific purchasing view, confirms whether a valid source of supply exists, and verifies the purchasing organization and group assignment — tracing the issue to a missing purchasing info record and resolving it within the hour.
2. Troubleshooting Goods Receipt Posting Errors
What it is: Diagnosing why a warehouse user can't post a goods receipt against an open PO.
Scenario: A warehouse clerk reports MIGO is throwing an error during receipt posting. The consultant checks the PO's status, confirms the plant and storage location setup, and reviews the movement type configuration, ultimately finding the PO had already been fully received in error during a prior shift — requiring a reversal before the new receipt can post correctly.
3. Investigating Blocked Invoices
What it is: Working through why an invoice has been held back from payment during the three-way match.
Scenario: Accounts payable flags an invoice stuck in blocked status. The consultant compares the PO price and quantity against the goods receipt and the invoice, identifies a price mismatch beyond the configured tolerance, and works with the buyer to confirm whether the vendor's price genuinely changed or a data entry error occurred.
4. Fixing Master Data Inconsistencies
What it is: Correcting material master, vendor, or purchasing data that's causing downstream transaction errors.
Scenario: A material shows conflicting units of measure between two plants, causing incorrect quantities on transfer orders. The consultant traces the inconsistency back to the original material creation, corrects the relevant views, and documents the fix to prevent it from recurring during future material creation.
5. Supporting Stock Discrepancy Investigations
What it is: Helping warehouse and inventory teams figure out why physical stock doesn't match what SAP shows.
Scenario: A cycle count reveals 50 fewer units of a component than the system expects. The consultant reviews recent movement history, checks for unposted transactions, and confirms whether stock was sitting in blocked or quality inspection status rather than unrestricted — ultimately tracing the gap to a goods issue that was posted against the wrong storage location.
6. Handling Partial Goods Receipts and Follow-Up Procurement
What it is: Managing scenarios where a supplier delivers less than the full ordered quantity.
Scenario: A PO for 1,000 units results in a delivery of only 850. The consultant confirms the partial receipt posts correctly, verifies the PO history reflects the remaining open quantity, and advises the buyer on whether to expect a follow-up shipment or raise a separate requisition for the shortfall.
7. Configuring and Adjusting Release Strategies
What it is: Setting up or modifying the approval workflows that route purchase requisitions and POs to the right approvers.
Scenario: Finance requests that any PO above a new, higher value threshold now requires an additional approval layer. The consultant updates the release strategy configuration, tests it in a sandbox environment, and confirms with the business that the new approval chain behaves as expected before moving it to production.
8. Managing Special Procurement Scenarios
What it is: Supporting non-standard procurement processes like subcontracting, consignment, or stock transport orders.
Scenario: A manufacturing plant reports that finished goods aren't being received correctly after a subcontracting operation. The consultant reviews the subcontracting PO's component consumption, checks the BOM assignment, and identifies that a component quantity was miscalculated during the original order, requiring a correction before the finished material can post properly.
Go Deeper Into These Real Project Scenarios
A few of the activities above come up often enough in real SAP MM work that we've covered them in much more detail elsewhere — worth reading if any of the scenarios above felt relevant to what you're currently learning or working on:
- If #6 (partial goods receipts) stood out to you: our full walkthrough of SAP S/4HANA MM Purchase Order Delays: Real-World Scenario digs into exactly this kind of quantity-mismatch troubleshooting in much greater depth.
- If #8 (special procurement scenarios) is new territory for you: SAP MM Consignment Process: Step-by-Step Guide with Real-World Scenario breaks down one of the most commonly tested special procurement types, with a full end-to-end example.
- If #4 and #10 (master data and migration issues) feel like your weak spot: Types of Data in SAP MM: A Complete Guide to Master, Transaction & Organizational Data is the foundational read that makes master data troubleshooting much easier to reason about.
- If you want to see how all 15 of these activities fit into a full project lifecycle, not just isolated tickets: SAP S/4HANA MM: Practical Guide & Real Project Experience walks through the complete business-requirement-to-go-live journey these support activities are part of.
- If you're newer to SAP MM and some of the transaction references above felt unfamiliar: keep SAP S/4HANA MM T-Codes: Essential Transaction Codes Every SAP MM Professional Should Know bookmarked as a quick-reference guide.
9. Supporting Month-End and Period-Close Activities
What it is: Helping ensure MM-related transactions are properly reflected before financial periods close.
Scenario: Finance flags several goods receipts that haven't generated corresponding invoices, leaving open balances in the GR/IR account. The consultant works through the list, identifying which are genuinely pending invoices versus data errors, and helps clear or correct entries before the period closes.
10. Validating and Supporting Data Migration
What it is: Checking that material, vendor, and transactional data has migrated correctly, particularly during a system upgrade or go-live.
Scenario: During an ECC-to-S/4HANA migration, the consultant is asked to validate that legacy vendor records converted correctly into the new Business Partner model, spot-checking a sample of records against the original data and flagging discrepancies for correction before go-live.
11. Handling User Authorization Issues
What it is: Diagnosing why a user can't access a transaction or perform an action they should be authorized for.
Scenario: A newly onboarded buyer reports they can't release purchase requisitions. The consultant checks the user's assigned roles and authorization objects, confirms the user is missing a required role, and coordinates with the security team to get it assigned correctly.
12. Supporting UAT and Regression Testing
What it is: Helping business users test MM processes during testing cycles and confirming that fixes or changes haven't broken existing functionality.
Scenario: After a configuration change to accommodate a new plant, the consultant runs through a standard set of regression test cases — create PR, convert to PO, post GR, post invoice — to confirm the change hasn't introduced unintended side effects elsewhere in the process.
13. Explaining System Behavior to Business Users
What it is: Translating technical system behavior into plain language business users can actually act on.
Scenario: A procurement manager is confused about why a PO's price doesn't match what they negotiated with a vendor. The consultant walks them through how pricing conditions, info records, and contracts interact, showing exactly which condition record is driving the discrepancy and what needs to change to correct it going forward.
14. Documenting Root Cause and Resolution for Recurring Issues
What it is: Writing up clear documentation when an issue is resolved, especially if it's likely to recur.
Scenario: After resolving a recurring goods receipt error caused by a specific movement type misconfiguration, the consultant documents the root cause and fix in the team's knowledge base, so the next support analyst who sees the same symptom can resolve it in minutes instead of hours.
15. Participating in Change Requests and Small Enhancements
What it is: Handling ongoing, smaller-scale configuration changes and enhancements requested by the business after go-live.
Scenario: The warehouse team requests a new storage location be added to support a facility expansion. The consultant gathers the specific requirements, configures the new storage location, tests it against standard inbound and outbound processes, and coordinates the change through the organization's change control process before releasing it to production.
Why This List Matters for Anyone Learning SAP MM
Notice what's missing from this list: there's no entry that says "create a purchase order" or "post a goods receipt" as a standalone skill. That's deliberate. On a real project, those transactions are the easy part — the actual job is investigating why something didn't work as expected, tracing a problem back to its root cause, and communicating clearly with the people affected by it. If you're preparing for an SAP MM role, these 15 activities are a far more accurate picture of day-to-day work than any transaction-code tutorial.
Frequently Asked Questions
What does an SAP MM consultant actually do day to day? Most of the day-to-day work involves troubleshooting — investigating PO creation failures, goods receipt errors, blocked invoices, stock discrepancies, and master data issues — alongside supporting testing, documentation, and smaller configuration changes requested by the business.
Is SAP MM production support different from implementation work? Yes. Implementation work focuses on initial configuration, data migration, and testing before go-live, while production support focuses on troubleshooting live issues, handling change requests, and supporting ongoing business operations after go-live.
What skills matter most for SAP MM on-job support? Structured troubleshooting ability, solid understanding of master data and configuration, and clear communication with business users matter more day to day than memorizing transaction codes alone.
Do SAP MM consultants work directly with business users? Yes, regularly — explaining system behavior, gathering requirements for changes, and walking users through why a transaction behaved a certain way are all routine parts of the role.
What's the most common type of issue an SAP MM consultant handles? Purchase order creation failures, goods receipt errors, and blocked invoices are among the most frequently encountered issues, since they sit at the center of the procure-to-pay process where master data, configuration, and real-world variability intersect most often.
Ready to Learn the Way Real SAP MM Projects Actually Work?
Reading about these 15 activities is one thing — actually practicing them, through real scenario-based training, is what makes the difference between knowing SAP MM transactions and being genuinely project-ready.
Proexcellency's SAP S/4HANA MM training is built around exactly this kind of practical, scenario-based learning, covering real troubleshooting situations like the ones described above rather than isolated transaction walkthroughs.
Ready to go from theory to project-ready? Explore Proexcellency's SAP S/4HANA MM training and start learning how real on-job support work actually happens.