Results for “pa_proj_element_versions”

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

Overview

PA_PROJ_ELEMENT_VERSIONS is an Oracle Projects (PA) table that stores common versioned information related to tasks and structures within the Oracle E-Business Suite Projects module. The ETRM documentation describes its purpose succinctly: it holds versioned attributes for project elements, and is annotated "For future use," indicating that Oracle designed the structure to support versioning semantics for work breakdown structures (WBS), resource breakdown structures (RBS), and related task hierarchies that may be expanded in later releases or specific product configurations.

The table resides in the PA schema and is present as VALID in both Oracle EBS 12.1.1 and 12.2.2. Its documented physical schema in ETRM 12.2.2 contains 40 columns, with a single-column surrogate primary key, ELEMENT_VERSION_ID, enforced through PA_PROJ_ELEMENT_VERSIONS_PK. A unique index, PA_PROJ_ELEMENT_VERSIONS_U1, also exists on ELEMENT_VERSION_ID. Based on the foreign-key topology mined from the ETRM metadata — a large number of child tables reference this object on version identifier columns — this table behaves structurally like a Data Vault hub. This is a heuristic modeling suggestion rather than a documented Oracle classification: ELEMENT_VERSION_ID acts as the hub key, while descriptive columns and attribute flexfields behave as satellite-style attributes. It is the anchor that consolidates the "version" identity of project elements and structures.

Key Information Stored

The most significant columns in PA_PROJ_ELEMENT_VERSIONS include:

• ELEMENT_VERSION_ID — Surrogate primary key and the business-key candidate via the unique index PA_PROJ_ELEMENT_VERSIONS_U1. It is the version identity referenced by a wide range of dependent tables.
• PROJ_ELEMENT_ID — Foreign key to PA_PROJ_ELEMENTS, linking a version to its underlying project element (task, phase, or structure element).
• PROJECT_ID — Foreign key to PA_PROJECTS_ALL, identifying the owning project.
• OBJECT_TYPE — Identifies the kind of versioned object (for example, task or structure variants).
• PARENT_STRUCTURE_VERSION_ID — Self-referencing foreign key to PA_PROJ_ELEMENT_VERSIONS, establishing hierarchy between structure versions.
• WBS_LEVEL and WBS_NUMBER — Work breakdown structure level and formatted WBS number, enabling hierarchical reporting and ordering.
• DISPLAY_SEQUENCE and LEVEL_SEQUENCE — Ordering attributes used to present siblings and hierarchy levels consistently.
• RECORD_VERSION_NUMBER — Optimistic locking/versioning counter used by the applications framework.
• TASK_UNPUB_VER_STATUS_CODE — Status indicator for unpublished task versions.
• FINANCIAL_TASK_FLAG — Indicates whether the element version is treated as a financial task.
• PRG_GROUP, PRG_LEVEL, and PRG_COUNT — Attributes supporting progress grouping and progress computation.
• SOURCE_OBJECT_ID and SOURCE_OBJECT_TYPE — Identify the originating object when a version is derived or copied.
• CONNECT_PATH and DEFER_CODE — Structural traversal and scheduling/deferral attributes.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard Oracle descriptive flexfield columns for extensible, customer-defined attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — Standard WHO audit columns.

Common Use Cases and Queries

Typical uses center on resolving the current or specific version of a project task or structure and traversing the hierarchy. A common pattern joins versions to the underlying element and project:

• Retrieve all versions for a project: SELECT element_version_id, proj_element_id, object_type, wbs_number, wbs_level FROM pa.pa_proj_element_versions WHERE project_id = :project_id ORDER BY wbs_level, display_sequence;
• Resolve a version to its element: SELECT v.element_version_id, e.proj_element_id, e.element_number FROM pa.pa_proj_element_versions v JOIN pa.pa_proj_elements e ON e.proj_element_id = v.proj_element_id;
• Walk the hierarchy via the self-referencing parent: SELECT child.element_version_id, child.wbs_number, parent.element_version_id AS parent_version_id FROM pa.pa_proj_element_versions child LEFT JOIN pa.pa_proj_element_versions parent ON parent.element_version_id = child.parent_structure_version_id;

Because many tables (budget versions, percent completes, progress rollup, resource assignments, and workplan attributes) reference ELEMENT_VERSION_ID, the table is frequently used as a join hub in reporting on project structures, baselines, progress, and workplan configuration. Note that the ETRM description marks the table as "For future use," so reporting should treat its contents as versioning metadata rather than the primary transactional store.

Related Objects

Significant related objects and their join columns include:

• PA_PROJ_ELEMENTS — joined on PROJ_ELEMENT_ID (this table references it) and referenced back via PA_PROJ_ELEMENTS.PHASE_VERSION_ID.
• PA_PROJECTS_ALL — joined on PROJECT_ID.
• PA_BUDGET_VERSIONS — references this table via RBS_STRUCT_VERSION_ID and PROJECT_STRUCTURE_VERSION_ID.
• PA_PERCENT_COMPLETES — references OBJECT_VERSION_ID.
• PA_PROGRESS_ROLLUP — references OBJECT_VERSION_ID and STRUCTURE_VERSION_ID.
• PA_RESOURCE_ASSIGNMENTS — references WBS_ELEMENT_VERSION_ID and RBS_ELEMENT_VERSION_ID.
• PA_PROJ_WORKPLAN_ATTR — references LIFECYCLE_VERSION_ID and CURRENT_PHASE_VERSION_ID.
• PA_PROJ_ELEM_VER_STRUCTURE and PA_PROJ_ELEM_VER_SCHEDULE — reference ELEMENT_VERSION_ID.
• PA_PROJ_FP_OPTIONS — references RBS_STRUCT_VERSION_ID.
• PA_OBJECT_RELATIONSHIPS — references OBJECT_ID_FROM1 and OBJECT_ID_TO1.