Infor LN Freeze/Unfreeze Planning: Frozen Zones and Time Fences Explained
Freeze/unfreeze planning in Infor LN is the mechanism in Enterprise Planning (the cp package) that locks planned orders inside a defined time fence so MRP regeneration cannot reschedule, resize, or delete them. Freezing stabilizes the near-term schedule that the shop floor and suppliers are already executing, while unfreezing releases that horizon back to the planning engine when conditions change. Getting the frozen zone right is the difference between a stable weekly schedule and constant MRP nervousness. This guide explains how LN implements freezing, which parameters control it, and how planners should operate it day to day.
How the Frozen Zone Works in LN Enterprise Planning
In LN Enterprise Planning, each plan item carries planning horizons and time fences defined in the item planning data. Inside the frozen period, the planning run treats existing planned and firm planned orders as fixed: it will not reschedule them earlier, change quantities, or cancel them, and by default it will not insert new planned orders inside the fence. Exception messages are still generated, so planners see reschedule-in and reschedule-out signals without the system acting on them automatically. Outside the fence, LN regenerates freely. The practical effect is that the master production schedule for the next one to four weeks stays stable between planning runs, which is essential when work orders are already kitted and purchase orders are already confirmed with suppliers.
Key Parameters: Time Fences, Horizons, and Order Status
Several settings interact to produce freeze behavior, and misconfiguring any one of them reintroduces schedule churn. The time fence on the plan item defines the frozen window in working days. The order horizon and planning horizon bound how far out LN generates planned supply. Firming a planned order (converting it to firm planned status) protects it individually regardless of fences, and transferring it to execution creates the actual production or purchase order that planning no longer owns.
- Time fence (item planning data): number of workdays from the plan date during which planned orders are frozen
- Order horizon: window in which LN creates detailed planned orders; keep it beyond cumulative lead time
- Firm planned orders: individually locked orders a planner has committed, immune to regeneration changes
- Transfer to execution: converts planned orders into SFC production orders or purchase orders, removing them from cp control
When to Freeze and When to Unfreeze
Freeze length should roughly match your execution commitment window, not your comfort level. A machining plant with 5-day kitting cycles typically freezes 5 to 10 working days; an aerospace structures supplier with long-lead titanium may firm supply 12 weeks out but keep the automated frozen fence at 2 to 3 weeks. Unfreezing is appropriate when a customer pulls in a delivery under a DX-rated DPAS order, when a quality hold scraps planned input material, or during S&OP replanning at month boundaries. The discipline that matters: unfreeze deliberately in a simulation first, review the resulting exception messages, and only then apply changes to the actual plan, so a single hot order does not destabilize 200 others.
- Freeze horizon should equal or slightly exceed kitting plus final assembly lead time, typically 1-3 weeks
- Use plan simulations to test unfreeze impact before committing changes to the live plan
- Rate-priority DPAS orders justify targeted unfreezing of specific plan items, not a global fence change
- Review exception messages weekly; a rising reschedule-message count signals the fence is set too long
Common Freeze/Unfreeze Mistakes in LN
The most damaging pattern is planners firming everything. When 80 percent of planned orders are firm planned, MRP is effectively disabled and shortages surface as expedites instead of exception messages; a healthy plan keeps firm orders under 20 percent of the open horizon. Second, mismatched fences between levels: freezing a parent assembly for 15 days while its purchased components have no fence lets component orders walk away from the parent schedule. Third, teams often confuse the planning freeze with the finance period freeze in tfgld; they are unrelated controls. Finally, sites that run net-change planning multiple times daily against a short fence generate constant micro-adjustments, which is exactly the nervousness freezing exists to prevent.
How Netray Stabilizes LN Planning with AI Agents
Netray builds AI planning agents that sit on top of LN Enterprise Planning and manage the freeze boundary intelligently. The agents analyze exception message history, supplier OTD, and actual lead-time variance to recommend per-item time fences instead of one plant-wide setting, then monitor daily planning runs and flag firm planned orders that no longer need protection. At one defense electronics manufacturer, Netray agents cut reschedule exception volume by 62 percent and reduced planner firefighting time by roughly 12 hours per planner per week, while holding on-time delivery above 96 percent. Agents run on-prem against your LN database, so CUI-adjacent production data stays inside your CMMC boundary.
Frequently Asked Questions
What does freezing planned orders do in Infor LN?
Freezing in Infor LN Enterprise Planning locks planned orders inside the time fence defined on the plan item, so MRP regeneration cannot reschedule, resize, or delete them. LN still generates exception messages for those orders, but planners must act on them manually. This keeps the near-term production and purchase schedule stable between planning runs while the horizon beyond the fence continues to replan freely.
What is the difference between a frozen order and a firm planned order in LN?
A frozen order is protected because it falls inside the item time fence; the protection is positional and disappears as the fence rolls forward. A firm planned order is individually locked by a planner and stays protected regardless of where it sits in the horizon. Firm planned orders survive full regeneration until they are transferred to execution or manually unfirmed, so overusing them effectively disables MRP.
How long should the frozen zone be in Infor LN?
Set the frozen zone to cover your execution commitment window: kitting plus final assembly lead time, typically 5 to 15 working days for discrete manufacturers. Longer fences increase stability but delay response to demand changes and inflate reschedule exception counts. Best practice is per-item fences based on lead-time variance rather than one plant-wide value, reviewed quarterly against supplier and shop performance.
Key Takeaways
- 1How the Frozen Zone Works in LN Enterprise Planning: In LN Enterprise Planning, each plan item carries planning horizons and time fences defined in the item planning data. Inside the frozen period, the planning run treats existing planned and firm planned orders as fixed: it will not reschedule them earlier, change quantities, or cancel them, and by default it will not insert new planned orders inside the fence.
- 2Key Parameters: Time Fences, Horizons, and Order Status: Several settings interact to produce freeze behavior, and misconfiguring any one of them reintroduces schedule churn. The time fence on the plan item defines the frozen window in working days.
- 3When to Freeze and When to Unfreeze: Freeze length should roughly match your execution commitment window, not your comfort level. A machining plant with 5-day kitting cycles typically freezes 5 to 10 working days; an aerospace structures supplier with long-lead titanium may firm supply 12 weeks out but keep the automated frozen fence at 2 to 3 weeks.
Put this into numbers
Free interactive tools for exactly this problem. No signup to use them.
MRP Nervousness Assessment
A 10-question diagnostic that scores how badly your MRP plan churns between runs - and pinpoints which levers will stabilize it.
Free ToolBaan to Infor LN Migration Readiness Assessment
Score your organization's readiness to migrate from Baan IV or Baan V to Infor LN across ten dimensions, from data quality to executive sponsorship.
Free ToolInfor LN Multi-Site Rollout Planner
Model your Infor LN global rollout: enter sites, wave size, and complexity to get wave count, total timeline, program cost, and cost per site.
Ask Netray for a planning stability assessment that benchmarks your LN time fences and exception message volume against discrete manufacturing best practice.
Related Resources
Infor LN Warehouse Management: Setup and Optimization
Infor LN warehouse management setup guide: warehouse types, locations, inbound and outbound flows, handling units, and cycle counting optimization that cuts errors.
Infor LNInfor LN + ION Workflows: Automation Patterns
Infor LN and ION workflow automation patterns: BODs, ION Desk monitors, approval workflows, and API integration recipes that remove manual ERP busywork.
Infor LNInfor LN CPQ: Configure-Price-Quote for ETO Manufacturers
Infor LN CPQ guide for ETO and CTO manufacturers: product configurator integration, rules modeling, quote-to-order flow, and cutting quote cycles from weeks to days.