Infor M3 & CloudSuiteFree referencePDF, Excel, Word exportInfor M3

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

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.

Download:

Field	Meaning	Area	Seen in
CONO	Company number	Organisation	Every table and API call
DIVI	Division	Organisation	Finance, CSYTAB, many APIs
FACI	Facility	Organisation	Production, planning, CFACIL
WHLO	Warehouse	Inventory	MITBAL, MITLOC, order lines
WHSL	Warehouse location (stock location)	Inventory	MITLOC
ITNO	Item number	Item	MITMAS, MITBAL, OOLINE
ITDS	Item name (short description)	Item	MITMAS
FUDS	Item description (long)	Item	MITMAS
ITTY	Item type	Item	MITMAS
ITGR	Item group	Item	MITMAS
ITCL	Product group	Item	MITMAS
STAT	Status (item, record or master status depending on table)	General	MITMAS, CIDMAS, OCUSMA
UNMS	Basic unit of measure	Item	MITMAS
STQT	On-hand balance	Inventory	MITBAL, MITLOC
ALQT	Allocated quantity	Inventory	MITBAL, MITLOC
BANO	Lot number	Inventory	MITLOC, MITTRA
CAMU	Container	Inventory	MITLOC
REPN	Receiving number	Inventory	MITLOC
ORNO	Customer order number	Sales	OOHEAD, OOLINE
PONR	Order line number	Sales	OOLINE
POSX	Order line suffix	Sales	OOLINE
ORTP	Customer order type	Sales	OOHEAD, OOTYPE
ORST	Order status	Sales	OOHEAD, OOLINE
ORQT	Ordered quantity in basic unit of measure	Sales	OOLINE
ORDT	Order date (YYYYMMDD)	Sales	OOHEAD
DWDT	Requested delivery date (YYYYMMDD)	Sales	OOLINE
CUNO	Customer number	Sales	OCUSMA, OOHEAD
CUNM	Customer name	Sales	OCUSMA
SUNO	Supplier number	Purchasing	CIDMAS, MPHEAD
PUNO	Purchase order number	Purchasing	MPHEAD, MPLINE
PNLI	Purchase order line number	Purchasing	MPLINE
PNLS	Purchase order line subnumber	Purchasing	MPLINE
MFNO	Manufacturing order number	Production	MWOHED, MWOMAT
PRNO	Product number (the item being manufactured)	Production	MWOHED, product structure
MTNO	Material (component) number	Production	MWOMAT, product structure
CUCD	Currency code	Finance	Orders, invoices, price lists
TEPY	Payment terms	Finance	OOHEAD, CIDMAS
TEDL	Terms of delivery	Logistics	OOHEAD, MPHEAD
MODL	Delivery method	Logistics	OOHEAD, MPHEAD
CSNO	Customs tariff number	Compliance	Item and order data
ORCO	Country of origin	Compliance	Item and order data

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.

Get a mapped data dictionary for your M3

We can help produce a field-level dictionary for your M3 environment as an optional follow-up.

Optional. The tool and every export work without this. No spam.

How to use the glossary

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

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.

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

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.

Frequently Asked Questions

What does CONO mean in Infor M3?

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?

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?

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?

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.

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.

Talk to an Expert Explore More Free Tools