Skip to content

Processes: basic concepts

What are processes

A process is the component that CCH Tagetik uses to acquire, submit, process and log data on the customer’s activity, allowing them to take control of the quality of their data, reporting and planning. It consists of a workflow, or a sequence of activities, in which authorised users insert, submit and approve data in accordance with a finite logical/functional flow of work.

Working with processes in CCH Tagetik means recreating on the system your actual workflow used to collect and submit data in-house, processing that data accurately, and generating valid documentation for said data that meets your business’s short- and long-term needs.

Traditional processes and processes with dimension by step

Traditional processes act solely on the Entity dimension, while for processes with dimension by step you can specify a different dimension for each step of the process.

For more details on process with dimension by step, see Processes with dimension by step.

Function

CCH Tagetik Processes can be used both to enter and to process data in a centralised and accurate manner to produce reports, and to collaboratively manage data in order for it to be submitted and in order to monitor and plan business activities.

Based on their configuration, process workflows can be used to guide the collection and processing of all the data of an individual entity or company (entity workflow) or to submit an entity’s individual journals (journal workflow).

Process structure

To create data collection and processing logics specific to the entity’s business requirements, there must be the following structures:

  • the time dimension of the activities documented by the process
  • the entity authorised to enter and submit data
  • the logical steps of the process
  • the accounts on which to collect data
  • the rules for data entry
  • the processing modes for specific data or groups of data.

These structures are defined in the Business Workflow, Data model, Data entry and submission rules and Data Processing modules and are used by processes according to the logics defined at the level of the individual process.

The management of data within processes

Data is managed according to the following steps:

  • data entry, i.e. entering data in the application database.
  • submission, i.e. the validation and locking of original collected data or calculated data for each individual dimension.
  • processing data according to the system rules and logics and/or rules and logics defined by the user.
  • consolidation, i.e. the calculation of data at the group level as if it were a single entity for legal and reporting purposes.

The necessary elements for these steps are configured on the following pages of CCH Tagetik:

Configuration Page
Data entry Data Entry and Submission tile (see )
Submission
Data Processing Data Processing tile (see )
Consolidation

These general configurations are applied automatically to all processes set up in CCH Tagetik. The generic rules can be overridden to adapt them to a specific process. See .

Process configuration

CCH Tagetik has a default process ($Process) which allows you to use CCH Tagetik as a data mart, or a container for a subset of data and for reporting. This process is therefore predefined, but it still requires Process Data Model configuration (see Introduction to the Process Data Model).

IMPORTANT: like all system elements ($), the default $Process must not be deleted. However, it may be modified by configuring the PDM.

When CCH Tagetik is used as a collaborative tool, a dedicated process must be created according to the entity’s needs.

This requires intervening on several separate aspects in the various sections of the Definition of Process with dimension by step Page.

Process deployment

In CCH Tagetik, running deployment means applying to the system the parameters configured by the user in the interface, or updating the database tables with those parameters.

When deployment is run on processes, the system updates the database tables that manage the data entry rules in the various steps of the process and the checks on data prior to submission.

Deployment can be run on the Process definition page by the administrator user. Deployment can be run on all of the process’s parameters by clicking the Deploy button, or some of the process’s parameters by clicking the button corresponding to the configuration sections.

The parameters included in the last deployment, and therefore already applied within the system, can be consulted on the Definition result pages (e.g. Definition result: Mapping task workflow).

The order in which the records are inserted in the definition tables is important, since this determines the order in which the deployment processes the rows.

Individual processes can also be deployed from the general deployment page (see).