Scenario start and finish date

To define the scenario 's start date and finish date, use the Scenario Start Date and Scenario Finish Date fields in the Scenarios (cprpd4100m000) session.

The length of time between a scenario's start date and finish date affects the system performance if you roll the scenario. The rolling process recalculates all master-plan data from plan periods to separate days; then, the rolling process recalculates the data from days to plan periods.

The recalculation process also includes open orders with a start date before the start date of the scenario. The orders between the start date and the current date form the history of the master plan. To check what has happened in the previous periods, use this historic data. However, a longer history reduces the system performance of the planning process.

The goods flow before the scenario's start date is aggregated to one transaction at the scenario start date. Before the scenario's start date, no pegging information is available, because all transactions before the scenario's start date are anonymous.

Recommendations:

  • Do not make the period between the scenario's start date and finish date too long.
  • Do not set the scenario's start date too far before the current date.
Performance aspects
  • Effect on CPU: Yes
  • Effect on database growth: Not applicable