Skip to content

The Quick Data Loader function

Introduction

The Quick Data Loader is a utility which allows you to enter data CCH Tagetik quickly, en masse. In particular, it allows you to import data from the following sources into the Financial Workspace data structures and Analytical Workspace datasets:

  • one or more spreadsheets or text files
  • Analytical Workspace datasets
  • data tables from the CCH Tagetik database
  • external sever (through APO RESTful services with OData protocol)

Data entered via the Quick Data Loader is subject to the same loading checks as for data entry (user rights, editability privileges etc.).

Access to the Quick Data Loader function

The Quick Data Loader function can be accessed via the following entry points:

  • the consolidator cockpit
  • Analytical Workspace datasets

Quick Data Loader data processing can be initiated through:

Data loaded via the Quick Data Loader are marked as originating from the Quick Data Loader.

Data import steps

Data is imported via the Quick Data Loader by working in various windows/pages according to the following steps:

Steps Window/page
Definition of the data source and the target and uploading of the source into the Quick Data Loader Quick Data Loader - source/target definition window
Mapping of data from the source on the target information model and definition of the calculation and data management criteria Quick Data Loader - Import criteria definition window
Data import -
Displaying errors on blocked data in editability checks Quick Data Loader - Editability check outcome window
Displaying the import outcomes Quick Data Loader window: outcome

Data mapping

To run the data import, it is necessary to run the mapping between the data from the source with the structure and data from the target. When the Quick Data Loader is accessed via the contributor cockpit, the mapping operation must be executed manually. However, when the mapping is accessed from Analytical Workspaces, during the step of loading data from the source, the system will compare the source dimensions with the contextual dimensions at the entry point and run an automatic mapping of the consistent data. For example, if the source has scenario, period and entity dimensions that are identical to those included in the dataset from which the mapping window was opened, the system automatically runs the mapping of the three identical dimensions.

You can then modify the automatic mapping, by changing or removing the related dimensions, and manually add to the target one or more dimensions that are only present in the source.

If the source is an Analytical Workspace type source, the data is also mapped based on whether the target of the dataset’s analytical dimensions are included in the list and in the user rights.

Dynamic mapping

Dynamic mapping criteria can be created when data is loaded into Analytical Workspace and Financial Workspace. At the start of the data processing, these criteria calculate the data to be entered for each dimension, based on the execution context.

The possibilities for creating dynamic mapping criteria are as follows:

Element Description
Default function Defines the dimension data during the data extraction step. The function can be defined using the following criteria: - a constant - a context parameter (#PROCESS#, #SCENARIOS#, #PERIODS#, #ENTITIES#, #REFERENCE_DATE#, #TARGET_PARTITION#, #USER#, #AW_CODE#) - an Analytical Workspace parameter (which can be called using the syntax @parameter name@) - a parameter related to dimensional attributes (which can be called using the syntax ${ parameter }) - a unified SQL syntax (see Unified SQL syntax) - a {FILE_NAME} parameter relating to the name of the source file Note: In the case of a single file source then the displayed file name is the concatenated 12-character random NAMEFILE. - a {FILE_PATH} parameter relating to the path to the source file Note: in the case of a single file source, the value will not be defined.
SQL function Defines the data dynamically during the extraction and can apply small transformations. The definition of the function is alternative to the definition of a default value; the latter is left for backward compatibility reasons.

When dynamic mapping is created on a source/target relationship, the saved criteria are automatically applied in all data processing on the specific relationship.

Conversion of periodic amounts into progressive amounts

When the import destination is a gross or intercompany amount, but the amounts in the source are expressed in a periodic format (on a monthly, bi-monthly, etc. basis), the Quick Data Loader converts the amounts to a progressive format as required by the Financial Workspaces of CCH Tagetik . This calculation is applied to P&L accounts and other flows, or to variation accounts.

In single-submission processes, data loaded from the data source are made progressive without being enriched by data from CCH Tagetik. Depending on the period length, any periods needed, and not present on the target, are generated. The calculation is based on the period length indicated in the related dimension. For example, if the period length is bimonthly, progressive values are generated for periods 02, 04, 06...; or if the period length is half-yearly, progressive values are generated for periods 06, 12.

In the scenario/period submission processes, the periodic data of the loaded scenario/period are enriched with the progressive scenario/period data already present in CCH Tagetik. This calculation considers the period length and the carry forward policies indicated in the Quick Data Loader’s data management criteria.

Data for the previous scenario/period read by CCH Tagetik will depend on the type of data imported (Gross/intercompany) and also on the type of amounts present in the source (gross/minority).

Particular features of initiating via web forms

When the Quick Data Loader data process is initiated from a data entry web form, the target type depends on the matrices present in the web form. With matrices created in Financial Workspace on one or more sheets, the only type of target available is Data (Amounts, Intercompany). With matrices created in Analytical Workspaces on one or more sheets, the only type of target available is Analytical Workspace. When the form contains matrices in both Financial Workspace and Analytical Workspace, it is possible to choose the desired type of target.

Particular features of dimensions

Below are some dimensions that are only visible if the Target Type has been set to Data (Balances, Intercompany)):

Element Description
Period Length This allows you to indicate whether the period over which the source amounts are calculated is cumulative (adding amounts), or periodic (monthly, bimonthly, etc.).
Entity currency Indicates the entity currency This dimension is not visible because it is calculated automatically based on the entity currency for the process being run.
Entity currency amount Indicates the value of the amount of the transaction converted into the entity currency. If not mapped to a source column, it is automatically calculated as a conversion of the transaction amount.
Amount Indicates an amount type data. For this dimension, it is not possible to specify a default value. Relating several columns from the source to this dimension will activate the Measures mode, which allows you to: - define a list of dimensions from the template, typically not present in the source, on which the related measures will be based - indicate, for each measure, the values that the template dimensions must assume

Default Value

For some dimensions the defaults are already set:

Element Default
Scenarios - in the case of a submission process for period scenario, the context scenario from which the Quick Data Loader is opened
Period - in the case of a submission process for period scenario, the context period from which the Quick Data Loader is opened
Entity the entity of the context from which the Quick Data Loader is opened (in the case of opening from the process cockpit, only in the case of a single entity selected)
Category the amount system category $AMOUNT
Custom dimensions the default targets of the entity in case of opening from a single entity otherwise the default custom dimensions defined in configuration
Measures (Dataset fields of type Text and Number) - default set in the definition of the relevant Dataset field.

The default cannot be set manually, but only by selection from the relevant value range.