Financial Consolidation and Close Validations

Validations ensure data integrity. The following validations run for Financial Consolidation and Close applications.

In addition to these Financial Consolidation and Close, system and generic validations are run on nodes, hierarchies, viewpoints, and properties in the application. See System Validations and Generic Predefined 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	Source Type	Description	Scope
Account Dynamic Calc	Financial Consolidation and Close	The Traditional and Net Assets seeded account dimension includes Level 0 members that are defined as Dynamic Calc. These members must have at least one member added as a child.	Node
Alias Uniqueness	Planning	Alias are not unique among a group of sibling nodes	Siblings
Cube Data Storage	Planning	Default Data Storage is Shared or Label Only but Data Storage for cube is not Shared or Label Only	Node
Data Storage	Planning	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	Planning	Bottom level node names in a date attribute dimension are not in mm-dd-yyyy format	Node
Default Movement Level	Financial Consolidation and Close	The Default Movement property is defined on a node other than a bottom level node	Node
Dynamic Calc	Financial Consolidation and Close	A level 0 member has Data Storage set to Dynamic Calc but does not have a formula.	Node
Entity Level 0 Data Storage	Financial Consolidation and Close	A level 0 member has a Data Storage value of something other than Store, Never Share, Shared, or Dynamic Calc.	Node
Exchange Rate Type	Planning	Exchange Rate Type is not None and Data Type is not Currency	Node
Formula Allowed	Planning	Data Storage is not Dynamic Calc or Dynamic Calc and Store	Node
Is Default Movement Ancestor	Financial Consolidation and Close	The Is Default Movement property is defined on a node that is not a descendant of FCCS_Mvmts_Subtotal	Viewpoint
Is Default Movement Level	Financial Consolidation and Close	The Is Default Movement property is defined on a node other than a bottom level node	Node
Member Name Conflicts	Planning	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	Planning	Member name is not unique across all nodes used in an application	Application-bound node types
Numeric Attribute Name	Planning	Bottom level node names in a numeric attribute dimension are not in numeric format	Node
Plan Types	Planning	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
Plug Account Data Storage	Financial Consolidation and Close	If an account is designated as a Plug account, then it cannot be a Dynamic Calc account.	Node
Predefined Member	Planning Modules	If the Enterprise Predefined Member property equals True for a node, it can only be moved or reordered. You cannot edit the node or modify the Enterprise Predefined Member property on the node.	Node
Shared Member before Base Member	Planning	Shared members appear above base members in a hierarchy	Viewpoint
Shared Members	Planning	Shared members are not in the same dimension	Application-bound node types
Smart List Required	Planning	Smart List is missing for member if Data Type is Smart List	Node
Source Plan Type	Planning	Source Plan Type is not a valid Plan Type for the member	Node
Store Data Storage	Financial Consolidation and Close	A member has Data Storage set to Store but is not a level 0 member.	Node
Time Balance Flow for Balance Sheet	Financial Consolidation and Close	Time Balance for accounts in the Balance Sheet hierarchy (that is, nodes under the predefined member FCCS_Balance Sheet) is not set to Flow.	Node
Variance Reporting	Planning	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

Note:

Most predefined 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 Fusion Cloud Enterprise Data Management.

The only predefined validations that are run against predefined members are the Predefined Member and Alias Uniqueness validations.

Invalid Characters, First Characters, and Values for Financial Consolidation and Close

When you register a Financial Consolidation and Close 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 Financial Consolidation and Close .

You can edit these values by editing the property parameters. See Editing Property Parameters