SAP MM: Inventory Management and Movement Types in SAP

โšก Smart Summary

Inventory Management in SAP MM tracks every goods movement through movement types, material documents, and stock types, driving receipts from purchase orders, transfers between plants, and issues for delivery in one unified module.

  • ๐Ÿ”˜ Movement Types: Three-digit keys such as 101, 201, 311, and 601 identify the purpose of each goods movement and drive posting logic, stock accounts, and reversal behaviour.
  • โ˜‘๏ธ Movement Indicators: B for purchase order, F for production order, L for inbound delivery, and blank for no reference reuse the same movement type across different source documents.
  • โœ… Material Document: Every movement writes a material document that captures source and destination storage locations, quantity, and the movement type that classifies the change.
  • ๐Ÿงช Reversals: Every movement type has a paired reversal: 101 pairs with 102, 311 with 312, and 601 with 602, so a wrong posting is corrected without deleting the original document.
  • ๐Ÿ› ๏ธ Configuration OMJJ: Transaction OMJJ is the customising cockpit for movement types, letting an MM lead adjust field selection, account grouping, and reason codes.
  • ๐Ÿค– AI Assist: Machine-learning models forecast stock levels, flag anomalous movements, and Copilot for SAP drafts BAPI_GOODSMVT_CREATE calls for bulk posting from external systems.

SAP MM Inventory Management and Movement Types

Inventory Management in SAP MM

Inventory Management is the SAP MM sub-module that tracks the physical stock of every material at every plant and storage location. It rests on four core processes: movement type maintenance, reservations, goods receipt, and goods issue.

Basic goods receipt was already covered in the purchase order topic, where a receipt is posted against an existing PO. Inventory Management extends that model to every kind of movement — PO receipts, production-order receipts, transfers between plants and storage locations, issues for delivery, and unplanned scrapping.

The most important transactions and functions are covered in the sections below.

What is Movement Type in SAP?

Movement Types are three-digit indicators of the purpose of a goods movement — for example, moving stock between storage locations, receiving stock from a purchase order, issuing stock for a delivery, or receiving finished goods from a production order.

The movement type classifies the posting, drives the account determination in Finance, controls which fields appear on the goods-movement screen, and decides whether the material document has a source location, a destination location, or both.

Movement types in SAP โ€“ Examples

Movement types ship with predefined settings in the standard SAP system and can be customised to match business needs. A movement type is a three-digit identification key for a goods movement such as 101, 201, 311, or 321.

The same movement type can serve different processes when combined with a movement indicator. For example, movement type 101 with indicator B is used for goods receipt against a purchase order, while movement type 101 with indicator F is used for goods receipt against a production order.

The next screen shows how the movement-type maintenance screen appears. Movement types are configured through transaction OMJJ.

  1. Execute the OMJJ transaction. On the initial screen, choose Movement type, then enter the movement-type range you want to edit.
  2. The screen that appears has a dialog structure on the left. These nodes drive the settings applied to each movement type.
  3. Selecting any node updates the detail screen on the right with the settings that belong to it.

OMJJ movement type maintenance screen โ€” dialog structure and settings

Full OMJJ configuration falls outside the scope of this tutorial because it requires deep knowledge of the MM inventory-management processes. The important point for now is what the movement type and movement indicator represent.

Feel free to take a tour of the OMJJ transaction to see the settings available at both movement-type and movement-type/indicator level.

To summarise, movement types classify how goods flow through inventory. A few common examples:

  • Movement type 101 — goods receipt.
  • Movement type 311 — stock transfer from one storage location to another in one step.
  • Movement type 601 — goods issue for an outbound delivery.

Every movement type has a paired reversal movement type. To cancel 311 the reversal is 312. Similarly, 101 reverses with 102, and 601 with 602.

A material document is the SAP document that records the processing of a goods movement (receipt, issue, or transfer). Creating a material document actually moves stock quantity in the way defined by the movement type.

If movement type 311 is set on the material document, the material is transferred from one storage location to another. If it is 101, the material document has no source location but does have a destination (receipt). If it is 601, the material document has only a source location and no destination (issue).

Types of Stock in SAP MM

Every stock quantity in SAP MM sits in a specific stock category. The category decides whether the quantity is available for planning, reserved for orders, or locked out of MRP. The main stock types are:

  • Unrestricted-use stock — freely available, counted in MRP, and ready to consume or ship.
  • Quality inspection (QI) stock — posted after receipt, not usable until a usage decision in QM releases it.
  • Blocked stock — damaged or on-hold quantity that must not be consumed. Not counted in MRP.
  • Stock in transit — issued from the sending plant, not yet received at the destination during a two-step transfer.
  • Consignment stock — vendor-owned stock at the buyer’s premises. Ownership transfers only on withdrawal.
  • Returns stock — goods returned by a customer, pending a decision to scrap, block, or return to unrestricted.

Reports MMBE (stock overview), MB52 (warehouse stock list), and MB5B (stock on posting date) show every stock type by material, plant, and storage location.

Common Inventory Management Transactions

Daily inventory work usually happens in a small set of transactions. The core list to know:

  • MIGO — the unified goods-movement transaction. Handles receipt against PO, receipt against production order, transfer, and issue in one screen.
  • MB1A — goods issue (movement types 201, 261, 551, 601, and reversals).
  • MB1B — transfer posting between storage locations or plants (movement types 311, 313, 411, 412).
  • MB1C — other goods receipt without reference (movement types 501, 561 initial stock upload).
  • MB01 — goods receipt for a purchase order (legacy transaction; MIGO is the modern replacement).
  • MB51 — material document list report filtered by movement type, date, plant, or material.
  • MB52 — warehouse stock list by material and storage location.
  • MMBE — stock overview by plant, storage location, and stock category.
  • MB5B — stock on posting date, useful for period-end audit and balance verification.

Programmatic movements use BAPI BAPI_GOODSMVT_CREATE, which is the recommended route for external clients, LSMW loads, and RPA scripts that post stock movements.

Goods Receipt Scenarios

As covered earlier, a goods receipt can be posted with reference to a purchase order, a production order, an inbound delivery, or without any reference for other kinds of receipts.

Movement-type behaviour changes according to the movement indicator. Several indicators specify the reference-document type and, in combination with the movement type, drive posting behaviour:

  • B — purchase order.
  • F — production order.
  • L — inbound delivery.
  • Blank — no reference.
  • Other — not significant for this introduction.

The combination of movement type and movement indicator classifies every goods receipt precisely and links the material document to the correct source document in the process chain.

FAQs

A movement type is a three-digit key such as 101, 201, 311, or 601 that classifies the purpose of a goods movement. It drives account determination, field selection, and the reversal counterpart for every material document.

101 receipt from PO or production, 201 issue to cost centre, 261 issue to order, 311 transfer between storage locations, 561 initial stock upload, and 601 issue for delivery. Every one has a reversal (102, 202, 262, 312, 562, 602).

A single-letter tag that says which reference document is behind a receipt: B purchase order, F production order, L inbound delivery, blank for none. It lets one movement type behave differently per source document.

The SAP document written by every goods movement. It stores movement type, source and destination locations, quantity, material, plant, and posting date. Header table MKPF, item table MSEG. Reports include MB51 and MB03.

MIGO is the unified transaction. It replaces MB01, MB1A, MB1B, MB1C, MB31, and MB0A. MIGO handles receipts against PO or production order, issues, transfers, and cancellations from one screen and is standard in S/4HANA.

Unrestricted-use, quality inspection, blocked, stock in transit, consignment, and returns. MMBE, MB52, and MB5B report every category by plant and storage location.

Machine-learning models forecast demand from historical MSEG movements, spot anomalous postings that hint at fraud or a wrong movement type, and recommend safety-stock levels per plant, feeding the results back into MRP for tighter service levels.

Copilot for SAP drafts BAPI_GOODSMVT_CREATE calls, generates the ABAP wrapper for LSMW or an RPA script, and validates movement-type and indicator pairing. Users review the generated code before posting to production.

Summarize this post with: