Create Forecaster modules and views to store source data, insights and results.
Module best practices
To build source modules:
- Forecaster requires views for the source modules. It can be a custom view that you create, or the default view.
- Use easily recognizable names for your saved views. This enables you to find them further on in the forecast process. Example:
Historical data last 18 months. - Only include line items that you need results for.
If a line item isn't included in the module or saved view, the forecast action does run. But the results for those line items aren't produced.
Maximum supported data
Forecaster supports:
- Up to 100,000 unique items.
If you have a large data set, consider chunks of smaller data. - Up to 1,095 time periods.
For example:
1,095 days ÷ 365 days = a max of 3 years
Module guidelines
The table below lists the Forecaster modules, and whether they're compulsory, source, or output modules. Modules appear in the order they must be created.
| Modules | Required / Optional | Details / Purpose |
| Historical data (source) | Required | Historical values for the target time series. |
| Related data (source) | Optional | Recommended if related data is available. |
| Attributes (source) | Optional | Recommended if attribute data is available. |
| Time and item-level insights (output) | Optional | For a detailed view of data insights with a time stamp. |
| Item-level insights (output) | Optional | For a detailed view of data insights. |
| Forecast results (output) | Required | Backtest and future values for the target time series. |
| Explainability results (output) | Optional | To view explainability data within Anaplan. |