M3 Reference

MWOOPE

Prefix: VOtransaction

Manufacturing 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

Module: ManufacturingCompany-partitioned (CONO)Header: MWOHED

What the badges mean

Prefix: MM: Prefix: the table’s 2-character physical-column prefix (e.g. MM on MITMAS) — 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 than CONO alone (see the quirks guide).

Used in the library

KPI definitions

K-08Schedule Attainment

K-13First Pass Yield

Dashboard patterns

D-06Production Schedule Performance

Header & line

MWOOPE lines join back to their header MWOHED — and the CONO — so a line never fans out across companies.

Fields

5 fields · 4 key

5 fields.

Table fields: key flag, field name, column alias, description, data type, length, and decode flags. 5 fields.
Key	Field	Alias	Description	Type
Key	VOCONO	CONO	Company	numeric
Key	VOFACI	FACI	Facility	alphanumeric
Key	VOMFNO	MFNO	Manufacturing order number	alphanumeric
Key	VOOPNO	OPNO	Operation number within the order	numeric
	VOPLGR	PLGR	Work center the operation runs at	alphanumeric

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading MWOOPE 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.

Query parameters

CatalogSchemaCompany (CONO)Facility (FACI)Manufacturing order (MFNO)

Include optional filters (2)

5 parameters not filled: <catalog>, <schema>, <company>, <FACI>, <MFNO>

-- ============================================================
-- Table  : MWOOPE — Manufacturing 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
-- Purpose: Column-selected read of MWOOPE — auto-generated from field metadata
-- Grain  : One row per company (CONO) + VOFACI + VOMFNO + VOOPNO
-- 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.VOCONO AS "Company",
  m.VOFACI AS "Facility",
  m.VOMFNO AS "Manufacturing order number",
  m.VOOPNO AS "Operation number within the order",
  m.VOPLGR AS "Work center the operation runs at"
FROM <catalog>.<schema>.MWOOPE m
WHERE
  m.VOCONO = <company>
  -- AND m.VOFACI = '<FACI>'
  -- AND m.VOMFNO = '<MFNO>'
ORDER BY m.VOFACI;

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

MWOHEDMWOOPEheader line · 1:N
-- 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