Infor M3 Order Status Codes Reference
This reference explains the two-digit M3 13.x customer order statuses that Infor documents, with the program that sets each, and shows which fields hold purchase order, manufacturing order and distribution order status. It covers fewer codes than some lists online on purpose: every row is confirmed.
| Order type | Status code | Meaning | Reached by | Table.field | Next status | Notes |
|---|---|---|---|---|---|---|
CO header | 10 | Preliminary | Order entered as preliminary in OIS100 when the CO type requires approval (Preliminary CO in OIS010/E) | OOHEAD order status | 11-19 or 20 | The order cannot continue in the flow until approved |
CO header | 11-19 | Preliminary approval steps | Set on the E panel or with options 21 and 22 in OIS115 Customer Order. Approve | OOHEAD order status | 20 | Statuses for options 21 and 22 are defined in the OIS115 settings (F13). They show approval progress, not order progress |
CO header | 20 | Approved | Change status to 20 in OIS100, or approve all lines with option 19 in OIS115 | OOHEAD order status | Normal order flow | |
CO line | 22 | Not allocated | Line entered without allocation, or after deallocation | OOLINE.OBORST | 33 | A line returns to 22 if its allocated quantity is set back to zero |
CO line | 33 | Allocated | Automatic allocation (per the allocation method in MMS002) or manual allocation | OOLINE.OBORST | 44 | A completely allocated order has its order status raised to 33 |
CO line | 44 | Picking list printed | Release for picking from MWS410 Delivery Toolbox (manual or automatic per dispatch policy MWS010) | OOLINE.OBORST | 66 | Lines allocated after release can land on a new suffixed picking list at 44 |
CO line | 66 | Delivered | Delivery reported, or status changed to 66 in OIS300 Customer Order. Open Toolbox | OOLINE.OBORST | 77 | Status 66 on the line is what moves the delivery towards invoicing |
CO line | 77 | Invoiced | Invoicing of the delivery the line belongs to | OOLINE.OBORST | - | Final normal status of a line; OBIVQT holds the invoiced quantity |
CO delivery | 60 | Ready to invoice | Option 16 Release for invoicing in OIS150 CO Delivery. Open, or on its E panel | Delivery status in OIS150 | Invoiced | The delivery can now be picked up by invoicing |
CO delivery | 61 | Proof of delivery / approval required | Delivery created with status 61 as set in OIS010/E for the CO type | Delivery status in OIS150 | 60 | Deliveries wait at 61 until approved |
CO delivery | 62-66 | Not yet ready to invoice, internal review | Delivery created with the status selected in the Status field of OIS010/E for the CO type | Delivery status in OIS150 | 60 | Used for internal approval of deliveries before invoicing |
CO header | Lowest / highest | Lowest and highest line status on the order | Updated by M3 as lines change status | OOHEAD.OAORSL / OOHEAD.OAORST | - | Query OAORSL to find orders with any line still open |
PO line | Lowest / highest | Lowest and highest status on the PO line | Updated as the line moves through order, receipt, inspection and invoice | MPLINE.IBPUSL / MPLINE.IBPUST | - | Read the code list for your version in the PPS200 field help |
MO | Status | Manufacturing order status | Updated by release, material issue, reporting and close | MWOHED.VHWHST | - | Read the code list for your version in the PMS100 field help |
DO | Status | Distribution order status | Updated by release, issue and receipt | Distribution order header and lines (MMS100 / MMS101) | - | Read the code list for your version in the MMS100 field help |
Only codes confirmed in Infor M3 documentation or by Infor community answers are listed. For PO, MO and DO the table shows where the status is stored; use the field help (F1) on the status field in PPS200, PMS100 and MMS100 for the full code list on your 13.x system rather than copying lists from SyteLine or LN, which use different codes.
Get a stuck-order analysis
Send us a list of orders stuck at a status and your CO type settings, and we will trace why they do not move.
Optional. The tool and every export work without this. No spam.
How to use it
Search by code (33) or by program (OIS150) to see what a status means and how a record got there. M3 statuses are two-digit numbers where the first digit is the stage and the second digit refines it, so an order header carries the lowest and highest line status rather than a single value. When you build a report, filter on the line status in OOLINE for line-level questions and on the lowest status in OOHEAD for order-level questions such as orders not yet fully delivered.
Where this lives in M3
Order type settings in CO Type. Open (OIS010) decide a lot: whether orders start as preliminary (10) and which status a delivery is created with (60, 61 or one of 62-66 for review). Allocation is driven by the allocation method on the item and warehouse in MMS002 and the warehouse settings in MMS005. Release for picking is in MWS410 Delivery Toolbox, with automatic or manual release set in the dispatch policy (MWS010). Deliveries are managed in OIS150 CO Delivery. Open, and the Customer Order Toolbox OIS300 shows line status across orders.
Worked example: why is this order not invoiced?
A line shows 66 Delivered in OIS300 but no invoice appears. Open the delivery in OIS150. If its status is 61, the CO type in OIS010/E is set to require proof of delivery, so someone must approve it. If it is between 62 and 66, the delivery is held for internal review. Option 16 Release for invoicing moves it to 60, and the next invoicing run picks it up. If the line itself is stuck at 44, the delivery was never reported; check the picking list and the delivery in MWS410.
Version differences and gotchas
Status sets differ between M3 versions and are partly configurable through the CO type, so a status that means one thing in one order type can be skipped in another. Do not reuse status tables from SyteLine (CSI) or LN; they use different codes and concepts. For PO, MO and DO, read the code list from the field help in your own system and record it here with the Excel export. OIS115 approval statuses describe approval progress, not order progress.
Frequently Asked Questions
What does status 33 mean in M3?
33 means Allocated. Order lines get status 33 when stock is allocated to them, either by the automatic allocation run or manually, and a completely allocated order has its order status raised to 33. The next step is normally release for picking, which moves the line to 44.
What is status 44 on an M3 customer order line?
44 means a picking list has been printed or released for the line. Lines allocated after a delivery was released for picking can be placed on a new suffixed picking list and also show 44. The line stays at 44 until the pick and delivery are reported.
Why is my M3 delivery stuck at status 61?
The CO type in OIS010/E creates deliveries with status 61, which needs proof of delivery or approval before invoicing. Approve it in OIS150 CO Delivery. Open, for example with option 16 Release for invoicing, which sets status 60 Ready to invoice.
Where do I see the full list of M3 status codes?
Use the field help (F1) on the status field in the program, for example OIS100 for customer orders, PPS200 for purchase orders and PMS100 for manufacturing orders. The M3 Business Engine user guides on docs.infor.com describe statuses inside each process chapter.
If you want planners and customer service to ask M3 why an order is stuck in plain English on your own servers, we can set that up.
Related Tools
Infor M3 OOHEAD and OOLINE Customer Order Columns Reference
Column-level reference for M3 customer order tables OOHEAD and OOLINE and the delivery tables they join to, with keys, joins and the OIS100MI fields that fill them.
Infor M3 & CloudSuiteInfor M3 Customer Order Status Tracking Worksheet
Document what each customer order status means in your M3 setup, stage by stage, and share it with the order desk.
Infor M3 & CloudSuiteInfor M3 H5 Hot Keys and Function Keys Reference
Keyboard shortcuts for M3 programs in the H5 client: function keys, list options, paging, and the Mac setting that makes them work.
Infor M3 & CloudSuiteInfor M3 Inventory and Allocation Tables Reference (MITBAL, MITLOC, MITALO, MITTRA)
Column-level reference for M3 stock, balance identity, allocation, material plan and transaction tables, with keys, joins and the programs that maintain them.
More Infor M3 & CloudSuite tools
See all- Infor M3 Program Reference (MMS001, OIS100, PMS100)
- Infor M3 MI API Transaction Call Generator
- 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
- Infor M3 Interface and Integration Inventory Worksheet
Keep exploring
Free tools
- Infor M3 Customer Order Status Tracking WorksheetDocument what each customer order status means in your M3 setup, stage by stage, and share it with the order desk.
- 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.
- Infor M3 Core Database Tables ReferenceLook up the main M3 tables, their two-letter column prefix and the key fields you join on. Searchable and exportable.
ERP fixes and how-tos
- Infor M3 manufacturing order material not allocated or shortWhy Infor M3 manufacturing order components show as not allocated or short, how to read MWOMAT and MITALO, and how to fix it before release.
- Infor M3 goods receipt against a purchase order, and how to reverse itHow to receive a purchase order in Infor M3, handle over and under delivery, and reverse a wrong receipt without damaging stock, costing or invoice matching.
- 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.
Runs with your ERP
- Medius AP automation and Infor M3 via Medius ConnectHow Medius AP automation posts supplier invoices into Infor M3 via Medius Connect: capture, PO matching, approvals, partner connectors, setup, pitfalls.
- 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.
Guides
- Infor M3 Manufacturing Execution: Orders, Reporting, and CostingInfor M3 manufacturing execution setup: product structures, routings, MO statuses, operation and receipt reporting, and shop floor data capture practices.
- Infor M3 Quality Management System Configuration GuideHow Infor M3 supports quality management, product traceability and compliance in regulated manufacturing: inspection plans, lot status, non-conformance, CAPA.
- 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.
AI on your ERP
- Infor M3 Customer Order Management With AI for Status, Allocation and Promise DatesAI for Infor M3 customer order management: answer order status, allocation and delivery date questions from OOHEAD and OOLINE data without exposing it publicly.
- 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.
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 add an AI chatbot to Infor M3How to add an AI chatbot to Infor M3 for staff and customers: grounded in M3 data via the API, embedded in a portal or Teams, and able to run fully on-prem.