Import data via Quick Data Loader

Introduction

By importing data via Quick Data Loader, the following activities are performed simultaneously:

• data transfer from source to target
• Data editability check

Steps of data import into target (Amounts, Intercompany)

The data import into target (Amount, Intercompany) takes the following steps:

1. The records in the selected data source are read.
2. If Measures mode is enabled, the Amount dimension is defined (by pivoting) with the values on the columns mapped as Measures, while the dimensions on which the measures move are defined with the default values.
3. Values are calculated for dimensions that are not directly populated in the data source.
4. Records that do not satisfy the filters inherited from the execution context (see Data mapping) are deleted.
5. If the period length indicates exact amounts, conversion to progressive amounts is performed (see Transformation ofConversion of periodic amounts into progressive amountsunts).
6. An editability check of the data to be deleted and/or inserted is performed.
7. The records in CCH Tagetik suitable for control are modified.

Editability checks on targets (Amounts, Intercompany)

If, during the data editability check, the system detects anomalies in the data types to be loaded and/or in the loading process, the processing is interrupted and the detail of the records causing the warnings is displayed (see Quick Data Loader - Editability check outcome window).

Importing data to an Analytical Workspace target

Data import to an Analytical Workspace target follows the following steps:

1. Reading of all record in the selected data source.
2. Deleting records that do not meet the filters inherited from the execution context (see Data mapping).
3. Editability check of data to be deleted and to be inserted (depending on the loading mode)
4. Input on the dataset of records satisfying these checks with application of the defaults set on the measure type fields if not managed as input.

Editability checks on the Analytical Workspace target

Below is the list of editability checks for the Analytical Workspace targets:

• dataset with at least one measure belonging to a step greater than or equal to the execution step
• existing, active and visible scenario for the current user
• existing scenario/period, not blocked, and belonging to the run process
• existing Entity, belonging to the run process and editable for the current user
• Existing Entity node
• existing account, belonging to the process and visible to the current user
• Existing Account node
• existing category, belonging to the process and visible to the current user
• account (or account/category) belonging to the process and to a step greater than or equal to the run step
• existing custom dimensions visible to the current user
• Existing custom dimension node
• existing and editable Ctp Entity for the current user
• existing and editable Ctp Custom dimension for the current user
• existing currency
• existing variation/detail type
• existing and visible analytical dimensions for the current user
• Existing analytical dimension node
• existence analysis of duplicate keys, both in the source data only and in the simulation of the situation after the deletion and insertion steps

Standard Process

• Entity belonging to the run process and not submitted for the current phase
• Entity node not submitted for the current step

Multidimensional Process

• Dimension element of the current step belonging to the run process and not submitted for the current step. Elements of the dimensions linked to the other unsubmitted steps in the step to which they belong.
• Unsubmitted node of the dimension of the current step. Nodes of the dimensions linked to other unsubmitted steps in the step to which they belong.

If during the data editability check the system detects anomalies, the data processing is interrupted and the detail of the records causing the warnings is displayed (see Quick Data Loader - Editability check outcome window).

Restriction checks on Analytical Workspace targets

Dimensions-related visibility checks for the current user are only performed if the relevant dimension is present on the target dataset.

Process checks for Analytical Workspace targets

Process and step checks are only carried out when, in addition to the presence of account, category and dataset information, it is possible to uniquely derive scenario, period and Entity information compatible with the partitioning of the target dataset:

Partitioning type	Required conditions
Unpartitioned Datasets	Scenario, Period and Entity columns are required
Datasets partitioned by business cycle
Datasets partitioned by business cycle and entity