ChartFields, Rules, and Trees in Combination Editing

The following are general recommendations concerning efficiencies and ChartFields, rules, and trees.

How Many ChartFields to Use

For example, it might be required that only certain departments post to asset, liability, and equity accounts and that other departments post only to revenue and expense accounts. In the first instance, this involves defining editing rules for a combination that includes two ChartFields: Account and Department for department values that are limited to the balance sheet accounts.

You can also limit the departments that can post to income statement accounts to those recording particular product costs by introducing a third ChartField, Product, to the combination definition.

While any number of combinations is possible, limiting the combinations to three or fewer ChartFields optimizes performance.

How Many Combination Rules to Use

Analyze the proposed combination rules and decide which are critical and which are not. The more rules that you implement, the more time that it takes to edit the transactions and maintain the rules.

Ranges of ChartField Values in Trees for Combination Editing Rules

You can use PeopleSoft trees to set up combination edit rules having ranges of ChartField values rather than static values. Ranges of values can make it easier to keep ChartField combination edit rules current with changes in the ChartField values of your organization.

You can use spring, summer and winter trees with combination editing and you can further restrict values available from these trees through the use of tree levels and nodes.