Come and explore the exciting new features of our solution Lucanet Data Collection! We update our CFO Solution Platform on a regular basis to offer you the latest features and improvements.
The versions of all solutions that you are currently using and those of the CFO Solution Platform are displayed when you select About Lucanet from the Help section in the CFO Solution Platform.
In Lucanet Data Collection, a variable of a regular validation rule can now refer to a single drill down element instead of the aggregated value. This applies to row and column drill downs with the dimensions Partner, Transaction type, and Adjustment level. For example, a rule can check that the partner 000 Default on intercompany accounts equals zero. If the row or column of the variable has a drill down for one of these dimensions, the context menu of the variable contains the options for selecting, changing, and removing the drill down element. For other variables, the context menu does not contain these options. Without a drill down element, the variable refers to the aggregated value.
Context menu of a variable with the 'Select drill down' option
When Data Collection executes the rule, the variable uses the value of the selected element in the form of the reporting entity. If the form contains no row for the element, the variable resolves to zero. If the element is not available in the reporting package, the validation results display the rule as Not evaluated. The validation results display the selected element as part of the variable path.
If an administrator removes the drill down dimension from the row or column in the form template, the rule moves to Invalid status. Intercompany validation rules do not support drill down elements.
In Lucanet Data Collection, the import from Consolidation & Financial Planning (CFP) now replaces each imported column of a form in full. For each lowest-level cell of an imported column, the import writes the value from CFP. If CFP returns no value for a cell, the import clears the cell. Previously, existing values remained in cells without a CFP value.
Columns with the period value type N/A, total columns, and formula columns keep their content. If a value moves from one partner to another in CFP, the next import clears the row of the previous partner and fills the row of the new partner.
The import from Consolidation & Financial Planning (CFP) now also transfers data into CFP pivot tables with drill down. This applies to row drill downs, column drill downs, and tables with both, and to all five dimensions Local account, Partner, Cost center, Transaction type, and Adjustment level. Previously, the import wrote only the aggregate value to the cell, and tables with Local account drill down were excluded from the import.
For a row drill down, the import creates one subordinate row per element that has a value in CFP. With several levels, the import nests the rows in the level order of the form template. For a column drill down, the drill down dialog displays at each level only the elements that exist in CFP beneath the selected element. If a table has both, the import writes each value to the intersection of the row element and the column element.
Superordinate rows, totals, and the pivot table cell display the sum of the imported values. Only the lowest configured level is editable. If the drill down already contains data, the import first displays a confirmation dialog. Collectors can still add elements manually after the import.
CFP pivot table with drill down rows created by the CFP import
Collectors and administrators can now export a form in status In Progress, Submitted, or Approved to an Excel workbook. To do so, select More actions | Export to Excel in the form header. Data Collection generates the workbook, and your browser downloads the file. The file name combines the names of the form template and the reporting entity with the period. The export is not available while a data import is in progress for the form.
The workbook contains one sheet per table, named after the section and the table. Each sheet contains all rows and columns of the table with the labels displayed in Data Collection, including superordinate rows, total rows, formula columns, and read-only columns. The sheet lists drill down rows at all levels beneath their superordinate row. The sheet of a section also lists the values of form elements that are not tables.
Formula columns contain the calculated values, i.e. not Excel formulas. Empty cells remain empty.
Administrators can now configure a drill down at row level and at column level in the same CFP pivot table. Each of the dimensions Local account, Cost center, Partner, Transaction type, and Adjustment level can be used on only one of the two axes; dimensions already used on the other axis are disabled in the Configure Drill Down dialog. The number of drill down levels per axis is limited only by the number of dimensions not used on the other axis. If you configure a row drill down on a row with subordinate rows, the configuration applies to all subordinate rows at every level, including rows added later. For the Partner dimension, the new Require transaction currency details option in this dialog determines whether collectors must enter transaction currency details for each partner.
'Configure Row Drill Down' dialog with the 'Require transaction currency details' option
During data collection, row drill down elements are displayed as subordinate rows directly in the table. Collectors add elements with the Add button at each level and enter values directly in the cell. If a column drill down is also configured for the column, collectors enter the values in the drill down dialog, which displays the full path from the table to the column. For partners with required transaction currency details, collectors click the arrow icon on the partner row to open a transaction table in which they record one or more transactions per partner; the cell displays their sum.
Transaction table for a partner row in the drill down dialog
In the column mapping of an Excel import, you can now map the same Excel column to a column in more than one table of the form. Within a single table, each Excel column can still be mapped only once. After the mapping, Data Collection no longer offers the column for that table but keeps it available for all other tables. If you remove a mapping, the column becomes available again for that table. The import writes the value of the Excel column to every mapped target column. Previously, the column had to be duplicated in the Excel file to supply several tables.
