Search Results quantity_total

Overview

PA_TASK_BUDGETS_V is an APPS-owned reporting view in the Oracle E-Business Suite Projects (PA) module, listed as VALID and described in the ETRM metadata as "Retrofitted." It presents task-level budget data drawn from project budget versions, exposing cost, revenue, quantity, and descriptive attributes organized by task. The view resolves the parent/child hierarchy of project tasks through a sort-order function, allowing budget lines to be reported in a tree-walk sequence suitable for structured reporting and integration.

Because it exposes BUDGET_STATUS_CODE, the view is frequently consulted when users need to identify whether a given budget version is in a working, submitted, or baselined state. This makes it a common source for budget inquiry screens, extract programs, and downstream data feeds that must distinguish active budget versions from preliminary ones.

Underlying Base Objects

The ETRM metadata records three referenced base objects: the view PA_TASK_BUDGETS2_V, and the packages PA_BUDGET_UTILS and PA_TASK_UTILS. The view text confirms that PA_TASK_BUDGETS_V is defined directly over PA_TASK_BUDGETS2_V. The PA_TASK_UTILS package contributes the SORT_ORDER_TREE_WALK function, invoked with PARENT_TASK_ID and TASK_NUMBER to produce the hierarchical SORT_ORDER column. The PA_BUDGET_UTILS package supplies supporting budget logic referenced during view resolution and is listed among the dependencies.

The relationship is therefore one of aggregation and enrichment: PA_TASK_BUDGETS2_V provides the granular task budget rows and measures, while the package functions add hierarchical ordering and budget-context logic. PA_TASK_BUDGETS_V rolls those granular rows up by budget version, project, budget type, version number, status, and task identity, delivering one consolidated row per task per budget version.

Key Columns

• BUDGET_VERSION_ID – Identifier of the budget version to which the row belongs; the primary grouping key.
• PROJECT_ID – Project owning the budget version.
• BUDGET_TYPE_CODE – Classification of the budget (for example, cost or revenue budget type).
• VERSION_NUMBER – Sequential version number within the budget type.
• BUDGET_STATUS_CODE – Status of the budget version, used to distinguish working drafts from submitted or baselined versions.
• TASK_ID, TASK_NUMBER, TASK_NAME – Task identity and descriptive attributes.
• PARENT_TASK_ID – Parent task in the work breakdown structure.
• SORT_ORDER – Hierarchical ordering value derived via PA_TASK_UTILS.SORT_ORDER_TREE_WALK.
• RAW_COST_TOTAL – Summed raw cost for the task budget line.
• BURDENED_COST_TOTAL – Summed burdened (fully loaded) cost.
• REVENUE_TOTAL – Summed revenue amount.
• QUANTITY_TOTAL – Summed quantity.

Common Use Cases and Queries

Typical use cases include budget-versus-actual reporting, baseline budget extracts, and integration feeds requiring task-level budget amounts in WBS order. The following query lists baselined task budgets for a project in hierarchical order:

• SELECT task_number, task_name, budget_status_code, raw_cost_total, burdened_cost_total
• FROM apps.pa_task_budgets_v
• WHERE project_id = :p_project_id
• AND budget_status_code = 'BASELINED'
• ORDER BY sort_order;

A second common pattern filters on multiple status codes to compare working and baselined versions, or aggregates RAW_COST_TOTAL and BURDENED_COST_TOTAL by BUDGET_VERSION_ID for summarized reporting. Joins to PA_PROJECTS and PA_TASKS on PROJECT_ID and TASK_ID are standard when descriptive project or task attributes are required.