Results for “structure_name”

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

Overview

PA_STRUCTURE_VERSION_NAMES_V is a read-only database view owned by the APPS schema within the Oracle E-Business Suite Projects (PA) module. It is documented as valid in both EBS 12.1.1 and 12.2.2. The view presents structure version names and structure numbers associated with project elements, joining structure version records to their parent project elements to expose descriptive attributes such as project ID, structure name, publication date, and status code.

Per the ETRM metadata, the view "selects structure version name and structure number" and is explicitly annotated as being "For future use." This designation indicates that the object is not central to standard delivered Projects functionality in the current release; it is provisioned for anticipated use, and Oracle's documentation does not assign it a prominent role in shipped concurrent programs, forms, or reports. Consequently, its practical role in Oracle EBS reporting and integration is that of a supplemental, read-only source for structure version identification, usable in custom extracts and ad hoc queries rather than in core delivered flows. Because it carries a "for future use" status, implementers should treat any dependency on it cautiously, recognizing that its behavior and viability may be subject to change across releases or patches.

Underlying Base Objects

The view is defined over two referenced base objects, both accessed through APPS-owned synonyms:

• PA_PROJ_ELEM_VER_STRUCTURE (SYNONYM) — the structure version table, aliased as PEVS in the view text. It supplies the version name, version number, element version ID, published date, and status code.
• PA_PROJ_ELEMENTS (SYNONYM) — the project elements table, aliased as PPE. It supplies the project element ID, element name, and project ID.

The join is established on two conditions: PEVS.PROJ_ELEMENT_ID equals PPE.PROJ_ELEMENT_ID, and PEVS.PROJECT_ID equals PPE.PROJECT_ID. This composite join ensures that each structure version row is matched to the correct project element within the same project. An additional filter, PEVS.PROJECT_ID <> 0, excludes records with a zero project identifier, which in Projects schemas typically denote placeholder or internal rows rather than genuine project assignments. The resulting view therefore represents a one-structure-version-per-element perspective scoped to legitimate project identifiers.

Key Columns

The documented columns and their meanings are as follows:

• STRUCTURE_VERSION_NAME — the name of the structure version, sourced from PEVS.NAME. This is the column most closely associated with the search term "structure_version_name."
• STRUCTURE_VERSION_NUMBER — the numeric version identifier, sourced from PEVS.VERSION_NUMBER.
• ELEMENT_VERSION_ID — the unique identifier of the structure element version (PEVS.ELEMENT_VERSION_ID).
• PROJ_ELEMENT_ID — the project element identifier (PPE.PROJ_ELEMENT_ID) linking to the element master.
• STRUCTURE_NAME — the name of the parent project element (PPE.NAME).
• PROJECT_ID — the project identifier (PPE.PROJECT_ID) scoping the record.
• PUBLISHED_DATE — the date the structure version was published (PEVS.PUBLISHED_DATE).
• STATUS_CODE — the lifecycle status of the structure version (PEVS.STATUS_CODE).

Note the distinction between STRUCTURE_VERSION_NAME and STRUCTURE_NAME: the former identifies the version itself, while the latter identifies the underlying project element. Confusing these two columns is a common source of error in custom SQL.

Common Use Cases and Queries

Typical scenarios include listing all published versions of a project's structures, joining structure versions to project metadata, and filtering by status code. A representative query follows:

• SELECT v.STRUCTURE_VERSION_NAME, v.STRUCTURE_VERSION_NUMBER, v.STRUCTURE_NAME, v.PROJECT_ID, v.PUBLISHED_DATE, v.STATUS_CODE FROM APPS.PA_STRUCTURE_VERSION_NAMES_V v WHERE v.PROJECT_ID = :project_id ORDER BY v.STRUCTURE_VERSION_NUMBER;
• SELECT v.STRUCTURE_VERSION_NAME, v.STRUCTURE_VERSION_NUMBER, v.PROJECT_ID FROM APPS.PA_STRUCTURE_VERSION_NAMES_V v WHERE v.PUBLISHED_DATE >= :from_date;
• SELECT v.STRUCTURE_NAME, v.STRUCTURE_VERSION_NAME, v.STATUS_CODE FROM APPS.PA_STRUCTURE_VERSION_NAMES_V v WHERE v.STATUS_CODE = :status_code;

Given the "for future use" annotation, these queries should be validated against the target environment before being embedded in production integrations or concurrent programs.