1. Administering and Working with Oracle Enterprise Data Management Cloud
  2. Administration
  3. Understanding Validations and Constraints
  4. Working with Application Specific and Generic Validations

Working with Application Specific and Generic Validations

Application Specific Validations

Application specific validations are validations that apply to a specific application type. For example, Planning specific validations are created automatically when you register a Planning application. For details about the validations that are created for each application type, see:

Generic Validations

Generic validations are validations that apply to all application types except for Users applications. When you register any application type other than Users applications, these validations are automatically created for that application:

Table 21-5 Generic Validations

Name Description Scope
Equivalent Nodes with Filter All nodes in this viewpoint that match a specified filter expression (or all nodes, if there is no filter expression) must exist in all related viewpoints in at least one location. See Configuring Related Viewpoints.

This validation is disabled by default.

 Related Viewpoints
Ownership Approval Permission

An ownership approval property for a node refers to a user who does not have at least Participant (Read) access to the viewpoint. See Understanding Ownership Approvals.

This validation is disabled by default.

 Node and user node

Managing Enforcement and Severity of Validations

By default, all application specific and generic validations are enforced with a severity of Error. You can change the severity or disable each validation at the dimension level. Disabled validations are no longer run for data in the dimension.

To manage the enforcement and severity of validations:

  1. Inspect the dimension that you want to manage a validation for. See Inspecting Dimensions.
  2. Select the Validations tab to view the predefined validations that are run on that dimension.
  3. Click Edit.
  4. To enable or disable a validation, select or clear the Enabled check box.
  5. To modify the validation severity, click Edit Validation Settings edit validation settings icon and then select the severity for the validation (Error, Warning, Ignore) at the Request Submit, Approve, Commit, and Viewpoint Validate and Export stages.

    See Understanding Validation Severity.

  6. Click Save.

Note:

For Oracle Financials Cloud General Ledger and Oracle E-Business Suite General Ledger applications, if the validation for upper case node names should not be enforced, then in addition to disabling the Uppercase Node Name validation at the application level you must also update the Case setting for Core.Name property at the override level. See Editing Property Parameters.