Results for “budget”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PA_PRJ_FC_RESULTS_V is a base view owned by the APPS schema in Oracle EBS Projects (PA). Its documented description is "Base View for Budget Funds Check Results - Project Level -- Not Integrated to External Budget." The view presents the outcome of budgetary funds check processing aggregated to the project level, combining budgeted, actual, and encumbrance amounts for a given project and budget version across a defined date range. Because the description explicitly states it is not integrated to an external budget, the view is intended for internal funds check reporting within Oracle Projects rather than for reconciliation with an external budgetary system.

The view carries a VALID status in ETRM 12.2.2 and functions as a reporting and integration layer over the project balance view, providing a consolidated, version-aware summary for project-level funds availability analysis.

Underlying Base Objects

Two objects are documented as referenced by this view:

  • PA_PROJECT_BAL_V (VIEW) — The principal data source. PA_PRJ_FC_RESULTS_V is defined directly over this project balance view, aggregating its BUDGET, ACTUALS, and ENCUMBRANCES columns.
  • PA_BUDGETARY_CONTROLS_PKG (PACKAGE) — The budgetary controls package associated with funds check processing. This package embodies the funds check logic that produces and consumes the results surfaced by the view.

The documented view text is a straightforward aggregation:

SELECT PROJECT_ID, BUDGET_VERSION_ID, START_DATE, END_DATE, SUM(BUDGET), SUM(ACTUALS), SUM(ENCUMBRANCES) FROM PA_PROJECT_BAL_V GROUP BY PROJECT_ID, BUDGET_VERSION_ID, START_DATE, END_DATE

This confirms the view simply rolls up PA_PROJECT_BAL_V to project level for each budget version and date range, without additional joins or filtering.

Key Columns

  • PROJECT_ID — Identifier of the project to which the funds check result applies. This is the project-level grouping key.
  • BUDGET_VERSION_ID — Identifier of the budget version against which the funds check is evaluated, allowing results to be distinguished across budget versions.
  • START_DATE — Beginning of the date range for which the aggregated result is calculated.
  • END_DATE — End of the date range for the aggregated result.
  • BUDGET — Summed budget amount for the project, version, and date range.
  • ACTUALS — Summed actual costs recorded for the project, version, and date range.
  • ENCUMBRANCES — Summed encumbrance amounts for the project, version, and date range.

Together, BUDGET, ACTUALS, and ENCUMBRANCES provide the components used to assess funds availability, typically by comparing budget against the consumption represented by actuals and encumbrances.

Common Use Cases and Queries

The view supports funds check result reporting at project level. Typical scenarios include reviewing available funds per project and budget version, and validating funds check outcomes during budgetary control processing.

Sample query — all funds check results for a specific project:

SELECT project_id, budget_version_id, start_date, end_date, budget, actuals, encumbrances FROM apps.pa_prj_fc_results_v WHERE project_id = :project_id;

Sample query — comparing budget against actuals plus encumbrances:

SELECT project_id, budget_version_id, budget, actuals, encumbrances, (budget - (actuals + encumbrances)) AS available FROM apps.pa_prj_fc_results_v WHERE budget_version_id = :budget_version_id ORDER BY project_id;