Results for “milestone_flag”

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

Overview

PA_STRUCT_PUB_TASK_VERS_V is an Oracle Projects (PA) view owned by the APPS schema. It exposes the published structure version of project tasks and project elements together with their scheduling attributes. The view is the reporting-facing representation of the published work breakdown structure — the version of a project's task hierarchy that has been formally released for execution and reporting, as opposed to working or draft versions that remain subject to change. The name itself encodes its purpose: "STRUCT" for structure, "PUB" for published, "TASK" for task-level elements, and "VERS" for version.

Because the view filters on a published status internally, consumers do not need to append their own status predicates when querying released structure data. This makes it a convenient and reliable source for Oracle Projects reporting, custom concurrent programs, Discoverer workbooks, OBIEE repositories, and inbound/outbound integrations that must read only sanctioned project structure information. It is particularly relevant to users examining task scheduling characteristics, including whether a task is a milestone, which is controlled by the MILESTONE_FLAG column.

Underlying Base Objects

The view is defined over three base objects, each referenced through a synonym in the APPS schema:

• PA_PROJ_ELEMENT_VERSIONS — the project element version header, supplying the project identifier, project element identifier, parent structure version, and element version identifiers.
• PA_PROJ_ELEM_VER_STRUCTURE — the structure version definition, supplying the structure version name, published date, and structure status code.
• PA_PROJ_ELEM_VER_SCHEDULE — the element version scheduling record, supplying scheduled start and finish dates, the critical flag, the milestone flag, and planned effort.

Joins are made on PROJECT_ID between all three sources, on PARENT_STRUCTURE_VERSION_ID equal to the structure's ELEMENT_VERSION_ID, and on PROJ_ELEMENT_ID and ELEMENT_VERSION_ID between the element version and its schedule. A hard-coded predicate restricts the result set to structures whose STATUS_CODE is 'STRUCTURE_PUBLISHED', so only published structures are returned.

Key Columns

• PROJECT_ID — the project that owns the structure version.
• PROJ_ELEMENT_ID — the project element (task) identifier being described.
• PARENT_STRUCTURE_VERSION_ID — the element version identifier of the parent structure to which this element belongs.
• STRUCTURE_VERSION_NAME — the name of the published structure version.
• ELEMENT_VERSION_ID — the specific version of the project element within the structure.
• PUBLISHED_DATE — the date the structure version was published.
• SCHEDULED_START_DATE / SCHEDULED_FINISH_DATE — the scheduled window for the element in this version.
• CRITICAL_FLAG — indicates whether the element lies on the critical path.
• MILESTONE_FLAG — indicates whether the element is treated as a milestone. This is the column most frequently searched in association with this view.
• PLANNED_EFFORT — the planned effort recorded for the element version.
• STRUCTURE_STATUS_CODE — the status of the structure, which for rows returned by this view is 'STRUCTURE_PUBLISHED'.

Common Use Cases and Queries

Typical uses include extracting the complete published task hierarchy for a project, identifying milestones within a published schedule, listing critical-path tasks, and feeding downstream reporting or integration pipelines with sanctioned structure data.

To list milestones in the published structure of a given project:

• SELECT project_id, proj_element_id, structure_version_name, scheduled_start_date, scheduled_finish_date, planned_effort FROM pa_struct_pub_task_vers_v WHERE project_id = :project_id AND milestone_flag = 'Y';

To retrieve all published elements with their schedule attributes:

• SELECT project_id, proj_element_id, element_version_id, scheduled_start_date, scheduled_finish_date, critical_flag, milestone_flag FROM pa_struct_pub_task_vers_v WHERE project_id = :project_id ORDER BY scheduled_start_date;

Because the view already enforces the published-status filter, queries remain concise and consistent, and results are aligned with the structure version that Oracle Projects has released for execution and reporting.