Results for “milestone_flag”

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

Overview

PA.PA_PROJ_ELEM_VER_SCHEDULE is a versioned scheduling attribute table within the Oracle Projects (PA) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores workplan scheduling attributes that are maintained at the project element version level, meaning each record corresponds to a specific versioned instance of a project element (task, deliverable, or work package) rather than to the element itself. The table is documented as being reserved "for future use" in the ETRM metadata, so while its structure is fully deployed, its runtime population and functional exploitation in standard flows may be limited or product-version dependent.

From a heuristic Data Vault modeling perspective, the foreign key topology — four outbound references to PA_PROJ_ELEMENT_VERSIONS, PA_PROJECTS_ALL, PA_PROJ_ELEMENTS, and JTF_CALENDARS_B — classifies this object as a link. It associates versioned elements with projects, base elements, and calendars, while also carrying descriptive scheduling attributes (dates, durations, flags, slack) that behave satellite-like. The presence of both a surrogate unique key on PEV_SCHEDULE_ID and a unique constraint on ELEMENT_VERSION_ID reinforces a one-to-one relationship between a version and its schedule record.

Key Information Stored

The table contains 64 documented columns. The most operationally significant are:

• PEV_SCHEDULE_ID — surrogate primary key, protected by unique index PA_PROJ_ELEM_VER_SCHEDULE_U1.
• ELEMENT_VERSION_ID — foreign key to PA_PROJ_ELEMENT_VERSIONS; unique index PA_PROJ_ELEM_VER_SCHEDULE_U2 makes this the principal business-key candidate.
• PROJECT_ID — foreign key to PA_PROJECTS_ALL, identifying the owning project.
• PROJ_ELEMENT_ID — foreign key to PA_PROJ_ELEMENTS, the base (non-versioned) element.
• CALENDAR_ID — foreign key to JTF_CALENDARS_B, the scheduling calendar used for date computations.
• SCHEDULED_START_DATE / SCHEDULED_FINISH_DATE — planned schedule dates.
• ESTIMATED_START_DATE / ESTIMATED_FINISH_DATE and ACTUAL_START_DATE / ACTUAL_FINISH_DATE — estimated and actual date baselines.
• EARLY_START_DATE / EARLY_FINISH_DATE and LATE_START_DATE / LATE_FINISH_DATE — CPM forward/backward pass results.
• DURATION, ACTUAL_DURATION, ESTIMATED_DURATION, EXT_ACT_DURATION, EXT_REMAIN_DURATION, EXT_SCH_DURATION — duration measures across planned, actual, estimate, and external sources.
• MILESTONE_FLAG, CRITICAL_FLAG, EFFORT_DRIVEN_FLAG, LEVEL_ASSIGNMENTS_FLAG — scheduling behavior flags.
• FREE_SLACK / TOTAL_SLACK — float values derived from network scheduling.
• *_ROLLUP columns (SCHEDULED, ESTIMATED, ACTUAL start/finish rollups) — summarized dates surfaced upward through the workplan hierarchy.
• Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, RECORD_VERSION_NUMBER, LAST_UPDATE_LOGIN) and the 15 ATTRIBUTE flex columns for customer extension.

Common Use Cases and Queries

Because the object is versioned, queries typically join to PA_PROJ_ELEMENT_VERSIONS to filter by version, then to PA_PROJECTS_ALL or PA_PROJ_ELEMENTS for project or element context. A representative reporting query for milestone schedules might select:

• SELECT s.element_version_id, s.project_id, s.scheduled_start_date, s.scheduled_finish_date, s.critical_flag, s.total_slack FROM pa.pa_proj_elem_ver_schedule s WHERE s.milestone_flag = 'Y' AND s.project_id = :project_id;
• Comparing baseline versus actual performance by selecting ESTIMATED_* versus ACTUAL_* date pairs per element version.
• Critical-path reporting using CRITICAL_FLAG, FREE_SLACK, and TOTAL_SLACK for schedule risk analysis.
• Calendar-driven rescheduling, joining CALENDAR_ID to JTF_CALENDARS_B to determine working-day windows.
• Duration variance analytics using PLANNED_EFFORT, DURATION, ACTUAL_DURATION, and EXT_* duration columns.

Given the "for future use" designation, analysts should verify population before relying on the table for production reporting and prefer public Oracle Projects APIs or concurrent programs where available.

Related Objects

• PA_PROJ_ELEMENT_VERSIONS — parent of the version, joined on ELEMENT_VERSION_ID.
• PA_PROJECTS_ALL — project master, joined on PROJECT_ID.
• PA_PROJ_ELEMENTS — base element definition, joined on PROJ_ELEMENT_ID.
• JTF_CALENDARS_B — calendar definition, joined on CALENDAR_ID.
• PA_PROJ_ELEM_SCHEDULES / workplan scheduling views — frequently expose or aggregate this data for project scheduling displays.
• PA_PROJECTS / PA_TASKS summary views — commonly populated from versioned scheduling attributes for reporting.