---
title: "All Steps at a Glance"
description: "Before the import into reporting entities is performed, the objects required for this must be created and configured based on their data source(s). The required objects can be created in any order. However, because the objects are built upon each other and interconnected, we recommend following the sequence of steps outlined."
source_url: https://support.lucanet.cloud/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/all-steps-data-import-reporting-entities
language: en
last_updated: 2023-08-16
---
# All Steps at a Glance - Importing Data into Reporting Entities

## Overview

Before the import into reporting entities is performed, the objects required for this must be created and configured based on their data source(s). The required objects can be created in any order. However, because the objects are built upon each other and interconnected, we recommend following the sequence of steps outlined.

{% process-steps %}
{% process-step title="Preliminary Considerations" %}
**Before** configuring the import and creating objects in Lucanet, consider and define the following:

- Which data are to be imported?
- From which Excel file are the data to be derived?
- Has the Excel file already been filled with values?
- Which elements of the Lucanet data model (data levels, reporting entities, etc.) are to be filled with the data?
{% /process-step %}
{% process-step title="Creating an Assignment Table" %}
**Assignment tables** are used to save all elements imported from the source systems (accounts, reporting entities and cost centers, partners, transaction currency, transaction types, data levels, adjustment levels) and their assignment to elements in the **Lucanet database**. Assignments are defined during the data import and can then be changed or deleted **at any time**.

If necessary, create an assignment table (see chapter [Creating an Assignment Table](https://support.lucanet.cloud/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/creating-assignment-table.md)).
{% /process-step %}
{% process-step title="Defining and Configuring Data Sources" %}
In order to import data from an source system, thesource of the data must be defined. For this purpose, a **data source** for importing an Excel file must be created in the tree view for the **Importing data into reporting entities** workspace.

Create a data source and configure the data source (see chapter [Defining Data Sources](https://support.lucanet.cloud/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source.md)).
{% /process-step %}
{% process-step title="Editing the Audit Trail (Optional)" %}
The data import can only take place if the import of data into the desired reporting entities for the desired period is allowed by the corresponding [audit trail](https://support.lucanet.cloud/en/documentation/glossary.md#audit-trails).

If necessary, edit the audit trail in Lucanet.Financial Client.

{% info-box %}
Audit trails are configured under the **Posting and planning** folder in the **Audit trails** workspace, by default.
{% /info-box %}
{% /process-step %}
{% process-step title="Creating and Executing the Data Import" %}
All data that is imported into reporting entities is transferred to the current Lucanet database using **data imports**. The **Data import** element is used to determine which data source and assignment table are to be used during the import.

The actions in the detail view of the data import are used to execute the data import, create assignments in the assignment table used and save the data import. You can create any number of data imports.

Create a data import (see chapter [Creating and Executing a Data Import](https://support.lucanet.cloud/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/creating-executing-data-import.md)).
{% /process-step %}
{% process-step title="Assigning Data" %}
If, during a data import, new elements have been read in for the first time from the dimensions **Accounts**, **Reporting entities** and **cost centers**, **Partner**, **Transaction currency**, **Data levels**, **Adjustment levels**, or **Transaction types**, these elements must be **assigned** (only once).

The data cannot be imported if there are any **assignment errors**. Assignment errors are displayed in the data import object.

- Check the assignments and/or rectify any faulty assignments (see chapter [Assigning Data](https://support.lucanet.cloud/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/assign-data.md)).
- Import the data (see chapter [Creating and Executing a Data Import](https://support.lucanet.cloud/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/creating-executing-data-import.md)).
{% /process-step %}
{% process-step title="Updating the Data Import (Optional)" %}
The data import can be updated **manually** or **automatically** in connection with the **Lucanet job control**.

- The data import is updated manually by importing the data again (see section [Creating and Executing a Data Import](https://support.lucanet.cloud/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/creating-executing-data-import.md)).
- The automatic update must be configured in **Lucanet.Server Administrator** in the job control.

{% info-box %}
Job control is configured in Lucanet.Server Administrator.
{% /info-box %}
{% /process-step %}
{% process-step title="Finalizing Data Import" %}
Every data import can be **finalized** in order to prevent it from being changed or deleted.

If necessary, close the data import (see chapter [Finalizing the Data Import](https://support.lucanet.cloud/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/completing-data-import.md)).
{% /process-step %}
{% /process-steps %}