All Steps at a Glance - Importing Data into Reporting Entities

Last updated on 2025-06-23

Overview

Before the import into Lucanet.Financial Warehouse is performed, the objects required for this must be created and configured based on their data source(s). Because the objects are built upon each other and interconnected, we recommend following the sequence of steps outlined. 

Preliminary Considerations

Before configuring the import and creating objects in Lucanet, consider and define the following:

  • Are the technical conditions for the data import met?
  • Do two databases and a technical user with read and write permission exist for these databases?
  • Is Lucanet.Financial Warehouse already set up?
  • Is SEA required? If so, has SEA already been installed? (see Installing and Using Lucanet.Script Execution Application.)

SEA (Lucanet Script Execution Application) is a Lucanet application that is required when ERP/financial source systems are operated on-premises and data from these systems needs to be imported into the Lucanet CFO Solution Platform via script.

  • What are the content requirements?
  • Are there one or more source system(s)?
  • Per source system:
    • Is there a script used to connect the source system?
    • Which transformations need to be performed for the data when writing to Lucanet.Financial Warehouse?
    • For which elements of the Lucanet data model (data levels, reporting entities, etc.) are the transformed data to be prepared?

Uploading Scripts

Using scripts, data from various source systems can be read, changed, optionally augmented, and imported into Lucanet Financial Warehouse.

Load scripts into the Scripts workspace (see Scripts).

Defining a Data Source

In order to import data from an source system, the source of the data must be defined. To do so, a data source used to import an Excel file must be created in the tree view of the workspace Importing data into Lucanet.Financial Warehouse.

Create a data source and configure the data source (see Defining Data Sources).

Defining Data Transformation(s) (Optional)

Transformation rules in data transformations are optional. Transformation rules determine how the data from the source system are to be transformed before they are written to Lucanet.Financial Warehouse.

If necessary, create at least one data transformation (see Creating and Configuring Data Transformations).

Defining Execution Settings

For which elements of the Lucanet data model (data levels, adjustment levels, reporting entities, fiscal years, and accounting periods) the data are to be imported is specified for a selected data source in the execution settings.

Define execution settings (see Creating and Configuring Execution Settings).

Creating and Executing the Data Import

The import is started with the Execute function in the detail view of execution settings or folders.

Import the data (see Executing the Data Import).

Editing Period Locks (Optional)

The data import can only take place if the import of data into the desired reporting entities for the desired period is allowed. If periods into which you want to import data are locked, you will not be able import the data. You will then have to unlock the desired periods in the Period locks workspace.

If necessary, edit the period locks (see Period Locks).