Setup & Admin - Data Processing window
Excel > CCH® Tagetik > 
Design > (Left-hand panel) click form > 
> 
Data Processing
Purpose of window¶
This window allows you to configure the data processing to be run by the form.
Elements of the data processing selection step (⅕)
| Element | Description |
|---|---|
| ETL job for tables | Data processing that loads metadata from an external source to the CCH Tagetik database via an ETL Job |
| ETL job for values | Data processing that loads data from an external source to the CCH Tagetik tables of values via an ETL Job. |
| Preliminary data processing on Original scenarios | Data processing to be run on original scenarios before collecting the data |
| Preliminary data processing on Consolidation scenarios | Data processing to be run on consolidation scenarios before starting data collection and consolidation operations |
| Closing | Closing data processing (allocations) |
| Entity data processing | Data processing to be run on original scenarios during data collection |
| Consolidated | Data processing to be run on consolidation scenarios during the consolidation process |
| Cash Flow Planning | Specific data processing for the Cash Flow Planning module |
| Calculation logics | Data processing that allows you to run classic and advanced calculation logics (e.g. MD scripts) |
| Monthly splitting | Data processing that runs the new monthly splitting procedure. This procedure allocates an amount of a scenario/period on a range of scenarios/periods according to the set rules. |
| Form - Break Back | Break-back data processing that distributes the values present at the node level on the lower levels |
| Process cube | Data processing that updates CCH Tagetik cubes |
| Algebraic operations | Data processing that allows you to copy, organise progressively, delete and compress the data of a scenario |
| Monthly splitting | Data processing that runs the old monthly splitting procedure. This procedure allocates an amount of a scenario/period on a range of scenarios/periods based on a driver. |
| Forecast | Data processing that generates a forecast scenario based on an actual scenario and a budget scenario |
| LOANS_PLANNING - Bank loans depreciation calculation plan | Data processing that creates the entity’s bank loans depreciation plan |
| Data Transformation | Data processing that runs the Data Transformation Package of one or several Analytical Workspaces. Applicable on all Analytical workspaces in the environment which have at least one associated DTP. |
| Tagetik model process | Data Discovery: Qlik View Model process |
| Send generic email | Data processing that allows you to send an email on saving or via a link |
| Update Financial Workspace from Analytical Workspace | Data processing that allows you to automatically synchronise the data of an Analytical Workspace dataset and the Financial Workspace data structures. To do this, Financial Workspace mapping, which defines the loading method and the relationship between the dimensions and the CCH Tagetik logics must have been configured (see Quick Data Loader - Datasource mapping page). |
| Loading to Analytical Workspace | Data processing that allows you to load data from external datasources onto physical partitions of Analytical Workspace Datasets (e.g. the form content). |
| SUBMISSION_MD - Multi-organisation submission | Multi-organisation submission data processing on nodes for the analytical dimension by process / scenario / period / workflow / step |
| APPROVAL_MD - Multi-organisation approval | Multi-organisation approval data processing on nodes for the analytical dimension by process / scenario / period / workflow / step |
| REJECTION_MD - Multi-organisation rejection | Multi-organisation rejection data processing on nodes for the analytical dimension by process / scenario / period / workflow / step |
| Stored Procedures | Data processing that runs a stored procedure. See Stored procedure. |
| ML Training | Data processing that trains a Machine Learning Model |
| ML Execute | Data processing that runs the prediction of a previously trained Machine Learning Model |
| Deploy | Data processing that runs a deployment for all users, scenarios and periods as if it were run from a workflow task. To run the deployment for all processes, Enable all processes must be selected. Otherwise, the deployment will only concern the process used to run the report. The visible deployments correspond to those reported in the general deploy item in the Admin menu. |
Options in the parameters configuration step (⅖)
This step shows the available parameters for the data processing selected in the first step. Those shown in bold are mandatory. If errors are returned during this step, the data processing will be interrupted.
Note: if the data processing selected during the first step is Data Transformation, the mandatory DTP field will appear with the DTPs of the Analytical Workspaces chosen in that step.
The configuration options for each parameter are detailed below.
| Option | Description |
|---|---|
| Automatically | Only for dimensional parameters The system retrieves the value from any input parameters in the form, the global filter, the tab filter (tab active at launch) and the matrix filter (the latter only if there is only one matrix in the sheet). The value returned will be the same as that returned by the cell field on the flat dimension of the parameter. For example, if the parameter is of Entity type, then the value will be equal to that taken through the $Entity cell field. See the cell field definition mode below for further understanding |
| Excel Cell | The system retrieves the value of the parameter from the desired Excel cell of the current sheet, specified with the syntax cell H30. |
| Insert | Allows the user to enter the parameter value. |
| Select | Allows the user to select the value of the parameter from a list of possible values. |
| Cell field | The system retrieves the value of the parameter from a cell field. If this option is used for a dimensional parameter, it is preferable to type in an expression that, when defined, returns a node or leaf, not its code or description. For example, for an entity-type parameter, the expression $Entity must be used, not $Entity.code. The cell field is resolved by taking into account the form input parameters, the global filter, the tab filter (tab active at launch) and the matrix filter (the latter only if there is only one matrix in the sheet) |
If the chosen data processing is a DTP, and if this DTP refers to reporting parameters , then the system displays a further screen with the following options
| Option | Description |
|---|---|
| Automatically | Only for dimension parameters. The system retrieves the value from any input parameters in the form, the global filter, the tab filter (tab active at launch) and the matrix filter (the latter only if there is only one matrix in the sheet). The value returned will be the same as that returned by the cell field on the flat dimension of the parameter. For example, if the parameter is of Entity type, then the value will be equal to that taken through the $Entity cell field. See the cell field definition mode below for further understanding |
| Insert | Only for text-type parameters. Allows the user to enter the parameter value. |
| Select | Only for dimension parameters. Allows the user to select the value of the parameter from a list of possible values. |
| Cell field | The system retrieves the value of the parameter from a cell field. If this option is used for a dimensional parameter, it is preferable to type in an expression that, when defined, returns a node or leaf, not its code or description. For example, for an entity-type parameter, the expression $Entity must be used, not $Entity.code. The cell field is resolved by taking into account the form input parameters, the global filter, the tab filter (tab active at launch) and the matrix filter (the latter only if there is only one matrix in the sheet) |
Note: Boolean- and dictionary-type parameters are not supported.
Options in the execution configuration step (⅘)
| Option | Description |
|---|---|
| Force refresh | Reloads the form with data updated after running the data processing. |
| Override refresh dimensions tree | Reloads the dimensions tree with metadata updated after running the data processing. |
| Run when saving data | The system automatically runs the data processing on saving the form opened in data entry to ensure that the data processing is run on updated data. |
| skip tab filters | Excludes the values of the tab filters present in the form from the Automatic definition of the parameters. |
| "When saving data, please use modified cells for setting automatic parameters" | The system only considers the filters of the edited cells for the purpose ofAutomatic definition of the parameters. For example, if two periods of a matrix containing 12 periods have been edited, the system only considers the filters of those cells to define the automatic parameters. |
| "At Runtime, show a link for the run" | On opening a form in data entry mode, the system creates a link to the data processing from which it can be run. |
Buttons in the save step (5/5)
| Element | Description |
|---|---|
| Copies the string in the Visual Basic macro to run the data processing. See Macro custom. | |
| Uses a shared dictionary item in the description. | |
| Removes the shared dictionary item in use. |