Predefined Validations
Predefined validations are created automatically when you register an application, and they enforce the requirements for the external system based on the application type or Oracle Fusion Cloud Enterprise Data Management requirements.
For example, when you register a Planning application, a predefined validation ensures that member names are unique across all nodes used in the application, and when you register a Financials Cloud General Ledger application, a predefined validation ensures that node end date is after its start date.
There are two types of predefined validations:
- Application-specific predefined validations apply only to specific types of applications. Most application-specific predefined validations are enforced on bound data in a dimension. They are enabled by default, but you can disable them or set the severity level at the dimension level (see Configuring Validation Enforcement and Severity).
- Generic predefined validations apply to all types of applications except Users applications. You can enable and disable them on the Validations tab of the dimension inspector. See Configuring Validation Enforcement and Severity.
Source Application Types for Validations
All predefined validations have a source application type which identifies the type of application the validation originated from. Applications can have predefined validations from multiple source types.
Planning validations represent the basic Cloud EPM Platform validations. Other Cloud EPM application types will therefore have validations with the Planning source type, as well as their own validations. For example, a Financial Consolidation and Close application has validations with Planning source types (such as Alias Uniqueness) as well as validations with Financial Consolidation and Close type (such as Default Movement Level).
Application-specific Predefined Validations
For details about the application-specific predefined validations that are created for each application type, see:
- Planning and FreeForm Validations
- Financial Consolidation and Close Validations
- Enterprise Profitability and Cost Management Validations
- Tax Reporting Validations
- Oracle Financials Cloud General Ledger Validations
- E-Business Suite General Ledger Validations
Generic Predefined Validations
When you register any application type other than Users applications, these validations are automatically created for that application:
Note:
All generic validations are disabled by default.Table 23-5 Generic Validations
| Name | Description | Scope |
|---|---|---|
| Duplicate Name Check Against In Flight Requests | When adding or renaming a node, checks to see
if there are any In Flight, Blocked, or Future
Dated requests that contain request items to add
or rename a node with the same name.
Note: This validation can be enforced during the Request Submit and Request Approve stages only. See Configuring Validation Enforcement and Severity. |
Node and In Flight requests |
| 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. | 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. |
Node and user node |
| Previously Merged Node | Nodes that are added in the viewpoint cannot have the same name as nodes that were previously merged as part of the matching process. See Working with Matching and Deduplication. | Node |