Planning and FreeForm Validations
Validations ensure data integrity. The following validations run for Planning, FreeForm, and Planning Modules applications.
In addition to these Planning and FreeForm validations, system and generic validations are run on nodes, hierarchies, viewpoints, and properties in the application. See System Validations and Generic Validations.
Note:
For validations with a scope of Viewpoint in the table below, for hierarchy-set bound viewpoints the validation is run for the bound viewpoint.Name | Description | Scope |
---|---|---|
Alias Uniqueness |
Alias are not unique among a group of sibling nodes |
Siblings |
Cube Data Storage |
Default Data Storage is Shared or Label Only but Data Storage for cube is not Shared or Label Only |
Node |
Data Storage |
Default Data Storage is Shared or Label Only but Data Storage for cube is not Shared or Label Only Note: This is not checked if the member is not in the cube. |
Viewpoint |
Date Attribute Name |
Bottom level node names in a date attribute dimension are not in
|
Node |
Exchange Rate Type |
Exchange Rate Type is not None and Data Type is not Currency |
Node |
Formula Allowed |
Data Storage is not Dynamic Calc or Dynamic Calc and Store |
Node |
Member Name Conflicts |
Member name is the same as a dimension name, a cube, or an attribute dimension defined for the current application |
Node and data chain |
Name Uniqueness |
Member name is not unique across all nodes used in an application |
Application-bound node types |
Numeric Attribute Name |
Bottom level node names in a numeric attribute dimension are not in numeric format |
Node |
Plan Types |
Plan Type is set to True but the parent does not have a True value Note: This validation is skipped if the parent is a predefined member. |
Viewpoint |
Shared Member before Base Member |
Shared members appear above base members in a hierarchy | Viewpoint |
Shared Members |
Shared members are not in the same dimension |
Application-bound node types |
Smart List Required |
Smart List is missing for member if Data Type is Smart List |
Node |
Source Plan Type |
Source Plan Type is not a valid Plan Type for the member |
Node |
Variance Reporting |
Variance Reporting is not Expense when Account Type is Expense or Variance Reporting is Non-Expense if Account Type is anything other than Expense or Saved Assumption. |
Node |
The following validations run for Planning Modules applications only.
Name | Description | Scope |
---|---|---|
Predefined Member |
You cannot edit the Predefined Member node or property |
Node |
Note:
In Planning Modules applications, most application-specific validations are not run against predefined members (that is, nodes with PLN.Enterprise Predefined Member set to True), because these members are imported from the external application and are not able to be edited in Oracle Enterprise Data Management Cloud.
The only application-specific validations that are run against predefined members in Planning Modules applications are the Predefined Member Edit, Predefined Member Property, and Alias Uniqueness validations.
Note:
The Source Plan Type, Formula Allowed, and Plan Type validations are not checked on shared nodes (Data Storage = shared). The imports and exports at the application level transform these values as required by Planning and Planning Modules.
Invalid Characters, First Characters, and Values for Planning and FreeForm
When you register a Planning
or FreeForm application,
validations for invalid characters, first characters, and values are automatically
configured for the Core.Name
and Alias
properties.
For a list of these characters and values, see Naming Restrictions for
Dimensions, Members, and Aliases in Administering Planning .
You can edit these values by editing the property parameters. See Editing Property Parameters