# Infor M3 Planning Time Fence: Settings, the Planning Workbench and Typical Mistakes

> Source: https://netray.co/erp-help/infor-m3-planning-time-fence-workbench-settings
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

In M3 MRP, time fences define how close to today the planning engine is allowed to create or change orders. The demand time fence controls which demand is considered firm, and the planning time fence stops automatic order creation inside it, leaving the planner to decide in the planning workbench. Most missing planned orders come from time fence values that are too long for the item's real lead time.

## Kind

how-to

## System

infor-m3

## Erp

Infor M3

## Module

Supply Chain Planning / MRP

## Query

infor m3 planning time fence

## Alternate Queries

- infor m3 planning workbench
- m3 demand time fence planning time fence
- m3 mrp time fence misconfiguration

## Applies To

Infor M3 (current releases) item-warehouse planning; field labels may differ slightly between versions

## Steps

### How to check and set time fences

**Items:**

- Open the item-warehouse planning data (the Item. Connect Warehouse maintenance, MMS002) and find the planning parameters: order type, lead time, lot sizing and the time fence fields.
- Check whether a demand time fence and a planning time fence are set, and in which unit (days or periods). Zero or empty usually means no fence.
- Compare the fence to the real lead time. A fence longer than the lead time means demand inside the fence is not auto-planned even though you could still meet it.
- Run the MRP planning for one item and warehouse. Then open the planning workbench for that item and review proposals, messages and the dates.
- Check proposals inside the fence. They need a manual decision (release, move, or ignore) because the engine does not create them automatically.
- Adjust the fence on the item-warehouse record, or on the planning policy if your setup uses a shared parameter, and rerun planning for the same item.
- Verify the result in the workbench: the proposals should now appear where you expected, with correct dates.
- Document the fence policy by item class so planners know why an order appears inside or outside the fence.

## Sections

### Demand time fence versus planning time fence

**Body:**

The demand time fence is about which demand the plan trusts. Inside it, the plan is driven by customer orders and not by forecasts, which avoids overplanning against a forecast for next week that actual orders have already replaced.

The planning time fence is about change. Inside it, the engine does not create or reschedule orders automatically because the lead time is too short to change the plan safely. Anything it needs there appears as a message for the planner.

### How it interacts with the planning workbench

**Body:**

The workbench is where planned proposals and messages are reviewed and released. Proposals inside the fence are not hidden, but they require a deliberate action. A planner who only expects the engine to create them will think MRP is broken.

A good routine is to review the workbench by exception: filter on messages inside the fence, decide which to release now, and then rerun planning so the net result is consistent with what was released.

### Typical misconfigurations

**Body:**

Common mistakes: a fence copied from a long-lead item to a short-lead item, a demand time fence so long that forecasts are effectively ignored, a fence defined in the wrong unit, and fences set on the warehouse of the producer but not of the consuming warehouse.

Also watch for phantom shortages: inside the fence the plan shows a shortage with no proposal, the planner assumes MRP is wrong, and a manual purchase is made at a premium. A fence policy by item class prevents this.

## Pitfalls

- A fence longer than the item's lead time.
- Expecting auto-created orders inside the planning time fence.
- Fence values in days where periods were intended.
- Fixing one warehouse and forgetting the others.
- Not rerunning planning after releasing proposals.

## Ai Angle

An assistant grounded in M3 can answer why there is no planned order for this item by reading the item-warehouse parameters, fences, demand and supply and stating which condition applies. ERPray is read-only and shows the queries; changes to the fence stay with your planning lead.

## Faq

### What is a planning time fence in M3?

**Answer:** It is a period close to today inside which MRP does not automatically create or reschedule orders. Inside the fence, shortages appear as messages the planner must decide on, typically in the planning workbench.

### What is the difference between the demand and planning time fence?

**Answer:** The demand time fence defines how far ahead demand is treated as firm, usually customer orders over forecast. The planning time fence defines how close to today the engine stops changing the plan automatically.

### Why does MRP not create an order for a shortage?

**Answer:** Often the shortage is inside the planning time fence, the item is not set for supply planning, or existing supply covers it. Check the fences and the item-warehouse parameters first.

### Where do I set time fences in M3?

**Answer:** In the item-warehouse planning data, maintained through MMS002, and possibly through shared planning parameters depending on your setup. Confirm field names on your version.

## Search terms

infor m3 planning time fence, infor m3 planning workbench, m3 demand time fence, m3 mrp, m3 item warehouse planning, infor m3 planned orders, m3 mms002, m3 supply planning

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