Results for “rbs_struct_version_id”

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

Overview

PA_BUDGET_VERSIONS is the central table in the Oracle Projects (PA) module that stores the definition and metadata for every version of a project budget, forecast, or financial plan. Each row represents a discrete plan version — for example an original budget, a revised budget, a current forecast, or a what-if planning version — associated with a given project. Because a single project can carry cost, revenue, and combined plan types across multiple versions over its lifecycle, this table acts as the identity and control record that all budget and forecast detail lines ultimately reference.

In the documented schema for EBS 12.1.1 and 12.2.2, the table resides in the PA schema and contains 105 columns. A heuristic Data Vault classification mined from the foreign-key structure suggests this table behaves as a hub: its primary key (BUDGET_VERSION_ID) is a stable surrogate identifier that many downstream tables and facts reference, while descriptive and status attributes are carried alongside it. Practically, PA_BUDGET_VERSIONS is the parent record that governs which plan lines, balances, and adjustments are considered current, baselined, or in progress.

Key Information Stored

The most operationally significant columns include:

• BUDGET_VERSION_ID — surrogate primary key (PA_BUDGET_VERSIONS_PK) uniquely identifying each plan version.
• PROJECT_ID — the project to which the version belongs; joins to PA_PROJECTS_ALL.
• BUDGET_TYPE_CODE — approved cost, approved revenue, or other plan type; FK to PA_BUDGET_TYPES.
• VERSION_NUMBER and VERSION_NAME — the ordinal and user-facing label of the version.
• BUDGET_STATUS_CODE — lifecycle state such as working, submitted, or baselined.
• FIN_PLAN_TYPE_ID — financial plan type definition; FK to PA_FIN_PLAN_TYPES_B.
• CURRENT_FLAG / ORIGINAL_FLAG / CURRENT_ORIGINAL_FLAG — indicators of whether the row is the current and/or original version.
• RESOURCE_LIST_ID — the resource list applied to the plan; FK to PA_RESOURCE_LISTS_ALL_BG.
• PROJECT_STRUCTURE_VERSION_ID and RBS_STRUCT_VERSION_ID — the project and resource breakdown structure versions; both FK to PA_PROJ_ELEMENT_VERSIONS.
• PARENT_PLAN_VERSION_ID — self-referencing FK linking a version to its parent (e.g., a revise-from source).
• PERIOD_MASK_ID, FIRST_BUDGET_PERIOD — time-phasing controls; FK to PA_PERIOD_MASKS_B.
• Plan totals (e.g., TOTAL_PROJECT_RAW_COST, TOTAL_PROJECT_BURDENED_COST, TOTAL_PROJECT_REVENUE) and EST_* estimate columns — summarized financial amounts for the version.
• BASELINED_BY_PERSON_ID / BASELINED_DATE and APPROVED_COST_PLAN_TYPE_FLAG / APPROVED_REV_PLAN_TYPE_FLAG — baseline and approval tracking.

Two unique indexes define business-key candidates: PA_BUDGET_VERSIONS_U1 on BUDGET_VERSION_ID, and PA_BUDGET_VERSIONS_U2 on the combination of PROJECT_ID, BUDGET_TYPE_CODE, BUDGET_STATUS_CODE, VERSION_NUMBER, FIN_PLAN_TYPE_ID, VERSION_TYPE, and CI_ID. The _U2 index is the meaningful natural-key constraint within a project.

Common Use Cases and Queries

Typical usages include identifying the current budget or forecast for a project, reconciling baseline versus current plan amounts, and driving reported plan-versus-actual comparisons.

• Find the current approved cost budget for a project:

  SELECT budget_version_id, version_name, version_number
  FROM   pa_budget_versions
  WHERE  project_id = :p_project_id
  AND    budget_type_code = 'APPROVED_COST'
  AND    current_flag = 'Y';

• List all baselined versions for a project by version number:

  SELECT version_number, version_name, baselined_date
  FROM   pa_budget_versions
  WHERE  project_id = :p_project_id
  AND    budget_status_code = 'BASELINED'
  ORDER BY version_number;

• Join summarized version amounts to project details:

  SELECT p.project_number, b.version_name,
         b.total_project_raw_cost, b.total_project_revenue
  FROM   pa_budget_versions b, pa_projects_all p
  WHERE  b.project_id = p.project_id
  AND    b.current_flag = 'Y';

Reporting scenarios include budget versus actual dashboards, forecast rollups, and audit of baselined change history across plan versions.

Related Objects

PA_BUDGET_VERSIONS has an extensive relationship footprint. Key dependents and references include:

• PA_BUDGET_LINES and PA_BUDGET_ACCT_LINES — detail plan lines and accounted amounts, joined on BUDGET_VERSION_ID.
• PA_PROJECTS_ALL — parent project; joined on PROJECT_ID.
• PA_FIN_PLAN_TYPES_B and PA_BUDGET_TYPES — plan type and budget type lookups via FIN_PLAN_TYPE_ID and BUDGET_TYPE_CODE.
• PA_PROJ_ELEMENT_VERSIONS — project and resource structure versions via PROJECT_STRUCTURE_VERSION_ID and RBS_STRUCT_VERSION_ID.
• PA_BC_BALANCES, PA_BC_COMMITMENTS_ALL, PA_BC_PACKETS — burdening and bracketing records referencing BUDGET_VERSION_ID.
• PA_FP_ELEMENTS, PA_FP_ADJ_LINES, PA_FIN_PLAN_ADJ_LINES — financial plan elements and adjustments joined on the version key.
• PA_RESOURCE_ASSIGNMENTS and PA_ALLOC_RUN_TARGETS — resource and allocation processes keyed by BUDGET_VERSION_ID.
• PA_PROJ_FP_OPTIONS — configuration referencing multiple version columns for generation source plans.
• GMS_BALANCES — grants management balances linked to BUDGET_VERSION_ID.
• PA_BUDGET_ENTRY_METHODS and PA_PERIOD_MASKS_B — entry method and period mask lookups.

These relationships confirm that PA_BUDGET_VERSIONS is a foundational hub that anchors the majority of Oracle Projects' planning, forecasting, and budgetary control data.