SyteLine forecasting, planning horizon and planning calendar
syteline advanced forecasting
Also searched as
- syteline planning horizon calendar
- syteline mrp system
- SyteLine forecast MRP setup
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.
Applies to: SyteLine 9.x and CloudSuite Industrial 10.x (MRP and APS)
Configure forecast-driven planning
- 1Decide which items are forecast-driven (make-to-stock, long lead time) and which are order-driven.
- 2Enter or import a forecast for those items by period, based on history and sales input, and review it each cycle.
- 3Set how forecast and actual orders interact so orders consume forecast instead of adding to it.
- 4Set the planning horizon long enough to cover the longest cumulative lead time of your products, plus buffer.
- 5Confirm the planning calendar reflects real working days, holidays and shutdowns, since lead times are converted through it.
- 6Set time fences and lot sizing on items so near-term plans are stable.
- 7Run MRP in a test site and review planned orders against expectations for a sample of items.
- 8Review exceptions weekly and adjust forecast, safety stock or lead times based on what you learn.
How forecast enters the plan
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
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
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.
Try it here, free
MRP Planning Time Fence Calculator
Derive a demand time fence and planning time fence from your lead times and see how much of the horizon is frozen.
Common 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.
How an ERP-grounded AI assistant handles this
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.
Frequently asked questions
How does SyteLine MRP use a forecast?
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?
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?
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?
No. Standard MRP handles forecast-driven planning. APS adds finite capacity scheduling, which matters when capacity constraints drive delivery performance.
Related
How to Run MRP in SyteLine
MRP in SyteLine runs from Planning > MRP Processing as either a full Regenerative run or a Net Change run against demand from customer orders, forecasts, and safety stock; results appear as planned orders and Action Messages in the Planner Workbench.
How-toHow to Use the MRP Planner Workbench in SyteLine
After MRP or APS generates planned orders and exception messages, a planner reviews them item by item in the planner workbench, then firms, changes or releases them into job orders, purchase requisitions or transfer orders. The skill is reading the messages in the right order and releasing only what is real demand.
Error fixTroubleshooting SyteLine MRP and APS regeneration that fails or hangs
A SyteLine MRP or APS run that fails to complete, hangs indefinitely, or errors partway through is most often caused by data integrity problems (a BOM loop, an item with an invalid lead time or missing routing), a scheduling engine (APS) process that is stuck or resource-starved, or a concurrent MRP run conflict. Check the MRP/APS log first for the specific item or job it stopped on before assuming it is a system capacity issue.
AdvancedHow to Tune APS Finite Scheduling Performance in SyteLine
A slow APS run in SyteLine is almost always caused by an oversized planning horizon, too many resources marked as constrained, or an unindexed staging table, rather than the scheduling algorithm itself. Trimming the horizon, scoping constrained resource groups, and running incremental instead of full regenerative schedules typically cuts run time dramatically.
Error fixFixing SyteLine's 'Object reference not set to an instance of an object' error
This is a generic .NET NullReferenceException surfacing through the SyteLine IDO Runtime, not a SyteLine-specific error code. It almost always means a form, script or IDO method referenced a field, row or object that came back null, usually after a customization, a missing related record, or a view/IDO method call before the form finished loading. Turn on detailed client logging and check the most recent customization or form event first.
Error fixDiagnosing and fixing SyteLine session timeout errors
SyteLine session timeouts come from one of three independent layers: the IDO Data Service session timeout on the app server, the IIS/application pool idle timeout for the web (Mongoose Web) client, or a load balancer/proxy idle timeout in front of a CloudSuite hosted environment. Fixing the wrong layer is the most common mistake - you need to identify which layer is actually expiring the session before changing anything.
AI for ERPAI for Infor SyteLine and CloudSuite Industrial
Add grounded AI to Infor SyteLine or CloudSuite Industrial: natural-language answers, agents over IDOs and ION, on-prem or CloudSuite deployment.
AI for ERPAI on Infor SyteLine for Industrial Machinery Makers: Configured Orders, Projects and Service Parts
AI on Infor SyteLine for industrial machinery manufacturers: configure-to-order BOMs, project cost, spare parts and warranty, private and read-only by default.
Stuck on Infor SyteLine (CloudSuite Industrial)?
Talk to engineers who work inside Infor SyteLine (CloudSuite Industrial) every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- MRP Planning Time Fence CalculatorDerive a demand time fence and planning time fence from your lead times and see how much of the horizon is frozen.
- SyteLine Database Growth Forecast CalculatorProject database size, backup storage and the effect of archiving for a SyteLine SQL Server database over a planning horizon.
- SyteLine MRP vs APS AssessmentAnswer ten questions about capacity, routing complexity and planning cadence to see whether SyteLine MRP is enough or an APS tool is worth evaluating.
ERP fixes and how-tos
- How to Tune APS Finite Scheduling Performance in SyteLineWhy SyteLine APS finite scheduling runs slow and how to fix it: planning horizon, constrained resources, incremental vs regenerative runs, SQL tuning.
- Troubleshooting SyteLine MRP and APS regeneration that fails or hangsSyteLine MRP or APS regeneration runs that hang, time out, or fail usually trace to bad BOM/routing data, a locked scheduling engine process, or insufficient app server resources. Here is the diagnostic order.
- SyteLine APS error 30012: what to check before rerunningTroubleshoot SyteLine APS error 30012: check the APS service, data sync between SyteLine and APS, then rerun the schedule. A tested order of checks.
Guides
- Demand Forecasting Configuration in Infor SyteLineConfigure SyteLine demand forecasting with statistical models, forecast consumption, demand management parameters, and accuracy measurement for production planning.
- How to Set Up Planning Parameters in Infor SyteLineStep-by-step guide to setting up planning parameters in Infor SyteLine. Configure MRP settings, planning horizons, time fences, and demand management policies.
- AI Demand Forecasting Inside Your ERP: Better Numbers Into MRPAI demand forecasting in ERP: machine learning models that cut forecast error 20-40% and feed MRP in SyteLine, Infor LN, and M3 with planner-ready numbers.
AI on your ERP
- AI Demand Forecasting for Manufacturers: Better Numbers and an Explanation Planners Can TrustAI demand forecasting explains ERP forecast changes in plain language, flags exceptions for planners, and handles short-history SKUs without Excel overrides.
- AI for SyteLine Production Planning and Scheduling (MRP and APS)AI for SyteLine production planning and scheduling: explain late jobs, find constraint work centers, review MRP output and APS results in plain English, privately.