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.
| 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.
Related Tools
Infor M3 Core Database Tables Reference
Look up the main M3 tables, their two-letter column prefix and the key fields you join on. Searchable and exportable.
Infor M3 & CloudSuiteInfor M3 SQL Query Generator
Fill in company, warehouse and filters to get ready-to-adapt SQL against MITMAS, MITBAL, OOHEAD, OOLINE and MPLINE.
Infor M3 & CloudSuiteInfor M3 Bookmark URL Generator
Generate M3 bookmark strings that open a given program on a specific record, with option and panel, for links and mashups.
Infor M3 & CloudSuiteInfor M3 Cloud Migration Readiness Assessment
Ten questions to gauge how ready an on-prem M3 estate is for a move to Infor CloudSuite, with prioritized next steps.
More Infor M3 & CloudSuite tools
See all- Infor M3 Program Reference (MMS001, OIS100, PMS100)
- Infor M3 MI API Transaction Call Generator
- Infor M3 Customer Order Status Tracking Worksheet
- Infor M3 Item Master Upload Worksheet
- Infor M3 MEC Mapping Design Template
- Infor M3 H5 Script Review Checklist
- Infor M3 Upgrade Test Checklist
- Infor M3 Facility and Warehouse Structure Worksheet
- Infor M3 Fit-Gap Analysis Worksheet
New to Infor M3? Start with the Infor M3 guide and toolkit, or plan with Training Path Builder, Upgrade Path Planner, ERP Table and Field Explorer.
Keep exploring
Free tools
- Infor M3 MEC Mapping Design TemplateA fill-in design document for an M3 Enterprise Collaborator mapping, from partner and flow to field rules and error handling.
- M3 MI API Batch Load Time EstimatorEstimate how long a bulk load through M3 APIs will run and how added parallel threads change it, using your own measured response time.
- Infor M3 AI Assistant Sizing and Value CalculatorSize the GPUs and estimate the monthly value and payback of a private, on-prem AI assistant for Infor M3.
ERP fixes and how-tos
- Infor M3 SDK, MI APIs and REST API Documentation GuideDeveloper map of the Infor M3 SDK: MI programs, the REST API through ION API, authentication, example calls, and where to find the official documentation.
- Private AI Layer for Infor M3 On-Prem: Reference ArchitectureReference architecture to add a private AI assistant to Infor M3 on-prem: data access paths, retrieval, permissions, sizing and rollout, no cloud needed.
- Infor M3 Date Format: User Setting, API and DatabaseHow dates work in Infor M3: the user display format in MNS150, the 8-digit YYYYMMDD format used by MI APIs and tables, and how to convert them.
Runs with your ERP
- Infor M3 Scheduling Workbench and M3: finite scheduling explainedHow Infor M3 Scheduling Workbench schedules against capacity and materials and writes orders back to M3 via PSMI, with setup, pitfalls and AI help.
- TrueCommerce EDI and Infor M3TrueCommerce managed EDI for Infor M3 (also VISUAL and other Infor ERPs): documents, data flows, setup steps, pitfalls, alternatives and where AI helps.
- Infor EDI Managed Service and Infor M3 over IONHow Infor's EDI managed service connects to Infor M3 through ION with pre-built trading partner links: data flows, setup steps, pitfalls and a private AI layer.
Guides
- Infor M3 API Performance Optimization GuideOptimize Infor M3 API performance. MI program tuning, API call batching, caching strategies, and connection pool management for high-volume integrations.
- Infor M3 API Integration with MI Programs and RESTInfor M3 API integration guide covering MI programs, the m3api-rest v2 endpoint, ION API gateway OAuth, Event Hub, and error handling for reliable interfaces.
- Infor M3 API Toolkit: A Developer's Guide to MI Programs and MvxAPIBuild robust integrations with the Infor M3 API toolkit. Learn MI programs, MvxAPI patterns, and transaction handling for M3 13.4+ environments.
AI on your ERP
- Infor M3 AI: A Practical Path from MI Programs to a Private AssistantInfor M3 AI explained: grounded natural-language answers over MI programs and MEC, agents for distribution and manufacturing, on-prem or EU private cloud.
- Infor M3 Supply Chain Planning With AI That Explains the MRP OutputAI for Infor M3 supply chain planning: explain MRP action messages, review planned orders, and trace shortages through MITBAL and MITMAS on private infrastructure.
Integrations
- How to add AI agents to Infor M3How to add AI agents to Infor M3: a tool layer over MI programs and ION, read-first workflows for POs, MO and CO exceptions, and human approval on writes.
- How to build an MCP server for Infor M3How to build a Model Context Protocol server for Infor M3: which read-only tools to expose over MI programs, ION or on-prem auth, transports, scoping and audit.