Skip to content

Examples of mapping

Introduction

Some specific examples of entity/node, step and task workflow mapping are provided below.

Entity/node, step and task workflow mapping

In this example, two steps of a budget process, called Payroll planning and IT Costs, are mapped in order to achieve specific functional objectives, such as:

  • setting the Payroll planning step to run the planning on the individual employee for American entities, and on the headcount for all other entities.
  • enable only submission for contributor and consolidator nodes.
  • enable the Corporate entity as the only entity authorised to enter data on the IT Costs step.

In CCH Tagetik, these objectives correspond to the following settings, developed in the procedures in this module:

Settings Procedure
Diversify the task workflow of a step depending on the entity Step (Payroll planning)/Entity mapping
Enable only submission for contributor and consolidator nodes Step (Payroll planning)/Node mapping
Enable only the Corporate node (organisational hierarchy parent) to enter data in the IT costs step , excluding all other entities. Step (IT Costs)/Entity mapping

Step (Payroll planning)/Entity mapping

In this example, the Payroll planning step must run the planning on the individual employee for American entities, and on the headcount for all other entities. To do this, the following operations are necessary:

  • Create a step/entity relationship that defines the general behaviour to be applied to the entire organisational hierarchy. To do this, the PPA task workflow of the payroll planning by headcount is related to the Payroll planning step and the entity is the parent (or root) 000 Entities node of the process’s organisational hierarchy.
  • Create a step/entity relationship that defines the specific behaviour to be applied to an individual entity of the organisational hierarchy. To do this, the PPU task workflow of the payroll planning by employee is related to the Payroll planning phase and the entity is the USA node to which the American entities in the organisational hierarchy are related.

Procedure

IMPORTANT: the order in which the relationships are added to the table determines the order in which they are read by the system, which manages subsequent rows as exceptions to the previous rows. If there are both general and specific relationships (with exceptions and overrides), the specific relationships must be positioned after the general relationships.

  1. On the Elements tab of the Mapping task workflow page, click : a new row will appear.
  2. Select the new row and, in the Attributes tab, select the Payroll planning phase, the PPA task workflow, and the 000 Entities entity. This is the parent node of the process’s organisational hierarchy
  3. Click Save.
  4. Click .
  5. Select the new row and, in the Attributes tab, select the Payroll planning phase, the PPU task workflow, and the USA entity. This is the node of American entities.
  6. Click Save.

Step (Payroll planning)/Node mapping

For contributor and consolidator nodes, it is necessary to enable data submission only. This is automatic, since the system associates the default task workflow $STEP that contains only one submission operation to every node within the mapping.

Step (IT Costs)/Entity mapping

In this example, in the entire IT Costs phase, the Corporate entity must be the only entity in the organisational hierarchy authorised for data entry and submission. To do this, the following operations are necessary:

  • Create a phase/entity relationship that prevents any behaviour on the entire organisational hierarchy. To do this, the task workflow $$ - Empty task flowchart is related to the IT Costs step and the entity is the parent node of the process’ organisational hierarchy.
  • Create a step/entity relationship that defines the specific behaviour to be applied to an individual entity in the organisational hierarchy. To do this, the IT Costs task workflow and the entity X00 - Corporate are related to the IT costs step.

Note: excluded entities are identified with a grey traffic light on the process cockpit.

Procedure

IMPORTANT: the order in which the relationships are added to the table determines the order in which they are read by the system, which manages subsequent rows as exceptions to the previous rows. If there are both general and specific relationships (with exceptions and overrides), the specific relationships must be positioned after the general relationships.

  1. On the Elements tab of the Mapping task workflow page, click : a new row will appear.
  2. Select the new row and, in the Attributes tab, select the IT Costs step, the Task workflow $$ - Empty task flowchart, and the 000 Entities entity. This is the parent node of the process’s organisational hierarchy
  3. Click Save.
  4. Click .
  5. Select the new row and, in the Attributes tab, select the IT Costs step, the IT Expenses task workflow, and the X00 - Corporate entity.
  6. Click Save.