1. User's Guide
  2. Using Process Management
  3. Process Management Validation

Process Management Validation

When you create an application, you can select a validation account. During the Review process, when you try to promote, submit, approve, sign off, or publish the process unit, the system checks whether the account value in the Validation account equals zero or NODATA. If it does not, the system displays a message that it cannot perform the action.

If the application is set up to use phased submissions, you can set validation accounts for each submission phase.

When you promote, submit, approve, sign off, or publish a process unit, the system also checks the data to ensure that it has an OK, OK SC, or NO DATA status. If the process unit does not have one of these statuses, you must recalculate, translate, or consolidate the data before you can perform any process management action.

The system also checks the process unit to see if the data is locked. You cannot perform any process management actions until the data is unlocked. You can only lock data when it is published. See Locking Data.

The process level of the parent entity must always be lower than or equal to all of its immediate children. The process level of the child entity must always be greater than or equal to all of its immediate parents.

Validation for Promotion

When you promote a process unit, the system also performs these additional validation checks:

  • It checks the process level of direct descendants to ensure that you are not promoting an entity to a level that is higher than the lowest level of all of the entity’s dependents.

  • If you are using a different currency for the entity, the system checks the process level for the entity’s input currency to ensure that a current translation is being used.

  • If you are using a node component, the system checks the currency process unit that applies to the parent’s input currency to ensure that the node values are correct.

Validation for Rejection

When you reject a process unit, the system performs these additional validation checks:

  • It checks the process level of the immediate parents to ensure that you are not rejecting an entity to a level that is lower than all of the entity’s parents.

  • If the Value dimension equals the input currency for an entity, the system checks the input currency for all of the parents. If the parent’s input currency is the same as the entity’s input currency, the system checks the node process unit. If the parent’s input currency is different, the system checks the process level of the parent’s currency at the entity level.

  • If the Value dimension uses a currency other than the input currency for an entity, the system checks the level of the node process unit.

  • If the Value dimension indicates that you are using a node process unit, the system checks the process level for the parent’s input currency process unit.