Results for “pa_task_fc_results_v”

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

Overview

PA_TASK_FC_RESULTS_V is a Projects (PA) module reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes forecast or budgetary control results summarized at the task level, aggregating budget, actual, and encumbrance amounts by project, task, budget version, and date range. The view consolidates data from the project balances view PA_PROJECT_BAL_V and derives additional filtering logic through joins with PA_TASKS.

The view's primary role is to support reporting and integration needs where task-level financial rollups are required, particularly for tasks that participate in the budgetary control hierarchy. It is referenced alongside PA_BUDGETARY_CONTROLS_PKG, indicating a functional association with Oracle Projects budgetary control processing. Because it is a view rather than a table, it is not a storage object; it materializes results dynamically from its underlying sources at query time.

Underlying Base Objects

The ETRM metadata documents three referenced base objects: PA_BUDGETARY_CONTROLS_PKG (a package), PA_PROJECT_BAL_V (a view), and PA_TASKS (accessed via a synonym). The view text confirms that PA_PROJECT_BAL_V supplies the core financial measures, while PA_TASKS provides the task hierarchy used to identify qualifying tasks.

The definition comprises a UNION of two branches. The first branch joins PA_PROJECT_BAL_V to PA_TASKS and filters for rows where the parent task ID is not null, effectively selecting child-level tasks. The second branch selects top-level tasks by matching the task ID against a subquery that counts top task IDs in PA_TASKS, ensuring that uppermost tasks are also included. Both branches aggregate budget, actuals, and encumbrances using SUM and GROUP BY on budget version, project, task, and dates. This UNION structure ensures both child and top-level tasks are represented without double counting.

Key Columns

• PROJECT_ID — Identifier of the project to which the task-level results belong.
• TASK_ID — Identifier of the task for which the aggregated amounts are reported.
• BUDGET_VERSION_ID — The budget version associated with the summarized budget, actual, and encumbrance figures.
• START_DATE — Beginning date of the reporting period for the aggregated balances.
• END_DATE — Ending date of the reporting period for the aggregated balances.
• BUDGET — Summed budget amount for the task, version, and period.
• ACTUALS — Summed actual costs incurred against the task for the same grouping.
• ENCUMBRANCES — Summed encumbrance amounts, representing committed but not yet actualized funds.

Common Use Cases and Queries

This view is typically used to produce task-level budget versus actual versus encumbrance comparisons, to feed budgetary control exception reporting, and to support downstream integrations where per-task financial rollups are required. A representative query retrieving summarized results for a single project follows:

• SELECT project_id, task_id, budget_version_id, start_date, end_date, budget, actuals, encumbrances FROM pa_task_fc_results_v WHERE project_id = :p_project_id ORDER BY task_id, start_date;
• Aggregate across tasks for a project: SELECT project_id, SUM(budget) total_budget, SUM(actuals) total_actuals, SUM(encumbrances) total_encumbrances FROM pa_task_fc_results_v GROUP BY project_id;
• Filter by budget version to isolate a specific forecast or control scenario: SELECT * FROM pa_task_fc_results_v WHERE budget_version_id = :p_version_id;

Because the view derives from PA_PROJECT_BAL_V, query performance depends on the indexing and volume of the underlying project balances data and the PA_TASKS hierarchy. Consumers should apply PROJECT_ID and BUDGET_VERSION_ID predicates to constrain result sets, as unfiltered queries may return substantial row counts across all projects.