MWOMAT
Prefix: VMtransactionManufacturing order materials — one row per component line on an order, with required and reported quantities; copied from the product structure at order creation and then consumed against, joined to its header by MFNO
What the badges mean
- Prefix: MM
- Prefix: the table’s 2-character physical-column prefix (e.g.
MMonMITMAS) — every field alias on the table carries it. Join by matching aliases across tables, not full column names (see the quirks guide). - master
- Data class: what the table holds — master data, balances, transaction documents, code/reference tables, or history.
- Shared across companies
- The table carries no
CONO— rows aren’t partitioned per company (see the quirks guide). - Division-level
- The table carries
DIVI— rows are scoped below company to a division, one layer more granular thanCONOalone (see the quirks guide).
Header & line
MWOMAT lines join back to their header MWOHED — and the CONO — so a line never fans out across companies.
Fields
8 fields · 4 key
8 fields.
| Key | Field | Alias | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | VMCONO | CONO | Company | numeric | ||
| Key | VMFACI | FACI | Facility | alphanumeric | ||
| Key | VMMFNO | MFNO | Manufacturing order number | alphanumeric | ||
| Key | VMMSEQ | MSEQ | Material sequence number within the order | numeric | ||
| VMMTNO | MTNO | Component item consumed — joins to the item master on ITNO | alphanumeric | |||
| VMREQT | REQT | Required quantity of the component for the order | numeric | |||
| VMRPQT | RPQT | Reported (issued) quantity of the component so far | numeric | |||
| VMWHLO | WHLO | Warehouse the component is issued from | alphanumeric |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading MWOMAT on Databricks — numeric YYYYMMDD dates are wrapped to NULL, verified status ladders are decoded, and the CONO anchor is in place. Set your Unity Catalog location, company, and filter values below; they’re substituted into the SQL and the copy button.
5 parameters not filled: <catalog>, <schema>, <company>, <FACI>, <MFNO>
-- ============================================================
-- Table : MWOMAT — Manufacturing order materials — one row per component line on an order, with required and reported quantities; copied from the product structure at order creation and then consumed against, joined to its header by MFNO
-- Purpose: Column-selected read of MWOMAT — auto-generated from field metadata
-- Grain : One row per company (CONO) + VMFACI + VMMFNO + VMMSEQ
-- Notes : Auto-generated skeleton for a prefixed physical M3 schema or a landing schema normalized to the prefixed names in this catalog. Raw Data Lake property names vary with the published object: map them through Data Catalog before running this SQL. Dates are numeric YYYYMMDD (0 = none, mapped to NULL); all curated status values are decoded inline. Audit columns (RGDT/RGTM/LMDT/CHNO/CHID) omitted — see the quirks guide.
-- ============================================================
SELECT
m.VMCONO AS "Company",
m.VMFACI AS "Facility",
m.VMMFNO AS "Manufacturing order number",
m.VMMSEQ AS "Material sequence number within the order",
m.VMMTNO AS "Component item consumed — joins to the item master on ITNO",
m.VMREQT AS "Required quantity of the component for the order",
m.VMRPQT AS "Reported (issued) quantity of the component so far",
m.VMWHLO AS "Warehouse the component is issued from"
FROM <catalog>.<schema>.MWOMAT m
WHERE
m.VMCONO = <company>
-- AND m.VMFACI = '<FACI>'
-- AND m.VMMFNO = '<MFNO>'
ORDER BY m.VMFACI;Verified September 2026
Relationships
Diagram of 1-hop neighbors — join details below. CSYTAB decode edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
-- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON MWOHED.VHMFNO = MWOMAT.VMMFNO AND MWOHED.VHFACI = MWOMAT.VMFACI AND MWOHED.VHCONO = MWOMAT.VMCONO
Programs That Use This Table
More Manufacturing tables
- MWOOPEManufacturing order operations — one row per operation step on an order with its work center; the grain for capacity and labor reporting, joined to its header by MFNO
- MPDHEDThe product structure header — one row per product and structure type per facility, the design-time recipe that manufacturing orders are created from
- MPDMATProduct structure materials — one row per component in a product structure, with the quantity consumed per unit produced; the design-time counterpart of MWOMAT, joined to its header by PRNO + STRT
- MWOHEDThe manufacturing order header — one row per order, carrying the product being made, its status ladder, ordered and completed quantities, and start/finish dates; the manufactured product number joins to the item master on ITNO