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
Fields
10 fields · 3 key
| 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 MWOHEDon 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 : 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 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
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;7 parameters not filled: <catalog>, <schema>, <company>, <FACI>, <MFNO>, <DATE_FROM>, <DATE_TO>
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.VHFACI = CFACIL.CFFACI AND MWOHED.VHCONO = CFACIL.CFCONOON MWOHED.VHWHLO = MITWHL.MWWHLO AND MWOHED.VHCONO = MITWHL.MWCONOON MWOHED.VHMFNO = MWOMAT.VMMFNO AND MWOHED.VHFACI = MWOMAT.VMFACI AND MWOHED.VHCONO = MWOMAT.VMCONOON MWOHED.VHMFNO = MWOOPE.VOMFNO AND MWOHED.VHFACI = MWOOPE.VOFACI AND MWOHED.VHCONO = MWOOPE.VOCONO