---
title: "Provision via script (#2075)"
description: "After creating a Provision via Script (#2075) data source, the settings for importing data via script are configured in the detail view of the data source."
source_url: https://support.lucanet.cloud/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source/data-source-script
language: en
last_updated: 2023-08-16
---
# Provision via script (\#2075)

## Overview

After creating a **Provision via Script (#2075)** data source, the settings for importing data via a script are configured in the detail view of the data source.

## General Properties

The following general properties of the data source can be configured in the upper area of the detail view:

| Option | Description |
|---------|---------|
| Name | Name of the data source |
| Drill down to posting level | Script to be used for drill-down to posting level (optional) |
| Display scanned documents | Script that enables the display of scanned documents (optional) |

## 'Configuration' Tab

The **Configuration** tab consists of the following sections:

### The following scripts are executed during the data import

Adding script

#### Script

Scripts to be executed during data import. All scripts from the **Scripts** workspace can be selected.

#### Application

Location where the respective script is to be executed

{% warning-box %}
If the script is to be executed on an SEA instance, you must choose the created **application** in the **Application** drop-down list (see [Creating SEA Applications on the CFO Solution Platform](https://support.lucanet.cloud/en/documentation/consolidation-financial-planning/basic-configuration-cfp/install-and-use-opsea.md#createApplication)).

**Lucanet Script Execution Application** ( **SEA** for short) is a Lucanet application that you need if you operate ERP/financial source systems on-premises and want to import data from these systems into the Lucanet CFO Solution Platform using an ETL script.
{% /warning-box %}

### The following data are imported

Options for data imports

#### Import type

The desired import type:

- Transaction figures or balances (selection when importing)
- Transaction figures
- Balances
- Balances - schedules only
- Transaction figures incl. automatic contra entry (only planning)

#### Data levels

Data levels into which the data are to be imported.

Enter the name of the data level in the **DataLevelCode** column.

{% warning-box %}
This field is only displayed if the corresponding variable is defined in the selected script.
{% /warning-box %}

#### Adjustment levels

Adjustment levels into which the data are to be imported.

Enter the name of the adjustment level in the **AdjustmentLevelCode** column.

{% warning-box %}
This field is only displayed if the corresponding variable is defined in the selected script.
{% /warning-box %}

#### Accounting periods per year

Number of accounting periods per year (default: 12)

- If you specify a number greater than 12, all periods greater than 12 are imported by default into period 12. You have the option to specify whether the additional periods are to be imported with a suffix into separate adjustment levels.
- If you specify a number greater than 12, then it is only possible to import transaction figures.

### The following dimensions are imported

Selection of dimensions to be imported

Specify which dimensions are to be imported. The **Account** dimension is always activated. If necessary, change the displayed dimension code in the **DimensionCode** column.

**Cost centers in the Balance Sheet**: If the use of the **Cost center** dimension is activated, you can specify whether a drill down by cost centers should be performed in the balance sheet:

- **Use default cost centers always (recommended)**: The default cost center is used
- **Use specified cost centers**: The cost center whose code was specified for the dimension **Cost center** will be used

### Reclassify values

Options for reclassifying values

If necessary, specify whether you want to **reclassify values** during the data import. The following options are available:

#### Present intercompany postings on separate accounts

Accounts and partner for intercompany postings.

If the use of the **Partner** dimension is activated, the corresponding accounts and partners can be specified in the **Accounts to be analyzed** table.

#### Attach suffix to account name

Suffix for account name.

Specify the desired suffix in the displayed **DimensionCode** field.

#### Reclassify debtors with credit balances and creditors with a debit balance

Reclassification of debit or credit balances when importing balances or opening balance sheet values.

Specify the desired code in the **DimensionCodefor the ‘Subledger account’ dimension** field. In the **Accounts to be analyzed** area, the account range ( **Account from** and **Account to**) and the balances to be reclassified ( **Credit** or **Debit**) must be specified.

## 'Reporting Entities’ Tab (Conditional)

'Reporting entities' tab

{% warning-box %}
The **Reporting entities** tab is only displayed if the corresponding variable is defined in the selected script.
{% /warning-box %}

The **Reporting entities** tab defines which reporting entities are available for selection when importing the data. The configuration corresponds to the configuration for data sources of type **Lucanet.Financial Warehouse (#2068)**. For the complete description of all options, see [Specifying Reporting Entities](https://support.lucanet.cloud/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source/data-source-lnfwh.md#reportingentity).

In addition, importing data into reporting entities via a script offers the possibility to split data imports into several import files and store them in a predefined folder structure (see [Splitting Data Imports During First Execution](https://support.lucanet.cloud/en/documentation/consolidation-financial-planning/imports-journals/importing-data-into-reporting-entities/defining-data-source/data-source-lnfwh.md#split)).

If necessary, contact your Lucanet consultant to find out whether your script can be configured accordingly.

## 'Uses' Tab

The elements that use the data source are displayed on the **Uses** tab.

You can open the respective element by clicking the link in the **Name** column.

'Uses' tab