How You Determine Applicable Control Budgets

Settings That Affect Applicable Control Budgets

Use the following settings of the Control Budget Filter to indicate how you're controlling costs:

Ledger only
Project
Ledger or project

Note: Control budgets for a project are created automatically when you baseline a project budget in Oracle Fusion Project Management . Project Management puts the control budget in use, populates the budget balances, and opens the budget period statuses.

How Applicable Control Budgets Are Determined

When you set the Control Budget Filter to Ledger only, the Budgetary Control process matches the following two attributes on a transaction to determine the applicable control budgets:

Ledger
Budget Date: Compares the budget date of the transaction to the from and to periods in the control budget.

When you set the Control Budget Filter to Project or Ledger or project, the Budgetary Control process matches the following attributes on a transaction to determine the applicable control budgets:

Ledger
Project
Budget Date: Compares the budget date of the transaction to the from and to periods in the control budget.

Controlling Costs by Ledger

The following example illustrates how the ledger and budget date of a transaction determine the applicable control budgets when you're controlling costs by ledger.

Assume the following control budgets:

Control Budget	Ledger	Start Period	End Period
Operations Budget	Vision City	FY2015	FY2015
Capital Budget	Vision Capital	FY2015	FY2020
Parks Budget	Vision City	March 2015	October 2015

When transactions are entered, the budgetary control engine determines if the control budgets are applicable as shown in this table:

Transaction Number	Ledger	Budget Date	Operations Budget	Capital Budget	Parks Budget
101	Any ledger value	01-JAN-2014	No	No	No
102	Vision City	19-JAN-2015	Yes	No	No
103	Vision Capital	19-JAN-2015	No	Yes	No
104	Vision City	04-MAR-2015	Yes	No	Yes
105	Vision Special Projects	Any date	No	No	No

Controlling Costs by Project

The following example illustrates how the ledger, project values and budget date of a transaction determine the applicable control budgets when you're controlling by project.

Assume you're controlling by project, but you also want to control some non-project costs. You have set the Control Budget Filter to Ledger or project, and entered the following control budgets:

Control Budget	Ledger	Project	Award
HQ Office Move	Vision City	HQ Office Move	Any or no award assigned to the project
Roadways	Vision City	Roadways	2016
Operations Budget	Vision City	Any or no project on the transaction
Mayor Office Budget	Vision City	No project on the transaction

In this example, the HQ Office Move and Roadways control budgets are created by Project Management.

When transactions are entered, the budgetary control engine determines if the control budgets are applicable as shown in this table:

Transaction Number	Ledger	Project	Award	HQ Office Move	Roadways	Operations Budget	Mayor Office Budget
201	Vision City	HQ Office Move		Yes	No	Yes	No
202	Vision City	Telco		No	No	Yes	No
203	Vision Capital	Telco		No	No	No	No
204	Vision City			No	No	Yes	Yes
205	Vision City	Roadways	2016	No	Yes	Yes	No