ChartField Definition
All delivered PeopleSoft General Ledger and Project Costing ChartFields are available as key ChartFields for Commitment Control.
Configuring ChartFields for Commitment Control
If the delivered ChartFields do not meet your requirements, you can configure Commitment Control ChartFields for your specific organizational practices.
Budget Reference ChartField
Commitment Control provides a budget reference ChartField that uniquely identifies a budget. The budget reference ChartField enables you to perform comprehensive reporting on budgets that span multiple years and that overlap other multiyear budgets.
Budgetary-Only ChartField Values
When you define a ChartField value and select this option, the ChartField value can be used for budget purposes only and is not available for recording actual transactional entries. With the exception of the affiliate ChartFields, the Budgetary Only option is available for ChartFields supported by Commitment Control.
You usually establish budget control using summary Budgetary Only ChartField values instead of establishing a budget for each detail transactional ChartField value. You then set up ChartField translation trees to roll up the detail transactional-level ChartField values to the summary budgetary ChartField level values.
For example, if Account is a key ChartField, and you budget at a translated level, you designate your budget level accounts as budgetary-only when you define them in the Account component. Budgetary-only accounts are then available for budgeting but unavailable for use at the source transaction level. This prevents users from using high-level roll up accounts in detail transactions.
Commitment Control Override for Account
When you define an Account ChartField value and select this option on the Account page, the Account value is not subject to budget controls and receives an automatic override. Transactions containing account values with the override option will pass budget checking regardless of the control ChartField value and the budget processor issues warnings instead of errors for all exceptions that can be overridden.
Note:
It is important to note that this is only applicable for overrideable errors, such as Exceeds Budget. It does not override errors that cannot be overridden, such as No Budget Exists. This override is similar to the transaction override and requires at least a zero amount budget row to pass edit.