Results for “lowest_task”

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

Overview

PA_STRUCTURE_VERSIONS_V is an Oracle EBS Projects (PA) view owned by the APPS schema. According to the ETRM 12.2.2 metadata, it selects all structure-related attributes and is designated "For future use." This designation is significant: the view is a denormalized union of project element, element version, structure, schedule, progress, and status attributes, exposed as a single queryable surface for reporting and integration purposes. It is commonly searched in the context of "current_phase_version_id," reflecting its role in resolving the active (current) version of a project structure element such as a phase, task, or work package.

The view does not store data itself; it is a read-only projection over the Projects structure model, joining the definition of a structure (its type and mapping) with the versioned instances of that structure and the scheduling and progress attributes attached to each version. It is useful for reporting on baseline, current, and published versions of project structures without requiring callers to navigate the base transactional tables individually.

Underlying Base Objects

The documented referenced base objects include the principal Projects structure tables: PA_PROJ_ELEMENTS (element definitions), PA_PROJ_ELEMENT_VERSIONS (versioned instances of each element), PA_PROJ_ELEM_VER_STRUCTURE (structure membership of a version), PA_PROJ_ELEM_VER_SCHEDULE (dates and planned effort per version), PA_PROJ_STRUCTURE_TYPES and PA_STRUCTURE_TYPES (structure type definitions), PA_PROJ_PROGRESS_ATTR (progress and percent-complete attributes), PA_PROJ_WORKPLAN_ATTR, and PA_PROJECT_STATUSES and PA_PROJECTS_ALL for status and project context. Lookup and calendar values are resolved via FND_LOOKUPS, PA_LOOKUPS, and JTF_CALENDARS_TL. Person names are drawn from PER_ALL_PEOPLE_F.

The view also references several PL/SQL utility packages, including PA_PROJECT_STRUCTURE_UTILS (used in the GET_STRUC_TYPE_FOR_STRUCTURE call in the view text), PA_PROJ_ELEMENTS_UTILS, PA_PROJ_STRUC_MAPPING_UTILS, PA_PROGRESS_UTILS, PA_WORKPLAN_ATTR_UTILS, PA_RELATIONSHIP_UTILS, PA_DELIVERABLE_UTILS, PA_CURRENCY, and FND_GLOBAL. One referenced synonym, PJI_FM_XBS_ACCUM_TMP1, is a temporary accumulation object. These package references imply that some columns are derived at query time rather than read directly from a column.

Key Columns

• PROJ_ELEMENT_ID, ELEMENT_VERSION_ID, PEV_STRUCTURE_ID — identifiers for the element, its version, and the structure version instance. These are the join keys that let a caller resolve the current version of a phase or task; the "current_phase_version_id" search typically resolves to ELEMENT_VERSION_ID filtered by CURRENT_FLAG and structure type.
• PROJECT_ID, ELEMENT_NUMBER, NAME — project and element identification attributes.
• VERSION_NUMBER, EFFECTIVE_DATE, STATUS_CODE, PROJECT_STATUS_NAME — versioning and status metadata.
• ORIGINAL_FLAG, CURRENT_FLAG, LATEST_EFF_PUBLISHED_FLAG — flags with accompanying lookup meanings (LK1, LK2, LK3) that distinguish the original, current, and latest effective published versions.
• LOCK_STATUS_CODE, LOCKED_DATE, LOCKED_BY_PERSON_ID, PUBLISHED_DATE, PUBLISHED_BY_PERSON_ID — governance attributes with person full names from PER_ALL_PEOPLE_F.
• SCHEDULED/ESTIMATED/ACTUAL_START_DATE and _FINISH_DATE — schedule dates, plus derived variances computed as date differences against baseline dates.
• BASELINE_START_DATE, BASELINE_FINISH_DATE, BASELINE_AS_OF_DATE — baseline context.
• PROGRESS_STATUS_CODE, PERCENT_COMPLETE_ID, COMPLETED_PERCENTAGE, DATE_COMPUTED — progress rollup attributes.
• STRUCTURE_TYPE, CALENDAR_ID, CALENDAR_NAME, PLANNED_EFFORT — structure classification and scheduling context.

Common Use Cases and Queries

The view is typically used to report on the current or published version of project structure elements, to compare baseline versus scheduled dates, and to resolve version identifiers for downstream integration. A representative query for the current phase version follows:

SELECT project_id, proj_element_id, element_version_id, element_number, name,
  version_number, effective_date, project_status_name
FROM apps.pa_structure_versions_v
WHERE current_flag = 'Y'
  AND project_id = :p_project_id;

To identify the latest effective published version for reporting, filter on the published flag and order by version:

SELECT proj_element_id, element_version_id, version_number,
  published_date, structure_type
FROM apps.pa_structure_versions_v
WHERE latest_eff_published_flag = 'Y'
  AND structure_type = :p_structure_type
ORDER BY version_number DESC;

Because the view is documented as "for future use," implementers should confirm its column semantics against the current patch level before relying on it in production reporting, and prefer direct queries against the underlying PA_PROJ_* tables where the view's derived or NULL placeholder columns are insufficient.