Skip to content
M3 Reference

OCUSMA

Prefix: OKmaster

The customer master — one row per customer per company, with name and address, country, currency, and the default payment, delivery, and sales-rep terms new orders inherit

Module: Customer OrdersCompany-partitioned (CONO)
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).
In field listings, K marks a primary-key field.
Used in the library

Fields

15 fields · 2 key

15 fields.

Table fields: key flag, field name, column alias, description, data type, length, and decode flags. 15 fields.
KeyFieldAliasDescriptionTypeLengthFlags
KeyOKCONOCONOCompanynumeric
KeyOKCUNOCUNOCustomer number — the natural key order headers join onalphanumeric
OKSTATSTATCustomer status — whether the customer is active for new businessalphanumeric
OKCUNMCUNMCustomer namealphanumeric
OKCUA1CUA1Customer address, first linealphanumeric
OKTOWNTOWNCityalphanumeric
OKCSCDCSCDCountry codealphanumeric
OKCUCDCUCDCurrency the customer trades inalphanumeric
OKTEPYTEPYPayment terms new orders and invoices inheritalphanumeric
OKTEDLTEDLDelivery terms new orders inheritalphanumeric
OKMODLMODLDelivery method new orders inheritalphanumeric
OKSMCDSMCDSalesperson responsible for the customeralphanumeric
OKECARECARArea, state, or province within the customer's country — the geographic slice for regional sales analyticsalphanumeric
OKPONOPONOPostal codealphanumeric
OKPHNOPHNOTelephone numberalphanumeric

Field provenance: hand-curated.

Boilerplate SQL

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

4 parameters not filled: <catalog>, <schema>, <company>, <CUNO>

-- ============================================================
-- Table  : OCUSMA — The customer master — one row per customer per company, with name and address, country, currency, and the default payment, delivery, and sales-rep terms new orders inherit
-- Purpose: Column-selected read of OCUSMA — auto-generated from field metadata
-- Grain  : One row per company (CONO) + OKCUNO
-- 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
  c.OKCONO AS "Company",
  c.OKCUNO AS "Customer number — the natural key order headers join on",
  c.OKSTAT AS "Customer status — whether the customer is active for new business",  -- status: decode c.OKSTAT against your configuration — see quirks guide #statuses
  c.OKCUNM AS "Customer name",
  c.OKCUA1 AS "Customer address, first line",
  c.OKTOWN AS "City",
  c.OKCSCD AS "Country code",
  c.OKCUCD AS "Currency the customer trades in",
  c.OKTEPY AS "Payment terms new orders and invoices inherit",
  c.OKTEDL AS "Delivery terms new orders inherit",
  c.OKMODL AS "Delivery method new orders inherit",
  c.OKSMCD AS "Salesperson responsible for the customer",
  c.OKECAR AS "Area, state, or province within the customer's country — the geographic slice for regional sales analytics",
  c.OKPONO AS "Postal code",
  c.OKPHNO AS "Telephone number"
FROM <catalog>.<schema>.OCUSMA c
WHERE
  c.OKCONO = <company>
  -- AND c.OKCUNO = '<CUNO>'
ORDER BY c.OKCUNO;

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

  • OOHEADOCUSMAforeign key · N:1
    -- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON OOHEAD.OACUNO = OCUSMA.OKCUNO AND OOHEAD.OACONO = OCUSMA.OKCONO
  • ODHEADOCUSMAforeign key · N:1
    -- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON ODHEAD.UACUNO = OCUSMA.OKCUNO AND ODHEAD.UACONO = OCUSMA.OKCONO
  • FSLEDGOCUSMAforeign key · N:1
    -- Uses this catalog's prefixed M3 column names; map raw Data Lake properties through Data Catalog first. ON FSLEDG.ESCUNO = OCUSMA.OKCUNO AND FSLEDG.ESCONO = OCUSMA.OKCONO

Programs That Use This Table

More Customer Orders tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Infor. Infor, Infor M3, and Infor CloudSuite are trademarks of Infor and/or its affiliates.