Enable Budgetary Control
You enable budgetary control for ledgers, business units assigned to a ledger, projects, transaction types, and journal sources and categories. The options you select can have critical implications in the way Oracle Fusion Budgetary Control handles your transactions.
When you enable budgetary control, you must consider these options:
-
Control Budget Filter
-
Fail Budgetary Control for Budget Dates Not in Valid Budget Date Range
-
Default Date Rule
Control Budget Filter
To determine how the budgetary control engine processes transactions, use the Control Budget Filter option . Transaction processing is based on one of these options:
-
Ledger only
-
Project
-
Ledger or project
When you enable a ledger or business unit for budgetary control, the budgetary control engine evaluates the transactions and the control budget filter value. It then determines which control budget to use for checking the funds available balance.
Budgetary Control Validation Failures
Transaction Budget Date Fails Outside of Date Range Across All Control Budgets
Budget dates can either pass or fail budgetary control validation. These validations are based on whether they're within the period range of control budgets that are past the defining stage and aren't permanently closed.
By default, Budgetary Control allows transactions with budget dates outside of control budget periods to pass validation. To fail these transactions during budgetary control validation, you must set the Transaction budget date falls outside of date range across all budgets budgetary control validation failure option to Yes.
Transactions Without Project Attributes Don't Have a Matching Chart of Account Based Control Budget
A transaction without project attributes can have a budget date within the period range of all control budget periods, but not match a budget period for a chart of account based control budget. This can happen when these conditions are met:
-
Control Budget Filter setting is either Project or Ledger or project.
-
Period range for the chart of account based control budgets is shorter than the period range for project control budgets.
By default, Budgetary Control allows transactions without project attributes that don't match a chart of account based control budget to pass validation even if the Transaction budget date fails outside of the date range across all control budgets budgetary control failure option is set to Yes. To fail these transactions with a No chart of accounts control budget status, you must set the Transaction without project attributes don't have a matching chart of account based control budget budgetary control validation failure option to Yes..
Default Date Rule
To select the budget date for the budgetary control liquidation of a prior related or backing document, use the Default Date Rule drop-down list. These are the options:
-
System date
-
Current transaction budget date
-
Prior related transaction budget date
Let's look at an example. When you match an invoice to a PO, the budget date for the liquidation of the PO is determined by the default date rule for the business unit. And these are the details:
-
system date is today
-
invoice budget date is 13-APR-15
-
PO budget date is 5-MAR-15
Then Budgetary Control determines the budget date of the purchase order liquidation as shown in this table:
|
Default Date Rule |
Purchase Order Liquidation Budget Date |
|---|---|
|
System date |
Today's date |
|
Current transaction budget date |
13-APR-15 |
|
Prior related transaction budget date |
5-MAR-15 |