Results for “lock_status_code”

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

Overview

PA.PA_PROJ_ELEM_VER_STRUCTURE is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores structure attributes associated with project element versions. Per the ETRM documentation, the object is described as holding "the structure attributes which are versioned" and is explicitly flagged as reserved "for future use." The table is marked VALID in the PA schema and is documented with 41 columns, a primary key named PPE_PK, and two unique indexes that act as business-key candidates.

The table sits at the intersection of the project element definition model and the project element versioning model: it references PA_PROJECTS_ALL, PA_PROJ_ELEMENTS, and PA_PROJ_ELEMENT_VERSIONS through foreign keys. Because each foreign key relationship links a parent entity to this child record, the heuristic Data Vault classification is link. This classification should be treated as a modeling suggestion rather than a definitive architectural statement, since the object is documented as a future-use structure rather than an actively populated one.

Key Information Stored

The surrogate primary key is PEV_STRUCTURE_ID, which is also the column carried by the unique index PA_PROJ_ELEM_VER_STRUCTURE_U1. A second unique index, PA_PROJ_ELEM_VER_STRUCTURE_U2, spans PROJECT_ID, PROJ_ELEMENT_ID, and NAME, forming the natural business-key candidate for a structure row.

• ELEMENT_VERSION_ID — foreign key to PA_PROJ_ELEMENT_VERSIONS; identifies the element version whose structure is described.
• PROJECT_ID — foreign key to PA_PROJECTS_ALL; the owning project.
• PROJ_ELEMENT_ID — foreign key to PA_PROJ_ELEMENTS; the project element being versioned.
• VERSION_NUMBER — the version ordinal for this structure record.
• NAME and DESCRIPTION — identifying and descriptive text; NAME participates in the U2 business key.
• CURRENT_FLAG, ORIGINAL_FLAG, LATEST_EFF_PUBLISHED_FLAG — status flags distinguishing the current, original, and latest effectively published versions.
• EFFECTIVE_DATE, PUBLISHED_DATE, PUBLISHED_BY_PERSON_ID — date and person audit for version publication.
• CURRENT_BASELINE_DATE, CURRENT_BASELINE_PERSON_ID, ORIGINAL_BASELINE_DATE, ORIGINAL_BASELINE_PERSON_ID — baseline tracking columns.
• LOCK_STATUS_CODE, LOCKED_BY_PERSON_ID, LOCKED_DATE — record-locking controls.
• STATUS_CODE and WF_STATUS_CODE — lifecycle and workflow status indicators.
• PM_SOURCE_CODE, PM_SOURCE_REFERENCE, SOURCE_OBJECT_ID, SOURCE_OBJECT_TYPE — sourcing and integration metadata.
• CONC_REQUEST_ID, PROCESS_CODE, PROCESS_UPDATE_WBS_FLAG, CHANGE_REASON_CODE — concurrent processing and change-tracking context.
• PURGED_FLAG and RECORD_VERSION_NUMBER — purge and optimistic-locking support.

Common Use Cases and Queries

Because the table is documented as future use, most activity is investigative: confirming whether any rows exist, inspecting structure definitions attached to element versions, and auditing flag or status distributions.

• Determining whether the object is populated: SELECT COUNT(*) FROM pa.pa_proj_elem_ver_structure;
• Listing structures for a project element by joining to PA_PROJ_ELEMENTS: SELECT s.pev_structure_id, s.name, s.version_number, s.current_flag, e.proj_element_id FROM pa.pa_proj_elem_ver_structure s, pa.pa_proj_elements e WHERE s.proj_element_id = e.proj_element_id;
• Auditing version state using stored flags: SELECT element_version_id, version_number, current_flag, original_flag, latest_eff_published_flag, effective_date FROM pa.pa_proj_elem_ver_structure ORDER BY element_version_id, version_number;
• Comparing baseline and publication dates for reporting on versioning discipline.
• Reviewing concurrent request activity through CONC_REQUEST_ID and PROCESS_CODE where processing metadata is present.

Related Objects

• PA_PROJ_ELEMENT_VERSIONS — joined via ELEMENT_VERSION_ID = ELEMENT_VERSION_ID; the parent version header.
• PA_PROJECTS_ALL — joined via PROJECT_ID = PROJECT_ID; the owning project.
• PA_PROJ_ELEMENTS — joined via PROJ_ELEMENT_ID = PROJ_ELEMENT_ID; the underlying project element.
• PA_PROJ_ELEM_VERSION_* companion tables in the PA schema that share the element-version naming convention.
• PA_PROJECTS and PA_PROJECT_STRUCTURE views that present project element hierarchies for reporting.
• PA_PROJECT_PUBLIC_API and related PA public APIs, which should be used in place of direct DML.