Budgeting and forecasting in Navita is done by using input forms. Budget and forecast values can be entered manually, but the input forms also enable automated calculations. Input forms are located under Data -> Input forms.

The layout of the input form can be altered by using the various controls in the toolbar.

RefreshUpdates the view after changes made by user
Transaction dataShows more detailed transaction information of selected cell such as account, period and user 
Break rulesFind break rule for selected cell function shows how the value in selected cell splits to accounts, business units and in time. Edit split rule for selected cell functions allows users to add new rules and make changes to existing rules.
Edit value and commentFunction to add comments to entered values and/or edit entered values
View Commented ValuesOpens a report of all commented values in new tab in the browser. Commented values can be filtered by various controls e.g. business units, accounts, data level, time an 
General optionsGeneral settings for the input layout
Collapse allCollapses all expanded hierarchies
Hide empty rowsHides all rows without any values
Columns visibilityControls the amount of columns shown on the input from. Columns visibility will be looked at more closely in the following section.
Reset to defaultReturns the input form to default settings
Add bookmarkSaves changes made to the layout, columns etc. Saved input forms are found in Shortcuts under Data -> Input forms.
Planning scenario gridFunctions in the planning scenario grid will be discussed in the following section.
Object gridControls the rows, business units and dimensions shown on the input form
Value set gridType, format mode, factor and data levels of values shown on each column are controlled in the planned value set grid. 

Column visibility settings

Columns visibility function allows the user to change the order and the number of columns on every input form. Following instructions show how to do that: 

1. Open the input form which requires changes

2. Once it is open, click Columns visibility on the input form and the following pop up will open.

3. Functionalities of each column will show up on the right side under actions when mouse pointer is hovered over the trigger area: 

4. Hidden columns are colored grey and italic on the above list

5. Clicking 'OK' will make the changes effective

6. To make the changes permanent, save the input form by clicking "Add bookmark" on the ribbon. Otherwise the old layout of input form will remain. 

Input form with added calculations

If the input form is attached to a planning scenario, it will be found under Data -> Input forms -> Shared. Planning scenarios enable automated calculations by using various Input codes. Below is an example of an input form which is attached to a Budget planning scenario. The input form also shows a separate column for rows which are calculated by input codes:

Adding input codes

Adding a new input code is possible to rows where it says "none" in the input code column. Double click the text "none" and the following drop down lists all the available input code types:

After the right input type is selected, a new window will open up where the parameters of the input code can be set. The different types of input codes will be covered more in detail in their own separate articles.

Another way to add an input code is by clicking 'New input code' in the planning scenario grid. Planning scenario settings such as beginning and ending of the scenario can be amended under 'Edit':

As mentioned earlier, input code can be added only to rows with text "none". In addition, Input code column may contain the following symbols:

 this symbol means that input code cannot no be added to the input code column. The row could be a total/subtotal of several other values. The account type of the row may also prevent the use of input code on account group level. In this case, the input code can only be added to account level.

This symbol means that input code already exists but it has been added to a lower level in the organization hierarchy. A row may only have one input code. The existing input code can be examined by drilling down in the organization hierarchy to the right level:


Above symbols indicate that an input code already exists but it has been added to a lower or higher level in the account structure. In the below example, the input code is on account group level preventing input codes to be added to lower levels:

Input code value entry

Most of the input codes require additional parameters for calculating the values. For example, growth percentage from previous year needs a percentage. These Input Code Values or IC Values are entered to their own data level either on 'IC Values' or 'IC or current values'.

Percentages are entered either on yearly columns or monthly columns, depending on the selected date mode of the planned values. In above example the selected date mode is year. 

Calculations and results

'Run' button in the Planning scenario grid will execute the actual calculation after the IC values have been entered. The results of the calculations can be examined by changing the data level back to the planned level(=budget). However, depending on the structure of the input form and visible columns, changing data level may not be necessary. Different data levels are explained below:

  • IC or current values: shows absolute values on rows which does not have input codes and IC values on rows which have input codes.
  • IC Values: shows only IC values.
  • Budget (planned) or Forecast (planned): show absolute values on all rows including the calculated results: