Search Results sub_level_seq

Overview

PA.PA_PROJ_ELEM_VER_TMP is a global temporary table (GTT) in the Oracle Projects (PA) schema. It serves as a transient staging structure used during the processing of project element version data, most notably in the generation and rendering of the Work Breakdown Structure (WBS) hierarchy. Because it is a global temporary table with a data duration of SYS$TRANSACTION, the rows inserted by a session are visible only to that session and are purged automatically at transaction commit or rollback. This makes it well suited to short-lived, session-scoped computation of hierarchical WBS relationships without persisting intermediate results.

From a Data Vault modeling perspective, the table is classified heuristically as standalone, lacking the multi-key linkage structures that characterize hubs or links. It is best understood as a transient staging or derived structure rather than a durable modeled entity; its ELEMENT_VERSION_ID does reference PA_PROJ_ELEMENT_VERSIONS, but the table exists to hold computed sequencing values for the duration of a processing call.

Key Information Stored

The table contains nine documented columns, all of type NUMBER. The most significant are:

• ELEMENT_VERSION_ID — Identifier of the project element version; the only documented foreign key, referencing PA_PROJ_ELEMENT_VERSIONS. Functions as the principal business key for joining to element version data.
• PROJECT_ID — The project to which the element version belongs.
• TASK_ID — The task associated with the element version.
• PARENT_TASK_ID — The parent task in the hierarchy, enabling parent-child traversal of the WBS tree.
• WBS_LEVEL — The depth of the element within the WBS hierarchy.
• WBS_NUMBER — The WBS number assigned to the element.
• DISPLAY_SEQUENCE — The ordering used when presenting siblings in the WBS.
• LEVEL_SEQUENCE — Sequence value used to order elements at a given level.
• SUB_LEVEL_SEQ — Sequence value used to order subordinate elements beneath a parent. This is the column most closely associated with the "sub_level_seq" search term, and it drives the ordering of nested WBS components during tree construction.

No surrogate primary key is enforced on this temporary table; it is populated and consumed positionally by the calling process.

Common Use Cases and Queries

The table is populated by Oracle Projects routines that compute and order the WBS hierarchy for a project element version. Typical uses include rendering the WBS tree in forms, validating hierarchy depth, and generating ordered reports of project structure. Diagnostic queries follow the documented pattern:

• Retrieve all staged rows: SELECT PROJECT_ID, TASK_ID, PARENT_TASK_ID, ELEMENT_VERSION_ID, DISPLAY_SEQUENCE, WBS_LEVEL, WBS_NUMBER, LEVEL_SEQUENCE, SUB_LEVEL_SEQ FROM PA.PA_PROJ_ELEM_VER_TMP;
• Reconstruct the hierarchy by ordering on WBS_LEVEL, LEVEL_SEQUENCE, and SUB_LEVEL_SEQ to obtain the correct depth-first presentation sequence.
• Join to PA_PROJ_ELEMENT_VERSIONS on ELEMENT_VERSION_ID to enrich staged rows with element version attributes.

Because data is transaction-scoped, queries must execute within the same session and transaction that populated the table.

Related Objects

• PA.PA_PROJ_ELEMENT_VERSIONS — Referenced by ELEMENT_VERSION_ID; the primary source of element version attributes.
• PA.PA_PROJECTS_ALL — Provides project context for PROJECT_ID.
• PA.PA_TASKS — Provides task context for TASK_ID and PARENT_TASK_ID.
• APPS.PA_PROJ_ELEM_VER_TMP — The APPS synonym granting access to the table.
• PA WBS APIs and concurrent programs — Populate and consume the temporary table during hierarchy processing.