Errors and Warnings

Exceptions fall into two categories: errors and warnings.

Errors

Errors are exceptions that have failed budget checking because they do not conform to the rules established for that control budget. Transactions with errors are not allowed by the system to update the Commitment Control budget ledgers. Most errors occur when a transaction has at least one line that exceeds at least one budget and is over tolerance. Depending on the configuration of your control budgets, the exact reason that a budget has insufficient funds will vary from budget to budget. The budget may be on hold, closed, or simply lacking a sufficient available budget amount.

Transactions with errors stop at the budget check stage and do not proceed until they are corrected or overridden and are budget checked again.

These are errors that you might encounter:

Error Code Overridable? Description Notes

E1

Y

Exceeds budget and is over tolerance.

N/A

E2

N

No budget exists.

N/A

E3

N

Budget is closed.

N/A

E4

Y

Budget is on hold.

N/A

E5

N

Transaction has offset account.

The transaction line contains an account value that is reserved as an offset account.

E6

Y

Budget date is out of bounds.

N/A

E7

Y

Spending authority over budget.

Credit transaction caused spending authority (available budget balance) to exceed original budgeted amount.

This error does not occur if you selected Allow Increased Spending Authority for the control budget definition on the Ledgers for a Unit - Commitment Control Options page.

See Adding Commitment Control Ledger Groups to a Business Unit.

E8

N

CF (ChartField) funding source error.

A funding source allocation row for a funding source enabled budget exists without a corresponding budget amount having been entered in the Commitment Control ledger data table (LEDGER_KK).

See Project Costing and Control Budgets with Funding Source.

E9

N

Cumulative calendar data not found.

Budget is defined for cumulative budgeting with a cumulative calendar, but the calendar is not found.

See Budget Period Calendars and Cumulative Budgeting.

E10

N

Cumulative date range not found.

Budget is defined for cumulative budgeting with a cumulative date range, but the date range is not found.

E11

Y

Exceeds budget and is over tolerance for referenced budget.

When a transaction (such as a voucher) and its referenced documents (such as purchase orders) impact different budgets, the Budget Processor budget-checks the liquidation rows for the referenced documents separately from the transaction itself. Errors E11 through E20, E23 through E26, E30, E32, and E37 occur for the referenced (liquidation) row.

See Budget Processor.

E12

N

No budget exists for referenced budget.

See E11.

E13

N

Budget is closed for referenced budget.

See E11.

E14

Y

Budget is on hold for referenced budget.

See E11.

E15

N

Transaction has offset account for referenced budget.

See E11.

E16

Y

Budget date is out of bounds for referenced budget.

See E11.

E17

Y

Spending authority over budget for referenced budget.

See E7, E11.

E18

N

CF (ChartField) funding source error for referenced budget.

See E8, E11.

E19

N

Cumulative calendar data not found for referenced budget.

See E9, E11.

E20

N

Cumulative date range not found for referenced budget.

See E10, E11.

E21

Y

Exceeds statistical budget and is over tolerance.

Occurs for budgets with statistical budgeting enabled.

See Statistical Budgeting.

E22

N

Statistical budget does not exist.

See E21.

E23

Y

Exceeds statistical budget and is over tolerance for referenced row.

See E21.

E24

N

Statistical budget does not exist for referenced row.

See E11, E21.

E25

Y

Spending authority over statistical budget for referenced row.

See E7, E11, E21.

E26

N

Ledger definition data not found for referenced row.

See E11.

E27

Y

Spending authority over statistical budget.

See E7, E21.

E28

N

Referenced document has been finalized.

The transaction (such as a voucher) has a referenced document (such as a purchase order) that has already been fully liquidated.

E29

N

Funding source allocation not found.

There are no funding source allocations for the funding source enabled budget related to the transaction.

See Project Costing and Control Budgets with Funding Source.

E30

N

Funding source allocation not found for referenced budget.

See E11, E29.

E31

N

Current budget period not in cumulative range.

Cumulative budgeting has been set up incorrectly for the budget, such that a budget period defined as part of the cumulative range does not, in fact, fall within the cumulative range.

For example, assume that you set up cumulative budgeting for the date range of 01/01/20X2 through 02/28/20X2 and include monthly budget periods 20X2M1 (covering January), 20X2M2 (covering February), and 20X2M3 (covering March). The budget period 20X2M3 does not fall within the cumulative date rage, and an error results when you budget-check a transaction whose budget date falls within budget period 20X2M3.

See Budget Period Calendars and Cumulative Budgeting.

E32

N

Current budget period not in cumulative range for referenced row.

See E11, E31.

E33

Y

Funding is expired.

The budget date on the transaction line is beyond the expiration date specified on the Expiration CF (ChartField) page within the budget definition and the transaction line is attempting to reduce the budget's remaining spending authority.

E34

Y

Budget date outside specified dates.

The budget date on the transaction line is outside either the begin or end date specified on the Expiration CF (ChartField) page within the budget definition.

E35

N

Required key CF (ChartField) is blank.

Value Required option is set to Required for this key CF (ChartField) on Budget Definitions - Keys and Translations page, but on the transaction line this CF (ChartField) does not have a value.

E36

N

ChartField combination errors exist.

The budget journal line violates the ChartField combination rules.

E37

Y

Statistical budget is on hold for referenced budget.

See E11.

E38

Y

Statistical budget is on hold.

N/A

E40

N

Statistical budget is not enabled on the budget definition.

Apply to budget journal edit.

E42

N

Transaction has account that belongs to an excluded account type.

The budget journal line contains an account value that belongs to an excluded account type.

E43

N

Transaction has excluded account.

The budget journal line contains an account value that is excluded from commitment control.

E44

N

Budget period is invalid.

Apply to budget journal edit.

E45

N

Non key CF (ChartField) has a value.

Non key CF (ChartField) on the budget journal line should be blank.

E46

N

Invalid ChartField value.

The budget journal line contains invalid ChartField value.

E47

N

ChartField value not valid for budget.

The budget journal line contains invalid ChartField value for budget.

E48

N

CF (ChartField) value not at tree level.

The budget journal line contains a ChartField value not at the defined tree level.

E49

N

Key ChartField is blank.

Key ChartField on the budget journal line is blank.

E50

N

Child budget exceeds the parent budget.

Applies to child budget journal edit when Child Budgets Exceed Option is not checked on Budget Definitions - Control Budget Options page.

The Budget Processor issues this error when processing a child budget journal having a child budget ledger group.

E51

N

Child budget exceeds the parent budget.

Applies to parent budget journal edit when Child Budgets Exceed Option is not checked on Budget Definitions - Control Budget Options page.

The Budget Processor issues this error when processing parent budget journal having the parent budget ledger group.

E52

N

Invalid ledger value.

N/A

E54

N

FS Allocation not defined

Funding source allocation is not defined.

E57

N

Entry Event value is required.

Entry Event value is blank on the budget journal line when Entry Event is set to Required on Installation Options - Entry Event page.

E58

N

Entry Event should be blank.

Entry Event value is not blank on the budget journal line.

E59

N

Invalid Entry Event code.

The budget journal line contains an invalid Entry Event code.

E60

N

Funding Source allocations are not yet completed.

Funding Source allocation errors exist.

E61

Y

The Funding Source does not have enough funding.

The Funding Source does not have enough funding to cover the expense on the control ChartField when the control option is Control or Control Initial Document on initial document.

E62

N

The amount of credit transaction is over the Overall Amount.

The amount of credit transaction is over the Overall Amount defined on the funding source allocation page.

E63

N

Funding Source value is required.

Applies to budget journal edit.

E64

N

Parent budget does not exist.

Applies to budget journal edit.

E65

N

Exceeds funding source allocation amount.

Applies to budget journal edit.

E66

N

Funding Source value should be blank.

Applies to budget journal edit.

E67

N

Budget Date is null.

Applies to budget journal edit.

E90

N

Invalid budget definition.

N/A

E91

N

Translation tree error found.

N/A

E92

N

SetID error found.

N/A

E96

N

Budget period not found.

N/A

E97

N

Budget definition not found.

N/A

E98

N

No fiscal year calendar found.

N/A

E99

N

Invalid parent/child reference.

Applies to budget journal edit.

Warnings

Warnings are exceptions that do not conform to the rules of the control budget, but have been passed along and update the Commitment Control ledgers nonetheless. Warnings function as exceptions that are automatically overridden, as well as alerts to certain situations that could adversely impact the budget and budgetary processing.

The Budget Processor issues warnings, rather than errors, in the following situations:

  1. The system inherently defines the transaction exception as a warning.

    This is the case, for example, with the warning that the budget date does not equal the accounting date and the warning that the transaction exceeds the remaining available budget but is within tolerance.

  2. The control option for the control budget definition is Track with Budget, or Control Initial Document.

    If you selected one of these options when you defined your budgets, you determined that transactions that would otherwise generate an error exception merely require an audit trail and examination and do not need to be stopped.

    If the control option is Track with Budget, you receive warning exceptions, except when there is no budget for a transaction, which results in an error exception. If the control option is Control Initial Document, you receive error exceptions for the initial document and warning exceptions for subsequent transactions.

    Note:

    Whether the option is Track without Budget or Track with Budget, you receive warnings for any error that can be overridden; however, errors that cannot be overridden might be logged.

    Also note that commitment control detail ledger groups, which by definition are set to track without budget, do not receive budget exceeds warnings.

These are the warnings:

Warning Code Description Notes

W1

Exceeds budget but is within tolerance.

Transaction exceeds available budget balance, but is within the tolerance allowed.

See Hierarchy of Control Budget Attributes.

W2

Exceeds budget, but is a track or non-initial transaction.

Transaction exceeds budget, but the control option for the control budget definition is Tracking with Budget, Tracking without Budget, or Control Initial Document.

For tracking without budget, no warning is issued for detail tracking ledger groups. If it is not a detail tracking ledger group and a budget row exists, even if it is for a zero amount, a W2 warning is issued if the transaction exceeds the available spending. If no budget row exists, no warning is issued.

See Hierarchy of Control Budget Attributes.

W4

Override of the error of Exceeds budget and is over tolerance.

Overrides always generate warnings.

W5

SA (spending authority) exceeds non-control budget amount.

Credit transaction caused spending authority (available budget balance) to exceed original budgeted amount for a budget whose control option is Tracking with Budget, or Tracking without Budget, or Control Initial Document.

This warning does not occur if you selected Allow Increased Spending Authority for the control budget definition on the Ledgers for a Unit - Commitment Control Options page.

See W2.

See Adding Commitment Control Ledger Groups to a Business Unit.

W6

Override of the error of SA (spending authority) exceeds budgeted amount.

See W4.

W7

Override of the error of Budget is on hold.

See W4.

W8

Override of the error of Budget Date is out of bounds.

See W4.

W9

Closed budget periods exist in cumulative set.

One or more budget periods within a cumulative budgeting set has been closed.

See Budget Period Calendars and Cumulative Budgeting.

W10

Override of the error of Statistical budget is on hold.

N/A

W21

Exceeds statistical budget but is within tolerance.

See W1.

See Statistical Budgeting.

W22

Exceeds non-control statistical budget.

See W2, W21.

W24

Override of the error of exceeds statistical budget.

See W4.

W25

SA (spending authority) exceeds non-control statistical budget amount.

See W5, W21.

W26

Override of the error of SA (spending authority) exceeds statistical budget amount.

See W4.

W27

No liquidation on statistical amount due to different statistics code.

Warning is issued when a transaction (such as a voucher) and its referenced document (such as a purchase order) have different statistics code, so that the liquidation of the referenced document does not occur.

W33

Override of the error of Funding is expired.

Warning is issued if you override the E33 exception

W34

Budget date outside dates specified on the Expiration CF (ChartField) page.

Warning is issued if you override the E34 exception.

W35

Associated expenditure budget is below zero.

Warning is issued if a reduction in revenue causes the remaining spending available for an associated expenditure budget inclusive of tolerances to fall below zero.

W36

Required key CF (Chartfield) is blank.

Warning is issued if the control option is Tracking without Budget.

W37

Associated statistical expenditure budget is below zero.

Warning is issued if a reduction in revenue causes the remaining spending available for an associated statistical expenditure budget inclusive of tolerances to fall below zero.

W38

Funding is expired.

The budget date on the transaction line is beyond the expiration date specified on the Expiration CF (ChartField) page within the budget definition and the transaction line is attempting to increase (put money back into) the budget's remaining spending authority.

W57

Entry Event code is blank.

Warning is issued when Entry Event value is blank on the budget journal line and Entry Event is set to Optional on Installation Options - Entry Event page.

W61

Override of error for Funding Source does not have enough funding.

N/A

W62

Exceeds available funding.

Warning is issued when the Funding Source does not have enough funding to cover the expense on the control ChartField and the control option is Tracking with Budget, Tracking without Budget, or Control Initial Document on non-initial document.

W63

The amount of a credit transaction is over the total funding source spending.

N/A

W64

Parent does not exist.

Warning is issued when the Child Budgets Exceed Option is checked on Budget Definitions - Control Budget Options page.

Note:

Early warnings, or notifications that a predefined percentage of a budget has been committed for spending or spent, are not exceptions. You set them up on the Notify Preferences page.

Related Topics