This chapter provides an overview of auditing and repairing trees and discusses how to:
Use the Repair Tree program.
Review audit results.
Review individual reports.
Tree repairs should be performed on trees that are having problems or have had major changes made to them.
Before using the repair programs, you should first run audits to learn which trees, if any have problems and which utility will repair the damaged tree. Review the audit reports to determine the correct solution for repairing your tree. You may need to run more than one utility program.
The Repair Tree program is designed for administrators who need a wide range of utilities with which to work. Besides containing various utilities for repairing trees, the Repair Tree program also includes the Tree Audits utility.
The Tree Auditor program is only the Tree Audits utility, and is designed for users who only need to audit trees.
Running the utility programs may result in a large number of updates to the tree. Because the system automatically puts a lock on a tree while the process is running, you should run these programs during off-work hours, to lower the risk of users trying to access the tree.
You should also perform a backup of your tree tables before running the repair programs.
Note. If you expect that saving a tree will take an especially long time due to an audit running as a part of saving process or on account of large, memory-intensive trees, PeopleSoft recommends that you save the trees as drafts, then run the audits with Application Engine using the Repair Tree or Tree Auditor programs. After the audits have completed without finding any problems the tree status will be automatically changed to Valid Tree.
Use the Repair Tree Application Engine program to both audit and repair trees.
Note. You can also use the Tree Auditor Application Engine program to audit trees.
Access the Repair Tree page.
The following table lists the types of audits performed from the Repair Tree program. These audits differ from those performed on the Tree Definition and Properties page.
Audit Type |
Checks For |
Purpose |
Orphan tree leaves. |
Lists detail values that refer to an invalid tree node number. |
|
Detail Values |
Detail values not found in the tree. |
Lists any detail values that are found in application table but are not defined in the tree. This audit is only performed if the All Detail Values check box, on the tree’s Definition and Properties page is selected. |
Detail Values |
Duplicate detail values. |
Lists any detail values that are defined more than once in the tree. This audit is only performed if the Allow Duplicate Detail Values check box, on the tree’s Definition and Properties page is cleared. |
Detail Values |
Detail values with overlapping ranges. |
Lists detail values that are defined as a range of values that overlap another detail value’s range of values. This audit is only performed if the Allow Duplicate Detail Values check box, on the tree’s Definition and Properties page is cleared. |
Detail Values |
Nodes with no child nodes or detail values specified. |
Lists any nodes that do not have any detail values or child nodes defined. This audit is performed for detail value trees only. |
Nodes without a parent. |
Lists tree nodes that refer to an invalid tree node number. |
|
Node Audit |
Tree node numbers that are greater than end numbers. |
Lists tree nodes with end numbers greater than the node number. |
Node Audit |
Tree node end numbers that are greater than the parent’s end number. |
Lists tree nodes with end numbers greater than the parent node's end number. |
Node Audit |
Tree nodes with overlapping ranges. |
Lists tree nodes whose node number and ending node number overlaps with another range of node numbers. Note. When this occurs the tree is corrupted. |
Node Audit |
Node level numbers that are less than the parent node’s level number. |
Lists any tree node with level numbers less than the parent's level number. |
A level record name in the Tree Structure table that does not exist in Record Definition table. |
Lists tree structures that reference an invalid record name for the tree level application data. |
|
Structure Audit |
A node record name in the Tree Structure table that does not exist in Record Definition table. |
Lists tree structures that reference an invalid record name for the tree node application data. |
Structure Audit |
A detail record name in the Tree Structure table that does not exist in Record Definition table. |
Lists tree structures that reference an invalid record name for the tree detail values application data. |
Structure Audit |
A missing tree structure record. |
Lists any trees that refer to a tree structure that is not found in the Tree Structure table. |
See Also
Select Reports with Data to list only those reports that contains data. This is the default. Select All Reports to list all reports. |
|
Lists each available report, with report title and total row count. Click Select to access each report. The Select link is inactive for reports with zero row count. |
Access a report page by clicking its Select link.
Reports contain the following information:
Instructions and recommendations on how to correct the problem.
Tree identifying information, if more than one tree is affected. This includes:
SetID.
Set control value.
Tree name.
Effective date.
Node information for the affected nodes, which might include:
Node name.
Node number.
Node end number.
Parent node.
Parent node number.
Parent level number.
Range from.
Range to.
Details on fixing problems associated with reports are given below.
Parent Node Does Not Exist
If there are no other audit errors for this tree, then running the Correct Parent Node Numbers utility program should correct this problem.
Do not run the Correct Parent Node Numbers utility program if there are other audit problems with this tree. The other errors should be addressed first before trying to correct problems by running the utility program.
Run the Delete Orphan Tree Objects utility to delete these records.
Tree Node Numbers Are Greater Than End Number
Use PeopleSoft Tree Manager to delete these nodes and then run the Reset Tree Node Gaps utility program. You will then need to use PeopleSoft Tree Manager to reinsert the problem nodes.
Note. Deleting a node causes all of its children to be deleted. Therefore, if the problem node has child nodes or leaves under it, you will have to recapture those as well. If it is not possible to use PeopleSoft Tree Manager to delete the problem nodes, call the PeopleSoft Support Center for help to analyze this problem.
Tree Node’s End Number Is Greater Than Parent’s End Number
Use PeopleSoft Tree Manager to delete these nodes and then run the Reset Tree Node Gaps utility program. You will then need to use PeopleSoft Tree Manager to reinsert the problem nodes.
Tree Nodes with Overlapping Ranges
Use PeopleSoft Tree Manager to delete these nodes and then run the Reset Tree Node Gaps utility program. You will then need to use PeopleSoft Tree Manager to reinsert the problem nodes.
Node’s Level Number Is Less Than Parent’s Level Number
The level numbers can be corrected by either:
Switching the levels in PeopleSoft Tree Manager.
Running the Correct Level Numbers utility to reset all invalid level numbers on the tree.