Skip to content

Process Data Model examples

Introduction

Some specific examples of settings for various types of PDM are provided below.

Example of a Process Data Model by account/step

This example describes a situation in which all entities insert and consolidate data on the same accounts and according to the following contributor/consolidator steps:

  1. Collection of revenue and cost of sales data
  2. Collection of OPEX data
  3. Collection of CAPEX data

The default PDM ($PDM) can be used for this process.

Procedure

Application database > Processes tile > select process > > Process setup (Process Data Model section)

Application database > Navbar > Processes & Workflows > Process > select process > > Process definition > (Process Data Model section)

  1. In the Process Data Model section, in Type, select By Account.
  2. Click to open a page showing the details of the default PDM.
  3. Select the accounts to be inserted in the various steps.
To select accounts from... Then...
Account tab Select the accounts individually or as a node in an accounts hierarchy.
Form exceptions tab Select individual forms or a node from the group of forms. Selecting a form selects all the editable accounts contained in it.
4. Indicate the gross step to which the selected accounts must be related: on submitting the indicated step, the entry of gross data on all of that step’s accounts is blocked, except for overrides.

IMPORTANT: actions are run in the order in which they are presented in the table. If Excluded is selected as the last action for an account, it is excluded from the whole process.

Example of Process Data Model by account/category/step

This example describes a statutory data collection process according to the following contributor/consolidator steps:

  1. Intercompany data collection
  2. FS data collection
  3. Collection of supplementary note details and variations data
  4. Collection of entity journals

The same accounts as steps 2 and 3 are managed in step 4, but according to the entity journal categories. Whereas amount categories are considered in phases 2 and 3.

Procedure

Application database > Processes tile > select process > > Process setup (Process Data Model section)

Application database > Navbar > Processes & Workflows > Process > select process > > Process definition > (Process Data Model section)

  1. In the Process Data Model section of the Process definition page, in Type, select By account/category.
  2. Click to open the Define Process Data Model page.
  3. In the Account tab of the Define Process Data Model page, define the account/category pairs for which data are collected and the relative step:
  4. Select the normal P&L and balance sheet accounts.
  5. For these accounts, in Categories, select the Amount categories and in Step, choose step 2, because this is the step in which you want to close the collection of gross data.
  6. Select the detail P&L accounts and the variation balance sheet accounts.
  7. For these accounts, in Categories, select the Amount categories and in Step, choose step 3, because this is the phase in which you want to close the collection of detail and variation accounts.
  8. Select normal detail accounts and variation accounts (both P&L and balance sheet).
  9. For these accounts, in Categories, select the Entity journal accounts and in Step, choose step 4, because this is the step in which you want to close the entry of entity journals.

Comments

No definition is entered for step 1 because intercompany data is submitted in this step.

In the definition of the details of accounts/categories for which data must be entered, only the gross step is considered, i.e. the step in which the entry of gross data of a certain entity must be blocked.

The intercompany step, in which the entry of intercompany data is blocked, is determined by the step in which an intercompany matching cockpit has been inserted.

The only operation required to manage the matching of intercompany entries in step 1 is therefore creating a relationship between the intercompany cockpit and step 1 in the process rules. Thus, the system blocks the entry of intercompany entries for all accounts included in the intercompany cockpit upon submission of step 1.

For accounts excluded from the cockpit, however, the entry of intercompany entries is blocked when submitting the gross step to which the account is related.

Example of a Process Data Model by account/step with contributor steps and consolidator steps

This example describes a data collection process for generating the consolidation according to the following three steps:

  1. Data collection by entity - contributor step
  2. Collection of supplementary note details and variations - contributor step
  3. Collection of consolidation journals - consolidator step

With the contributor and the consolidator using different steps, a single PDM can be used; in this example it is the default $PDM.

Procedure

Application database > Processes tile > select process > > Process setup > (Process Data Model section)

Application database > Navigation Panel > Processes & Workflows > Process > select process > > Process definition > (Process Data Model section)

  1. In the Account tab on the Define Process Data Model page, select the Include action and define the accounts on which to collect data.
  2. In Step, indicate the gross step to which the selected accounts must be related: on submitting the indicated step, the entry of gross data on all of that step’s accounts is blocked, except for overrides.

Note: consolidator steps are not included among the selectable steps. 3. Click Save to return to the Process definition page. 4. Run deployment. 5. Click to view the accounts involved in the contributor and consolidator steps of the data model.