Search Results pa_report_types_u1

Overview

PA.PA_REPORT_TYPES is a seed-data configuration table in the Oracle Projects (PA) schema that defines the catalog of report types available within Oracle E-Business Suite. Each row identifies a reporting construct — for example, a progress report or a project status report — and controls the page layout, generation method, and effective dating governing how that report is produced and rendered. The table resides in the APPS_TS_SEED tablespace, which confirms its role as reference and setup data rather than transactional data accumulated through day-to-day user activity.

In Oracle EBS 12.1.1 and 12.2.2, PA_REPORT_TYPES functions as the master definition point for report rendering behavior. Self-service reporting functionality, particularly Oracle Projects progress reports, consults this table to determine the appropriate page layout and whether that layout may be overridden at the project level. Records are not typically maintained directly by end users; they are seeded by the application and extended through controlled configuration.

Viewed through a Data Vault modeling lens, the dependency structure suggests a hub-leaning classification. The table is referenced by multiple downstream tables, notably PA_PROGRESS_REPORT_VERS and PA_OBJECT_PAGE_LAYOUTS, and does not itself reference other database objects. This pattern — a narrow, relatively stable business key referenced by dependent tables — is characteristic of a hub entity in a dimensional or Data Vault style model.

Key Information Stored

The surrogate primary key is REPORT_TYPE_ID, a system-generated number of up to 15 digits that uniquely identifies each report type. It is enforced by the PA_REPORT_TYPES_PK constraint and mirrored by the unique index PA_REPORT_TYPES_U1.

The principal business-key candidate is NAME, an 80-character value holding the report type name. In ETRM 12.2.2 documentation, this column participates in the unique index PA_REPORT_TYPES_U2. The remaining columns capture the definition and lifecycle of each report type:

• PAGE_ID — identifier of the Page Layout associated with the report type, linking reporting behavior to Oracle page layout metadata.
• OVERRIDE_PAGE_LAYOUT — a flag indicating whether the page layout may be overridden at the project level.
• DESCRIPTION — a 240-character description of the report type.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective start and end dates controlling when the report type is active.
• GENERATION_METHOD — a 30-character value describing how the report is generated.
• RECORD_VERSION_NUMBER — used for optimistic record locking in self-service applications.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide audit and concurrency tracking.
• ZD_EDITION_NAME — the editioning column present in the 12.2.2 documented schema, reflecting the Online Patching editioning model introduced in EBS 12.2.

Common Use Cases and Queries

The primary use case is identifying active report types and their associated page layouts. A typical query filters on effective dates to return only currently valid entries:

• Listing active report types: SELECT REPORT_TYPE_ID, NAME, PAGE_ID, GENERATION_METHOD FROM PA.PA_REPORT_TYPES WHERE SYSDATE BETWEEN NVL(START_DATE_ACTIVE, SYSDATE) AND NVL(END_DATE_ACTIVE, SYSDATE + 1);
• Resolving the layout for a specific report: SELECT PAGE_ID, OVERRIDE_PAGE_LAYOUT FROM PA.PA_REPORT_TYPES WHERE NAME = :report_name;
• Joining to versions to trace usage: SELECT rt.NAME, v.* FROM PA.PA_REPORT_TYPES rt, PA.PA_PROGRESS_REPORT_VERS v WHERE rt.REPORT_TYPE_ID = v.REPORT_TYPE_ID;
• Auditing configuration changes through WHO columns: SELECT NAME, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM PA.PA_REPORT_TYPES ORDER BY LAST_UPDATE_DATE DESC;

In 12.2 environments, queries should account for the ZD_EDITION_NAME column when constructing unique lookups, as editioning affects visibility of rows during online patching. Reporting on generation method distribution and override eligibility is also common when assessing reporting configuration consistency.

Related Objects

The following objects depend on or reference PA.PA_REPORT_TYPES through documented foreign key relationships:

• PA.PA_PROGRESS_REPORT_VERS — references REPORT_TYPE_ID, associating each progress report version with its report type. This is the most significant downstream transactional link.
• PA.PA_OBJECT_PAGE_LAYOUTS — references REPORT_TYPE_ID, connecting page layout definitions to report types.
• APPS.PA_REPORT_TYPES — the APPS-layer synonym or view exposing the seed data to the application schema.

Additionally, the PAGE_ID column implies a relationship to Oracle page layout metadata used by the Oracle Applications Framework, though no explicit foreign key is documented. Together these relationships position PA_REPORT_TYPES as the hub from which reporting configuration propagates into version and layout structures.