Search Results old_level

Overview

PA.PA_PROJ_ELEMENTS_TMP is a global temporary table in the Oracle Projects (PA) schema, registered in Oracle E-Business Suite 12.1.1 and 12.2.2 under the FND Design Data namespace PA.PA_PROJ_ELEMENTS_TMP. As a global temporary table, its data is visible only to the session that inserted it; other concurrent sessions cannot see or affect those rows. The documented data duration is SYS$TRANSACTION, meaning rows survive only for the duration of the defining transaction and are purged automatically at commit or rollback. This makes the object a transient working area rather than a persistent store of project structure data.

The table holds project element (work breakdown structure and task) projection records used during processing of project and task hierarchies — for example, during project copy, structure versioning, rollup recalculation, or the derivation of a parent-child tree prior to a permanent write. The Columns list exposes the full set of attributes carried by each transient row.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. In Data Vault modeling terms this suggests the table does not act as a hub, link, or satellite in its own right; it is better modelled as a staging or transient structure whose attributes can be split across PA_PROJ_ELEMENT_VERSIONS and task hierarchy entities. Because it is populated within a single session's transaction and then discarded, it is not a candidate for historical tracking.

Key Information Stored

The table carries fifteen documented columns. The most consequential are:

• PROJECT_ID, TASK_ID, PARENT_TASK_ID, TOP_TASK_ID — the numeric identifiers that anchor a row in the project/task hierarchy. PARENT_TASK_ID and TOP_TASK_ID are essential for reconstructing ancestor paths and top-of-structure membership.
• PROJ_ELEMENT_ID and ELEMENT_VERSION_ID — the project element and its structure version. ELEMENT_VERSION_ID is documented as referencing PA_PROJ_ELEMENT_VERSIONS; TOP_TASK_ID references PA_TOP_TASKS_IT.
• LEVEL_SEQUENCE and OLD_LEVEL — the user's search term OLD_LEVEL is a NUMBER column recording the previous depth or level of the element before a restructure or rollup operation. LEVEL_SEQUENCE records the working level in the current session, so the pair supports before-and-after comparison of hierarchy depth.
• DISPLAY_SEQUENCE and WBS_NUMBER — ordering and human-readable hierarchy identification. WBS_NUMBER is VARCHAR2(240), accommodating multi-segment work breakdown strings.
• SCHEDULED_START_DATE and SCHEDULED_FINISH_DATE — scheduled date boundaries carried through the transient projection.
• DURATION, DEFER_CODE, and PARENT_STRUCTURE_VERSION_ID — duration in the element's units, a deferral indicator, and the version of the parent structure at the time of processing.

The metadata documents no surrogate primary key or unique index; because the table is transient and session-scoped, uniqueness is enforced implicitly by the populating process rather than by a declared constraint.

Common Use Cases and Queries

The dominant use is intra-session hierarchy manipulation. A typical pattern is to inspect rows written by the current session after a copy or restructure operation, comparing OLD_LEVEL with LEVEL_SEQUENCE to detect elements whose depth changed:

• Detect re-parenting: SELECT PROJECT_ID, TASK_ID, OLD_LEVEL, LEVEL_SEQUENCE FROM PA.PA_PROJ_ELEMENTS_TMP WHERE OLD_LEVEL <> LEVEL_SEQUENCE;
• Walk the transient tree via CONNECT BY PRIOR TASK_ID = PARENT_TASK_ID START WITH TASK_ID = TOP_TASK_ID.
• Verify ordering consistency using DISPLAY_SEQUENCE and WBS_NUMBER before committing a rebuilt structure.
• Confirm that a process terminated cleanly: because duration is SYS$TRANSACTION, residual rows indicate an uncommitted transaction or an abnormal exit.

Reporting against this table outside its defining session is not meaningful, since no data persists and other sessions cannot see it.

Related Objects

The dependency metadata records that PA.PA_PROJ_ELEMENTS_TMP references no database object, but is referenced by the APPS synonym PA_PROJ_ELEMENTS_TMP. Two foreign-key relationships are documented:

• PA.PA_PROJ_ELEMENT_VERSIONS — joined on PA_PROJ_ELEMENTS_TMP.ELEMENT_VERSION_ID = PA_PROJ_ELEMENT_VERSIONS.ELEMENT_VERSION_ID, supplying the versioned definition of each element.
• PA.PA_TOP_TASKS_IT — joined on PA_PROJ_ELEMENTS_TMP.TOP_TASK_ID = PA_TOP_TASKS_IT.TOP_TASK_ID, identifying the top task of the structure.

Practically, the transient rows mirror attributes of PA.PA_PROJ_ELEMENTS and its versions, and are consumed by the concurrent programs that populate project and task hierarchies. Consumers should always qualify the table with the PA schema and treat any row set as valid only within the transaction that created it.