You create Forecaster modules and views to store source data, insights and results.
Module best practices
As you build source modules:
- It's a best practice to save a view for each source module (see Saved views for details).
- Forecaster requires views for the source modules, though they can be the default view.
- Use easily recognizable names for your saved views, as you might have to choose from a long list of views. Examples:
Historical data last 18 months(good view name)New data view(a name that's difficult to recall and identify later)
Maximum supported data
Forecaster supports up to 100,000 unique items. If you have a large data set, consider data tranches (chunks of smaller data). Forecaster also supports 1,095 time periods. For example: daily data might be 1,095 divided by 365 days equals a maximum of three 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. |
Create a historical data module
Create a related data module
Create an attributes module
Create data insights modules
Create a forecast results module
Create an explainability results module