# Infor LN Warehousing Order Types and Origins Reference > Source: https://netray.co/tools/infor-ln-warehousing-order-types-reference > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Reference of the order origins that feed LN warehousing, their direction, source package and what to check. ## Category infor-ln ## Erp Infor LN ## Audience - Warehouse consultant - LN logistics analyst - Warehouse manager ## Tool **Kind:** worksheet **Mode:** reference **Columns:** #### Order origin **Key:** origin **Type:** text #### Direction **Key:** direction **Type:** text #### Source package **Key:** source **Type:** text #### Typical flow **Key:** flow **Type:** text #### What to check **Key:** check **Type:** text **Rows:** **Origin:** Purchase order **Direction:** Inbound **Source:** td Order Management (tdpur) **Flow:** Receipt of purchased goods into a warehouse, optional inspection, then put-away **Check:** Receipt warehouse, inspection setting, unit of measure conversion **Origin:** Purchase return **Direction:** Outbound **Source:** td Order Management (tdpur) **Flow:** Return to supplier issued from stock **Check:** Valuation of the return and the credit expected **Origin:** Sales order **Direction:** Outbound **Source:** td Order Management (tdsls) **Flow:** Pick, pack and ship against a customer order **Check:** Allocation, reservations, delivery terms **Origin:** Sales return **Direction:** Inbound **Source:** td Order Management (tdsls) **Flow:** Customer return received, inspected and restocked or scrapped **Check:** Return reason and target stock status **Origin:** Production order receipt **Direction:** Inbound **Source:** ti Manufacturing (tisfc) **Flow:** Finished or semi-finished output received from the shop floor **Check:** Receipt warehouse and quantity reported **Origin:** Production order material **Direction:** Outbound **Source:** ti Manufacturing (tisfc) **Flow:** Material issued from stock to a production order **Check:** Backflush versus manual issue and supply point **Origin:** Warehouse transfer **Direction:** Both **Source:** wh Warehousing **Flow:** Move stock between warehouses or between locations **Check:** In-transit handling and valuation across warehouses **Origin:** Inventory adjustment **Direction:** Both **Source:** wh Warehousing **Flow:** Correct stock quantity after a count or error **Check:** Authorization and the cost effect of the adjustment **Origin:** Cycle counting **Direction:** Both **Source:** wh Warehousing **Flow:** Count a set of items or locations and post the differences **Check:** Count tolerances, who approves differences **Origin:** Service order material **Direction:** Outbound **Source:** ts Service **Flow:** Spare parts issued for service work **Check:** Service warehouse and billing link **Origin:** Project material **Direction:** Outbound **Source:** tp Project **Flow:** Material issued to a project budget **Check:** Project cost line and warehouse ownership **Origin:** Manual or ad hoc order **Direction:** Both **Source:** wh Warehousing **Flow:** Warehouse order created directly without a source document **Check:** Reason, traceability and who is allowed to create these **Notes:** Order origin names and their exact list differ by LN version and enabled functionality. This reference gives the common business flows only. Confirm the origin domain in your own data dictionary and the order procedure setup in your warehousing parameters. ## Content **Intro:** Infor LN warehousing orders do not exist on their own: each one is created because something upstream happened, such as a purchase receipt, a sales shipment or a production issue. This reference lists the common order origins, whether they are inbound or outbound, and what to check for each. **Sections:** #### How to use the table **Body:** Search by origin, direction or package to find the flow you are analyzing. Consultants use it while designing warehouse procedures, analysts use it when explaining why a warehouse order exists, and administrators use it to decide which origins need a procedure and a location. Export to Excel and add columns for your own warehouse, procedure ID and owner so it becomes the master of your process design. #### The logic behind origins **Body:** In LN, orders from purchasing, sales, manufacturing, service and projects create warehouse orders and order lines through the warehousing module, while transfers, adjustments and counts are created inside warehousing. Each origin follows an order procedure that defines the steps such as receipt, inspection, storage, picking and shipping. The direction decides whether stock increases or decreases. Master data in warehousing master data (whwmd) and transactions in inventory handling (whinh) tie the model together. **Bullets:** - Inbound origins raise stock after receipt - Outbound origins reduce stock at issue or shipment - Transfers and adjustments need separate authorization #### Common mistakes **Body:** A frequent mistake is mixing up the order origin with the order type used in costing or planning. Another is leaving manual orders unrestricted, which leads to inventory that cannot be traced to a source document. Teams also forget that returns need their own procedure and valuation rules, and that a transfer between warehouses can leave stock in transit that affects planning. Review each origin against a real example before go-live and keep the procedure design in one place. **Cta:** If you are untangling LN warehouse flows, we can show how a read-only assistant explains why a warehouse order exists and what is blocking it. **Faq:** #### What is a warehousing order in Infor LN? **Answer:** It is the order that instructs the warehouse to receive, store, pick or ship goods, created from a source such as a purchase, sales or production order, or directly inside warehousing for transfers, counts and adjustments. #### Where do LN warehousing orders come from? **Answer:** Mostly from other packages: purchase and sales in order management, material and receipts from manufacturing, parts from service and material from projects. Warehousing also creates its own orders for transfers, adjustments and cycle counts. #### What does the whinh module do? **Answer:** whinh is the inventory handling module in the warehousing package. It deals with warehouse orders, order lines and inventory transactions. Master data sits in whwmd, and inbound and outbound processing are in whinr and whout. #### Can I create warehouse orders manually? **Answer:** Some can be created directly, such as transfers or adjustments. Restrict that with authorizations and require a reason, because manual orders have no source document and are harder to audit later. ## Search terms infor ln warehouse order types, infor ln warehousing order origin, whinh warehouse orders, infor ln inbound outbound orders, infor ln warehouse transfer order, ln warehousing reference, infor ln inventory transaction types --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json