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
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
| 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 MWOMATon 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.
-- ============================================================
-- 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 Infor Data Lake-landed M3 data. Dates are numeric YYYYMMDD (0 = none, mapped to NULL); status ladders decoded inline where verified. 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;5 parameters not filled: <catalog>, <schema>, <company>, <FACI>, <MFNO>
Relationships
1-hop neighbors — click a table to navigate there. CSYTAB decode edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON MWOHED.VHMFNO = MWOMAT.VMMFNO AND MWOHED.VHFACI = MWOMAT.VMFACI AND MWOHED.VHCONO = MWOMAT.VMCONO