Configuration data versioning

The configuration data is specific to the cycle period process, and is versioned (locked) for the duration of the cycle period.

This table lists the configuration data and the point at which the data is versioned (locked):

These are the scenarios where the configuration data is versioned:

• Create: When a new cycle period is created, and the status of the Cycle is set to Pending.
  • Changes in the configuration prior to the creation of a cycle period are considered.
  • Process Calendar events are created (including associated workflows) and synchronized to the cycle period bucket dates at the specified Periodicity. In addition, notes can be created for the selected Cycle Period.
  • Changes made during the cycle period process are not considered, till the next cycle period is created.
• Start: When the cycle period is started, and the status of the Cycle is changed from Pending to Running.
  • Changes in the configuration prior to the starting of a cycle period are considered.
  • OLAP database elements are created using calendars, planning hierarchies, measures, and calculation rules.
  • Scenario Processes are started and workflows related to Scenario Processes are initiated.
  • Changes made after the cycle period status is set to Running are not considered, till the start of a new cycle period or the cycle period is Resumed with Refresh.
• *(Cycles Definition): Changes made to the cycle definition calendar between Create and Start are supported. If the cycle definition calendar is updated:
  • The current planning bucket (%FirstPeriod at calendar level to store scenario values), separates the cycle period process dates (current bucket) from the first planning bucket of the cycle period (%FirstPeriod).
  • This supports the changes made to the calendar when the cycle period status is set to Pending, since the calendar and the cycle period are not directly connected.
• **(Code lists used in Custom Calendars and Planning Hierarchies): The code lists that are attached to a planning hierarchy or custom calendar are versioned, since the parent object is versioned.
  Note: The code lists that are not attached to the cycle, or mapping code lists cannot be versioned.
• ***(Worksheets): Worksheets of a running cycle period use the latest configuration data. However, the worksheets are versioned after completion of the cycle period. This allows users to use the latest content for cycles that are in progress, and still have access to a completed cycle with different measures defined.

These configuration data are not versioned (locked) and use the latest definition available:

• Code Lists not linked to a planning hierarchy or custom calendar
• Data Security
• Data Sources
• Events and Searches
• Forecast Engine Settings
• History Replacement Engine Settings
• Interface Services
• Macros
• Mappings
• Roles and Permissions
• SCV configuration
• SCV datasheets
• Workflow definitions (ION)
• Worksheets*
  Note: Worksheets of a running cycle period use the latest configuration data. However, the worksheets are versioned after the completion of the cycle period. This allows users to use the latest content for cycles that are in progress, and still have access to a completed cycle with different measures defined.