MARD table — MARD Storage Location Stock Table

One row in MARD represents the stock situation for one material in one storage location within one plant. It is created when the material is extended to that storage location, either explicitly through master data maintenance or implicitly the first time a goods movement posts stock into it. The row carries quantity fields split by stock category: unrestricted-use, quality inspection, blocked, stock in transfer between plants, and restricted-use stock. All quantities are in the base unit of measure of the material, not in any alternate unit. MARD does not carry value; the same material at the same plant has a single value bucket in MBEW regardless of how many storage locations its quantity is spread across. MARD is a quantity ledger at the storage location grain, nothing more.

MARD is client-dependent and reasonably narrow per material, so a selection on MATNR plus WERKS plus LGORT is fully selective and returns at most one row. Never select on MATNR alone across a large material master when the intent is a single plant or location; restrict WERKS first if the plant is known, since that alone cuts the table down enormously compared to scanning by material. Do not filter on LABST equal to zero expecting to find dead stock reliably, because a row with all quantity fields at zero can legitimately exist after the location was extended but never received stock, and conversely a location with real stock elsewhere is not visible from a zero row here.

To confirm that a reported stock shortage is a storage location issue rather than a plant-wide shortage, select MARD by MATNR and WERKS with no LGORT restriction and compare LABST across all returned storage locations. If total quantity across locations matches what MRP or the stock overview expects but is concentrated in one LGORT while the transaction being executed points at another, the problem is a storage location split, not missing stock. Cross-check the same MATNR/WERKS against MBEW to confirm the value side is unaffected.

MARD continues to exist as a database table in S/4HANA and is still readable directly, but the underlying source of truth for quantities moved to the material document line item data model. Stock quantities are derived from that document-based model and MARD is kept consistent through the compatibility layer, so reads against MARD return correct current values without any application change required. Custom code that reads MARD directly still works; code that expected to insert or update MARD directly needs review, since direct writes bypass the document-based update logic.

Inventory management or warehouse operations within the MM team owns discrepancies in MARD quantities, since they trace back to goods movements and storage location master data extension. Finance gets involved only when the value side in MBEW is in question, which MARD alone cannot answer.

MSEG and MKPF hold the movement documents that build MARD balances and are the first place to trace how a quantity got to its current value. MCHB carries the batch split of the same quantity when the material is batch-managed. MSKA and MKOL carry special stock quantities such as sales order and consignment stock that never appear in MARD. MBEW carries the value corresponding to MARD's quantity. T001L and MARC hold the storage location and plant master data that must exist before a MARD row can be created.