MWOHED
Prefix: VHtransactionThe 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
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).
Fields
10 fields · 3 key
10 fields.
| Key | Field | Alias | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | VHCONO | CONO | Company | numeric | ||
| Key | VHFACI | FACI | Facility the order is manufactured in | alphanumeric | ||
| Key | VHMFNO | MFNO | Manufacturing order number | alphanumeric | ||
| VHWHST | WHST | Order status — the two-char ladder the order walks from creation through release, reporting, and completion | alphanumeric | |||
| VHPRNO | PRNO | Product being manufactured — joins to the item master on ITNO | alphanumeric | |||
| VHORQT | ORQT | Ordered quantity to manufacture | numeric | |||
| VHMAQT | MAQT | Quantity manufactured (completed) so far | numeric | |||
| VHSTDT | STDT | Planned start date | numeric | |||
| VHFIDT | FIDT | Planned finish date | numeric | |||
| VHWHLO | WHLO | Warehouse the finished product is received into | alphanumeric |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading MWOHED 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.
7 parameters not filled: <catalog>, <schema>, <company>, <FACI>, <MFNO>, <DATE_FROM>, <DATE_TO>
-- ============================================================
-- Table : MWOHED — The 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
-- Purpose: Column-selected read of MWOHED — auto-generated from field metadata
-- Grain : One row per company (CONO) + VHFACI + VHMFNO
-- 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
wo.VHCONO AS "Company",
wo.VHFACI AS "Facility the order is manufactured in",
wo.VHMFNO AS "Manufacturing order number",
wo.VHWHST AS "Order status — the two-char ladder the order walks from creation through release, reporting, and completion", -- status: decode wo.VHWHST against your configuration — see quirks guide #statuses
wo.VHPRNO AS "Product being manufactured — joins to the item master on ITNO",
wo.VHORQT AS "Ordered quantity to manufacture",
wo.VHMAQT AS "Quantity manufactured (completed) so far",
CASE WHEN wo.VHSTDT = 0 THEN NULL ELSE TO_DATE(CAST(CAST(wo.VHSTDT AS BIGINT) AS STRING), 'yyyyMMdd') END AS "Planned start date", -- YYYYMMDD, 0 → NULL
CASE WHEN wo.VHFIDT = 0 THEN NULL ELSE TO_DATE(CAST(CAST(wo.VHFIDT AS BIGINT) AS STRING), 'yyyyMMdd') END AS "Planned finish date", -- YYYYMMDD, 0 → NULL
wo.VHWHLO AS "Warehouse the finished product is received into"
FROM <catalog>.<schema>.MWOHED wo
WHERE
wo.VHCONO = <company>
-- AND wo.VHFACI = '<FACI>'
-- AND wo.VHMFNO = '<MFNO>'
-- AND wo.VHFIDT >= <DATE_FROM> -- yyyyMMdd numeric
-- AND wo.VHFIDT <= <DATE_TO> -- yyyyMMdd numeric
ORDER BY wo.VHFACI;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.VHFACI = CFACIL.CFFACI AND MWOHED.VHCONO = CFACIL.CFCONO-- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON MWOHED.VHWHLO = MITWHL.MWWHLO AND MWOHED.VHCONO = MITWHL.MWCONO-- 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-- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON MWOHED.VHMFNO = MWOOPE.VOMFNO AND MWOHED.VHFACI = MWOOPE.VOFACI AND MWOHED.VHCONO = MWOOPE.VOCONO
Programs That Use This Table
More Manufacturing tables
- MWOMATManufacturing 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
- 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