Tax Reporting Validations

Validations ensure data integrity. The following validations run for Tax Reporting applications.

Note:

Validations in the external Tax Reporting application are implemented as Recommendations and are not enforced on the simple or classic dimension editors. By default, Tax Reporting validations in Oracle Fusion Cloud Enterprise Data Management are implemented with the Error severity. You can change the severity to Warning. See Configuring Validation Enforcement and Severity.

In addition to these validations, 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
Alias Application Uniqueness Tax Reporting Alias is not unique across the dimensions in the application Bound node types across the application

Alias Uniqueness

 Planning

Alias are not unique among a group of sibling nodes

Siblings
Consolidated ETR (Account dimension only) Tax Reporting Descendants of any of the following nodes have the CETR value assigned to the Consolidated ETR attribute:
  • TRCS_TempGSTotal
  • TRCS_TempSTTotal
  • TRCS_TaxLossesCFSTotal
  • TRCS_TaxCreditTotal
  • TRCS_VATotal
  • TRCS_RTempTotal
  • TRCS_RTaxLossesPreCFSTotal
  • TRCS_RTaxCreditTotal
  • TRCS_RVATotal
  • TRCS_RTaxAttribTotal
 Viewpoint
Cube Data Storage Planning

Default Data Storage is Shared or Label Only but Data Storage for cube is not Shared or Label Only

 Node
Current Additional Total Accounts Shared (Account dimension only) Tax Reporting Bottom node descendants of TRCS_CurrentAddtlTotal must also be shared descendants of TRCS_CurrentAddtlETRTotal Viewpoint

Data Storage

 Planning

Only one instance of a node can be set to non-shared data storage. All other instances of the node must be Shared.

 Viewpoint

Date Attribute Name

 Planning

Bottom level node names in a date attribute dimension are not in mm-dd-yyyy format

Property
Domicile (Entity dimension only) Tax Reporting Domicile has to be set for all bottom node entities and also for the parent entities which have Parent Tax calculation enabled. Viewpoint

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
Intercompany Entity Validation (Entity dimension only) Tax Reporting Intercompany should be set on bottom entities only

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

 Bound node types across the application
NCI Account (Account dimension only) Tax Reporting NCI Account should only be set on a Permanent Difference Stat to Tax or GAAP to Stat Account

Node

Numeric Attribute Name

 Planning

Bottom level node names in a numeric attribute dimension are not in numeric format

Property

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 Accounts (Account dimension only) Tax Reporting Intercompany Account must be Yes and Is Plug Account must not be set to define a Plug 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

 Tax Reporting Shared members appear above base members in a hierarchy Viewpoint
Single NCI Account (Account dimension only) Tax Reporting At most one tax account should have the NCI Account set Viewpoint

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
Tax Data and Tax Data Type (Account dimension only) Tax Reporting Bottom node descendants of TRCS_TaxAccounts must have both the Tax Type and Tax Data Type attributes assigned. Viewpoint

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
Weighted Ownership Account (Account dimension only) Tax Reporting At most one tax account should have the Weighted Ownership Account set. Viewpoint

Invalid Characters, First Characters, and Values for Tax Reporting

When you register a Tax Reporting 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 Restrictions for Dimensions, Members, Aliases, and Forms in Administering Tax Reporting

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