# Infor M3 Field Name Glossary: What ITNO, WHLO, FACI and ORNO Mean

> Source: https://netray.co/tools/infor-m3-field-name-glossary-reference
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Searchable list of common M3 field codes and what they mean, useful for MI APIs, reports and mapping documents.

## Category

infor-cloudsuite

## Erp

Infor M3

## Audience

- M3 consultant
- M3 developer
- Business analyst

## Tool

**Kind:** worksheet

**Mode:** reference

**Columns:**

#### Field

**Key:** field

**Type:** text

#### Meaning

**Key:** meaning

**Type:** text

#### Area

**Key:** area

**Type:** text

#### Seen in

**Key:** example

**Type:** text

**Rows:**

**Field:** CONO

**Meaning:** Company number

**Area:** Organisation

**Example:** Every table and API call

**Field:** DIVI

**Meaning:** Division

**Area:** Organisation

**Example:** Finance, CSYTAB, many APIs

**Field:** FACI

**Meaning:** Facility

**Area:** Organisation

**Example:** Production, planning, CFACIL

**Field:** WHLO

**Meaning:** Warehouse

**Area:** Inventory

**Example:** MITBAL, MITLOC, order lines

**Field:** WHSL

**Meaning:** Warehouse location (stock location)

**Area:** Inventory

**Example:** MITLOC

**Field:** ITNO

**Meaning:** Item number

**Area:** Item

**Example:** MITMAS, MITBAL, OOLINE

**Field:** ITDS

**Meaning:** Item name (short description)

**Area:** Item

**Example:** MITMAS

**Field:** FUDS

**Meaning:** Item description (long)

**Area:** Item

**Example:** MITMAS

**Field:** ITTY

**Meaning:** Item type

**Area:** Item

**Example:** MITMAS

**Field:** ITGR

**Meaning:** Item group

**Area:** Item

**Example:** MITMAS

**Field:** ITCL

**Meaning:** Product group

**Area:** Item

**Example:** MITMAS

**Field:** STAT

**Meaning:** Status (item, record or master status depending on table)

**Area:** General

**Example:** MITMAS, CIDMAS, OCUSMA

**Field:** UNMS

**Meaning:** Basic unit of measure

**Area:** Item

**Example:** MITMAS

**Field:** STQT

**Meaning:** On-hand balance

**Area:** Inventory

**Example:** MITBAL, MITLOC

**Field:** ALQT

**Meaning:** Allocated quantity

**Area:** Inventory

**Example:** MITBAL, MITLOC

**Field:** BANO

**Meaning:** Lot number

**Area:** Inventory

**Example:** MITLOC, MITTRA

**Field:** CAMU

**Meaning:** Container

**Area:** Inventory

**Example:** MITLOC

**Field:** REPN

**Meaning:** Receiving number

**Area:** Inventory

**Example:** MITLOC

**Field:** ORNO

**Meaning:** Customer order number

**Area:** Sales

**Example:** OOHEAD, OOLINE

**Field:** PONR

**Meaning:** Order line number

**Area:** Sales

**Example:** OOLINE

**Field:** POSX

**Meaning:** Order line suffix

**Area:** Sales

**Example:** OOLINE

**Field:** ORTP

**Meaning:** Customer order type

**Area:** Sales

**Example:** OOHEAD, OOTYPE

**Field:** ORST

**Meaning:** Order status

**Area:** Sales

**Example:** OOHEAD, OOLINE

**Field:** ORQT

**Meaning:** Ordered quantity in basic unit of measure

**Area:** Sales

**Example:** OOLINE

**Field:** ORDT

**Meaning:** Order date (YYYYMMDD)

**Area:** Sales

**Example:** OOHEAD

**Field:** DWDT

**Meaning:** Requested delivery date (YYYYMMDD)

**Area:** Sales

**Example:** OOLINE

**Field:** CUNO

**Meaning:** Customer number

**Area:** Sales

**Example:** OCUSMA, OOHEAD

**Field:** CUNM

**Meaning:** Customer name

**Area:** Sales

**Example:** OCUSMA

**Field:** SUNO

**Meaning:** Supplier number

**Area:** Purchasing

**Example:** CIDMAS, MPHEAD

**Field:** PUNO

**Meaning:** Purchase order number

**Area:** Purchasing

**Example:** MPHEAD, MPLINE

**Field:** PNLI

**Meaning:** Purchase order line number

**Area:** Purchasing

**Example:** MPLINE

**Field:** PNLS

**Meaning:** Purchase order line subnumber

**Area:** Purchasing

**Example:** MPLINE

**Field:** MFNO

**Meaning:** Manufacturing order number

**Area:** Production

**Example:** MWOHED, MWOMAT

**Field:** PRNO

**Meaning:** Product number (the item being manufactured)

**Area:** Production

**Example:** MWOHED, product structure

**Field:** MTNO

**Meaning:** Material (component) number

**Area:** Production

**Example:** MWOMAT, product structure

**Field:** CUCD

**Meaning:** Currency code

**Area:** Finance

**Example:** Orders, invoices, price lists

**Field:** TEPY

**Meaning:** Payment terms

**Area:** Finance

**Example:** OOHEAD, CIDMAS

**Field:** TEDL

**Meaning:** Terms of delivery

**Area:** Logistics

**Example:** OOHEAD, MPHEAD

**Field:** MODL

**Meaning:** Delivery method

**Area:** Logistics

**Example:** OOHEAD, MPHEAD

**Field:** CSNO

**Meaning:** Customs tariff number

**Area:** Compliance

**Example:** Item and order data

**Field:** ORCO

**Meaning:** Country of origin

**Area:** Compliance

**Example:** Item and order data

**Notes:** Field meanings reflect common usage in M3. The same four letters can have a slightly different label on different screens, so confirm against the field help (F1) in your own release.

## Content

**Intro:** Infor M3 uses four-letter field codes everywhere: in tables, in MI API requests, in Data Fabric objects and in MEC mappings. This glossary decodes the ones you meet daily so you can read an API response or a mapping document without hunting through screens.

**Sections:**

#### How to use the glossary

**Body:** Search for the code you see in an API response or a table, for example WHLO or PONR. The Seen in column points you at the tables and programs where it appears. Use the Area filter by typing a word such as Sales or Inventory. Export the whole list to Excel and keep it as the shared vocabulary for your integration and migration team.

#### How codes combine with prefixes

**Body:** In a database table the four-letter code gets a two-letter table prefix, so the item number is MMITNO in MITMAS and OBITNO in OOLINE. In MI API calls the prefix is dropped and you pass ITNO. Knowing this lets you translate between a SQL column, an API field and a screen field quickly.

**Bullets:**

- SQL column: prefix plus code, such as OBORNO
- API field: code only, such as ORNO
- Screen: label text, with the code visible in field help

#### Common mistakes

**Body:** Dates in M3 are stored as eight digit numbers in YYYYMMDD form, so sending a formatted date string to an API fails or is misread. Another trap is the order line key: PONR alone is not enough when line suffixes are in use, so include POSX. Finally, quantities such as ORQT are in the basic unit of measure, while some APIs also accept alternate units.

**Cta:** If your team spends time translating between M3 field codes and business terms, we can set up an assistant that explains and queries them using your own data dictionary.

**Faq:**

#### What does CONO mean in Infor M3?

**Answer:** CONO is the company number. M3 separates data by company, so almost every table and API call carries it. Divisions (DIVI) and facilities (FACI) sit beneath the company for finance and logistics scoping.

#### What date format does M3 use?

**Answer:** M3 normally stores dates as an eight digit number in YYYYMMDD form, for example 20261019. APIs expect the same format, so convert dates from Excel or other systems before sending them.

#### Are field codes the same in every language?

**Answer:** Yes. The four-letter codes are technical names and stay constant, while labels on screens are translated by language. This is why the codes are the best common language between consultants and developers.

#### Where can I see a field's code in M3?

**Answer:** Open the field help in the program, which shows the technical field name. The program's Panel and field documentation and the API transaction metadata also list field names for each program and transaction.

## Search terms

m3 field names, infor m3 itno, m3 cono divi faci whlo, m3 field glossary, m3 api field list, m3 orno ponr meaning, infor m3 abbreviations

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json