Data validation rules in Oracle EPM Planning (PBCS/EPBCS) are configurable conditional logic checks applied to cells in planning data entry forms — displaying colour-coded alerts or informational messages when entered data violates predefined business conditions, and optionally preventing the form from being saved until the conditions are resolved. Data validation rules operate at the intersection level — checking specific account, entity, period, and scenario combinations — and produce visible feedback to the planner without requiring a separate business rule execution or form save-refresh cycle. In a headcount planning form, a data validation rule might flag any salary input that exceeds the applicable grade ceiling, or alert when a new hire date precedes the budget start date. In a capital planning form, a rule might flag when capex entered for an approved project exceeds its authorised budget amount. These checks surface data quality issues at the point of entry — when they are fastest and cheapest to correct — rather than in the post-consolidation budget review.
Data Validation Rule Types
| Validation Type | Behaviour | Use Case |
|---|---|---|
| Informational | Displays a message when condition is met; does not prevent save | Alert planner that entered growth rate is above guideline — for awareness only |
| Warning | Displays a highlighted cell indicator; does not prevent save | Flag salary above grade ceiling — planner can proceed but deviation is visible |
| Error | Displays error message; prevents the form from being saved until resolved | Prevent submission when total headcount exceeds approved headcount limit |
| Cross-form validation | Checks value against data from another form or another account | Validate that revenue in the regional form matches the sum of product-level revenues |
Data Validation Rules vs Business Rules
Data validation rules and business rules serve different purposes in EPM Planning. Business rules perform calculations — spreading annual values to monthly periods, copying data between scenarios, running allocation logic. Data validation rules perform checks — evaluating whether entered data meets defined conditions and surfacing the result visually in the form. Both types of logic are part of the planning model’s quality assurance architecture, but they operate at different points in the user workflow: data validation rules operate immediately when a cell value changes, providing instant feedback; business rules operate when explicitly triggered (by the user clicking a rule button, by a task list step, or by the form save event if configured as a “smart push”). For a complete planning data quality framework, both are needed — validation rules catch individual cell-level violations at entry time, and business rules perform cross-entity and cross-period quality checks after the data is saved.
GCC Planning Context
Data validation rules for GCC enterprise planning models frequently incorporate regional compliance constraints. A Saudi entity headcount planning form might include a validation rule that checks whether the planned headcount Saudisation percentage meets the entity’s Nitaqat target band — displaying a warning when the planned workforce composition would result in an unfavourable Nitaqat classification. A UAE entity capital planning form might validate that planned expenditure in free zone entities does not include items restricted under the entity’s free zone licence. These compliance-linked validations convert policy requirements into automated checks within the planning interface, reducing the risk that compliance constraints are overlooked during the budget cycle.
What Goes Wrong in Practice
The most common data validation rule failure is a validation condition that references an account or entity member that was subsequently removed from the application — producing a broken validation rule that neither validates correctly nor fails cleanly. The form loads without error, but the validation rule is silently inactive because its referenced member no longer exists. Data validation rules must be reviewed as part of any dimension structure change that retires or renames the account or entity members that validation conditions reference.
How Loop Wise Solutions Implements Data Validation
We implement data validation rules as part of the planning form specification — documenting each rule’s condition, the dimension intersections it monitors, the rule type (informational, warning, or error), and the message displayed to the planner. Rules are tested with boundary data — values that should pass, values that should trigger warnings, and values that should produce errors — before the form is deployed to the planning user community.
