What's New in Lucanet Data Collection

Administrators can now add formula columns and formula rows to pivot tables and CFP pivot tables.

When a table contains both formula rows and formula columns, you can set a Formula precedence on the element to control which result is displayed in cells at their intersection.

For details, see Configuring Tables in Form Templates.

CFP Pivot tables based on Schedule workspaces now automatically include Value query columns. Value query is a transaction type specific to a Schedule in CFP. These columns are read-only for collectors, can be used as operands in total and formula columns, and are included in CFP imports. They are excluded from Excel and Lucanet.Financial Warehouse imports.

Transaction type and adjustment level are now available as drill-down dimensions for both rows and columns in pivot table and CFP pivot table elements. Together with local account, cost center, and partner, all five CFP dimensions can now be configured as drill-down dimensions.

For details, see Configuring Tables in Form Templates.

Administrators can now add optional instructions to a form template using a rich text editor in the detail view of a form template. The instructions are copied to each form when a data collection process starts. Collectors access the instructions via the Show instructions button in the form header, which opens a dialog displaying the instruction text.

For details, see Creating and Configuring Form Templates.

Intercompany validation rules now support optional tolerance thresholds per currency. You can configure an Absolute threshold, a Percentage threshold, or both. When both are set, the rule passes if the difference falls within either threshold.

The intercompany validation results now distinguish four statuses:

The calculated difference is always shown in the results, even when the result is Passed.

For details, see Creating and Configuring Validation Rules.

Regular validation rules that reference more than one form template are now only executed if all referenced form templates are included in the reporting package. Rules that reference one or more templates that are not in the reporting package are skipped and do not appear in the validation results. No administrator configuration is required.

For details, see Creating and Configuring Validation Rules.

When a form is open, you can now navigate directly to another form for the same reporting entity without returning to the data collection list. Click the form template name in the navigation path at the top of the screen to open a drop-down menu listing all form templates you are authorized to access for the current entity within the current process. The drop-down menu displays each form's name and current status.

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

Data collection administrators can now reopen a form that has been approved. Reopening transitions the form back to In Progress, notifies the collector, and allows corrections to be made through the normal editing and approval process. Other forms in the same reporting package are not affected.

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

Data Collection now supports exporting postings directly to Consolidation & Financial Planning. Administrators mark one or more currency columns per CFP Pivot table as Used for postings in the form template. CFP then retrieves and imports the postings via the existing workflow for a data source of type Provision via script using the dedicated Import from DC script.

For the Data Collection-side configuration, see Configuring Tables in Form Templates. For the CFP import workflow, see Importing Data Collection Postings into CFP.

A new element type, Dynamic table, lets data collectors add, duplicate, and remove rows themselves during data collection, up to a maximum that Data Collection administrators configure. This is useful for variable-length data — for example, fixed asset lists, intercompany loan schedules, or provision schedules — where the number of rows differs from one reporting entity to another.

Data Collection administrators define the column structure once in the form template, and each data collector enters as many rows as they need during data collection.

For details on configuring Dynamic tables, see Creating and Configuring Form Templates. For the collector workflow, see Entering, Validating, and Approving Data.

You can now duplicate any element directly from the detail view of a form template. The duplicate inherits the configuration, mappings, required-field status, and all language labels of the original, so you do not have to rebuild similar elements from scratch.

You can now change the display order of rows and columns in a Pivot table or CFP Pivot table by drag-and-drop. Rows can also be moved under a different superordinate row to restructure the hierarchy. Collected data, drill-down configurations, and aggregations are not affected by reordering — values stay bound to their row and column identifiers.

When you add a CFP Pivot table element, you can now choose which rows to include from the source Consolidation & Financial Planning workspace before the table is created, instead of pulling all eligible rows in automatically. Three selection modes are available — Select all, Show items only, and Custom selection — and the original hierarchy is preserved in the resulting table.

You can now group validation rules by category using free-form tags, then filter the rules list by one or more tags. Tags apply equally to Regular and Intercompany validation rules and have no effect on rule logic or execution.

Tags can be assigned to a single rule directly in the rule's configuration, or to several rules at once from the validation rules list using the new Assign tags and Remove tags bulk actions.

When configuring a Regular validation rule, you can now reference superordinate rows directly, not just the lowest-level rows. The rule uses the aggregated value of the superordinate row — the same value displayed for it in the form. This makes it easier to write rules that compare subtotals without listing each subordinate row individually.

The Select items and/or accounts drop-down list in the Intercompany rule configuration now hides form templates and pivot tables that have no partner-related configuration, so only elements that are actually eligible for intercompany validation appear.

In the same drop-down, you can now select a superordinate row to automatically include all of its eligible subordinate rows.

The Data Collection list now shows the result of the last intercompany validation execution in a dedicated IC Validation result column, separate from the existing Validation results column. Process-level and form-level rows show the IC status; entity-level rows are empty. Point at an indicator to see the exact error and warning counts.