Example of Setting the Control Budget Filter
This example illustrates how to use the Control Budget Filter to determine how the budgetary control engine processes transactions associated with a ledger, project, or both.
When a ledger or business unit is enabled for budgetary control, the budgetary control engine evaluates the transactions to determine which control budget to use for checking the funds available balance.
Scenario
You have defined the following control budgets for VC (Vision City):
Control Budget |
Ledger |
Project |
Award |
---|---|---|---|
VC Ops |
Vision City Operations |
Any or no project on the transaction |
|
VC Ops Administration |
Vision City Operations |
No project on the transaction |
|
VC Ops Park Swings |
Vision City Operations |
Park Swings |
2016 |
VC Ops OOW Conference |
Vision City Operations |
OOW Conference |
Any or no award assigned to the project |
These control budgets can only be defined when the Control Budget Filter assigned to the Vision City Operations ledger is the value as shown in the following table:
Control Budget |
Ledger Only |
Project |
Ledger or Project |
---|---|---|---|
VC Ops |
Yes |
No |
Yes |
VC Ops Administration |
No |
Yes |
Yes |
VC Ops Park Swings |
No |
Yes |
Yes |
VC Ops OOW Conference |
No |
Yes |
Yes |
Resulting Applicable Control Budgets
When you enter a transaction, the budgetary control engine uses the ledger and project values to determine if any control budgets are applicable, as shown in the following table:
Transaction Number |
Ledger |
Project |
Award |
VC Ops |
VC Ops Administration |
VC Ops Park Swings |
VC Ops OOW Conference |
---|---|---|---|---|---|---|---|
101 |
Vision City Operations |
Yes |
Yes |
No |
No |
||
102 |
Vision City Operations |
Park Swings |
2016 |
Yes |
No |
Yes |
No |
103 |
Vision City Operations |
OOW Conference |
Yes |
No |
No |
Yes |
|
104 |
Vision City Capital |
Park Swings |
2016 |
No |
No |
No |
No |
105 |
Vision City Capital |
No |
No |
No |
No |