MARM table — Units of Measure for Material

Each row in MARM represents one alternative unit of measure defined for one material, together with the factor that converts a quantity in that unit back to the material's base unit (stored in MARA-MEINS). A material with a base unit of EA might also have rows for CAR (case) and PAL (pallet), each carrying its own UMREZ/UMREN ratio. Rows also carry unit-specific physical data - length, width, height, volume, and gross weight for that packaging unit - and can carry an EAN/UPC barcode assigned specifically to that unit, which is how a single material can have one barcode for the each and a different barcode for the case. The base unit itself normally does not need a row in MARM because its conversion to itself is implicit, though some materials do carry one for barcode purposes.

MARM is small relative to MARA - one to a handful of rows per material - so it is never the bottleneck table in a query, but it is only useful read together with MARA-MEINS to know what the conversion is relative to. Always restrict on MANDT and MATNR; MEINH alone is not selective. Never assume UMREZ/UMREN reduce to a whole number ratio - read both fields and divide, do not guess from the unit name (a 'case' of 24 is not implied by the text CAR). If a material has no row for a given unit that appears on a document, the document line was entered with a unit not defined for that material, which is itself the finding.

Symptom: a goods receipt posted for 10 CAR shows as 240 EA in stock instead of the expected 120 EA. Select MARM where MATNR equals the material and MEINH equals CAR. Read UMREZ and UMREN. If UMREZ/UMREN is 24 EA per CAR, the system converted correctly and the expectation of 12 per case was wrong; if UMREZ/UMREN is 12, the master data conversion factor is wrong and needs correction with a forward-dated change, not a manual stock adjustment.

MARM is unchanged in S/4HANA as a transparent table and continues to be maintained through the standard material master transactions and the Manage Product Master Fiori app. It is exposed through the standard material master CDS views alongside MARA rather than through a dedicated compatibility view of its own, since it was not part of the classic MM tables that were split or aggregated in the S/4HANA data model conversion.

Master data governance or the MM/logistics data steward owns MARM content, since it is maintained through the material master units-of-measure view and touches purchasing, sales, and warehouse teams alike. A conversion factor dispute is resolved by checking who last changed the unit of measure view on the material, not by the functional team that noticed the wrong quantity downstream.

MARA holds the base unit that every MARM conversion is relative to. MARC and MVKE can restrict which units are proposed at plant or sales-area level even though the conversion itself lives in MARM. EKPO, MSEG, and RSEG carry the unit actually used on a given purchasing, goods movement, or invoice line, resolved against MARM at posting time. Material master maintenance transactions such as the material master change/create screens are what write and change MARM rows; goods movement and order entry transactions only read them.