Search Results structure_version_number




Overview
Explore in AI Chat

Overview

The APPS.PA_STRUCT_VERSIONS_LOV_AMG_V view is a public Oracle E-Business Suite database object owned by the APPS schema. It is registered in the Applications FND design data under the identifier PA.PA_STRUCT_VERSIONS_LOV_AMG_V and holds a VALID status in the ETRM 12.1.1 / 12.2.2 metadata repository. As its name and ETRM description indicate, the view exposes a list of structure versions used within Oracle Projects. It is characterized in the documentation as "a public view which may be useful for custom reporting or other data requirements" — an important designation, since it signals Oracle's intent that the object be available to customers and integrators for read-only querying rather than being treated as a private, internal-only artifact.

Functionally, the view serves as a lightweight list-of-values (LOV) source. Rather than requiring report authors to join the full set of project structure and structure-type tables manually, PA_STRUCT_VERSIONS_LOV_AMG_V presents structure version names, version numbers, identifiers, structure types, and status codes in a single, denormalized relation. Users who search on "structure_version_name" are typically attempting to resolve the user-facing name of a project structure version into its numeric identifier for downstream joins, or to present a picklist of valid structure versions in a concurrent program parameter or custom form.

Underlying Base Objects

The documented dependency list for this view is compact. It references four base objects through the APPS schema:

The ETRM metadata notes that PA_STRUCT_VERSIONS_LOV_AMG_V is not referenced by any other database object. This one-way dependency means the view is a pure consumer of its base relations and can be modified or extended by Oracle without cascading risk to dependent objects. For custom development, this is a favorable characteristic: the view is a stable read interface.

Key Columns

The view exposes eight columns of practical interest:

  • STRUCTURE_VERSION_NAME (VARCHAR2, 240) — the user-defined name of the structure version. This is the column surfaced by the LOV and the target of the "structure_version_name" search.
  • STRUCTURE_VERSION_NUMBER (NUMBER) — a system-generated sequence number for the structure version, useful for ordering and auditing.
  • STRUCTURE_VERSION_ID (NUMBER, 15) — the unique identifier for the element version; this is the value most consumers will carry forward as a foreign key.
  • STRUCTURE_TYPE (VARCHAR2, 80) — the project structure type class description.
  • STRUCTURE_ID (NUMBER, 15) — unique identifier for the structure version attributes.
  • PROJECT_ID (NUMBER, 15) — the owning project's identifier, enabling restriction to a single project's structures.
  • STATUS_CODE (VARCHAR2, 150) — the current status of the structure version.
  • STRUCTURE_TYPE_CLASS_CODE (VARCHAR2, 30) — the class code of the structure type, typically distinguishing work breakdown, resource, or organization structures.

Common Use Cases and Queries

The principal scenario is a query-driven LOV or a report that lists structure versions by project. The ETRM-supplied query can be used directly:

  • SELECT STRUCTURE_VERSION_NAME, STRUCTURE_VERSION_NUMBER, STRUCTURE_VERSION_ID, STRUCTURE_TYPE, STRUCTURE_ID, PROJECT_ID, STATUS_CODE, STRUCTURE_TYPE_CLASS_CODE FROM APPS.PA_STRUCT_VERSIONS_LOV_AMG_V;
  • Restrict to a project with WHERE PROJECT_ID = :project_id when constructing project-specific picklists.
  • Filter by STATUS_CODE to present only active or released versions.
  • Join STRUCTURE_VERSION_ID back to the base structure tables when the LOV must be combined with detailed element data.

Because the view is explicitly documented as suitable for custom reporting, it can be safely embedded in Discoverer workbooks, BI Publisher data templates, and concurrent program parameter LOVs without modifying Oracle-owned base objects.