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)
Fields
12 fields · 2 key
| 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 |
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.
Programs That Use This Table
- CRS610Customer maintenance — where customers are created and their OCUSMA terms managedPrimary sourceInteractive
- CRS610MICustomer API — reads and maintains customers programmaticallyPrimary sourceAPI
- OIS100Customer order entry — creates and maintains customer orders, writing the OOHEAD/OOLINE pairInteractive