Translating movement types, stock types, and warehouse management

How SAP's movement-type-driven inventory model — where a single integer bundles stock effect, account determination, screen control, and allowed fields — is decomposed in D365 across transaction type, item model group, inventory posting setup, and dimension configuration; and how SAP WM and EWM map to D365 basic and advanced warehousing.

What you will be able to do

• Describe what a SAP movement type encodes and explain why it has no single D365 equivalent
• Map SAP stock types to D365 inventory status and quality order concepts
• Identify the D365 configuration objects that collectively replace a SAP movement type
• Explain how SAP special stock categories (consignment, project stock) translate to D365
• State when basic warehousing is sufficient and when the D365 WMS module is required

Introduction

SAP's movement type is perhaps the most SAP-specific concept in the entire materials management module. A movement type is a two- or three-digit code — 101 for a goods receipt against a purchase order, 201 for a goods issue to a cost centre, 301 for a plant-to-plant transfer, 551 for a goods issue to scrapping — that bundles four…

SAP inventory structure: plant, storage location, stock types, and special stock

Plant + storage location (MARD). The main quantity table. One row per material per plant per storage location. Columns: unrestricted-use stock (LABST), quality-inspection stock (INSME), restricted-use stock (EINME), blocked stock (SPEME), in-transit stock (UMLME), and several special-stock indicator columns.

Movement types: what they encode and why they don't translate

The movement type (BWART) in MSEG is the most heavily loaded field in the SAP materials management data model. Consider two examples:

Warehouse Management: classic WM, EWM, and D365 equivalents

SAP offers two warehouse management levels. Classic WM (transactions LT01, LT0A) manages physical warehouse operations within a warehouse complex, using storage types (bulk, shelved, high-rack) and storage bins as the structural model. Transfer orders are the execution objects;

D365 inventory model: dimensions, on-hand, item model groups, and inventory close

D365 on-hand inventory is tracked at the intersection of the active storage and tracking dimensions. For a product with site, warehouse, batch, and serial number active, on-hand exists at the level of site + warehouse + batch + serial. The InventSum table holds quantity aggregates; InventTrans holds the individual inventory transactions.

Valuation, material ledger, and split valuation

SAP values inventory at the valuation area level, which is typically the plant (MARC-BWKEY). The MBEW table holds one record per material per valuation area, carrying the price control indicator (V = moving average, S = standard price), the standard price, and the total stock value.

Knowledge check

Summary

SAP's inventory model is movement-type-centric: a single code bundles stock effect, account determination, screen control, and document requirements. D365 distributes these concerns across transaction type, item model group, posting setup, and document configuration. The movement type table cannot be migrated;