Planning Versions
- [Object Versions] Managing multiple versions of attributes attached to object values
- [Time Units] Maintaining the time dimension of data
Planning versions define the version dimension of data in Bizview. Examples of planning versions can be ‘Budget 2017’, ‘Q1 Forecast’, ‘Q2 Forecast’, etc. The ‘Version ID’ is normally used in (Template Designer) when designing input forms on the ‘VERSION’ row.
Access Planning Versions by selecting Client administration > Other Items > Planning Versions.
To create a new planning version click the New button. Enter information according to the table below and select Save.
Below is a list of Planning Version fields:
Field | Description | Example | Note |
|---|---|---|---|
Version ID | The unique identifier of the planning version. | F1 | |
Description | The description of the planning version. | Forecast Q1 | |
Default access code | Determines if the planning version be available for Read, Read/Write, or none. | ||
Default Object Version ID | The default object version used when selecting the planning version in a selection pane. | ||
Open for entry from.. to | From and To dates when the planning version is open to the user for entering data. | 201310 - 201403 | The calendar dates between which the user can actually open an input FORM and enter and save values for the version. |
Valid from to | From and To dates for which the Input Form periods can be set. | 201401 - 201412 | The columns in the input planning FORM can only contain TIMEVAL inside this interval. |
Active | Determines if the planning version active or not. | If the planning version is "Inactive", the user can not enter and save values for that version. | |
Additional Version properties 1-3 | Extra free text attributes for the planning version. | Sometime used to indicate the ‘current year’ the planning version is used for. |
Additional Information
The ‘ACT’ Version ID is a reserved word in Bizview for actual data. It’s used in Datastore for all actual data loaded.
When defining Planning Versions, you should consider if the planning version should be ‘hard’ associated with the time-dimension. For example, you can create one ‘BUDGET’ planning version and use this version each year in combination with appropriate [time units] to save budget data for period 2016, 2017, etc. But you could, instead, create a separate planning version such as ‘BUDGET2016’, ‘BUDGET2017’ and include some kind of reference to time in the definition of the planning version. Both alternatives have pros and cons.
Copy Version
Use the function ‘Copy Version’ (link in the top of the Planning Versions window) to copy planning data from one version to another version. The data will be copied as-is from one version to another at the time the copy procedure is executed. This also implies that data stored on a particular month in the source version will be attached to the same period in the target version.
Select the source version (From version) from which you want to copy the planning data.
Select the To version to select the version you want to copy your data.
You can limit the number of periods you want to copy by using the ‘From’ and ‘To’ period selection drop-downs.
On the right side of the screen you will see how many records of planning data that will be copied (‘Records’), and how many currency rates records that will be copied (‘Curr Rates’).
Click the ‘Copy’ button to execute the copy procedure.
The field 'Adjust' is used to make Bizview automatically convert the dates of the data to be copied, according to the time unit adjustment you provide.
For example, ISOMONTH 201401 .. 201412 Adjust 12, will copy all values from 201401 to 201412 and adjust them to be 201501 .. 201512
Caution: Before you execute the copy operation, make sure that you have selected the correct target version. Any existing planning data in the target version will be deleted before the data is copied from the source version. The deleted data cannot be recovered.