Provision via script (#2075)
Last updated on 2025-11-28
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.
This article contains the following sections:
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:
Option
Description
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
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).
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.
Option
Description
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.
This field is only displayed if the corresponding variable is defined in the selected script.
Adjustment levels
Adjustment levels into which the data are to be imported.
Enter the name of the adjustment level in the AdjustmentLevelCode column.
This field is only displayed if the corresponding variable is defined in the selected script.
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.
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
If necessary, specify whether you want to reclassify values during the data import. The following options are available:
Option
Description
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 DimensionCode for 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)
The Reporting entities tab is only displayed if the corresponding variable is defined in the selected script.
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.
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).
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.
