Path: <datacolumns><datacolumn>

Contains the definitions of one data column.

The columns appear in the input or report template in the order in which the <datacolumn> elements occur in the definitions file.

Attributes

id: Data column ID

Note! Predefined example settings are available for datacolumn in Input and Report Template management by selecting the Add Example option instead of Insert.

Path: <datacolumn><account_statement>

Defines whether the data column is used for the account statement function (drill-down). The setting is used on the drill-down template for entering values for internal inventories and internal transactions.

Possible values:

•true

•false (default)

Path: <datacolumn><headers>

Contains the settings of the data column headers.

Remember to add the required number of rows for all headers in the workbook. Note that definition column headers and data column headers are placed on the same row in the workbook, and the data columns headers are always placed above them.

Path: <datacolumn><headers><header>

Defines header text of the data column.

You can also use variables in the headers (for more information, see Input and Report Template Variables). The header text will then be retrieved based on the value of the <dimensionudid> element, not the option selected by the user in the user interface. For example, if the <header> value is %PERIOD NAME% and the <dimensionudid> value is 12, the header text will be 'December' regardless of the user's selection.

Attributes

language: Language identifier that defines the language of the header text. The column header is displayed on the input or report template according to the active language.

Note! If headers are defined in the XML definitions file, they override translations defined in the Excel file.

Possible values:

•Languages used in the system.

•%COLDIMnn CODE%: Displays the code of the unit used in the data column.

Path: <datacolumn><dimensions>

Contains settings for entering or retrieving data, for example, the data type, year, period, document series etc. The settings defined in the definition file override the options the user selects in the user interface (in the input and report template Basic Options view). If the definition for some option is missing from the definition file, the option selected by the user is applied.

When creating an input or report template, remember to take the dimension and data type connections into consideration. For more information, refer to Clausion Financial Performance Management Administrator's Guide.

This element is not mandatory in reports. If the element is missing, the options selected by the user in the user interface are applied, and data of all document series is retrieved. For input templates, this element is required because a specific document series must be specified for input templates.

Path: <datacolumn><dimensions><dimension>

Contains the settings for one option.

Attributes

type: Defines the type of the option

Possible values:

•datatype

•account

•finyr

•finper

•document

•documentseries

•position

•dim00 ... dim09

•codim00

•oid

•inputtype (for input templates; see also <dimensionudid>).

Not in use: datatypever, coaccount

Path: <datacolumn><dimensions><dimension><hierarchy>

Defines the dimension hierarchy for entering or retrieving data.

Possible values:

•Hierarchy ID: The units are generated according to this specific hierarchy.

•%DIMnn HIERARCHY%: The units are generated according to the hierarchy selected by the user in the input or report template options view.

Path: <datacolumn><dimensions><dimension><level>

Not in use.

Path: <datacolumn><dimensions><dimension><dimensionudids>

Contains the IDs of the option.

Path: <datacolumn><dimensions><dimension><dimensionudids><dimensionudid>

Defines one ID for the option.

Several IDs can be used for dimension type 'documentseries'. Note, however, that if a report contains a definition with several dimensionudids for several document series, the drill-down definition file cannot have specified dimensionudids.

You can also use variables as dimensionudid values (for more information, see Input and Report Template Variables).

Note! If document series are defined for a data column in the input or report template definition file, the document and document series options in the Advanced Options tab in the user interface do not apply.

Possible values:

•ID for the option, for example, '12' for dimension type finper.

•With dimension type Account only the accounts set in datacolumn settings are retrieved, thus gaining performance. Note that if any data column does not have accounts set, all accounts are technically retrieved from the database, even if only few are shown on the template.

•%parent_n%: Data is retrieved from n levels above the selected unit in the hierarchy. Note that if the hierarchy is set in column settings, it overrides user's hierarchy selection in the user interface. Note also that if the <hierarchyyear> parameter is in use, it determines the year of the hierarchy. This parameter can be used on input templates and reports for 'report' type columns (<datacolumn><datafield datasource=report>).

For <dimension type='inputtype'>, the following values are available for <dimensionudid>:

•manualentry (default): Data is entered manually to the column.

•autocalculation: Data is generated through automatic calculation to the column.

•calculated: Data is generated to automatic calculated accounts.

•NCI: Data is generated through non-controlling interest calculation.

•reconciliation: Data is generated through automatic reconciliation calculation.

Note the following exceptions:

•For dimension types documentseries and codim00, 0–n <dimensionudid> elements can be used.

•For dimension inputtype, multiple <dimensionudid> elements can be used for report type data columns. When more than one input type is defined, the sum of all input types is displayed in the report.