Results for “pa_task_budgets2_v”

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

Overview

PA_TASK_BUDGETS2_V is an Oracle EBS Projects (PA) reporting view owned by the APPS schema. It presents project budget version information broken down to the task level, together with aggregated cost, burdened cost, revenue, and labor quantity amounts derived from the underlying budget lines and resource assignments. The view exists to flatten the multi-table relationship between budget versions, tasks, resource assignments, and budget lines into a single queryable structure that is convenient for reporting, extracts, and integration routines.

The view is delivered in both Oracle EBS 12.1.1 and 12.2.2 and carries a VALID status in the ETRM repository. It is defined through a UNION ALL construction that produces distinct result sets depending on configuration and task hierarchy, ensuring that project-level and task-level budget data are presented consistently regardless of the entry level defined for the budget.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects: PA_BUDGET_LINES (SYNONYM), PA_BUDGET_VERSIONS (SYNONYM), PA_RESOURCE_ASSIGNMENTS (SYNONYM), PA_TASKS (SYNONYM), and the PA_BUDGET_UTILS package. The synonyms resolve to the corresponding APPS-owned Project Accounting tables.

• PA_BUDGET_VERSIONS supplies the budget version identifier, project identifier, budget type code, version number, and budget status code.
• PA_TASKS supplies task-level detail, including TASK_ID, TASK_NUMBER, TASK_NAME, PARENT_TASK_ID, and TOP_TASK_ID used for hierarchical rollup.
• PA_RESOURCE_ASSIGNMENTS links budget versions and tasks to resource assignments and carries the TRACK_AS_LABOR_FLAG used to determine whether quantity should be counted as labor.
• PA_BUDGET_LINES stores the RAW_COST, BURDENED_COST, REVENUE, and QUANTITY amounts that are summed in the aggregation branches.
• PA_BUDGET_UTILS is invoked through GET_ENTRY_LEVEL_CODE, which governs whether the view returns project-level or task-level rows.

Because the definition relies on PA_BUDGET_UTILS.GET_ENTRY_LEVEL_CODE, the row shape returned by the view depends on the current entry-level configuration of the environment.

Key Columns

• BUDGET_VERSION_ID — Unique identifier of the budget version, inherited from PA_BUDGET_VERSIONS.
• PROJECT_ID — Identifier of the project to which the budget version belongs.
• BUDGET_TYPE_CODE — Classifies the budget (for example, approved cost or revenue budget).
• VERSION_NUMBER — Sequential version number of the budget.
• BUDGET_STATUS_CODE — Current status of the budget version.
• TASK_ID, TASK_NUMBER, TASK_NAME, PARENT_TASK_ID — Task identification and hierarchy attributes; these are returned as zero or NULL in the project-level branch.
• RAW_COST, BURDENED_COST, REVENUE — Summed monetary amounts from PA_BUDGET_LINES.
• QUANTITY — Summed quantity, counted only where TRACK_AS_LABOR_FLAG equals 'Y'.

Common Use Cases and Queries

Typical uses include budget-versus-actual reporting, task-level cost analysis, and data extraction for downstream warehouses. A representative query retrieving task-level budget amounts for a project is:

• SELECT budget_version_id, project_id, task_number, task_name, raw_cost, burdened_cost, revenue, quantity FROM apps.pa_task_budgets2_v WHERE project_id = :project_id AND budget_type_code = 'COST' ORDER BY task_number;
• Filtering on BUDGET_STATUS_CODE isolates approved or baselined versions.
• Joining back to PA_TASKS on TASK_ID supports hierarchical rollups using PARENT_TASK_ID.

Because the view is a UNION ALL, callers should expect identical column structures across branches and apply appropriate filters to avoid double counting between project-level and task-level rows.