
The default key date is a key date that is used in the entire planning model. You can specify a default key date for every real-time InfoCube or every DataStore object for direct updates in planning mode.
The following options are available for setting a key date:
Unspecified (default value is the system date, if all of the involved InfoProviders have the key date = unspecified).
Fixed Date
From Variable
All objects that depend on the key date - such as the filter, hierarchies used in the filter or hierarchies used in the 'from' and 'to' values of the copy/distribute functions - can be set to the default key date.
When a planning function is executed, the system calculates the default key date as follows:
If the aggregation level is created directly on a planning-relevant InfoProvider, the default key date is the same key date that is set for this InfoProvider.
If the aggregation level has been created on a MultiProvider, all the involved planning-relevant InfoProviders below the MultiProvider are checked. If all these InfoCubes have the setting unspecified, the default key date is the current system date. If one of the planning-relevant InfoProviders has a different setting for its key date, the first InfoCube that returns a specific value is the 'winner'. Variables are evaluated when they are returned.
You also have the option of using a different key date with every time-dependent object.
This can be useful in certain situations. For example: You want to use a specific hierarchy that is to be read with another key date than the master data attributes.
For more information on setting the planning key date, see Central Settings.