Results for “pa_proj_elements”

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

Overview

PA_PROJ_ELEMENTS is a Projects (PA) module table in the Oracle E-Business Suite PA schema. Per the ETRM metadata, it "stores the common non-versioned information related to tasks and structures" and is annotated as "for future use." It acts as a central anchor in the Projects data model, holding the identity, classification, and shared attributes of project elements — structural components such as tasks, phases, and work breakdown entries that are common across all versions of a project structure.

The table carries 67 documented columns and a single-column surrogate primary key, PA_PROJ_ELEMENTS_PK on PROJ_ELEMENT_ID, with an additional unique index PA_PROJ_ELEMENTS_U1 on PROJ_ELEMENT_ID and a composite business-key candidate PA_PROJ_ELEMENTS_U2 on (PROJECT_ID, OBJECT_TYPE, ELEMENT_NUMBER, PARENT_STRUCTURE_ID). A heuristic Data Vault classification mined from the foreign-key structure suggests this object behaves as a hub: it is referenced by a large number of dependent tables, including version, schedule, structure, progress, rollup, and reporting objects, which is consistent with a durable identity record at the center of the model.

Key Information Stored

The most significant columns include:

• PROJ_ELEMENT_ID — surrogate primary key, unique identifier of the element.
• PROJECT_ID — foreign key to PA_PROJECTS_ALL, identifying the owning project.
• OBJECT_TYPE — discriminates element types; part of the composite unique key PA_PROJ_ELEMENTS_U2.
• ELEMENT_NUMBER, NAME, DESCRIPTION — human-readable identification and descriptive attributes of the element.
• PARENT_STRUCTURE_ID — self-referencing foreign key establishing hierarchical relationships between elements; also part of U2.
• PHASE_VERSION_ID, PHASE_CODE — version and status linkage for the phase context.
• STATUS_CODE, WF_STATUS_CODE, TASK_STATUS, TASK_APPROVER_ID — lifecycle, workflow, and approval state.
• MANAGER_PERSON_ID, CARRYING_OUT_ORGANIZATION_ID, LOCATION_ID — ownership, organizational, and geographic assignments.
• TYPE_ID, TYPE_CODE, PRIORITY_CODE — classification and prioritization.
• BASELINE_START_DATE, BASELINE_FINISH_DATE, BASELINE_DURATION — baseline scheduling information.
• PROGRESS_WEIGHT, BASE_PERCENT_COMP_DERIV_CODE, INC_PROJ_PROGRESS_FLAG, PROGRESS_OUTDATED_FLAG — progress calculation controls.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — extensibility (DDF) columns supporting client-specific data.
• Standard EBS audit columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

The composite unique key (PROJECT_ID, OBJECT_TYPE, ELEMENT_NUMBER, PARENT_STRUCTURE_ID) is the most reliable business-key surrogate for identifying an element within a project hierarchy, while PROJ_ELEMENT_ID remains the canonical join column.

Common Use Cases and Queries

PA_PROJ_ELEMENTS is typically queried to enumerate structural elements of a project, resolve their hierarchy, and join to version or progress data. A representative query joins to the project header:

• SELECT e.proj_element_id, e.project_id, e.name, e.object_type, e.parent_structure_id, e.status_code FROM pa_proj_elements e WHERE e.project_id = :project_id;
• Hierarchical traversal — using PARENT_STRUCTURE_ID to walk the element tree within a project (CONNECT BY / recursive CTE).
• Version resolution — joining to PA_PROJ_ELEMENT_VERSIONS on PROJ_ELEMENT_ID to obtain versioned attributes.
• Progress reporting — joining to PA_PERCENT_COMPLETES and PA_PROGRESS_ROLLUP on OBJECT_ID / PROJ_ELEMENT_ID for completion and rollup metrics.
• Workplan and RBS analysis — joining to PA_PROJ_WORKPLAN_ATTR and PA_RESOURCE_ASSIGNMENTS on PROJ_ELEMENT_ID / RBS_ELEMENT_ID.
• Extensibility reporting — filtering or grouping on ATTRIBUTE_CATEGORY / ATTRIBUTE1–15 for client-specific dimensions.

Related Objects

• PA_PROJECTS_ALL — parent project; joined via PA_PROJ_ELEMENTS.PROJECT_ID.
• PA_PROJ_ELEMENT_VERSIONS — stores versioned element data; joined on PROJ_ELEMENT_ID.
• PA_PROJ_ELEM_VER_STRUCTURE and PA_PROJ_ELEM_VER_SCHEDULE — version structure and scheduling detail; joined on PROJ_ELEMENT_ID.
• PA_PERCENT_COMPLETES — completion percentages; joined on OBJECT_ID.
• PA_PROGRESS_ROLLUP — progress rollup results; joined on OBJECT_ID and PROJ_ELEMENT_ID.
• PA_RESOURCE_ASSIGNMENTS — resource assignments; joined on RBS_ELEMENT_ID.
• PA_PROJ_WORKPLAN_ATTR — workplan attributes; joined on PROJ_ELEMENT_ID.
• PA_TASK_TYPES and PA_PROJECT_STATUSES — reference lookups joined on TYPE_ID and PHASE_CODE respectively.
• PL/SQL APIs in the PA schema that maintain project structures operate against this table and its dependent objects.