Tree Structure Audit Results

Use the tree structure audit results to verify the tree structure's correctness and data integrity. The audit results include the following details:

  • The name of the validator, which is a specific validation check

  • The result of the validation, including a detailed message

  • Corrective actions to take if there are any validation errors

Running an Audit

Setting the status of a tree structure to active automatically triggers an audit of that tree structure. To manually trigger an audit, select Audit from the Actions menu on the Manage Tree Structures page. The Tree Structure Audit Result table shows a list of validations that ran against the selected tree structure.

Audit Validators

The following table lists the validators used in the audit process and describes what each validator checks for. It also lists possible causes for validation errors and suggests corrective actions.

Validator

Page

Description (what's validated)

Possible Cause for Validation Failure

Suggested Corrective Action

Restrict By Set ID

Manage Tree Structures: Specify Data Sources

If you select the Reference Data Set check box for the Restrict Tree Node List of Values Based on option, each of its data source view objects must have a reference data set attribute.

Even when the check box is selected, one or more data source view objects doesn't contain a reference data set attribute.

If reference data set restriction is required for this tree structure, include a reference data set attribute on all data sources. Otherwise, deselect the check box.

Available Label Data Sources

Manage Tree Structures: Specify Data Sources

If you select a list item from Labeling Scheme to specify a labeling scheme, the label data source view object specified for each data source must be accessible. Also, the primary keys must be valid. This restriction doesn't apply if you select None from the list.

  • Any of the specified label data source view objects doesn't exist.

  • Any of the specified label data source view objects doesn't have primary keys.

  • When a label data source view object is initially defined, the database registers the primary keys for the view object. If the view object is later modified such that its primary keys no longer match the primary keys that were registered earlier, this validation fails.

  • Correct the specified label data source view object.

  • Correct the primary keys of the specified label data source view object.

  • Do one of the following:

    • Correct the primary keys in the label data source view object to match the primary keys that were earlier registered in FND_TS_DATA_SOURCE.

    • Correct the primary keys registered in that table to match the new view object definition.

Row Flattened Table Name

Manage Tree Structures: Specify Performance Options

You must specify a valid row flattened table for the tree structure. It can either be the standard row flattened table FND_TREE_NODE_RF or another table.

  • The specified table doesn't exist in the database.

  • The specified table doesn't contain the same columns as the FND_TREE_NODE_RF table.

Correct the row flattened table definition.

Available Data Sources

Add Data Source

Each data source view object specified for the tree structure must be accessible, and all its primary key attributes must be valid.

  • Any of the specified data source view objects doesn't exist.

  • When you define a data source view object, keep the Use non-defined primary key columns check box deselected. The database automatically registers the primary keys for the view object. Select this check box if you want the database to register the primary keys you specify. However, if the registered primary keys contain any duplicates, this validation fails.

  • The Use non-defined primary key columns check box is selected in a data source, but the list of specified primary key columns doesn't match the primary keys defined in the corresponding data source view object.

  • Any common attribute that exists in both the data source view object and the tree node view object isn't of the same data type in both view objects.

  • Correct the specified data source view object.

  • Correct the duplicate column in the registered primary keys.

  • Correct the primary keys of the specified data source view object.

  • Correct any mismatch in data types.

Column Flattened Table Name

Manage Tree Structures: Specify Performance Options

You must specify a valid column flattened table for the tree structure. It can either be the standard row flattened table FND_TREE_NODE_CF or another table.

  • The specified table doesn't exist in the database.

  • The specified table doesn't contain the same columns as the FND_TREE_NODE_CF table.

Correct the column flattened table definition.

Restrict by Date

Manage Tree Structures: Specify Data Sources

If you select the Date Range check box for the Restrict Tree Node List of Values Based on option for a tree structure, each of its data source view objects must have effective start date and end date attributes. This validation doesn't take place when the check box isn't selected.

Even when the check box is selected, one or more of its data source view objects doesn't contain effective start date and end date attributes.

If the date restriction is required for this tree structure, include the effective start date and effective end date attributes on all data sources. Otherwise, deselect the check box.

Tree Node Table Name

Manage Tree Structures: Specify Definition

You must specify a valid tree node table for the tree structure. It can either be the standard row flattened table FND_TREE_NODE or another table.

  • No table is specified in the Tree Node Table field.

  • The specified table doesn't exist in the database.

  • The specified table doesn't contain the same columns as the FND_TREE_NODE table.

Correct the tree node table definition.