What Is Forecast Driven Replenishment?
First Introduced in NCR Counterpoint version 8.3.9, the Forecast Driven Replenishment feature was designed as a tool to select historical trend data for the purposes of forecasting future purchases. This forecasting feature can be used to create "What If" scenario reports based on historical data, and to then to actually generate physical Purchase Requests from that data.
The "Forecast Driven Replenishment" Feature uses predefined database Stored Procedures to collect specific data from Data Mart tables. By design and by default, when NCR Counterpoint is installed, these tables are not populated with any data. In order to use this feature it requires that the Data Aggregation feature is turned on, and scheduled.
The following sub-tasks settings are required for each feature that relies on aggregated data:
- The "Dashboard" feature requires all sub-tasks with Aggregation ID values of 1 through 7 to be on.
- "Forecast-driven Replenishment" feature requires all sub-tasks with Aggregation ID values of 9 through 15 to be on.
- The "Point of Sale Exceptions Report" feature requires all sub-tasks with Aggregation ID values of 16 through 21 to be on.
You can find additional details on this topic by doing a search in the general NCR Counterpoint help index using the keyword Forecast. This will show you details of the feature design, and some examples of it’s use.
As the documentation details… turning this feature on may cause a resource load drain on your server. So if you decide to turn the Data Aggregation feature on, CCS would recommend that you schedule this to run only in off hours when users are off the system, and when there are no backups or active file utilities being run on the database.
Depending on how much detailed data that you need, this might take some time quite some time to catch-up to the current date once data aggregation is turned on.
If you need assistance with setting-up Data Aggregation the CCS Retail Systems Support Department.
– John