Using a rolling scenarioIf a scenario is defined as a rolling scenario in the Scenarios (cprpd4100m000) session, LN regularly shifts the entire scenario a particular interval forward in time. Diagram The following diagram illustrates the rolling procedure. In this example, the rolling frequency is 7 days.
How to roll a scenario Use the Initialize, Roll, and Update Scenario (cprpd4200m000) session to roll a scenario. If you select a scenario that needs to be rolled, LN automatically performs a full update for that scenario:
If a multicompany scenario is rolled, LN also rolls all local scenarios that belong to the multicompany scenario. To determine if the specified scenario must be rolled, the difference between the current date and the Reference Date field date is taken and rounded down to an integer. A scenario needs to be rolled if the current date is greater than the reference date plus the rolling frequency. Example The difference is 5.8 days and the rolling frequency is 6 days. If the difference between the current date and the reference date is 5.8 days, LN will round down to 5 days and the scenario will not be rolled. Once the scenario is rolled, the date in the Reference Date field in the Scenarios (cprpd4100m000) session is adjusted by adding the number of the days specified by the rolling frequency to the old reference date, the time specified is preserved. Example If the reference date is 04-11-2010 08:29 and the rolling frequency is 5 days, the new reference date will be 09-11-2010 8:29. The Scenario Start/Finish Date fields are updates as well. This update affects the plan-period dates. These are updated in all item master plans and channel master plans present in the scenario. Because plan periods can be of unequal length, a special procedure is needed to redistribute the master-plan data over the new plan periods
Note When a scenario is rolled, the time is not adjusted when the new reference date is saved.The default time of 00:00:00 is maintained.
| |||||||||||