M3 Reference
OCUSMA
Prefix: OKmasterThe 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.
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).
In field listings, K marks a primary-key field.
Used in the library
Cross-ERP guides
Fields
15 fields · 2 key
15 fields.
| Key | Field | Alias | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | OKCONO | CONO | Company | numeric | ||
| Key | OKCUNO | CUNO | Customer number — the natural key order headers join on | alphanumeric | ||
| OKSTAT | STAT | Customer status — whether the customer is active for new business | alphanumeric | |||
| OKCUNM | CUNM | Customer name | alphanumeric | |||
| OKCUA1 | CUA1 | Customer address, first line | alphanumeric | |||
| OKTOWN | TOWN | City | alphanumeric | |||
| OKCSCD | CSCD | Country code | alphanumeric | |||
| OKCUCD | CUCD | Currency the customer trades in | alphanumeric | |||
| OKTEPY | TEPY | Payment terms new orders and invoices inherit | alphanumeric | |||
| OKTEDL | TEDL | Delivery terms new orders inherit | alphanumeric | |||
| OKMODL | MODL | Delivery method new orders inherit | alphanumeric | |||
| OKSMCD | SMCD | Salesperson responsible for the customer | alphanumeric | |||
| OKECAR | ECAR | Area, state, or province within the customer's country — the geographic slice for regional sales analytics | alphanumeric | |||
| OKPONO | PONO | Postal code | alphanumeric | |||
| OKPHNO | PHNO | Telephone number | alphanumeric |
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
-- 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-- 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-- 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
- CRS610 — Customer maintenance — where customers are created and their OCUSMA terms managedPrimary sourceInteractive
- CRS610MI — Customer API — reads and maintains customers programmaticallyPrimary sourceAPI
- OIS100 — Customer order entry — creates and maintains customer orders, writing the OOHEAD/OOLINE pairInteractive
More Customer Orders tables
- OOHEADThe customer order header — one row per order, carrying the customer, order type, dates, and currency, plus the pair of status fields (lowest and highest line status) that summarize where the order's lines stand
- OOLINEThe customer order line — one row per ordered item with quantities across the ordered/delivered/invoiced flow, price, warehouse, and planned delivery date; the core sell-side transaction, joined to its header by ORNO