Infor LN Enterprise Planning Not Generating Planned Orders
Infor LN planned orders not generated enterprise planning
Also searched as
- Infor LN MRP not creating planned orders
- LN item not planned in enterprise planning
- Infor LN generate planned orders no result
- Baan MRP no planned orders for item with demand
Short answer
When an item has demand but Enterprise Planning creates no planned orders, the cause is almost always planning master data: the item is not set to be planned, the planning horizon or time fences exclude the demand, the order policy or supply source is missing, or the planning run did not include the item. Check them in that order before suspecting the engine.
Applies to: Infor LN 10.x Enterprise Planning (item planning, supply and demand), also relevant for Baan IV and Baan 5 planning logic
How to find out why no planned orders appear
- 1Open the item's planning data for the planning company and confirm the item is flagged as planned in Enterprise Planning, with a planner and a supply source.
- 2Check the order system and order policy: a manual or no-planning setting keeps planned orders from being generated even with demand.
- 3Confirm demand actually exists in planning: sales orders, forecasts, dependent demand from a parent's planned or released order, and that their dates are inside the planning horizon.
- 4Look at the item's current inventory and supply: stock, safety stock and open purchase or production orders may already cover the demand.
- 5Verify the planning run scope included the item and the plant or warehouse, and that the run completed without errors.
- 6Review lead time and time fences. Demand inside a frozen fence is not changed by the run.
- 7Check the BOM and routing validity dates for a manufactured item, because an item with no valid BOM at the requirement date cannot be exploded.
- 8Rerun planning for just that item (net change or single item) and read the planning log for the item.
Is the item actually planned?
Enterprise Planning only touches items that are set up for it. An item can be fully valid for sales and purchasing and still be outside planning because its planning data is missing for that company or plant, or because its order system is set to a manual policy. Start here, because it is the cheapest check.
Look for the order policy as well. Lot-for-lot, fixed order quantity and periodic policies behave differently. A fixed order quantity of zero or a period with no days can make the engine produce nothing. For a manufactured item, check that the supply source is production, not purchase, and the other way round for bought items.
Horizons, time fences and dates
Planning only looks across its horizon. Demand beyond the end of the horizon is invisible to the run. Demand inside a frozen fence is also left alone, because the system assumes the near term is fixed by the planner. If the order date calculated by backward scheduling falls before the current date, the planned order may be created late or flagged rather than created at the position you expect.
Check the dates on the demand carefully. A sales order delivery date set months out may be correct, but the planned order will only be created if the horizon extends that far. Extend the horizon for long-lead items and review whether your cut-off setting is appropriate for the product family.
Supply that already covers demand
Often the planner expects a new order but existing supply meets the demand. Stock on hand, a purchase order due in time, a production order already released, or a reservation can all net the requirement. Safety stock raises the target but does not remove existing supply.
Inspect the projected inventory view for the item and read the net requirement per period. If the projected balance stays above zero and above safety stock for the whole horizon, the correct result is no planned order. If the balance goes negative and still nothing appears, return to planning master data.
BOM, routing and the planning run itself
A manufactured item requires a valid BOM for the requirement date. If the BOM version expires or has not started, the explosion fails or the dependent items receive no demand, which looks like a missing planned order one level down. Check effective dates on the BOM and routing as well as the production item data.
Finally, confirm the run. Planning can be started for a specific plant, a range of items or in net change mode. If the run excluded the item by selection, nothing is generated. Read the run log for the item. Messages there are the engine's explanation and are more reliable than guesses.
Common pitfalls
- !Assuming a valid sales item is automatically a planned item.
- !Looking at demand dates without checking the planning horizon and time fences.
- !Forgetting that existing supply or reservations already cover the requirement.
- !Overlooking expired BOM or routing effective dates for manufactured items.
- !Running planning with a selection range that excludes the item.
- !Changing order policy without telling the planner who relies on the old behaviour.
How an ERP-grounded AI assistant handles this
ERPray can answer a read-only question like why item X has no planned orders by reading its planning data, demand, supply and BOM validity together and listing which condition applies. It shows the query it used and uses your LN roles. Changes to planning data or reruns remain actions for an authorised planner.
Frequently asked questions
Why does Enterprise Planning show no planned orders for an item with sales orders?
Check whether the item is planned at all, whether the order policy allows planned orders, whether the demand falls inside the horizon, and whether existing stock or open orders already cover it. These four explain most cases.
Does safety stock create planned orders?
It raises the target level. If projected inventory falls below safety stock, planning creates supply to restore it. If existing supply keeps the balance above the target, no planned order is needed.
Why are dependent items missing planned orders?
Dependent demand comes from the parent's planned or released orders through the BOM. If the parent has no valid BOM at the requirement date, or the parent itself has no planned order, nothing flows down.
Should I rerun the whole plan to test a single item?
No. Run planning for that item or use net change, then read the item's planning log. A full run is slower and changes planned orders for every item in scope.
Related
How to calculate item cost prices in Infor LN
Infor LN calculates an item's cost price by rolling up material, labor, machine, subcontract and overhead costs defined against cost components, using the item's bill of material and routing as the calculation base for manufactured items and purchase price for bought items. The calculation can run in simulation mode to preview the result or in update mode to actually change the item's standard cost, which then drives inventory valuation and variance reporting going forward.
How-toHow to process inbound and outbound warehousing orders in Infor LN
Infor LN Warehousing splits every physical movement into inbound (goods arriving, mainly from purchase orders) and outbound (goods leaving, mainly for sales orders), each driven by its own warehouse order type. Inbound runs through intake, inspection if required, and put-away; outbound runs through order release, picking, packing and shipment confirmation, with each stage updating the order status other modules watch.
How-toHow Sales Schedules Work in Infor LN: Releases and Cumulative Quantities
A sales schedule in Infor LN holds a customer's rolling demand as a series of releases, each replacing the last, with lines split into firm and planned quantities. LN tracks cumulative quantities shipped against the customer's cumulative received so that a new release can be reconciled without double counting or dropping demand.
AdvancedHow to diagnose and fix a slow Infor LN session
A slow Infor LN session is usually caused by an unindexed or overly broad database query, unarchived data bloating a transaction table, or resource pressure on the Java application tier, and occasionally by a recently added custom DAL2 handler. The fix starts with isolating which tier the delay is actually in rather than guessing at a solution.
Error fixInfor LN bshell Process Stuck at 100% CPU: How to Diagnose and Fix It
A bshell process pinned at 100% CPU on the Infor LN application server almost always means one session is stuck in a 4GL loop, scanning an unindexed table, or waiting on a database lock. End the session from the Sessions Monitor first, then kill the OS process only if that fails, and check for a blocking database transaction before assuming it is a bug.
Error fixInfor LN Not Authorized to Run This Session: How to Fix It
Infor LN refuses to open a session with a not authorized message when the logged-in user's assigned role does not include that session, or when the session is blocked for the company they are logged into. Grant the session through Common > Authorization Management > Roles, or check the user's role and company context, and the session opens on retry. In most cases this is a permissions configuration issue, not a bug.
AI for ERPAI for Infor LN: Sessions, BODs, and Engineer-to-Order Work
Add grounded AI to Infor LN 10.x or CloudSuite: natural-language answers over sessions and BODs, agents for project and engineer-to-order work, on-prem options.
AI for ERPAI for Infor LN in Aerospace and Defense Manufacturing
AI grounded on Infor LN project, contract, and configuration management data for aerospace and defense manufacturers, with on-prem deployment for ITAR.
Stuck on Infor LN?
Talk to engineers who work inside Infor LN every week, and who build private AI that answers these questions from your own ERP data.