Checks on multidimensional matrices

Checks on opening

The attempt to open a Data Entry form (whether Line by Line or Multidimensional) on a Dataset partitioned by Scenario/Period/Entity is blocked and the user receives a warning message. At the moment, on the Multidimensional Process, the partition policy is understood to be by Scenario/Period only.

Editability checks

In a dataset design step, the user specifies an editability value for each field: Editable, Editable only on new rows or Read only.

Checks on saving

There are 4 types of editability checks on opening:

• consistency checks
• submission checks
• checks for locked scenario/periods
• checks for limitations in read only mode for user and dataset

Therefore, on saving data, when the form refers to a dataset or partition logics containing all the dimensions needed to identify the process submission status (Scenario, Period and Entity or Scenario, Period or Organization Dimension for multidimensional processes), the system performs consistency checks first of all. In other words, it verifies that the data entered are coherent with the definition of the process.

In particular, the type of control varies based on the following conditions:

Condition	Check
The dataset fields allow for the identification of the submission status of the entities for the various steps of the process.	The system performs a check on the data entered for the various entities in the step for which the form was run.
The dataset or partition logic contains the account dimension in the dataset fields.	The system verifies that, by Scenario, Period and Entity (or organization dimension) the Account (or Account/Category if the process is submitted by Account/Category) belongs to the process, the data have not been submitted and there are no limitations for the user.
The dataset or partition logic contains one or several Measures in the dataset fields.	The system verifies that, for Scenario, Period, Organization Dimension and Measures, the data are editable, belong to the process and have not been submitted and that there are no limitations for the user.

It also verifies that the following conditions are met:

• In the event that the Dataset contains the Category dimension, and it is accessed via a process with submission based on the Account, the Category, if specified, must belong to the categories filter configured in the process.

• An Account/Organization Dimension pair (or Account/Category/Organization Dimension triplet) belongs to a process if, in the definition for the entity’s Process Data Model, the account has been associated with a step of the process.

When the outcome of a check is negative, the form will not be saved and the user will receive an error message.

In case of Data Entry on category nodes containing several sub-nodes, the system fails to determine the appropriate lowest element node for data entry when the underlying sub-nodes refer to different lowest elements structures. As a result, it returns the error message 'Category - Conflicting Value' and prevents the data entry operation. Data entry on a single node works correctly.

It is not possible to check submission status if consistency checks have been disabled. If this happens, submission checks are not performed either.

For datasets that do not contain the dimensions needed to identify the process submission status, the system does not perform any check and saves the form, regardless of the form structure and the process submission status.

For further details on check configuration, see the Control section in Operations.