Budgetary Control Funds Status
Budgetary control funds status indicates the validation result of the transaction amount against the budget amount. You can set budgetary control for a project, task, resource, award, and funding source segments.
If a project is enabled for budgetary control and the business unit or ledger is also enabled for budgetary control, then a baselined budget version that's created using a budgetary control enabled financial plan type must exist for transactions that must be subjected to project budgetary controls. The following transactions are validated for funds:
- Purchase orders to an inventory destination and direct procurement of materials to a work order destination
- Transfer order expense costs
- Expense related requisitions
- Expense related purchase orders
- Supplier invoices (includes variances, prepayments, and application of prepayments)
- Expense related purchase order receipts
- Project cost transactions (created with Oracle Projects or third-party application source and imported using the Import Costs process)
- Work order costs excluding costs for direct procurement of materials to a work order destination
- Sales order costs
- Miscellaneous inventory issues
- Transfer order inventory costs
- Burden cost amounts for spend authorizations
- Payments
- Cross-charge transactions
- Transactions that are excluded for the ledger or business unit in the Manage Budgetary Control page.
Reviewing Funds Status Results
You can review transaction and budget level budgetary control results on the following pages listed in the table.
Page |
Section |
Action |
---|---|---|
Manage Unprocessed Costs This page displays funds check results at the transaction level. |
Search Results |
Alternatively,
|
Manage Project Costs This page displays:
|
Search Results |
Alternatively,
Else,
|
Manage Project Costs If the original transaction passes budgetary control validations but the adjustments:
|
Errors |
|
Manage Cost Distributions This page displays:
|
Search Results |
Alternatively,
|
Diagnostic Dashboard |
Diagnostic Test Run Status |
Generate the Project Budgetary Control Validation and Balance Activities diagnostic report. |
By default, transaction-level results are displayed in the secondary window. You can change the view to display budget-level results.
Understanding Funds Status Results
The following table describes funds status results of budgetary control on cost transactions.
Status |
Description |
---|---|
Blank |
Transaction isn't eligible for funds check or transaction isn't validated for funds. |
Passed |
Transaction successfully passed funds check. |
Failed |
Transaction failed funds check. |
Warning |
Transaction passed funds check with warnings. |
Failure Scenarios for Funds Check
The following table lists the scenarios in which transactions that are enabled for budgetary control validation can fail funds check.
Failure Scenario |
Resolution |
---|---|
No control budget exists |
Navigate to the Manage Budget Versions page, create a control budget by
setting the budget to baseline, and then trigger the funds check from the
respective transaction page.
|
Control budget is created but the budget date is outside the control budget date range |
For a non-sponsored project, you must either change the budget date or project dates and set the budget to re-baseline such that the control budget dates are updated. For a sponsored project, you must either change the budget date or the dates of the project and the award, and then submit the date changes from the Edit Award Details page. |
Control budget is created but the transaction amount is higher than the available budget |
Reduce the amount charged on the transaction or increase the budget amount. |
Control budget is created but the control budget is in closed or permanently closed status. |
For a closed control budget, you will need to redefine the control budget. For a permanently closed control budget, you can't redefine and have to use another project. |
Control budget is created but the control budget period is closed or permanently Closed status. |
For a permanently closed control budget period, you can't reopen and have to use another project. For a closed control budget period, you need to reopen the control budget
period. To open the control budget period:
Note: By default, all users don't have access to the control budget. You can
grant control budget data access to users using the Manage
Control Budget Data Access for Users task in the Setup and
Maintenance work area.
|
Burden enabled project but the burden schedule is inactive. |
Build the burden schedule for the project. |
Burden enabled project with an active burden schedule but the burden multiplier for a particular expenditure type is not present. |
Provide the burden multiplier for that exception type. |
The transaction failed budgetary control validation with one or more errors. |
|
Insufficient Funds | Check for the available funds and then take the appropriate
corrective action. For example, the corrective action could be to increase
the project budget with the missing amount and re-baseline or limit the
transaction to the available amount. Note: For sponsored projects, you can
check the budgetary control balances on the Award Overview page. For
non-sponsored projects, use the Budgetary Control Analysis Report to
check the budgetary control balances. |
The account rules assigned to the transaction account type are insufficient to derive a value for any of the segments of the chart of accounts. | If you're using mapping sets, then verify the mapping set input and output values defined in the subledger accounting setup and edit these values as appropriate. For more information, see Mapping Sets and How You Define Mapping Sets. |
- Review Budgetary Control Validation Errors
- Can I perform budgetary control validation for cross-charge transactions?
- Update Control Budget Dates with Project, Task, or Budget Line Dates for Nonsponsored Projects
- Update Control Budget Dates with Award Dates for Sponsored Projects
- Set Up Default Budget Account
- Secure Control Budget Definitions