Search Results pa_progress_report_vers_u1

Overview

PA.PA_PROGRESS_REPORT_VERS is a transactional table in the Oracle Projects (PA) schema that stores every version of a Status Report page type attached to a project or other project-related object. Each row represents a discrete, versioned snapshot of a Progress Report or Project Health page, capturing the report content, its reporting window, status, and publication state. The table is the version repository behind Oracle Projects' self-service Status Reporting feature, allowing users to draft, publish, cancel, and supersede reports while preserving a full historical audit trail.

The table resides in the APPS_TS_TX_DATA tablespace and is classified under FND Design Data as PA.PA_PROGRESS_REPORT_VERS. Its heuristic Data Vault classification is satellite-leaning: rows carry descriptive, time-variant attributes (status, overview, dates, who columns) tied to a parent object identifier plus a version surrogate, which is the classic shape of a satellite attached to a hub for the project/object and a link to the version chain. Under this modeling suggestion, OBJECT_ID / OBJECT_TYPE would anchor the hub, while VERSION_ID would resolve the version-chain link via VEA_VERSIONS.

Key Information Stored

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

• VERSION_ID — System-generated unique identifier of the page version. This is the surrogate primary key and is enforced by the unique index PA_PROGRESS_REPORT_VERS_U1, the documented business-key candidate.
• OBJECT_ID / OBJECT_TYPE — The owning object identifier and its type discriminator (for example, PROJECT_ID paired with object_type PA_PROJECTS). Together these scope the report to its project, task, or other project entity.
• PAGE_ID — Identifier of the underlying page layout.
• PAGE_TYPE_CODE — Page type discriminator such as PPR (Progress Report) or PH (Project Health).
• REPORT_STATUS_CODE — Lifecycle status of the page (for example, draft, submitted, published, canceled), which drives visibility and workflow.
• REPORT_START_DATE / REPORT_END_DATE — The reporting period covered by the report.
• REPORTED_BY — Identifier of the person who ran or authored the report.
• PROGRESS_STATUS_CODE — Overall progress status of the underlying object at the time of reporting.
• OVERVIEW and COMMENTS — Free-text summary (240 characters) and supplementary remarks.
• CURRENT_FLAG — Indicates whether the row represents the current published report, enabling single-row "latest" retrieval.
• PUBLISHED_DATE / CANCELED_DATE — Timestamps for publication and cancellation events.
• REPORT_TYPE_ID — Foreign key to PA_REPORT_TYPES, qualifying the kind of report.
• RECORD_VERSION_NUMBER / SUMMARY_VERSION_NUMBER — Locking columns used by self-service applications for concurrency control on records and summaries.
• Standard Who columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage centers on retrieving the current published report for a project, reconstructing a version history, or reporting on reporting cadence and status.

• Fetch the active published report for a project:

  SELECT * FROM pa.pa_progress_report_vers
WHERE object_id = :project_id
AND object_type = 'PA_PROJECTS'
AND current_flag = 'Y';

• Reconstruct full version history for a page:

  SELECT version_id, report_status_code, published_date,
      canceled_date, reported_by
FROM pa.pa_progress_report_vers
WHERE object_id = :project_id
ORDER BY version_id;

• Join to report types to classify published reports:

  SELECT v.version_id, t.name, v.report_start_date, v.report_end_date
FROM pa.pa_progress_report_vers v,
    pa.pa_report_types t
WHERE v.report_type_id = t.report_type_id
AND v.report_status_code = 'PUBLISHED';

• Concurrency-safe updates must honor RECORD_VERSION_NUMBER and SUMMARY_VERSION_NUMBER to avoid lost updates in self-service screens.

Related Objects

• PA.PA_REPORT_TYPES — Referenced via PA_PROGRESS_REPORT_VERS.REPORT_TYPE_ID; classifies each report.
• VEA.VEA_VERSIONS — Referenced via VERSION_ID; the versioning backbone providing version metadata.
• PA.PA_PROJECTS — Target of OBJECT_ID when OBJECT_TYPE = 'PA_PROJECTS'; the primary project anchor.
• PA.PA_TASKS — Alternative object target for task-level status reports.
• PA.PA_PAGE_LAYOUTS — Provides PAGE_ID context for the page layout used.
• PA.PA_PROGRESS_REPORT_DEFNS — Definition-level parent supplying page-type configuration.
• PER.PER_ALL_PEOPLE_F — Joins REPORTED_BY and Who columns to resolve report authors.
• FND.FND_USER — Resolves CREATED_BY / LAST_UPDATED_BY to application users.
• PA Progress Report public APIs — The status reporting APIs and concurrent programs that insert, publish, and cancel versions in this table.