Have a question about this requirement?

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Requirement

Rules can be created to validate cell level inputs by users

Functional Area

Data Management

Industries
All
DETAILS

Description

Data validation in Corporate Performance Management (CPM) software involves creating rules that ensure valid and standard inputs are entered into all cells within a dataset. These rules validate each cell level input against predefined parameters or checks, ensuring regularities, maintaining data integrity, and reducing the chance of errors or inconsistencies in the data.

Example Use Case

Scenario: An international financial firm uses planning software to run their monthly rolling forecast process. The department heads are required to enter in data when prior month expenses fall outside an expected tolerance.

Solution: Implementing cell level input validation rules on their prior month expense reporting is configured to require the department heads to justify expenses that fall outside of a mandated range. The system will not allow them to move forward until justification is provided.

Considerations

Cell level data validation and rules can be used well beyond the sample above. Consider other scenarios, like not allowing the users to insert expenses beyond a set budget. That may be useful for capping grant spending in a non-profit.

This functionality can be simple, such as making sure a field isn't left blank, or contain rules. Some products offer neither of these, while others include sophisticated validation tools that require consulting to setup. The offerings are broad. If this is important to you, dig into your specific use cases with the vendor.

Questions to Ask a Vendor

  • Validation Setup: How easy is it to establish and modify cell-level validation rules in your system? Are there any limitations on the variety or complexity of rules that can be created?
  • Error Reporting: How does your system handle reporting and rectification of input errors? Can you show us what the user sees?
  • Roles: Can the validation apply to certain users and not others?
  • Flexibility: Is the validation simple, like ranges, or can we associate it with drivers or formulas in the system?