MVKE table — MVKE Material Master Sales Organization Data

Each row in MVKE represents the sales data view of one material for one sales organization and distribution channel combination. It is created when a material is extended to a sales area via the material master sales views, and it is what SD transactions actually read when determining whether a material can be sold through a given channel. Fields here control sales status per channel, the delivering plant used for availability and shipping, the item category group that drives item category determination in the sales order, tax classification, and rebate relevance. A material can exist in MARA without ever having a row in MVKE, and that gap is the single most common reason a material cannot be entered on a sales order even though it exists and is not blocked at plant level.

MVKE is small relative to MARC or MARD but still client-dependent, so MANDT is implicit rather than something to restrict on manually in most tools. The real selectivity is MATNR plus VKORG and VTWEG together; querying by sales organization alone across all materials returns a very large result set with little diagnostic value. Always check whether a row exists at all before inspecting field values, because a missing combination is a different problem from a populated one with a bad status. Do not assume the sales area used in the order matches the one being checked; distribution chain assignment (sales org to distribution channel to division) determines which combinations are even valid, and that lives in customizing, not in MVKE itself.

Symptom: a sales order line rejects a material with a message that it is not maintained for the sales area, or blocked for sales. Selection: read MVKE for the exact MATNR, VKORG, and VTWEG from the order header. No row at all confirms the material was never extended to that sales area. A row exists but VMSTA is populated with a block value confirms a status block rather than a missing extension, and VMSTD shows when it was set, which helps correlate against a recent mass change or data load.

MVKE continues to exist as a transparent table on S/4HANA and is not one of the tables restructured by the Simple Logistics data model changes, since those changes focused on inventory and purchasing tables rather than the sales view of the material master. Reads and writes to MVKE still go through the standard material master maintenance transactions and the underlying data dictionary structure is essentially unchanged from ECC. Custom reports built directly against MVKE generally continue to work without adaptation.

Master data governance or the SD/MM master data team owns the content of MVKE, since extension and status maintenance happen through material master transactions typically owned by that function. A P2P consultant investigating a purchasing-side issue that surfaces through a sales-blocked material should confirm the finding here and hand the correction back to master data, not attempt a direct table fix.

MARA holds the client-level general data for the same material and is the natural first join. MARC holds plant-specific data and is where the delivering plant referenced by DWERK must actually be maintained for stock and procurement to work. T001W provides the plant master detail behind DWERK. Material master maintenance transactions write MVKE when the sales views are created or changed; sales order entry only reads it.