Run a calculation logic from workflow and from job

Tagetik allows the user to run a calculation logic also from a workflow model task or from a job task. Below we describe how to define a task from which to run a calculation logic inside a workflow model.

If we assume that we are inside a task flowchart and we want to define a new task for the execution of the calculation logics, we will have to follow the steps below:

  • define a new task by dragging the Calculation logics icon, assign a code and a description to the task;

  • the following parameters can be set up:

  • Calculation logic type. Typology of the calculation logic to be run. Possible values:

  • Basic

  • Others

  • All

  • Data type. Typology of data on which the calculation logics has to be run. Possible values:

  • Amounts. The calculation logic is run on gross amounts and IC entries;

  • Journals. The calculation logic is run on the entity journals and on the consolidation journals;

  • All (default value).

  • Category / Category node. Filters data on which the calculations logic will be run by category;

  • Journal number. Filters the journals on which the calculations logic will be run by journal number;
  • Calculation logic / Calculation logic node. The system runs only the specified calculation logics;
  • Sequence. The system runs only the calculation logics with the specified sequence;
  • Account / Account hierarchy node. The system determines automatically the calculation logics that involve the specified accounts;
  • Custom dimension 1...5 / Custom dimension 1...5 hierarchy node Filters data on which the calculations logic will be run by the elements of the custom dimension 1...5;
  • Filter calculation logics by data. The system automatically determines the logics to be run based on the filter set up on the dimensions on which the calculation logics will be run;
  • Consolidation scenario.

Let's see in detail the possibly set filters for partializing the calculation logics to be run.

  • Filter 1. If we specify to filter the calculation logics depending on data, the system processes all the calculation logics having as input accounts the accounts present on the data tables after applying the dimension filters and all the "indirect" ones, namely those having as input accounts the calculated accounts from the previous logics. In presence of this filter, the system ignores possible other filters of 2,3,4 type;
  • Filter 2. In presence of a filter on accounts and /or on an accounts hierarchy's, the system processes all the calculation logics having as input accounts those obtained be the union of the single accounts and the accounts related to the specified nodes. Also in this case, the system process all the "indirect" logics having as input accounts the calculated accounts from the from the previous logics. In presence of this filter the system ignores the possible other filters of 3,4 type;
  • Filter 3. In presence of a filter on the calculation logics and/or on the grouping's nodes, the system processes only the calculation logics which belong to the union of the single logics and the logics related to the nodes. This filter is applied in intersection with the filter on the sequence;
  • Filter 4. In presence of a filter on the sequence the system processes all the calculation logics with that sequence.