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)

Fields

12 fields · 2 key

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

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading OCUSMAon 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
-- ============================================================
-- 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 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
  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"
FROM <catalog>.<schema>.OCUSMA c
WHERE
  c.OKCONO = <company>
  -- AND c.OKCUNO = '<CUNO>'
ORDER BY c.OKCUNO;

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

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

  • OOHEADOCUSMAforeign key · N:1
    ON OOHEAD.OACUNO = OCUSMA.OKCUNO AND OOHEAD.OACONO = OCUSMA.OKCONO
  • ODHEADOCUSMAforeign key · N:1
    ON ODHEAD.UACUNO = OCUSMA.OKCUNO AND ODHEAD.UACONO = OCUSMA.OKCONO
  • FSLEDGOCUSMAforeign key · N:1
    ON FSLEDG.ESCUNO = OCUSMA.OKCUNO AND FSLEDG.ESCONO = OCUSMA.OKCONO

Programs That Use This Table

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

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.