Quick Answer — SAP MM T-Codes
- SAP MM has 100+ transaction codes spanning procurement (ME21N, ME51N), inventory (MIGO), stock display (MMBE), MRP (MD04, MD01N), and invoice verification (MIRO, MRBR).
- Core daily-use tcodes are unchanged in S/4HANA — ME21N, MIGO, MIRO, MMBE, MD04, ME11 all work exactly as they do in ECC.
- Vendor master changed significantly — MK01/XK01/FK01 (three separate views) are all replaced by the single Business Partner (BP) transaction in S/4HANA.
- MRP evolves in S/4HANA — MD01N (MRP Live) replaces MD01 batch processing, running in real time using HANA in-memory engine; MD04 and MDBT remain active.
- Classic Warehouse Management is deprecated — LT01/LT0A/LT11/LQ01 (Classic WM) are replaced by Embedded EWM Fiori apps in S/4HANA.
10+
Material Master
12+
Vendor / BP
14+
Requisitions & RFQ
14+
POs & Contracts
10+
Inventory Mgmt
15+
S/4 Changes
Key Takeaways
1
ME21N, MIGO, and MIRO are unchanged in S/4HANA — the three most-used daily transactions in SAP MM work identically in ECC and S/4HANA.
2
All vendor master tcodes (MK01, XK01, FK01) are replaced by BP — the Business Partner transaction is the single point of vendor master maintenance in S/4HANA.
3
MB1A, MB1B, MB1C are deprecated — MIGO with the correct movement type replaces all three legacy goods movement transactions in S/4HANA.
4
MD01N (MRP Live) replaces MD01 — S/4HANA's in-memory MRP engine runs real-time planning that is 10–100x faster than ECC batch-based MD01.
5
Classic WM (LT01 series) is deprecated — S/4HANA uses Embedded EWM; companies migrating must plan a separate WM-to-EWM workstream.
Before You Start
How to Read This Guide — Status Badges, ECC vs S/4HANA
SAP MM (Materials Management) covers the end-to-end supply-chain process within SAP — from vendor selection and procurement through goods receipt, inventory management, and invoice verification. This guide covers every meaningful tcode across all MM sub-modules, in both SAP ECC 6.0 and SAP S/4HANA, and tells you exactly what changed, what was replaced, and what to use in a modern S/4HANA environment.
Active Works in both ECC and S/4HANA — no change
Deprecated Obsolete in S/4HANA — use the replacement shown
Modified Available but behaviour or scope changed in S/4HANA
S/4 New New tcode introduced in S/4HANA, not present in ECC
SAP ECC — The Legacy Stack
- Separate vendor tables (LFA1/LFB1/LFBK) — maintained via MK01, XK01, FK01
- Material master with up to 44 views across organisational levels
- MRP via MD01/MD02 — batch-based run writing results to MDTB planning table
- Classic Warehouse Management: LT01/LT0A/LT11/LQ01/LQ02
- Separate goods movement transactions: MB1A, MB1B, MB1C alongside MIGO
- Goods movement documents stored in MKPF (header) / MSEG (line items)
- Purchase order data in EKKO (header) / EKPO (line items)
SAP S/4HANA — The New Architecture
- Business Partner (BP) replaces all vendor master tcodes (MK01/XK01/FK01 deprecated)
- Material master screens simplified and consolidated in S/4HANA Fiori apps
- MRP Live (MD01N) — real-time in-memory MRP using HANA; MDBT still for background
- Embedded EWM replaces Classic WM; LT01 series deprecated
- MIGO consolidates all goods movements — MB1A/MB1B/MB1C deprecated
- MATDOC replaces MKPF/MSEG as the single goods movement document table
- ME21N and MIRO still active; Fiori apps available alongside SAP GUI
ECC end-of-support: December 31, 2027. Every MM professional working today will encounter S/4HANA within the next 12–24 months — through new implementations or company migrations. The three practical changes to close the knowledge gap on right now: (1) vendor master goes from three tcodes to one (BP); (2) MRP batch becomes MRP Live (MD01N); (3) Classic WM becomes Embedded EWM. VoiSAP's MM training covers both ECC and S/4HANA so you are ready for either.
MM Master Data
Material Master T-Codes — Create, Change, Extend, Mass Maintenance
The material master is the central master data object in SAP MM — it stores all data about a material that the organisation procures, produces, stores, or sells. Every goods movement, purchase order, and MRP run reads from or writes to the material master. In S/4HANA, the material master views are simplified and some screens are consolidated, but MM01/MM02/MM03 remain the primary GUI transactions.
Material Master — Create, Change, Display
Material Master Transactions9 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| MM01 | Create Material Master | Modified | Still the primary material creation transaction in S/4HANA. In S/4HANA, material master screens are simplified — some ECC view combinations are consolidated and the Accounting views incorporate Material Ledger data natively. The Fiori equivalent is "Manage Product Master Data." MM01 via SAP GUI remains fully supported. |
| MM02 | Change Material Master | Active | Core change transaction for material master views — most commonly used for updating MRP parameters, purchasing data, accounting valuation class, or storage location data. Unchanged in S/4HANA. |
| MM03 | Display Material Master | Active | Read-only display of all material master views. Unchanged in S/4HANA. |
| MM06 | Flag Material for Deletion | Active | Flags a material at client, plant, or storage location level for archiving and deletion. Unchanged in S/4HANA. A deletion flag is a prerequisite for material archiving — it does not immediately delete the material. |
| MM17 | Mass Maintenance — Material Master | Active | Change multiple materials simultaneously across selected fields — e.g. update MRP type or reorder point across 200 materials at once. Unchanged in S/4HANA. |
| MM50 | Extend Material Master (to Org Levels) | Active | Creates material master views for a material in new plant, storage location, or sales organisation combinations. Used when a material needs to be procured or used in a new plant that didn't previously carry it. Unchanged in S/4HANA. |
| MM60 | Material List Display | Active | Generates a list of materials matching selected attributes — quick overview of the material portfolio. Unchanged in S/4HANA. |
| MR21 | Change Material Price (Standard / Moving Average) | Active | Changes the standard price or moving average price of a material without a goods movement — typically used to set a new standard price at the start of a period. Unchanged in S/4HANA; the posting hits ACDOCA alongside MATDOC. |
| MR22 | Debit/Credit Material (Manual Revaluation) | Active | Posts a manual inventory revaluation — debits or credits the material's stock value account. Used for write-downs, write-ups, or corrections. Unchanged in S/4HANA. |
Material master and the Material Ledger in S/4HANA: In S/4HANA, the Material Ledger is mandatory for all company codes that use MM. This means every material with a standard price (S) will have its actual period cost calculated by CKMLCP at month end — even companies that are not doing full actual costing. The MM01 Accounting views in S/4HANA therefore include Material Ledger status indicators that don't appear in ECC. This is the most important MM master data change to understand when moving from ECC to S/4HANA.
MM Master Data — Vendor / Business Partner
Vendor Master & Business Partner — The Biggest MM Change in S/4HANA
Vendor master management is the single most impactful change in SAP MM for S/4HANA. In ECC, vendors were maintained across three separate transaction families — MK01 for purchasing, FK01 for FI, and XK01 for both — each writing to different database tables. In S/4HANA, a single Business Partner (BP) record replaces all of them. Understanding this change is now a standard interview question for any S/4HANA MM role.
Vendor Master Transactions — ECC vs S/4HANA
Vendor Master — Create, Change, Display10 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| MK01 / MK02 / MK03 | Create / Change / Display Vendor (Purchasing View) | Deprecated | Replaced by BP in S/4HANA. MK01 created the vendor's purchasing-specific data (purchasing org, payment terms, incoterms, GR-based invoice verification flag). In S/4HANA, this data is maintained within the BP transaction under the MM vendor role (FLVN00). Do not use MK01/02/03 in S/4HANA. |
| XK01 / XK02 / XK03 | Create / Change / Display Vendor (Central — all views) | Deprecated | XK01 was the central vendor creation transaction that covered both FI and MM views in one step. Replaced by BP in S/4HANA. In S/4HANA, BP is the equivalent of XK01 — it manages all vendor roles (FI and MM) in a single transaction. |
| FK01 / FK02 / FK03 | Create / Change / Display Vendor (FI / Accounting View) | Deprecated | Replaced by BP in S/4HANA. FK01 maintained the FI-specific vendor data: reconciliation account, payment method, house bank, tolerance group. In S/4HANA, this is the FI vendor role (FLVN01) within BP. These tables are unified: BP stores everything in the central Business Partner data model (BUT000, BUT001 etc.). |
| BP | Business Partner — Central Master Data Maintenance | S/4 New | The single vendor (and customer) master transaction in S/4HANA. BP uses a role concept: assign role FLVN00 for MM vendor data (purchasing org, incoterms, payment terms) and FLVN01 for FI vendor data (reconciliation account, payment method). One BP record = one vendor with all views. The Fiori equivalent is "Manage Business Partner Master Data." |
| MK06 | Flag Vendor for Deletion (Purchasing) | Modified | Still available in S/4HANA but the preferred approach is to manage the lifecycle within BP by setting the Central Deletion Flag or blocking the BP record. MK06 can still trigger deletion flags on the purchasing side. |
| XK99 | Vendor Master Mass Change | Modified | Mass change of vendor master data — e.g. change payment terms across 100 vendors simultaneously. Still available in S/4HANA but BP is the primary maintenance path. Used for bulk updates where individual BP changes would be impractical. |
Purchase Info Records & Source Lists
Info Records, Source Lists, Quota Arrangement6 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| ME11 / ME12 / ME13 | Create / Change / Display Purchase Info Record | Active | Core MM master data — the agreed price and delivery time between a material and a vendor. Automatically defaulted in ME21N purchase orders. Used as the basis for the ME49 price comparison list. Unchanged in S/4HANA. |
| ME1M | Info Records by Material | Active | List all info records for a given material — useful to see all approved vendors and their prices. Unchanged in S/4HANA. |
| ME01 / ME03 | Maintain / Display Source List | Active | Source list defines which vendors are approved for a material and whether a source of supply is mandatory. Controls MRP sourcing behaviour. Unchanged in S/4HANA. |
| MEQ1 / MEQ3 | Maintain / Display Quota Arrangement | Active | Quota arrangement splits procurement of a material across multiple vendors in defined ratios — e.g. 60% from Vendor A, 40% from Vendor B. MRP uses quotas to split planned orders. Unchanged in S/4HANA. |
The Business Partner role concept — what it means in practice: In ECC, a common error was "vendor exists in MM but not in FI" — because MK01 and FK01 were separate steps and someone only ran one of them. In S/4HANA, BP forces you to assign both roles (FLVN00 and FLVN01) before the vendor is usable for both purchasing and payment. This eliminates the split-view problem permanently. For the full FI-side vendor (creditor) management picture, see SAP FICO T-Codes — Accounts Payable. For students transitioning from ECC to S/4HANA, the BP transaction feels quite different — it's worth practising it specifically in an S/4HANA system.
MM Purchasing — Requisitions & RFQ
Purchase Requisitions & RFQ T-Codes — The Front End of Procurement
The procurement process in SAP MM starts with a Purchase Requisition (PR) — an internal document expressing a need to procure material or services. PRs require approval and cannot be sent to vendors. Once approved and assigned to a source of supply, they are converted to Purchase Orders (ME21N) or trigger an RFQ (Request for Quotation) process when the vendor and price are not yet known. All these transactions are unchanged in S/4HANA.
Purchase Requisitions
Purchase Requisition Transactions7 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| ME51N | Create Purchase Requisition (Enjoy — single screen) | Active | The primary PR creation transaction. Unchanged in S/4HANA. The Fiori equivalent is "Create Purchase Requisition" (F2229) which offers workflow integration and approval directly in the browser. ME51N via SAP GUI remains fully supported. |
| ME52N | Change Purchase Requisition | Active | Change an existing PR — update quantity, delivery date, material, or account assignment. Unchanged in S/4HANA. |
| ME53N | Display Purchase Requisition | Active | Read-only display of a PR. Unchanged in S/4HANA. |
| ME5A | List Display of Purchase Requisitions | Active | List all PRs with flexible selection criteria — plant, material, requester, date range, processing status. Used by buyers to review open requisitions needing action. Unchanged in S/4HANA. |
| ME54N | Release (Approve) Purchase Requisition | Active | Manual PR release (approval) transaction. S/4HANA also supports workflow-based approval via Fiori "Approve Purchase Requisitions" app — more common in modern implementations. Unchanged tcode. |
| ME57 | Assign and Process Requisitions (Source Assignment) | Active | Assigns a source of supply (vendor, contract, or scheduling agreement) to approved requisitions and allows bulk conversion to purchase orders. One of the most used buyer workbench transactions. Unchanged in S/4HANA. |
| ME56 | Assign Source of Supply to PR | Active | Manually assign a source of supply to individual PR items without converting to PO. Unchanged in S/4HANA. |
RFQ — Request for Quotation
RFQ & Quotation Transactions6 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| ME41 | Create Request for Quotation | Active | Create an RFQ sent to multiple vendors asking for price proposals. Each vendor gets their own RFQ document. Unchanged in S/4HANA. |
| ME42 / ME43 | Change / Display Request for Quotation | Active | Change or display an existing RFQ. Unchanged in S/4HANA. |
| ME47 | Maintain Quotation (Enter Vendor Response) | Active | Enter the vendor's quoted price and delivery terms into their RFQ document to create a Quotation. Unchanged in S/4HANA. |
| ME48 | Display Quotation | Active | Read-only display of a quotation. Unchanged in S/4HANA. |
| ME49 | Price Comparison List (All Quotations) | Active | Shows all vendor quotations for an RFQ side by side — price, delivery time, and total cost comparison. Allows buyers to select the best vendor and mark others as rejected. Unchanged in S/4HANA. One of the most satisfying procurement transactions to use. |
MM Purchasing — Purchase Orders & Outline Agreements
Purchase Order & Contract T-Codes — The Core of SAP Procurement
Purchase Orders and Outline Agreements (Contracts and Scheduling Agreements) are the heart of SAP MM procurement. ME21N is one of the most-used transactions across any SAP MM environment — used daily by purchasing departments to issue standard, subcontracting, third-party, and consignment POs. All purchasing transactions are active and unchanged in S/4HANA, with Fiori equivalents available in parallel.
Purchase Orders
Purchase Order Transactions8 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| ME21N | Create Purchase Order (Enjoy — single screen) | Active | The primary purchase order transaction — used daily by every MM buyer. Handles all PO types: standard (NB), subcontracting (30), consignment (K), stock transport orders (UB), and service POs. Unchanged in S/4HANA. Fiori equivalent: "Manage Purchase Orders" (F1048A). |
| ME22N | Change Purchase Order | Active | Change an existing PO — update price, quantity, delivery date, or account assignment. Every change creates a version history in the PO change log. Unchanged in S/4HANA. |
| ME23N | Display Purchase Order | Active | Read-only display of any PO including delivery history and invoice history. Unchanged in S/4HANA. |
| ME2M | Purchase Orders by Material | Active | List all POs for a given material — useful for tracking all outstanding purchase orders for a specific item. Unchanged in S/4HANA. |
| ME2L | Purchase Orders by Vendor | Active | List all POs from a specific vendor — used for vendor spend analysis and overdue delivery tracking. Unchanged in S/4HANA. |
| ME2N | Purchase Orders by PO Number | Active | General PO list report with flexible filtering. Unchanged in S/4HANA. |
| ME29N | Release (Approve) Purchase Order | Active | Manual PO release for POs subject to a release strategy (approval workflow). S/4HANA also supports Fiori-based PO approval workflow. Unchanged tcode. |
| ME9F | Output / Print Purchase Order | Active | Generates output for a PO — print, email, fax, or EDI transmission to the vendor. Unchanged in S/4HANA. S/4HANA also supports BRF+ and SAP Forms for PO output design. |
Outline Agreements — Contracts & Scheduling Agreements
Contracts & Scheduling Agreement Transactions8 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| ME31K / ME32K / ME33K | Create / Change / Display Contract | Active | Contracts define a total quantity or value agreement with a vendor. Individual deliveries are released by creating release purchase orders against the contract via ME21N (with reference to ME31K doc). Unchanged in S/4HANA. Fiori: "Manage Purchase Contracts." |
| ME35K | Release Contract | Active | Releases a contract that has been set up with a release strategy requiring approval before release orders can be created against it. Unchanged in S/4HANA. |
| ME3M | Contracts by Material | Active | List all contracts covering a specific material — useful for buyers to check if a material is already under a long-term agreement before creating a spot PO. Unchanged in S/4HANA. |
| ME31L / ME32L / ME33L | Create / Change / Display Scheduling Agreement | Active | Scheduling agreements define an ongoing delivery arrangement with a vendor — specific quantities on specific future dates. Standard in automotive and high-volume manufacturing. Unchanged in S/4HANA. Fiori: "Manage Scheduling Agreements." |
| ME38 | Maintain Scheduling Agreement Delivery Schedule | Active | The most frequently used scheduling agreement transaction. Creates and updates the delivery schedule lines (firm and forecast periods) against an existing scheduling agreement. Driven by MRP in fully automated environments. Unchanged in S/4HANA. |
MM Inventory Management
Goods Movement T-Codes — MIGO, GR, GI, Transfer Posting
Inventory Management (MM-IM) covers all physical movements of stock — goods receipts from vendors, goods issues to production or cost centres, and transfers between storage locations or plants. MIGO is the central transaction for all of these movements in modern SAP. In S/4HANA, goods movements write to the MATDOC table (replacing MKPF/MSEG) and simultaneously update ACDOCA — making financial and inventory data always in sync without reconciliation steps.
Goods Movements — MIGO and Legacy Transactions
Inventory Movement Transactions8 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| MIGO | Goods Movement (All-in-One — GR, GI, Transfer) | Active | The central goods movement transaction in SAP MM. Handles all movement types in one interface: Goods Receipt against PO (mvt 101), GR against production order (101), Goods Issue to cost centre (201) or production order (261), Transfer Posting (311/312 within plant, 301 plant-to-plant), Return to Vendor (122), and reversal of any movement. Unchanged in S/4HANA. Fiori: "Post Goods Movement" (F0843) and "Receive Delivery" (F2386). |
| MB1A | Goods Withdrawal / Goods Issue (Classic) | Deprecated | Replaced by MIGO in S/4HANA. Use MIGO with movement type 201 (goods issue to cost centre), 261 (goods issue to production order), or 281 (goods issue to project). The MB1A interface is no longer available in S/4HANA. |
| MB1B | Transfer Posting (Classic) | Deprecated | Replaced by MIGO in S/4HANA. Use MIGO with movement type 311 (transfer within plant, storage location to storage location), 301 (plant-to-plant transfer), or 412 (transfer from consignment to own stock). MB1B is deprecated in S/4HANA. |
| MB1C | Other Goods Receipt (Without Reference) | Deprecated | Replaced by MIGO in S/4HANA. For receipts without PO reference, use MIGO with movement type 501 (receipt without reference). MB1C is deprecated in S/4HANA. |
| MBST | Cancel Material Document | Modified | Cancels (reverses) a posted goods movement document. Still available in S/4HANA but the preferred approach is to use MIGO with the "Cancellation" action directly referencing the material document number. MBST as a separate transaction is available but MIGO is preferred. |
| MB31 | Goods Receipt for Production Order | Modified | Still available in S/4HANA but MIGO is preferred for all goods receipts including production order receipts. MB31 remains for users who prefer a dedicated transaction for this specific movement type. |
| MB03 | Display Material Document | Active | Display a posted goods movement document (material document). In S/4HANA, material documents are stored in MATDOC (replacing MKPF/MSEG). MB03 is unchanged but reads from the new table structure transparently. |
| MB90 | Output Processing for Goods Movements | Active | Reprocess output (print, GR slip, delivery note) for goods movement documents. Unchanged in S/4HANA. |
MIGO Movement Types — The Complete Reference
Key MIGO Movement Types — ECC and S/4HANA14 movement types
| Mvt Type | Description | Reversal | Notes |
|---|---|---|---|
| 101 | Goods Receipt against Purchase Order | 102 | The most common movement type. GR against a PO line item — stock increases, GR/IR account credited, vendor open item created by MIRO. |
| 103 | Goods Receipt to Blocked Stock (against PO) | 104 | Used for quality-hold scenarios — stock received but not yet available for use. A 105 (release from blocked) moves it to unrestricted. |
| 122 | Return to Vendor (Delivery Returns) | 123 | Reverses a prior goods receipt and returns stock to the vendor. Reduces unrestricted stock and reverses the GR/IR posting. |
| 201 | Goods Issue to Cost Centre | 202 | Replaces MB1A for cost centre goods issues. Requires account assignment to a cost centre. Stock decreases; cost centre debited. |
| 261 | Goods Issue to Production Order | 262 | Component consumption for a production order. Reduces stock and debits the production order. Driven by backflushing or manual issue. |
| 281 | Goods Issue to Project (WBS Element) | 282 | Issues stock against a WBS element (project). Used when project stock is consumed directly from warehouse. |
| 301 | Transfer Posting — Plant to Plant (One Step) | 302 | One-step plant-to-plant stock transfer. Both the sending and receiving plant update simultaneously. Replaces MB1B for this scenario. |
| 303 / 305 | Transfer Posting — Plant to Plant (Two Steps) | 304 / 306 | Two-step transfer: 303 removes from sending plant (stock in transit); 305 receives at destination plant. Used when physical transit time matters. |
| 311 | Transfer Posting — Storage Location to Storage Location (One Step) | 312 | Moves stock between two storage locations within the same plant. Most common within-plant stock transfer. Replaces MB1B for this scenario. |
| 343 | Transfer to Quality Inspection Stock | 344 | Moves unrestricted stock to quality inspection status for sampling or re-inspection without a formal QM inspection lot. |
| 412 | Transfer — Consignment Stock to Own Stock | 413 | Converts vendor-consignment stock (still owned by vendor) into company-owned (valuated) stock. Triggers vendor liability. Replaces MB1B for this scenario. |
| 501 | Receipt without Purchase Order (Without Reference) | 502 | Receives stock with no PO, contract, or production order reference. Replaces MB1C. Should be exception-only — auditors flag high 501 volumes. |
| 551 | Scrapping / Goods Issue for Sampling | 552 | Posts inventory loss to a scrapping account. Used for material write-offs, breakage, and quality sample consumption. |
| 601 | Goods Issue for Delivery (SD-linked) | 602 | Triggered by SD outbound delivery (VL02N), not typically posted manually in MIGO. Reduces stock on goods issue of customer delivery. |
The reversal rule every MM consultant must memorise: Every movement type has a reversal — the reversal code is always the next consecutive number (101 reverses with 102, 201 with 202, 261 with 262, 311 with 312, and so on). In S/4HANA, these movement types are identical to ECC — only the database table that stores the result has changed (MATDOC replaces MKPF/MSEG). Movement type knowledge is one of the most tested topics in SAP MM interviews.
MM Inventory — Stock Display & Physical Inventory
Stock Reporting & Physical Inventory T-Codes
SAP MM provides a rich set of stock reporting transactions — from the quick single-material MMBE overview to the period-end MB5B snapshot and the GR/IR balance check MB5S. Physical inventory transactions (MI01 through MI07) manage the formal stock-count process. All of these are unchanged in S/4HANA, though the underlying data is read from MATDOC rather than MKPF/MSEG.
Stock Display & Reporting
Stock Display Transactions7 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| MMBE | Stock Overview — All Stock Types, All Levels | Active | The most-used stock display transaction in SAP MM. Shows unrestricted, quality inspection, blocked, and restricted-use stock for one material across all plants and storage locations. Also shows special stocks: consignment, sales order stock, project stock, stock in transit. Unchanged in S/4HANA. Fiori: "Stock Overview" (F1531). |
| MB52 | Warehouse Stocks of Material (List) | Active | List display of stock quantities for multiple materials and storage locations — unlike MMBE which shows one material, MB52 shows many. Includes total value. Unchanged in S/4HANA. |
| MB53 | Plant Availability — Stock at All Plants | Active | Shows stock availability for a material across all plants — useful for checking if another plant has stock before placing a purchase order. Unchanged in S/4HANA. |
| MB5B | Stocks for Posting Date (Historical Snapshot) | Active | Displays stock levels as they were on a specific historical date — essential for period-end stock reconciliation and audit queries. Unchanged in S/4HANA. |
| MB51 | Material Document List (All Goods Movements) | Active | List all posted material documents (goods movements) by material, plant, movement type, or date range. One of the most useful audit and troubleshooting transactions in MM. In S/4HANA reads from MATDOC; unchanged tcode. |
| MB5S | GR/IR Clearing Account Balances | Active | Shows the open GR/IR items — purchases received but not yet invoiced, or invoiced but not yet received. Key input for the MR11 GR/IR clearing process at period end. Unchanged in S/4HANA. |
| MB56 | Analyse Deadstock / Slow-Moving Stock | Active | Identifies materials with no movement for a specified period — used for inventory rationalisation and write-off analysis. Unchanged in S/4HANA. |
Physical Inventory Transactions
Physical Inventory — Count, Enter, Post6 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| MI01 | Create Physical Inventory Document | Active | Creates the formal counting document for stock-taking — lists materials and storage locations to be counted. Blocks posting of goods movements for counted items during the counting period. Unchanged in S/4HANA. |
| MICN | Create Physical Inventory Documents (Mass) | Active | Mass creation of physical inventory documents for multiple storage locations or materials in one run. Used for annual stock counts covering large warehouses. Unchanged in S/4HANA. |
| MI04 | Enter Inventory Count Results | Active | Enters the physically counted quantities against the physical inventory document. SAP holds both the book quantity and the counted quantity to calculate the difference. Unchanged in S/4HANA. |
| MI07 | Post Inventory Differences | Active | Posts the inventory adjustment — debits or credits the inventory account for the quantity difference. Creates both a material document (MATDOC in S/4HANA) and an FI accounting document. Unchanged in S/4HANA. This must be done before closing the MM period. |
| MI20 | Print List of Inventory Differences | Active | Generates a report of all count differences before or after MI07 posting — used for management review and audit documentation. Unchanged in S/4HANA. |
| MI00 | Physical Inventory Menu | Active | Overview menu giving access to all physical inventory transactions in one place — useful for users who don't navigate via the main SAP menu. Unchanged in S/4HANA. |
MM — Material Requirements Planning
MRP T-Codes — Planning Run, Stock/Requirements, Planned Orders
MRP (Material Requirements Planning) calculates what materials need to be procured or produced, in what quantities, and by when — based on demand signals (sales orders, planned independent requirements) and available supply (stock, open POs). In S/4HANA, MRP undergoes its most significant change: MD01N (MRP Live) replaces the legacy MD01 batch run with real-time in-memory processing using the HANA engine, delivering dramatically faster planning results. MD04 remains the day-to-day planning analysis transaction. With ECC end-of-support in December 2027, understanding MD01N is one of the most practical gaps for any MM consultant to close right now.
MRP Planning Run Transactions
MRP Run Transactions5 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| MD01 | MRP — Total Planning Run (All Materials, One Plant) | Modified | Classic batch-based MRP run for an entire plant. Still available in S/4HANA for compatibility but MD01N (MRP Live) is the S/4HANA strategic standard. MD01 writes to the legacy MDTB planning file; MD01N uses HANA in-memory processing — typically 10–100x faster depending on data volume. For new S/4HANA implementations, MD01 should not be used. |
| MD01N | MRP Live — Total Planning Run (S/4HANA) | S/4 New | The S/4HANA MRP Live transaction. Replaces MD01 as the standard planning run. Uses HANA's in-memory engine to calculate MRP results in real time for an entire plant. Can run interactively (foreground for small plants) or in background (via MDBT). Does not write to MDTB — uses HANA-native planning tables. This is the most important new tcode in SAP MM for S/4HANA. |
| MD02 | Single-Item Multi-Level MRP | Active | Runs MRP for a single material across all BOM levels — explodes dependent requirements down the BOM tree. Still active in S/4HANA. For interactive single-item planning in S/4HANA, MD03 or MD02 remain the options. |
| MD03 | Single-Item Single-Level MRP | Active | Runs MRP for a single material at one BOM level only — does not explode to components. Useful for re-planning a specific material quickly. Unchanged in S/4HANA. |
| MDBT | MRP — Background Processing (Scheduled Job) | Active | Used to schedule MD01N (or MD01 in ECC) as a background job via SM36. In S/4HANA, MDBT triggers MD01N (MRP Live) automatically when running in an S/4HANA system. Unchanged tcode — the underlying engine it calls changed from MDTB-based to HANA-based. |
MRP Analysis & Planned Independent Requirements
MRP Analysis & PIR Transactions8 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| MD04 | Stock/Requirements List — Single Material | Active | The most important daily MRP analysis transaction. Shows the current planning picture for one material: current stock, open POs and PRs (supply), sales orders and PIRs (demand), planned orders — all in date sequence. Users can drill into source documents from MD04. In S/4HANA, MD04 reads real-time data. Fiori: "Monitor Material Coverage" (MRP Cockpit) for mass analysis. Unchanged tcode. |
| MD05 | MRP List — Displays Last MRP Run Result | Active | Static snapshot of MRP results from the last planning run — unlike MD04 which is always current. Used to review what MRP calculated on a specific run date without new changes being incorporated. Available in S/4HANA but MD04 preferred for current planning view. |
| MD06 | Collective Display — MRP List | Active | Mass view of MRP lists for multiple materials with exception messages — shows materials that require planner attention (e.g. overdue receipts, supply shortages). Unchanged in S/4HANA. |
| MD07 | Collective Display — Stock/Requirements List | Active | Same as MD06 but using the live stock/requirements data (not the static MRP list). Shows current exception messages across many materials. Unchanged in S/4HANA. |
| MD61 / MD62 / MD63 | Create / Change / Display Planned Independent Requirements | Active | Planned Independent Requirements (PIRs) are the demand driver for make-to-stock scenarios — forecast quantities entered for a material that MRP uses to generate planned orders and purchase requisitions. Used in sales-plan-driven MRP environments. Unchanged in S/4HANA. |
| CO41 | Convert Planned Orders to Production Orders (Mass) | Active | Mass conversion of MRP-generated planned orders to production orders for PP. Unchanged in S/4HANA. (Also relevant for MM consultants who work at the MM/PP interface.) |
MM — Logistics Invoice Verification
Invoice Verification T-Codes — MIRO, MRBR, MR11, Period-End
Invoice Verification (MM-IV) is where procurement meets finance — the point at which a vendor invoice is matched against the purchase order and goods receipt, and an FI accounting document is created. MIRO is the central transaction. In S/4HANA, MIRO is unchanged and its accounting documents now post to ACDOCA (the Universal Journal) alongside the standard FI tables — meaning invoice postings are immediately reflected in real-time financial reporting. For the pure FI side of invoice and payment processing, see the SAP FICO T-Codes — Accounts Payable section.
Invoice Posting & Processing
Invoice Verification Transactions7 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| MIRO | Post Incoming Invoice (Logistics Invoice Verification) | Active | The central invoice verification transaction in SAP MM. Posts vendor invoices referencing a PO with 3-way match (PO — GR — Invoice). Checks price tolerance (OMBR) and quantity tolerance automatically. Creates an MM invoice document AND an FI accounting document simultaneously. In S/4HANA, MIRO posts to ACDOCA in real time. Fiori: "Post Incoming Invoice." Unchanged tcode. |
| MIR4 | Display Invoice Document (MM-IV) | Active | Read-only display of a posted MIRO invoice document. Unchanged in S/4HANA. |
| MIR6 | Invoice Overview (MM-IV) | Active | List display of all invoice documents with flexible filters — status (posted, parked, blocked), vendor, plant, date range. Unchanged in S/4HANA. |
| MIR7 | Park Incoming Invoice | Active | Parks an invoice for later completion and posting — creates a parked document without an FI posting. Used when invoice data needs review or approval before posting. Unchanged in S/4HANA. |
| MR8M | Cancel Invoice Document | Active | Cancels a posted MIRO invoice — creates a reversal document. Used when an invoice was posted incorrectly and needs to be corrected. Unchanged in S/4HANA. |
| ML81N | Post Service Entry Sheet | Active | Posts the service acceptance confirmation for service POs (limit and item-based service orders). Service entry sheets are the equivalent of a goods receipt for services — they trigger the financial posting. Unchanged in S/4HANA. |
| MIRA | Fast Invoice Entry (Invoice Cockpit) | Active | Simplified invoice entry for high-volume processing — designed for AP clerks who process many invoices quickly. Less flexible than MIRO but faster for standard scenarios. Unchanged in S/4HANA. |
Blocked Invoices & GR/IR Clearing
MRBR, MR11, Period-End Invoice Transactions4 codes
| T-Code | Description | S/4HANA Status | Notes / S/4HANA Change |
|---|---|---|---|
| MRBR | Release Blocked Invoices | Active | Critical for Accounts Payable. Shows all MIRO invoices automatically blocked due to price or quantity tolerance variances (configured in OMBR). An authorised user reviews and releases invoices before F110 can pay them. No F110 payment is possible until MRBR release. Unchanged in S/4HANA. Fiori: "Release Blocked Invoices" (F2163). |
| MR11 | Maintain GR/IR Clearing Account | Active | Clears residual GR/IR account balances at period end — e.g. a PO received 100 units but only 95 were invoiced, leaving a 5-unit residual open in the GR/IR account. MR11 either writes off the residual or posts a correction. Essential period-end step. Unchanged in S/4HANA. |
| MMPV | Close MM Posting Period / Open New Period | Active | Closes the current MM posting period and opens the next one. Must run monthly — before the FI period close. Without MMPV, goods movements will post to the wrong period. Unchanged in S/4HANA. |
| MMRV | Allow Posting to Previous MM Period | Active | Temporarily allows goods movements to post to the previous MM period — used when a late MIGO needs to hit the prior period for reconciliation purposes. Requires authorisation. Unchanged in S/4HANA. |
| CKMLCP | Material Ledger Closing Cockpit (Actual Costing) | Modified | Mandatory in S/4HANA for ALL company codes using MM. In ECC, Material Ledger was optional. In S/4HANA it is always active — CKMLCP must run monthly to close the ML period and calculate actual costs. Runs single-level price determination, multi-level price determination, and revaluation of consumption. Even companies using only standard costing (not actual costing) must close the ML period via CKMLCP. See also: SAP FICO T-Codes (CO-PC) for the full Product Costing context. |
| OMBR | Invoice Tolerance Keys — Configuration | Active | Configuration tcode for invoice verification tolerance settings — defines the price variance (%) and amount thresholds that trigger automatic blocking in MIRO. If MRBR is blocking too many (or too few) invoices, the tolerance keys in OMBR are the root cause to investigate. Unchanged in S/4HANA. |
The MIRO–F110 connection every MM consultant must know: MIRO posts the invoice and creates an open vendor line item in FI. MRBR must release any blocked invoices. F110 (Automatic Payment Program) then selects open vendor items and executes payment. The flow is: MIGO (GR) → MIRO (invoice) → MRBR (if blocked) → F110 (payment). In S/4HANA, all three MM steps are unchanged. The FI payment side (F110) is equally unchanged. This end-to-end flow is the single most tested process in SAP MM interviews.
S/4HANA Change Master List
Every MM Tcode Change in S/4HANA — Deprecated, Modified, New
This is the consolidation table every MM professional preparing for an S/4HANA migration or interview needs. All deprecations, modifications, and new tcodes in one place — with the reason behind each change and the correct S/4HANA approach.
SAP MM — S/4HANA Complete Change Reference16 entries
| ECC Tcode | What it did | S/4HANA Status | S/4HANA Replacement / Explanation |
|---|---|---|---|
| MK01 / MK02 / MK03 | Create / Change / Display Vendor — Purchasing View | Deprecated | Replaced by BP (Business Partner). In S/4HANA, assign role FLVN00 within BP for the purchasing view. LFB1 and LFA1 tables still exist as compatibility views; the primary storage is the BP data model (BUT000 family). |
| XK01 / XK02 / XK03 | Create / Change / Display Vendor — Central | Deprecated | Replaced by BP. XK01 was the combined FI + MM vendor creation transaction. BP is now the single central transaction for all views in one record. |
| FK01 / FK02 / FK03 | Create / Change / Display Vendor — FI View | Deprecated | Replaced by BP. In S/4HANA, assign role FLVN01 within BP for the FI accounting view (reconciliation account, payment method, house bank). |
| MB1A | Goods Withdrawal / Goods Issue (classic) | Deprecated | Replaced by MIGO. Use MIGO with the appropriate goods issue movement type (201 for cost centre, 261 for production order, 281 for project). MB1A screen is no longer available in S/4HANA. |
| MB1B | Transfer Posting (classic) | Deprecated | Replaced by MIGO. Use MIGO with transfer movement types: 311/312 (within plant), 301 (plant-to-plant), 412 (consignment to own stock). |
| MB1C | Other Goods Receipt (without PO reference) | Deprecated | Replaced by MIGO. Use MIGO with movement type 501 for receipt without reference. MB1C is no longer available in S/4HANA. |
| LT01 / LT0A / LT11 | Create / Confirm Transfer Orders (Classic WM) | Deprecated | Classic Warehouse Management is deprecated in S/4HANA. Use Embedded EWM (Extended Warehouse Management) Fiori apps for all warehouse operations. Companies on S/4HANA must plan WM → EWM migration. |
| LQ01 / LQ02 | Quant Management (Classic WM) | Deprecated | Classic WM quant management deprecated. EWM uses Storage Unit Management in Fiori apps. Basic stock overview (MMBE, MB52) is not impacted — only the warehouse-layer transactions. |
| MD01 | MRP Total Planning Run (Batch — entire plant) | Modified | Still available in S/4HANA but MD01N (MRP Live) is the strategic replacement. MD01 uses MDTB-based batch processing; MD01N uses HANA in-memory engine and is 10–100x faster. For new S/4HANA implementations, configure MD01N instead of MD01. |
| MM01 | Create Material Master | Modified | Still the primary transaction but screens are simplified in S/4HANA. Some ECC view combinations are consolidated. The Accounting views now incorporate Material Ledger data natively. Fiori: "Manage Product Master Data" available as the modern interface. |
| MKPF / MSEG | Material Document Header / Line Item Tables (DB) | Deprecated | Not a tcode — but worth knowing: MKPF and MSEG are replaced by MATDOC as the single material document table in S/4HANA. SAP GUI tcodes like MB03 and MB51 transparently read MATDOC; your ABAP custom reports reading MKPF/MSEG directly will need updating. |
| EKKO / EKPO | Purchase Order Header / Line Item Tables (DB) | Modified | EKKO and EKPO still exist in S/4HANA but the data model is extended. New fields added for S/4HANA features (e.g. SAP Business Network integration). MIGO, ME21N, ME23N all read/write correctly — only custom ABAP with direct EKKO/EKPO SELECTs may need review. |
| MD01N | (S/4HANA New) MRP Live — In-Memory Planning Run | S/4 New | New transaction in S/4HANA only. Replaces MD01 as the standard total planning run. Uses HANA in-memory processing for real-time, high-performance MRP. Can run interactively or via MDBT background job. The most important new MRP transaction for S/4HANA. |
| BP | (S/4HANA New) Business Partner — Central Master Data | S/4 New | Central business partner transaction replacing all vendor master (MK01/XK01/FK01) and customer master (XD01/VD01/FD01) transactions. Roles FLVN00 (MM) and FLVN01 (FI) cover all vendor views. One record per business relationship — replaces the split FI/MM vendor data model of ECC. |
| MIGO | Goods Movement (All-in-One) | Modified | MIGO is active and the tcode is unchanged — but in S/4HANA it writes to MATDOC (not MKPF/MSEG) and simultaneously updates ACDOCA (the Universal Journal). The posting is now a single atomic write to both inventory and finance. Functionally identical to use; architecturally simplified. |
| MIRO | Post Incoming Invoice (Logistics IV) | Modified | MIRO is active and unchanged as a tcode. In S/4HANA, MIRO postings write to ACDOCA alongside the standard FI tables. This means MIRO invoices are immediately visible in Universal Journal reports (FAGLL03H, KE30 etc.) without any period-end data transfer. Functionally identical to use. |
Frequently Asked Questions
SAP MM T-Code FAQ — 20 Most-Asked Questions Answered
For SAP MM beginners, the essential transaction codes to master first are:
MM01/02 (create/change material master), ME51N (create purchase requisition), ME21N (create purchase order), MIGO (goods receipt, goods issue, transfer posting), MIRO (logistics invoice verification), MMBE (stock overview), MD04 (stock and requirements list for MRP), ME11 (purchase info record), MRBR (release blocked invoices), and SPRO (customizing). In S/4HANA, add BP for vendor master creation and MD01N for MRP Live planning runs.The major SAP MM transaction code changes in S/4HANA are: (1)
MK01/MK02/MK03 replaced by BP for vendor purchasing master; (2) XK01/XK02/XK03 replaced by BP for vendor central master; (3) FK01/FK02/FK03 replaced by BP for vendor FI master; (4) MB1A/MB1B/MB1C (legacy goods movement transactions) deprecated in favour of MIGO; (5) MD01 MRP batch run replaced by MD01N (MRP Live) for in-memory planning; (6) Classic WM transactions LT01/LT0A/LT11/LQ01 deprecated in favour of Embedded EWM Fiori apps; (7) ME21N, MIGO, and MIRO still fully active but Fiori equivalents are the preferred interface in modern S/4HANA implementations.Yes,
ME21N (Create Purchase Order) is fully active and unchanged in SAP S/4HANA. It remains the standard SAP GUI transaction for creating purchase orders across all purchasing document categories — standard NB, subcontracting, consignment, stock transport orders, and service POs. The Fiori equivalent "Manage Purchase Orders" provides an enhanced browser-based interface but ME21N via SAP Logon is fully supported in all S/4HANA releases. Most S/4HANA implementations run both interfaces simultaneously — Fiori for end-users and role-based workflows, SAP GUI for power users, configurators, and complex purchasing scenarios.In SAP S/4HANA, all vendor master transactions —
MK01/MK02/MK03 (purchasing view), XK01/XK02/XK03 (central), and FK01/FK02/FK03 (FI view) — are replaced by the Business Partner transaction (BP). S/4HANA uses the Business Partner concept to manage all business relationships centrally. Within BP, vendor roles are assigned: FLVN00 for the MM purchasing role (purchasing organisation data, incoterms, payment terms) and FLVN01 for the FI accounting role (reconciliation account, payment method, house bank). This eliminates the need to create and maintain vendor data separately across FI and MM — one BP record covers all views.ME51N creates a Purchase Requisition (PR) — an internal procurement request. A PR expresses the need to purchase material or services and requires internal approval, but has no legal binding with any external vendor. ME21N creates a Purchase Order (PO) — the binding legal procurement document issued to a specific external vendor with confirmed quantities, prices, and delivery dates. The typical procurement flow is: ME51N (user raises PR) → approval via ME54N or workflow → ME57 (source assignment to a vendor or contract) → ME21N (PO created against the approved PR). Both transactions are unchanged in S/4HANA.MIGO (Goods Movement) is the single all-in-one transaction for all inventory movements in SAP MM. It handles: Goods Receipt against PO (movement type 101), GR against production order (101), GR without reference (501), Goods Issue to cost centre (201) or production order (261), Transfer Posting plant-to-plant (301) or storage location-to-storage location (311/312), Return to vendor (122), and cancellation of any prior goods movement. MIGO replaced the legacy MB1A/MB1B/MB1C transactions. In S/4HANA, MIGO is active and unchanged; Fiori equivalents are "Post Goods Movement" (F0843) and "Receive Delivery" (F2386).MB1A (Goods Withdrawal/Issue), MB1B (Transfer Posting), and MB1C (Other Goods Receipt without reference) are all deprecated in SAP S/4HANA in favour of MIGO. MIGO consolidates all goods movement types in a single transaction. To replicate MB1A, use MIGO with movement type 201 (cost centre issue) or 261 (production order issue). For MB1B, use MIGO with movement type 311 (within plant) or 301 (plant-to-plant transfer). For MB1C, use MIGO with movement type 501 (GR without PO reference). The movement type selected in MIGO determines the specific business scenario — and these movement types are identical in ECC and S/4HANA.MD04 (Stock/Requirements List) is the primary MRP analysis transaction for a single material. It shows the current planning picture in date sequence: current stock balance, open purchase orders and purchase requisitions (supply elements), planned orders, sales order requirements, dependent requirements from BOMs, and planned independent requirements (PIRs). From MD04, users can drill down to any source document, convert planned orders to purchase requisitions, and manually create supply elements. In S/4HANA, MD04 is still the primary GUI tcode for single-material planning analysis; the Fiori "MRP Cockpit" ("Monitor Material Coverage") provides a mass view across multiple materials simultaneously.MD01 is the classic SAP ECC total MRP planning run — it processes all materials in a plant in batch mode, writing planning results to the MDTB planning file table. MD01 is still available in S/4HANA for compatibility but is not the recommended approach for new implementations. MD01N is the SAP S/4HANA MRP Live transaction that leverages HANA's in-memory processing engine to run MRP calculations in real time — dramatically faster than batch-based MD01 for large material portfolios. MD01N can run interactively for a single plant or in background via MDBT. For S/4HANA implementations, MD01N is the strategic standard and should be configured as the primary planning run.MIRO (Post Incoming Invoice) is the Logistics Invoice Verification transaction for posting vendor invoices that reference a purchase order. It performs a 3-way match — PO vs Goods Receipt vs Invoice — and checks price and quantity tolerances automatically. MIRO creates both an MM invoice verification document and an FI accounting document simultaneously. FB60 is a pure FI transaction for posting vendor invoices with no PO reference — utility bills, rent, professional fees. FB60 creates only an FI accounting document with no MM integration and no 3-way match check. The key rule: PO-based invoice → MIRO. Non-PO invoice → FB60. Both are unchanged in S/4HANA.MR11 (Maintain GR/IR Clearing Account) is used to clear residual quantities and values in the GR/IR (Goods Receipt/Invoice Receipt) clearing account when goods receipts and invoice receipts do not balance. For example, if a PO was for 100 units, 100 were received via MIGO, but only 95 were invoiced via MIRO, the remaining 5-unit value sits open in the GR/IR account. MR11 allows an authorised user to clear these residual items — either by posting a write-off or by creating an adjustment entry. MR11 is a standard period-end closing transaction in SAP MM and is unchanged in S/4HANA. The MB5S report is used to identify which GR/IR items need MR11 clearing.SAP MM physical inventory transaction codes are:
MI01 (create physical inventory document), MI04 (enter inventory count results against the document), MI07 (post inventory differences after the count is confirmed), MICN (create inventory documents in mass for multiple storage locations), MI20 (print list of inventory differences), MI21 (print physical inventory document), MI00 (physical inventory menu — overview of all PI steps), MI10 (create or change inventory count without a prior document). In S/4HANA, the Fiori apps "Post Physical Inventory" and "Count Physical Inventory" are available alongside these GUI transactions. Physical inventory differences must be posted via MI07 before the MM period can be closed.MMBE (Stock Overview) is the primary stock display transaction in SAP MM. It shows current inventory quantities for a single material across all organisational levels — client, plant, storage location — and across all stock types: unrestricted use, quality inspection stock, blocked stock, and restricted-use stock. MMBE also shows special stocks: consignment stock (vendor-owned at your premises), sales order stock, project stock, and stock in transit between plants. Users can drill down from MMBE to the underlying material documents. MMBE is active and unchanged in S/4HANA; the Fiori equivalent is the "Stock Overview" app (F1531).Outline agreements are long-term procurement arrangements with vendors. There are two types: Contracts and Scheduling Agreements. A Contract (
ME31K) defines a total agreed quantity or value with a vendor; individual deliveries are released by creating release purchase orders against the contract via ME21N. A Scheduling Agreement (ME31L) defines a fixed delivery schedule with specific quantities on specific future dates. Key transaction codes: ME31K (create contract), ME32K (change), ME33K (display), ME35K (release contract), ME31L (create scheduling agreement), ME32L (change), ME38 (maintain delivery schedule lines). All are active and unchanged in S/4HANA.A Contract (
ME31K) is a value or quantity agreement with a vendor where the total volume is fixed but individual delivery quantities and dates are not specified upfront — buyers release individual purchase orders (release orders) against the contract as needed via ME21N. A Scheduling Agreement (ME31L) is more tightly integrated with production planning — it defines specific delivery quantities on specific future dates, maintained via ME38. Scheduling agreements are standard practice in automotive and high-volume manufacturing environments where just-in-time delivery and vendor-managed delivery schedules are required. Both types support price conditions, release strategies, and source list entries. Both are active and unchanged in S/4HANA.ME11 (Create Purchase Info Record) defines and stores the purchasing relationship between a specific material and a specific vendor — including the agreed price, applicable price conditions, planned delivery time (lead time in days), tolerance settings, and applicable purchase order text. When ME21N creates a purchase order for that material-vendor combination, SAP automatically defaults the price and delivery time from the info record. Info records are the foundation of price defaulting in SAP MM, the basis for the price comparison list (ME49) when evaluating quotations, and the link between source lists and pricing. ME11 is active and unchanged in S/4HANA.MRBR (Release Blocked Invoices) is used to review and release vendor invoices that were automatically blocked during MIRO processing because price or quantity variances exceeded the tolerance limits configured in OMBR (invoice tolerance key settings). When a MIRO invoice is blocked, no payment can be made via F110 until it is released. MRBR shows all blocked invoices with the reason for blocking — price variance, quantity variance, or other tolerance breach — and allows an authorised user to release individual invoices after investigation, or to return them for reversal via MR8M. MRBR is unchanged in S/4HANA; the Fiori equivalent is "Release Blocked Invoices" (F2163).Classic Warehouse Management (WM) — using transactions such as
LT01 (create transfer order), LT0A (create transfer order without reference), LT11 (confirm transfer order), LQ01/LQ02 (quant management), and LI01 (physical inventory for WM) — is deprecated in SAP S/4HANA. SAP S/4HANA uses Embedded Extended Warehouse Management (EWM), which provides equivalent and significantly enhanced WM functionality through Fiori apps. Companies migrating from ECC to S/4HANA that use Classic WM must plan a separate WM-to-EWM migration workstream. Basic inventory management (MIGO, MMBE, MB52) is not impacted — only the warehouse-layer transfer order transactions are replaced.SAP MM period-end closing transaction codes are:
MMPV (close the current MM posting period and open the next — must run monthly), MMRV (allow posting to the previous period if needed), MB5B (stock on posting date — for stock reconciliation), MB5S (display GR/IR account balances for MR11 analysis), MR11 (clear GR/IR account residuals), MI07 (post physical inventory differences), CKMLCP (Material Ledger period close — mandatory in S/4HANA for all company codes). The MM period must be closed before the FI period. In S/4HANA, the Fiori "Schedule MM Period Close" app supports automated period-end orchestration across plants.Key Fiori app replacements for MM transaction codes in S/4HANA:
ME21N → "Manage Purchase Orders" (F1048A); ME51N → "Create Purchase Requisition" (F2229); MIGO → "Post Goods Movement" (F0843) and "Receive Delivery" (F2386); MIRO → "Post Incoming Invoice"; MD04 → "Monitor Material Coverage" (MRP Cockpit); MMBE → "Stock Overview" (F1531); MRBR → "Release Blocked Invoices" (F2163); ME31K → "Manage Purchase Contracts"; MM01 → "Manage Product Master Data"; BP → "Manage Business Partner Master Data". All SAP GUI transaction codes remain supported alongside Fiori apps in S/4HANA — companies choose which interface to present to each user role based on process complexity and adoption strategy.Know every MM tcode. Now use them on a real system.
A reference page builds awareness.
Live SAP access builds careers.
VoiSAP's live online SAP MM training gives you hands-on access to a real SAP system — every transaction code on this page becomes second nature, not just memorized text. Trained by an 18-year SAP practitioner. 278+ Google reviews at 4.8 stars.
*Live SAP system access included. Canada & USA. 278+ Google reviews at 4.8 stars.
Related Resources on VoiSAP