# SyteLine forecasting, planning horizon and planning calendar

> Source: https://netray.co/erp-help/syteline-advanced-forecasting-planning-horizon-and-mrp
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

SyteLine MRP and APS plan against demand (customer orders plus forecast) over a planning horizon, using a calendar of working days. Forecast quality, how forecast is consumed by orders, and the horizon length drive most planning results. Exact parameter names and forms vary by release, so confirm against your documentation.

## Kind

how-to

## System

syteline

## Erp

Infor SyteLine (CloudSuite Industrial)

## Module

Planning / Forecast and MRP

## Query

syteline advanced forecasting

## Alternate Queries

- syteline planning horizon calendar
- syteline mrp system
- SyteLine forecast MRP setup

## Applies To

SyteLine 9.x and CloudSuite Industrial 10.x (MRP and APS)

## Steps

### Configure forecast-driven planning

**Items:**

- Decide which items are forecast-driven (make-to-stock, long lead time) and which are order-driven.
- Enter or import a forecast for those items by period, based on history and sales input, and review it each cycle.
- Set how forecast and actual orders interact so orders consume forecast instead of adding to it.
- Set the planning horizon long enough to cover the longest cumulative lead time of your products, plus buffer.
- Confirm the planning calendar reflects real working days, holidays and shutdowns, since lead times are converted through it.
- Set time fences and lot sizing on items so near-term plans are stable.
- Run MRP in a test site and review planned orders against expectations for a sample of items.
- Review exceptions weekly and adjust forecast, safety stock or lead times based on what you learn.

## Sections

### How forecast enters the plan

**Body:**

MRP combines firm demand from customer orders with forecast demand and nets both against inventory and supply. Without consumption logic, forecast and orders double count and inflate planned supply. The key is the rule that actual orders reduce the forecast in the same period or window.

Forecasts only help where they are better than nothing. For erratic or project items, forecasting adds noise, and planning from orders and safety stock is the honest approach.

### Planning horizon and time fences

**Body:**

The horizon is how far ahead the plan looks. If it is shorter than your cumulative lead time, MRP cannot see far enough to order long-lead purchased parts in time. If it is far too long, runs get slow and the distant plan is meaningless.

Time fences protect the near term. Inside the fence, the system does not reschedule or create new orders automatically, so planners decide manually. Set fences based on how long it takes to change production.

### The planning calendar

**Body:**

Lead times in working days are converted to dates using the calendar. A calendar with wrong holidays shifts every due date, and a calendar that ends before the horizon can stop the plan or produce errors. Extend the calendar each year before it runs out.

With APS, the work center calendars also govern capacity, so keep them aligned with the planning calendar.

## Pitfalls

- Forecast and orders double counted because consumption is not set up.
- A horizon shorter than cumulative lead time.
- Calendar not extended into the next year.
- Forecasting every item including erratic ones.
- Never reviewing planning exceptions, so errors persist.

## Ai Angle

An assistant over SyteLine data can compare forecast to actual demand by item, highlight items where forecast error is large, check horizon and calendar coverage, and explain why a planned order exists using the demand and supply behind it. It does not change forecasts on its own; planners approve changes.

## Faq

### How does SyteLine MRP use a forecast?

**Answer:** It treats forecast as additional demand over the planning horizon, nets it against inventory and supply, and, with consumption configured, reduces forecast as actual orders arrive. Without that rule you can overplan.

### How long should the planning horizon be?

**Answer:** At least the longest cumulative lead time of your products, plus a buffer for order cycles. Longer slows the runs without much benefit; shorter misses long-lead purchases.

### Why are my planned dates off by days?

**Answer:** Check the planning calendar for incorrect holidays or missing working days, and item lead times. Dates are computed from working days, so calendar errors shift everything.

### Do I need APS for forecasting?

**Answer:** No. Standard MRP handles forecast-driven planning. APS adds finite capacity scheduling, which matters when capacity constraints drive delivery performance.

## Search terms

syteline advanced forecasting, syteline planning horizon, syteline planning calendar, syteline mrp system, syteline forecast consumption, csi mrp parameters, syteline time fence, syteline demand planning

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