What's New in Lucanet Data Collection

Administrators can now control how data enters an editable column in pivot tables, CFP pivot tables, and dynamic tables. The new Entry method column option offers Manual & import — the default — Manual only, and Import only. Columns set to Manual only or Import only are marked with dedicated icons in the column header. Columns set to Import only are read-only during data collection. Columns set to Manual only cannot be selected in the column mapping step of Excel and Lucanet.Financial Warehouse imports, and CFP imports discard these columns from the import. After an import, a message lists any columns that were skipped because they are configured for manual entry only. Changes to the entry method apply only to new data collection processes.

Administrators can now limit which elements of the partner, transaction type, and adjustment level dimensions are available in drill downs. In the reporting package configuration, you select the elements of each drill down dimension in a searchable list with Select all and Deselect all actions; for partners, the additional In reporting package action selects exactly the partners that match the reporting entities in the package. The package-wide selection applies to all reporting entities, and you can configure a different selection for individual reporting entities. Collectors only see the selected elements, and import rows that contain excluded elements are rejected. Changes apply only to new data collection processes.

The intercompany validation results now display the rule description under the Details heading when you expand a rule — as in the results of regular validation rules. The description is displayed for every rule status. If a rule has no description, No description provided is displayed. The results display the description as it was when the validation was executed; changes to the rule appear only after the validation is executed again.

When a CFP pivot table is created, Data Collection records the structure of the source Consolidation & Financial Planning workspace. With the new Sync with CFP button in the detail view of a form template, administrators can now check an existing table for structural changes in CFP. The Select Rows to Include dialog is displayed; each changed element is marked with a colored label: Added for elements added in CFP, Deleted for elements that no longer exist in CFP, and Updated for elements whose name, superordinate element, or order has changed. A message at the top of the dialog summarizes the number of detected changes per type. You adjust the row selection directly in the dialog. Already collected data is preserved, and changes to the row selection apply only to new data collection processes.

In the intercompany validation results, you can now display the contact information of a counterparty's collectors. Click the phone book icon next to the counterparty name in the section header to open a dialog that lists each collector assigned to the counterparty in the reporting package, with their name and e-mail address. This way, you can follow up on an intercompany difference or missing data without leaving the application.

For details, see Entering, Validating, and Approving Data.

The results detail table now displays local accounts as expandable sub-rows. Where an item or account has a local account drill down, its local account sub-rows are displayed directly beneath the row, so you can see which local account causes an intercompany difference without returning to the form. Each sub-row displays the local account name and, depending on the configuration, the values in transaction currency, in reporting currency, or in both.

The intercompany validation results now identify counterparties that have not entered any data for a validation rule. The counterparty section header displays No data where the calculated difference normally appears, and the counterparty's rows are displayed with empty value columns. Your own values are displayed unchanged.

A counterparty is treated as having no data when it has not entered a value on any of the items or accounts in the validation rule definition. A validation rule only receives the status Passed when every counterparty has entered data on these items and accounts and the validation rule condition is met.

For details, see Entering, Validating, and Approving Data.

For intercompany validation rules that reconcile aggregated values in group currency, the results detail table now includes an Exchange rate column. Each row displays the numeric rate applied to convert the reporting entity's values to group currency. When the counterparties have different local currencies, each reporting entity's rows display the applicable rate. If a reporting entity's local currency is the same as the group currency, the column displays a rate of 1. For validation rules that reconcile aggregated values in transaction currency, the column is not displayed.

For details, see Entering, Validating, and Approving Data.