Infor LN & BaanGlossary

What Is Warehouse Order?

Also known as: LN warehousing order, warehouse order type, whinh order

Definition

A warehouse order is the execution document in Infor LN Warehousing that carries out an inbound, outbound or transfer movement. It is generated from an originating order such as a sales, purchase, production or transfer order, and its order type defines the procedure steps.

Warehouse Order Explained

Infor LN deliberately separates the commercial or manufacturing document from the physical movement. A sales order records what the customer bought and at what price; the warehouse order records what has to leave which warehouse, in what sequence of steps, and who confirms each one. The same separation applies to purchase receipts, production material issues and completions, and transfers between warehouses. Warehousing is a package in its own right for exactly this reason.

The warehouse order type is the control object. It defines which activities are part of the procedure and whether each is mandatory, manual or automatic. An inbound procedure might be receipt, inspection and put away, with inspection switched off for trusted suppliers or on for regulated material. An outbound procedure typically covers generating the outbound advice, releasing it for picking, confirming the pick and confirming shipment. Changing the order type changes the operational workflow without any code.

Warehouse orders also connect to the rest of the logistics chain. They generate the inventory transactions that drive valuation and the integration transactions that post to finance. They group into shipments and loads for transport planning and documentation. They can carry lot and serial data, and where handling units are in use they record which physical packages moved, which is what makes downstream traceability and packing documentation possible.

Because the procedure is configurable per order type, the same LN environment can run a very light process for internal transfers and a rigorously controlled one for customer shipments of regulated product. That flexibility is valuable but demands design discipline: every optional step you activate is a transaction someone must perform, and over-configured procedures are one of the most common reasons warehouse users complain that the new ERP is slower than the old one.

Why It Matters

The warehouse order type is where physical process design lives, so it directly sets how many clicks a picker or receiver performs.
Separating warehouse orders from commercial orders lets one shipment consolidate multiple sales orders cleanly.
Inbound inspection steps configured here are how regulated and aerospace receiving controls are actually enforced.
Warehouse orders generate the inventory and integration transactions that finance later reconciles, so misconfiguration surfaces in the ledger.

In Practice

A frequent go-live complaint is that shipping now takes far more steps than before. The cause is almost always an order type with every optional activity enabled and set to manual confirmation. Review each activity against a real operational need, automate the confirmations that add no control value, and reserve the full procedure for order types that genuinely require it.

Frequently Asked Questions

What is the difference between a sales order and a warehouse order in LN?

The sales order is the commercial agreement: customer, items, prices, terms and delivery commitments. The warehouse order is the physical execution document generated from it, covering which warehouse the goods leave, the picking and shipping steps, and the confirmations required. One sales order can generate several warehouse orders, and one shipment can consolidate lines from several sales orders.

What does a warehouse order type control?

It controls the procedure: which activities are included in the inbound, outbound or transfer flow, in what sequence, and whether each is automatic, manual or optional. Typical inbound activities are receipt, inspection and put away; typical outbound activities are outbound advice, release, pick confirmation and shipment. It also drives defaults such as the warehouse and inventory handling behavior.

Related Terms

Handling Unit

A handling unit in Infor LN is an identified physical package - a pallet, carton or container - tracked with its own ID. Handling units nest hierarchically, carry item, lot and serial data, and move through warehousing and shipping as a single scannable entity.

Integration Transaction

An integration transaction is the record Infor LN creates when a logistic event such as a receipt, issue, shipment or production completion must post to finance. Mapping schemes translate each transaction into the correct debit and credit ledger accounts and dimensions.

Multisite (Infor LN)

Multisite in Infor LN is the configuration pattern for running several plants, warehouses or legal entities in one environment using sites, enterprise units and multiple companies, with intercompany trade rules that price and post transfers between them automatically.

Go Deeper

Free Tool

Infor LN vs SyteLine Selector

Answer ten questions about your sites, manufacturing mode, and complexity to see whether Infor LN or SyteLine (CloudSuite Industrial) is the better fit.

Infor LN Implementation Cost: What to Budget

Infor LN implementation cost typically runs $500K to $5M+. See budget breakdowns by phase, license-to-services ratios, and the cost drivers for 2026 projects.

Infor LN to CloudSuite: Migration Playbook

Infor LN to CloudSuite migration playbook: Baan and LN version paths, extension conversion, ION integration rework, timelines, and defense compliance steps.

Working with Warehouse Order in a live environment? Our engineers do this every day - and our AI agents automate most of it.

Talk to an Expert Browse the Full Glossary

Back to Glossary

Try it here, free

Infor LN Warehousing Tables Reference (whinh, whwmd, whinr)

Open full tool

Table-by-table map of LN 10.x Warehousing: masters, warehouse orders, receipts, outbound advice, shipments, cycle counts, adjustments and inventory transactions.

Download:

Table	Description	Key fields	Important columns	Joins to	Session	Notes
tcmcs003	Warehouses (general)	cwar	typw warehouse type, cadr address, comp financial company, wmsc WMS controlled, inep include in enterprise planning	Every cwar field in wh tables	tcmcs0503m000 Warehouses	Still the warehouse master in LN 10.x; whwmd200 adds the warehousing settings.
whwmd200	Warehouses (warehousing data)	cwar	site, sloc locations, binb blocked for inbound, bout blocked for outbound, bcyc block during cycle counting, reje quarantine inventory, qwrh quarantine warehouse	whwmd200.cwar = tcmcs003.cwar	whwmd2500m000 Warehouses	One session shows fields from both tcmcs003 and whwmd200.
whwmd210	Item data by warehouse	cwar, item	iwhs status, valm valuation method, omth order method, sups supply system, reop reorder point, supw supply warehouse	whwmd210.item = tcibd001.item	whwmd2510m000 Item Data by Warehouse	uidt decides whether item-level ordering data is used.
whwmd215	Warehouse - item inventory	cwar, item	qhnd on hand, qall allocated, qord on order, qblk blocked, qbpl blocked for planning	whwmd215.item = tcibd001.item	whwmd2515m000 Warehouse - Item Inventory	Fastest source for on-hand totals per warehouse.
whwmd300	Warehouse locations	cwar, loca	zone storage zone, loct location type, filo fixed location, oclo occupied, full location full, ball blocked for all transactions	whinr140.cwar, loca = whwmd300.cwar, loca	whwmd3500m000 Warehouse - Locations	Only used when the warehouse is location controlled.
whwmd400	Items - warehousing	item	locc location controlled, lttr lot tracking, srtr serial tracking, niwo allow negative inventory, obpr outbound method	whwmd400.item = tcibd001.item	whwmd4500m000 Items - Warehousing	Item settings valid in every warehouse.
whinh200	Warehousing orders (header)	oorg, orno, oset	oorg order origin, orno order, oset set, otyp warehousing order type, hsta header status, sfty/sfco ship-from type and code, stty/stco ship-to type and code, pddt planned delivery date, prdt planned receipt date	whinh200.orno = tdsls400.orno when the origin is a sales order; tdpur400.orno for purchase	whinh2100m000 Warehousing Orders	oorg tells you which source table orno belongs to; see the order types reference for origin values.
whinh210	Inbound order lines	oorg, orno, oset, pono, seqn	lsta status, item, qoro ordered quantity, orun unit, qord inventory quantity, cwar warehouse, sfbp ship-from BP, prdt planned receipt date	whinh210.oorg, orno, oset = whinh200.oorg, orno, oset	whinh2110m000 Inbound Order Lines	One line per expected receipt from the source order.
whinh220	Outbound order lines	oorg, orno, oset, pono, seqn	lsta status, item, qoro ordered quantity in order unit, qord ordered quantity in inventory unit, cwar warehouse, pddt planned delivery date, shrt shortage, cncl canceled	whinh220.oorg, orno, oset = whinh200.oorg, orno, oset; pono links to the source line	whinh2120m000 Outbound Order Lines	Released sales order lines arrive here before outbound advice.
whinh225	Outbound advice	oorg, orno, oset, pono, seqn, sern	sern advice, item, cwar warehouse, locf from location, clot lot, qads advised quantity, qadv advised in inventory unit, rlsd released, pckd picked, runn run, shpm shipment	whinh225.oorg, orno, oset, pono, seqn = whinh220 key	whinh4525m000 Outbound Advice	Shows which location and lot the system advised for picking.
whinh300	Shipment notices (ASN)	sfbp, shid	shid shipment, stat status, pddt planned delivery date, shdt shipping date, asnr supplier ASN, cpro carrier tracking number	whinh300.shid = whinh310.shid	whinh3100m000 Shipment Notices	Inbound ASNs from suppliers; receipts can be created from them.
whinh310	Warehouse receipts (header)	rcno	rcno receipt, sfbp ship-from BP, dino packing slip, crdt creation date, stat status, cwar warehouse, shid shipment	whinh310.rcno = whinh312.rcno	whinh3110m000 Warehouse Receipts Overview	One receipt can cover lines from several inbound orders.
whinh312	Warehouse receipt lines	rcno, rcln	orno order, oset set, pono line, seqn sequence, item, qrcr received quantity in receipt unit, qrec received quantity in inventory unit, idat inventory date, insp inspection, conf confirmed	whinh312.orno, pono = whinh210.orno, pono	whinh3512m100 Warehouse Receipt Lines	Confirming the receipt updates these lines and posts inventory.
whinh425	Shipping containers	load, cntr	cntr shipping container, cnst container status, pitm packaging item, huid handling unit, grwt gross weight, volm volume, cpro carrier tracking number	whinh430.cntr = whinh425.cntr	whinh4125m000 Shipping Containers	Used when shipments are loaded into containers.
whinh430	Shipments (header)	shpm	shst status, load load, cntr shipping container, huid handling unit, corn customer order, sfco ship-from code, stco ship-to code, carr carrier/LSP, cdat date confirmed	whinh430.shpm = whinh431.shpm; tdsls406.shpm = whinh430.shpm	whinh4130m000 Shipments	Confirming the shipment triggers the sales delivery in tdsls406.
whinh431	Shipment lines	shpm, pono	shst status, item, clot lot, serl serial number, qpic picked, qshp shipped quantity, qnsh not shipped quantity, grwt gross weight	whinh431.shpm = whinh430.shpm	whinh4131m000 Shipment Lines	Shipped versus not shipped quantity explains short shipments.
whinh250	Warehousing orders history	Same identifying fields as whinh200	Header values at the time the order was processed	whinh250.orno = whinh200.orno	whinh2550m000 Warehousing Orders History	Line history is in whinh260 (inbound) and whinh270 (outbound).
whinh500	Cycle counting orders	orno, cntn	cntn count number, cwar warehouse, odat order date, ccst status, prcc process count, rcyn reconciliation	whinh500.orno = whinh501.orno	whinh5100m000 Cycle Counting Orders	Each recount increments the count number.
whinh501	Cycle counting order lines	orno, cntn, pono	loca location, item, clot lot, qstp stock point inventory, qcnt actual inventory, qvrc variance in inventory unit, cadj reason for variance, cdat date of count	whinh501.item = tcibd001.item	whinh5101m000 Cycle Counting Order Lines	Variance qvrc is what posts as an inventory adjustment.
whinh520	Adjustment orders	orno	cwar warehouse, odat order date, adrn reason for adjustment, adst status, mnad manual adjustment	whinh520.orno = whinh521.orno	whinh5120m000 Adjustment Orders	Header for manual inventory corrections.
whinh521	Adjustment order lines	orno, pono	item, cwar warehouse, loca location, clot lot, qstp stock point inventory, qadj actual inventory, qvrc variance, adrn reason, adat adjustment date, prcd processed	whinh521.item = tcibd001.item	whinh5121m000 Adjustment Order Lines	Processed lines create inventory transactions in whinr110.
whinr100	Stock point transactions	cwar, loca, item, trdt (per stock point)	idat inventory date, trdt transaction date, kost transaction type, qstk quantity, koor order origin, qhnd inventory after transaction, clot lot, serl serial number	whinr100.item = tcibd001.item	whinr1500m000 Warehouse - Item - Stock Point Transactions	Location and lot level transaction trail.
whinr110	Inventory transactions by item and warehouse	item, cwar, trdt, seqn	koor type of order, orno order, pono line, srnb sequence, rcno receipt, shpm shipment, qstk quantity, kost transaction type, qhnd inventory after transaction	whinr110.orno = source order (tdsls400, tdpur400, tisfc001) depending on koor	whinr1510m000 Item - Warehouse - Inventory Transactions	Main audit trail for stock movements per item and warehouse.
whinr140	Stock point inventory	cwar, loca, item, clot, idat	qhnd on hand, qblk blocked, qlal allocated, qord on order, effn effectivity unit, trdt last transaction date, bout blocked for outbound, bcyc blocked for cycle counting	whinr140.cwar, loca = whwmd300.cwar, loca	whinr1540m000 Stock Point Inventory	Inventory by location, lot and inventory date.

Physical tables are t + table code + company number (twhinh200100). SQL columns use t_ on SQL Server and t$ on Oracle. Tables and fields were checked against the LN 10.x online help for the sessions listed; quantities in whinh tables come in both order unit and inventory unit, so check the unit field next to each quantity. Order origin values for oorg are covered in the separate warehousing order types reference.