Defining Translation Trees for Budget Key ChartFields

Include the following steps when you define translation trees for key ChartFields:

1. Assign the detail table name as the tree node table in the tree structure.

   Each node must be a valid ChartField value, and you cannot use general labels such as ALLACCTS or ASSETS. For the account tree, or any tree based on a fully configurable ChartField, you can take advantage of the Budgetary Use Only check box and use a view selecting accounts with budgetary-use only value of y as the tree node table.

2. On the Tree Definitions and Properties page:

   1. Select the COMMITMENT CONTROL category.

   2. Deselect the All Detail Values in this Tree and Allow Duplicate Detail Values check boxes.

   3. Select Strictly Enforced levels.

3. When you define levels, deselect the All Values box for all but the first level.

   Warning! Level names cannot contain spaces.

4. After you define a tree, run the Budgetary Control Tree Audit (GLS8007) report to validate:

   • The tree structure and tree definition settings.

   • That all ChartField values are defined on the tree or represented by a detail node range.

   For more information, see Commitment Control Budgetary Control Tree Audit Page below.

Use the Commitment Control Budgetary Control Tree Audit page (RUN_GLS8007) to run the Commitment Control Budgetary Control Tree Audit SQR (GLS8007) report, which audits all budget key ChartField translation trees for completeness and accuracy. The report verifies the tree structure and definition options and identifies all ChartField values that are not defined as tree nodes or represented as tree details.

Navigation:

Commitment Control > Budget Reports > Budgetary Control Tree Audit > Commitment Control Budgetary Control Tree Audit

Run the report when you add new ChartField values. Also run the report periodically to make sure that all ChartFields are represented in the appropriate tree.

You must have a tree for each ChartField that you use as a budget key and that you want to translate.

The budget processor references the version of the tree that has the greatest effective date that is before or equal to the budget definitions effective date that is used to process a particular transaction. The budget definition's effective date is based on the budget date that is specified on every source transaction line.

The budget processor looks to the latest translation tree, that is, the tree with the latest effective date, to determine whether it is active or inactive when the processor is processing transactions with dates after the latest effective-dated tree. For example, assume that you have a tree for which the initial effective date is January 1, 1900 and its status is active. If you then create a tree for February 1, 2005 and set the status to inactive, the budget processor still looks to the latest tree with the effective date of February 1, 2005 for any transactions dated later than February 1, 2005. Under these conditions, the budget processor would not process using the active tree dated January 1, 1900, but would issue a message that an invalid tree exists because the February 1, 2005 tree is inactive.