Forecast Integration¶
The Forecast integration imports forecast data from your ERP or customer system into Knosc automatically on a scheduled basis. It can also be triggered manually from the Forecasts screen.
Triggering the Integration¶
The integration runs on an automated schedule configured per instance. To run it immediately, click Run Integration in the Forecasts toolbar.
Unique Line Identification¶
Forecast lines are identified uniquely by a composite key:
This key is used to determine whether an incoming line should be created, updated, or archived.
Upsert Logic¶
On each integration run:
| Scenario | Action |
|---|---|
| Line exists in new data and in Knosc | Update quantities, dates, and relevant fields |
| Line exists in new data but not in Knosc | Add as a new forecast line |
| Line exists in Knosc but not in new data | Archive the line (removed from current forecast) |
The archive captures the full history of forecast changes over time, enabling forecast accuracy analysis via Forecast Over Time and Forecast vs Sales.
Commit vs Planned Lines¶
Forecast integrations commonly distinguish between two line types:
| Type | Meaning |
|---|---|
| Firm | Confirmed demand - will convert to a sales order |
| Planned | Long-term estimate - guides planning but not committed |
The handling of each type is configurable per integration setup.
Unit of Measure Conversion¶
If forecast lines arrive in mixed units of measure, the system automatically converts quantities to the standard planning unit using the Unit Master.
External Item Mapping¶
If the source system uses customer-specific item numbers, the External Items table is used to map external item identifiers to internal item numbers.