Results for “pa_progress_report_vals_u1”

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

Overview

PA.PA_PROGRESS_REPORT_VALS is a transaction data table in the Oracle E-Business Suite Projects (PA) schema. It stores the region-level content of Progress Status Reports attached to a project, capturing one row per attribute value per region per report version. Progress Status Reports are the structured project reviews generated by project managers, and this table holds the actual page-type and region data produced for each version of a report, so that the report can be reconstructed, versioned, and printed.

The table resides in the APPS_TS_TX_DATA tablespace with PCT Free of 10, and its indexes are created in APPS_TS_TX_IDX. The documented physical schema in ETRM 12.2.2 lists 51 columns owned by PA, and the object status is VALID in both 12.1.1 and 12.2.2. From a Data Vault modeling perspective, the heuristic classification is standalone: the object carries no documented foreign key relationships to other tables, so it is best treated as an independent satellite-style structure keyed by its own composite identifier rather than as a hub or link within a modeled Data Vault. In practice the report version it belongs to is implied by VERSION_ID, which references the progress report version rather than a project directly.

Key Information Stored

The table is keyed by a composite primary key, PA_PROGRESS_REPORT_VALS_PK, defined over VERSION_ID, REGION_SOURCE_TYPE, REGION_CODE, and RECORD_SEQUENCE. This composite key is the surrogate primary key from the database's perspective, and it is also exposed as the unique index PA_PROGRESS_REPORT_VALS_U1, making it a documented business-key candidate for deduplication and lookup.

• VERSION_ID (NUMBER, 15) — Identifier of the version. This is the highest-level grouping column and the primary filter for reporting on a specific report version.
• REGION_SOURCE_TYPE — Part of the unique key; identifies the source context of the region being stored.
• REGION_CODE (VARCHAR2, 250) — The XML document path of the region. It is part of both the primary key and the secondary index PA_PROGRESS_REPORT_VALS_N1.
• RECORD_SEQUENCE (NUMBER) — Sequence of the records within a region, preserving ordering of the region's lines.
• RECORD_VERSION_NUMBER (NUMBER) — Used for record locking in self-service applications, enabling optimistic concurrency control when users edit a status report.
• ATTRIBUTE1 through ATTRIBUTE20 (VARCHAR2, 4000 each) — Generic columns holding the region attribute values. These are the descriptive payload of the report and the reason the table is very wide.
• UDS_ATTRIBUTE_CATEGORY and UDS_ATTRIBUTE1 through UDS_ATTRIBUTE20 — The user-defined (descriptive flexfield) portion of the region, allowing customers to add their own report fields without schema changes.
• LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who columns for audit and change tracking.

The secondary non-unique index PA_PROGRESS_REPORT_VALS_N1 covers VERSION_ID and REGION_CODE and supports retrieval of region content by report version.

Common Use Cases and Queries

The most frequent operational scenario is reconstructing a progress status report for printing, review, or archival. The table is queried by VERSION_ID with the region ordering supplied by RECORD_SEQUENCE.

• Listing all regions and values for one report version:

  SELECT region_source_type, region_code, record_sequence,
         record_version_number, attribute1, attribute2
    FROM pa.pa_progress_report_vals
   WHERE version_id = :p_version_id
   ORDER BY region_source_type, region_code, record_sequence;

• Locating the attributes held for a specific region by path: filter on REGION_CODE (and VERSION_ID) to use PA_PROGRESS_REPORT_VALS_N1 efficiently.
• Reporting on user-defined data for a category: filter on UDS_ATTRIBUTE_CATEGORY and select the UDS_ATTRIBUTE columns.
• Auditing changes over time: compare RECORD_VERSION_NUMBER, LAST_UPDATE_DATE, and LAST_UPDATED_BY to detect concurrent edits or stale self-service sessions.

Because attribute columns are generic VARCHAR2(4000) fields, reports should resolve their meaning against the region definition configured for the report page type rather than assuming fixed semantics.

Related Objects

The metadata classifies this object as standalone, with no documented foreign keys. The following relationships are inferred from the documented key and column naming rather than from enforced constraints, and should be validated against the actual 12.1.1/12.2.2 data model before use in custom code.

• PA.PA_PROGRESS_REPORT_VERSIONS — logical parent supplying the report version identified by VERSION_ID. Join column: PA_PROGRESS_REPORT_VALS.VERSION_ID = PA_PROGRESS_REPORT_VERSIONS.VERSION_ID.
• PA.PA_PROGRESS_REPORTS — the report header to which the versions belong; reached transitively through the version row.
• PA_PROGRESS_REPORT_VALS_PK — the composite primary key constraint on (VERSION_ID, REGION_SOURCE_TYPE, REGION_CODE, RECORD_SEQUENCE).
• PA_PROGRESS_REPORT_VALS_U1 — unique index on the same four columns; the documented business-key candidate and the object the user search term refers to.
• PA_PROGRESS_REPORT_VALS_N1 — non-unique index on (VERSION_ID, REGION_CODE) used for region retrieval.
• PA.PA_PROGRESS_REPORT_TEMPLATES — definition of regions and attributes that determine how the stored values are interpreted and displayed.
• FND design data PA.PA_PROGRESS_REPORT_VALS — the AOL-registered definition governing forms, concurrent programs, and self-service pages that read and write these rows.

Custom integrations should join to the version and report headers rather than to projects directly, since project identity is established at the report level and not stored on this table.