# Infor M3 MRP not creating planned orders: what to check

> Source: https://netray.co/erp-help/m3-mrp-not-creating-planned-orders-item-warehouse-planning
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

If M3 planning does not suggest an order for an item, the item-warehouse is usually not set up to be planned, the demand is not visible to planning in the horizon, existing supply already covers it, or the planning run did not include the item. Check the item-warehouse planning parameters first, then supply and demand, then the run itself.

## Kind

how-to

## System

infor-m3

## Erp

Infor M3

## Module

MMS / Planning (MRP)

## Query

Infor M3 MRP not creating planned orders

## Alternate Queries

- M3 MRP run no planned purchase orders
- M3 planning method item warehouse not planned
- M3 MRP does not suggest orders for item

## Applies To

Infor M3 Business Engine 13.x and later with MRP and the planning functions in MMS. Parameter names differ by version and by what your partner configured.

## Steps

### Checklist for an item that MRP ignores

**Items:**

- Confirm the item is active and has an item-warehouse connection for the warehouse you expect to be planned.
- On the item-warehouse, check the planning method and that the item is flagged to be included in MRP planning, not manual or no-planning.
- Check the planning parameters: order policy, lot sizing, lead times, safety stock and any planning time fence.
- Check demand: customer orders, forecasts, MO components and requisitions must exist in the planning horizon with the right warehouse.
- Check supply: confirmed purchase orders, MOs and on-hand may already cover the demand, in which case no new order is correct.
- Check whether the planning run covered the item: planning selection by item group, planner or warehouse can exclude it.
- Run planning again for just this item if your version supports single-item or net-change planning and read the planning results.

## Sections

### Item-warehouse setup is the usual cause

**Body:**

M3 plans at the item-warehouse level, not the item level. An item can be fully valid in the item master and still unplanned because its item-warehouse record uses a planning method that excludes it, has a missing supply source, or is connected to the wrong warehouse. Always start at the item-warehouse record.

The supply source matters too. A planned order needs to know whether to propose a purchase order or a manufacturing order, from which supplier or product structure. Missing a default supplier or missing a product structure and routing makes planning unable to create a proposal.

### Demand and supply in the horizon

**Body:**

Planning only looks as far as its horizon. If demand falls outside, nothing is planned. Time fences also freeze orders inside a window so planning will not create or change them, which looks like MRP not working when it is behaving as designed.

Net requirements are demand minus supply. If a purchase order with a delivery date inside the horizon already covers the demand, there is no gap. Read the supply and demand overview for the item before assuming planning is broken.

### Run selection and when the run last executed

**Body:**

Planning runs are usually scheduled as jobs with selection criteria. If the item group, planner code or warehouse is excluded, the item is skipped silently. Check the job parameters and the last execution log for errors, such as a locked record or missing data on a related item.

Net-change planning only processes items marked as changed since the last run. If a change did not flag the item, for example a direct data load, it can be missed until a full regeneration. This is a design trade-off between run time and completeness.

## Pitfalls

- Checking only the item master and not the item-warehouse record.
- Assuming a time fence is a bug, when the order is frozen inside the fence by design.
- Missing a default supplier or product structure, so planning has nothing to propose.
- Relying on net-change planning after bulk data loads that did not flag the items.
- Reading planned orders in the wrong warehouse or company.

## Ai Angle

An assistant grounded in M3, such as ERPray, can answer why an item was not planned by reading the item-warehouse planning fields, the demand and supply in the horizon, and the last planning job parameters, and showing each source. It does not run planning or change parameters; those remain with your planner and system administrator.

## Faq

### Why does MRP plan some items but not others?

**Answer:** Differences in the item-warehouse planning method, supply source, time fence or run selection. Compare a working item with the failing one field by field at the item-warehouse level. The difference is usually obvious once both are side by side.

### What is a planning time fence?

**Answer:** A window in which planning does not create or reschedule orders, to protect near-term execution. Demand inside the fence needs manual action. If MRP seems to ignore near-term demand, check the time fence on the item-warehouse.

### Does net-change planning find every change?

**Answer:** Only items flagged as changed since the last run. Changes made outside normal transactions, such as some data loads, may not flag the item. Run a full regeneration periodically to catch these.

### Should I fix this by creating the order manually?

**Answer:** A manual order gets you through today but leaves the planning setup broken, so the problem returns. Fix the item-warehouse setup, then let planning propose orders so lead times and lot sizes stay consistent.

## Search terms

m3 mrp no planned orders, infor m3 planning, m3 planning method, m3 item warehouse planning, m3 time fence, m3 net change planning, m3 mrp not working, m3 planned purchase order

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json