Results for “pa_progress_report_vals”

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

Overview

PA_PROGRESS_REPORT_VALS is a table in the Oracle Projects (PA) module of Oracle E-Business Suite, owned by the PA schema. It stores the actual values captured for different versions of a progress report page. In the Oracle Projects reporting framework, a progress report is composed of one or more pages, and each page is populated from a set of regions. This table persists the row-level data that belongs to those regions for a specific report version, making it the primary store of report content used for project progress reporting, status tracking, and historical version comparison.

Because captured values can originate from multiple sources (for example, a predefined region, a user-defined region, or another system-generated region), the table is keyed in part by REGION_SOURCE_TYPE, which identifies the origin of the region the value belongs to. This allows different source regions to coexist for the same version without collision.

From a Data Vault modeling perspective, the metadata's heuristic classification is standalone, indicating no foreign-key dependencies were mined. A practitioner might nonetheless view the object as a satellite candidate, since it records descriptive, version-dependent attribute values (including 20 generic ATTRIBUTEn columns and 20 UDS_ATTRIBUTEn columns) associated with a VERSION_ID acting as the parent hub reference.

Key Information Stored

The table contains 51 documented columns. The most significant are the following:

• VERSION_ID — identifies the progress report version to which the captured values belong; the leading column of the primary key.
• REGION_SOURCE_TYPE — the type or origin of the region supplying the value. This is the column referenced in the user's search and forms part of the primary key.
• REGION_CODE — the code identifying the specific region within the page; also part of the primary key.
• RECORD_SEQUENCE — the sequence number that orders records within a region; completes the primary key.
• RECORD_VERSION_NUMBER — tracks the version of an individual record line, supporting concurrency and change history.
• ATTRIBUTE1–ATTRIBUTE20 — flexible generic descriptive value columns used to hold the actual content captured for the region.
• UDS_ATTRIBUTE_CATEGORY and UDS_ATTRIBUTE1–UDS_ATTRIBUTE20 — user-defined (descriptive flexfield) context and value columns that extend the table without schema change.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS who-column audit trail.

Surrogate versus business key: the primary key constraint PA_PROGRESS_REPORT_VALS_PK is defined on (VERSION_ID, REGION_SOURCE_TYPE, REGION_CODE, RECORD_SEQUENCE). The unique index PA_PROGRESS_REPORT_VALS_U1 is defined on the same four columns, confirming the business-key candidate. There is therefore no separate single-column surrogate identifier; the composite of these four columns serves as the effective identifying key.

Common Use Cases and Queries

Typical scenarios include extracting reported values for a specific report version, reporting on values filtered by region source, and comparing content across versions.

• Retrieve all values for a version:

SELECT VERSION_ID, REGION_SOURCE_TYPE, REGION_CODE, RECORD_SEQUENCE, ATTRIBUTE1
FROM PA.PA_PROGRESS_REPORT_VALS
WHERE VERSION_ID = :version_id
ORDER BY REGION_SOURCE_TYPE, REGION_CODE, RECORD_SEQUENCE;

• Isolate values from a particular region source for a given region:

SELECT * FROM PA.PA_PROGRESS_REPORT_VALS
WHERE VERSION_ID = :version_id
AND REGION_SOURCE_TYPE = :region_source_type
AND REGION_CODE = :region_code;

• Compare two versions of the same region to detect changes.
• Report on user-defined flexfield content via UDS_ATTRIBUTE_CATEGORY and the corresponding UDS_ATTRIBUTEn values.

Reports should always constrain on VERSION_ID and, where relevant, REGION_SOURCE_TYPE, since the full key spans four columns and unrestricted full-table scans are costly.

Related Objects

The documented relationship data classifies this object as standalone, so no enforced foreign keys were mined. In practice, VERSION_ID logically associates with the progress report version parent object, and REGION_CODE associates with region definition metadata. The most significant objects to consider are the progress report header/version table that owns VERSION_ID, the region definition tables that define REGION_CODE and REGION_SOURCE_TYPE, the page definition tables that group regions into pages, and the Oracle Projects progress report extraction and reporting concurrent programs and PL/SQL APIs that read and write these values. When no enforced FK exists, joins should be validated against application logic rather than assumed to be referentially enforced at the database level.