Results for “wbs_element_version_id”

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

Overview

PA_RESOURCE_ASSIGNMENTS is the core planning table in the Oracle Projects (PA) module, residing in the PA schema. It stores resource assignments for a budget version at a branch of a project's work breakdown structure. Each row represents a single planning element — a named person, job, organization, non-labor resource, or role — positioned against a project, task, and budget version, with associated quantities, costs, revenues, and rate attributes. In Oracle EBS 12.1.1 and 12.2.2, this table underpins Project Resource Management, financial planning, budgeting, forecasting, and utilization reporting.

From a Data Vault modeling perspective, the heuristic classification places PA_RESOURCE_ASSIGNMENTS as a hub, evidenced by its surrogate primary key RESOURCE_ASSIGNMENT_ID and its extensive outbound foreign-key footprint. The table functions as a central integration point linking project structure, budgeting, human resources, procurement, and costing dimensions.

Key Information Stored

The surrogate primary key is RESOURCE_ASSIGNMENT_ID, enforced by the PA_RESOURCE_ASSIGNMENTS_PK constraint. Business-key uniqueness is documented via PA_RESOURCE_ASSIGNMENTS_U2, spanning BUDGET_VERSION_ID, PROJECT_ID, TASK_ID, RESOURCE_LIST_MEMBER_ID, PROJECT_ASSIGNMENT_ID, and CBS_ELEMENT_ID — this composite defines the natural grain of a planning assignment.

• BUDGET_VERSION_ID – the budget or forecast version the assignment belongs to (FK to PA_BUDGET_VERSIONS).
• PROJECT_ID – the project owning the assignment (FK to PA_PROJECTS_ALL).
• TASK_ID – the task or WBS branch where resources are planned (FK to PA_TASKS).
• ORGANIZATION_ID – the organization supplying or owning the resource (FK to HR_ALL_ORGANIZATION_UNITS).
• PERSON_ID / PROJECT_ASSIGNMENT_ID – the named resource and its assignment record.
• JOB_ID / PROJECT_ROLE_ID – job and role definitions used when planning by role rather than person.
• PLANNING_START_DATE / PLANNING_END_DATE – the assignment's planned duration.
• TOTAL_PLAN_QUANTITY, TOTAL_PLAN_RAW_COST, TOTAL_PLAN_BURDENED_COST, TOTAL_PLAN_REVENUE – aggregated planned amounts at the assignment level.
• STANDARD_BILL_RATE, AVERAGE_BILL_RATE, AVERAGE_COST_RATE – rate attributes driving pricing and cost roll-ups.
• SPREAD_CURVE_ID – the curve used to distribute amounts over periods (FK to PA_SPREAD_CURVES_B).
• EXPENDITURE_TYPE / EXPENDITURE_CATEGORY – classification for cost and revenue treatment.
• RESOURCE_ASSIGNMENT_TYPE / RES_TYPE_CODE – distinguishes labor, non-labor, and other resource categories.
• PARENT_ASSIGNMENT_ID – self-referencing hierarchy for nested assignments.

Common Use Cases and Queries

Typical reporting scenarios include budget-versus-actual comparisons, resource utilization analysis, rate override audits, and headcount forecasting. A representative join to the organization dimension — the table most frequently sought alongside this object — follows:

SELECT pra.resource_assignment_id,
       pra.project_id,
       pra.task_id,
       hou.name           organization_name,
       pra.total_plan_quantity,
       pra.total_plan_burdened_cost,
       pra.planning_start_date,
       pra.planning_end_date
FROM   pa.pa_resource_assignments pra,
       hr.hr_all_organization_units hou
WHERE  pra.organization_id = hou.organization_id
  AND  pra.budget_version_id = :p_budget_version_id
ORDER  BY hou.name, pra.task_id;

Because the table carries five distinct organization foreign keys — ORGANIZATION_ID, RATE_ORGANIZATION_ID, RATE_INCURRED_BY_ORGANZ_ID, RATE_OVERRIDE_TO_ORGANZ_ID, and RATE_EXPENDITURE_ORG_ID — queries that reconcile planning ownership against rate-source organizations must join HR_ALL_ORGANIZATION_UNITS multiple times with aliases. Resource planning extracts commonly aggregate TOTAL_PLAN_QUANTITY and TOTAL_PLAN_BURDENED_COST grouped by PROJECT_ID and BUDGET_VERSION_ID to power budget dashboards.

Related Objects

• PA_BUDGET_LINES – references RESOURCE_ASSIGNMENT_ID; links planning assignments to budget line detail.
• PA_PROJ_PERIODS_DENORM – references RESOURCE_ASSIGNMENT_ID, OBJECT_ID, and PARENT_ASSIGNMENT_ID; stores period-level spread amounts.
• PA_FIN_PLAN_ADJ_LINES and PA_FP_ADJ_ELEMENTS – reference RESOURCE_ASSIGNMENT_ID for financial plan adjustments.
• PA_BUDGET_VERSIONS – parent of BUDGET_VERSION_ID; defines the version context.
• PA_PROJECTS_ALL and PA_TASKS – project and task dimensions.
• HR_ALL_ORGANIZATION_UNITS – five separate relationships covering planning and rate organizations.
• PER_JOBS – referenced by both JOB_ID and RATE_JOB_ID for labor role definitions.
• PA_RESOURCE_LIST_MEMBERS and PA_PROJECT_ASSIGNMENTS – define the resource being planned.