Error Exception Handling

Once you are notified that a transaction has a budget checking error, you have four options for correcting it:

1. Change the transaction.

   Some of the ways you can change the transaction include:

   • Changing the transaction amount.

   • Changing the ChartField combinations.

   • Canceling and rerunning the transaction at a later date.

   • Overriding the budget date.

2. Change the budget.

   Some of the ways you can change the budget include:

   • Adjusting the budget amounts to allow the transactions to pass budget checking.

   • Increasing the budget tolerance.

   • Reopening a closed budget.

   • Modify the control budget definition.

3. Override a budget for the transaction, assuming the exception can be overridden.

4. Override the entire transaction for all affected budgets assuming that all of the lines have overridable exceptions logged against them.

In each case, you must have appropriate security clearance to perform the change or override. And you must rerun budget-checking.

Note:

An override is applicable only to the original entry. After the override, any change or additions to the original journal lines causes the system to cancel the override and reset the header status to (N) not checked. This is to prevent the adding of lines using the same overridden ChartField combination to create unauthorized overrides for different or larger amounts.

See Errors and Warnings.

Security for Adjusting Budgets and Budget Overrides

The security profile of each of your users determines which budgets they can adjust and which budgets, budget dates, and transactions they have the authority to override. You set up this authority when you set up Commitment Control security.

If commitment control security does not allow overrides for a particular user, the Allow Override option at the source transaction type level is irrelevant. Commitment control security supersedes the override option at the source transaction type level.

A user ID and date/time stamp appear on the inquiry pages when a budget or transaction has been overridden, and a warning is generated when the transaction is budget-checked again.

Note:

An override is applicable only to the original entry. After the override, any change or additions to the original journal lines causes the system to cancel the override and reset the header status to (N) not checked. This is to prevent the adding of lines using the same overridden ChartField combination to create unauthorized overrides for different or larger amounts.

Budget Overrides and Transaction Overrides

The transaction exceptions pages contain check boxes for Budget Override and for Transaction Override.

• Budget Override overrides exceptions for a specific budget for which the transaction failed budget checking.

  When a transaction references a budget marked for override for that transaction, every line on that transaction that would have failed the overridden budget passes with a warning flag.

• Transaction Override overrides an entire transaction for all affected budgets. You can select Transaction Override either before budget checking or after budget checking with errors.

  If Commitment Control Security is enabled, a user must be associated with a Super User rule in order to override at the transaction level. If Commitment Control Security is not enabled and the impacted source transaction type allows overrides, then all users can override at the transaction level. In both cases, if the transaction has been budget checked and has errors, the transaction override option on the exception inquiry page is active only if all of the errors are overridable.

  Note:

  An override is applicable only to the original entry. After the override, any change or additions to the original journal lines causes the system to cancel the override and reset the header status to (N) not checked. This is to prevent the adding of lines using the same overridden ChartField combination to create unauthorized overrides for different or larger amounts.