Skip to content

Process parametrization for the 'Allocation & Closing'

Process parametrization for the "Allocation & Closing"

The Process is the basic component of the Tagetik implementations since it manages all the data entry and automatic data processing activities.

A Process can be defined as a set of activities or tasks (workflow model) with a start date and an end date and which:

  • includes an approval workflow of inserted data (organization hierarchy);
  • can have a logical and functional workflow of the activities to be performed (Task FlowChart: for example, data loading, data processing run, adjustments entry, submission...);
  • operates on the whole data model or on a subset of it (process data model).

The allocation process can be defined as a "sub-process" used in the consolidation or financial planning processes in order to allocate, as correctly as possible, the costs and/or revenues on specific business units, services or activities which directly or indirectly generated them.

For further details about the process parametrization, consult the "Process" chapter of the user manual.

For the purposes of the allocation process, it is important to remember that in order to enable the allocation and closing data processing on any process the user has to:

  • enable the Enable Allocation and Closing option in the Data Processing area of the process detail definition window;
  • save.

Once the allocation and closing data processing has been enabled, the following information can be managed:

  • Execution plan. From this it is possible to manage the execution plan
  • Advanced rules. The system uses as advanced rule for the current process the generic rules defined from the administrator user web interface by following the path Setup & Admin > Data processing > Allocations & closing > Advanced rules Navigation panel> Data processing > Allocations & closing > Advanced rules. Here it is possible to override some settings of the generic rule (for example it is possible to specify that, when defining the rule, the user must specify a category for the current process on which the entries will be generated. Such category must not be the reading category as set in the generic rule) and make the system use the overridden rule rather that the generic one for the current process.