How-toInfor M3Warehouse / Picking

Pick Line vs Wave Line in Infor M3

Question
pick line vs wave line in infor m3

Also searched as

  • m3 wave picking
  • m3 pick list line
  • m3 warehouse wave release

Short answer

A pick line is the instruction to pick a quantity of an item from a location for one order line. A wave groups many such lines so the warehouse releases and works them together by time, route, carrier or zone. Terminology and screens depend on your M3 release and warehouse setup, so confirm against your own configuration.

Applies to: Infor M3 distribution and warehouse management. Wave functionality depends on release and licensed warehouse modules.

Decide which one you are looking at

  1. 1Open the pick list for a delivery and find the line level: item, quantity, location, lot. That is the pick line.
  2. 2Check whether your warehouse uses wave processing. If orders are released straight to pick lists, you may have pick lines but no waves.
  3. 3If waves are used, look at the wave header: release time, criteria such as carrier, route or customer, and status.
  4. 4Open the wave contents to see which pick lines belong to it.
  5. 5Confirm which one the user is blocked on: an unreleased wave stops all its lines, while a line problem, such as no stock at the location, stops only that line.
  6. 6Fix at the right level. Release or correct the wave for group problems, and correct stock or allocation for line problems.

Concept difference

The pick line is the work unit for the picker. It carries what to pick and from where, and it is confirmed when the picker reports the quantity. The wave is the control unit for the supervisor: when the work is released, how it is sequenced and how workload is balanced across pickers and docks.

In small warehouses lines are released one by one and waves add little. In busy ones, waves keep carrier cut-offs and zones under control.

When wave logic helps

Use waves when pick volume exceeds what a free-flow release can cope with, when orders must ship by carrier cut-off, or when pick zones need to be loaded evenly. Use direct pick lists when orders are few and urgent.

Be careful with consolidated or batch picking: one pick may serve several orders, and the split back to each order happens at packing or reporting.

Troubleshooting

If lines are missing from a pick list, check allocation first, because a line with no allocation cannot be picked. If an entire group is missing, check that the wave was released and met its criteria.

If a wave is stuck, look at the status and the oldest unconfirmed line. One unreported line can hold the wave open.

Try it here, free

Infor M3 Item Planning Parameter Worksheet

Open full tool

Work out safety stock and reorder point for each item and warehouse before loading planning parameters into M3.

Common pitfalls

  • !Fixing a wave-wide issue one line at a time.
  • !Releasing a wave before stock is allocated, creating empty picks.
  • !Assuming other sites use the same wave criteria.
  • !Forgetting to confirm lines so the wave never closes.
  • !Mixing terms between releases when searching documentation.

How an ERP-grounded AI assistant handles this

A warehouse supervisor's question is usually which waves are late and which lines hold them. A read-only assistant can answer by joining wave, pick list and allocation data, with the query shown. Netray can run it next to an on-prem M3 database.

Frequently asked questions

Is a wave the same as a pick list?

No. A pick list holds the lines for a delivery or task. A wave is a grouping and release mechanism for many lines or lists. Exact structures differ by setup.

Do I need waves in M3?

Only if volume and cut-offs justify them. Smaller sites often run on direct pick lists.

Why is a pick line not appearing?

Check allocation, order status and whether the wave it belongs to was released.

Related

Advanced

Infor M3 Allocation Table: MITALO Reference and Queries

M3 records material and stock allocations in the allocation table, MITALO, one row per allocation of an item to a demand such as a customer order line or a manufacturing order material line. The allocated total is also summarised on the item-warehouse balance, which is why the two can disagree when something goes wrong.

How-to

How to Enter a Customer Order in M3 (OIS100)

OIS100 (Customer Order. Open) is the primary M3 program for entering and maintaining customer orders, built as a header-then-line workflow: you first create the order header with customer, order type and delivery terms, then add order lines that each carry their own item, quantity, price and delivery date defaulted from customer and item agreements.

How-to

Infor M3 negative on-hand balance: how to find it and fix it

Negative stock in M3 almost always comes from an issue or reporting transaction posted against a balance ID that had not yet been received, or from a receipt that was reversed after the stock was consumed. Find the item and warehouse in the item-warehouse balance (MITBAL), compare it with the balance IDs (MITLOC), read the item transactions (MITTRA), and correct with a stock count or a proper receipt rather than a blind adjustment.

Error fix

M3 API Error: Record already exist

Record already exist means the MI Add transaction you called is trying to insert a key that is already present in the target M3 table, most often because a prior call succeeded and was retried, or because the key fields you built do not match what you think they match. Read the errorField and errorFieldGroup attributes on the response to see exactly which key field M3 flagged, then either switch to the matching Chg (change) transaction or fix the key construction in the caller.

Advanced

Paging M3 API MI List Transactions Past the Default Record Limit

M3 List transactions (the read/browse transaction most MI programs expose, such as CRS610MI.LstByNumber or OIS100MI.LstOrderHead) cap the rows returned per call using the MaxReturnedRecords input field, and by default many clients leave it low or unset, which looks like the API silently truncating results. Set MaxReturnedRecords explicitly, then loop the call using the last key values from the previous page as the starting position until fewer rows than the limit come back.

Error fix

M3 API Error: Not Authorized to Program

Not authorized to program (or the equivalent transaction-level authorization error) means the M3 user ID the integration authenticates as can log in fine but has not been granted access to that specific MI program, transaction, or company/division through its authority group. Fixing it means adding the program/transaction to the integration user's authority group in M3, not changing anything in the calling code.

AI for ERP

Infor M3 Customer Order Management With AI for Status, Allocation and Promise Dates

AI for Infor M3 customer order management: answer order status, allocation and delivery date questions from OOHEAD and OOLINE data without exposing it publicly.

Stuck on Infor M3?

Talk to engineers who work inside Infor M3 every week, and who build private AI that answers these questions from your own ERP data.

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

Guides

AI on your ERP

Integrations

Comparisons

Software