Search Results pa_report_types_pk

Overview

PA_REPORT_TYPES is a foundational configuration table in the Oracle Projects (PA) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It stores the report type definitions that allow project managers and administrators to generate multiple distinct reports for a single project. Each row represents a named report type that acts as a template, governing how report content is presented — including which page layout is used and how the report is generated.

In a Data Vault modeling context, PA_REPORT_TYPES is classified heuristically as a hub-leaning entity. Its structure — a surrogate primary key (REPORT_TYPE_ID) with descriptive attributes and no direct parent dependency — is characteristic of a reference or hub table from which dependent transactional records (report versions and page layouts) derive their identity. This classification suggests that report types are stable, reusable reference data rather than event or transaction records.

Key Information Stored

The table is owned by the PA schema and contains 15 documented columns in the 12.2.2 physical schema. The most significant columns are:

• REPORT_TYPE_ID — The surrogate primary key (PA_REPORT_TYPES_PK). It is also a candidate business key through the unique index PA_REPORT_TYPES_U1, which pairs it with ZD_EDITION_NAME.
• NAME — The user-defined report type name. Together with ZD_EDITION_NAME it forms the unique index PA_REPORT_TYPES_U2, making NAME the primary human-readable business-key candidate.
• PAGE_ID — Identifies the page or page definition associated with the report type, controlling its presentation.
• OVERRIDE_PAGE_LAYOUT — A flag indicating whether the report type overrides the default page layout.
• GENERATION_METHOD — Specifies the method by which the report is generated.
• DESCRIPTION — Free-text description of the report type.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective-dating columns governing the active period of the report type.
• RECORD_VERSION_NUMBER — Supports optimistic locking and concurrency control.
• ZD_EDITION_NAME — The editioning column supporting Online Patching (Edition-Based Redefinition) in 12.2.x databases.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN provide standard EBS who/when auditing.

Common Use Cases and Queries

Report types are queried most often to list available report configurations for a project, to resolve which report type a given progress report version belongs to, or to identify the page layout in use. A representative query joining report types to their dependent progress report versions is:

SELECT rt.report_type_id, rt.name, prv.progress_report_version_id
FROM pa_report_types rt, pa_progress_report_vers prv
WHERE rt.report_type_id = prv.report_type_id;

A second common pattern retrieves only currently active report types for lookup purposes:

SELECT report_type_id, name, description
FROM pa_report_types
WHERE SYSDATE BETWEEN NVL(start_date_active, SYSDATE)
AND NVL(end_date_active, SYSDATE);

Reporting teams use this table as a reference dimension when building project reporting extracts, joining NAME to transactional report data to produce readable output rather than raw IDs.

Related Objects

• PA_PROGRESS_REPORT_VERS — References PA_REPORT_TYPES via the foreign key column REPORT_TYPE_ID. This is the primary dependent child, linking each version of a progress report to its report type.
• PA_OBJECT_PAGE_LAYOUTS — Also references PA_REPORT_TYPES via REPORT_TYPE_ID, tying page layout definitions to their report type.
• PA_REPORT_TYPES_PK — The primary key constraint on REPORT_TYPE_ID.
• PA_REPORT_TYPES_U1 — Unique index on REPORT_TYPE_ID and ZD_EDITION_NAME.
• PA_REPORT_TYPES_U2 — Unique index on NAME and ZD_EDITION_NAME, enforcing uniqueness of report type names within an edition.

These relationships confirm PA_REPORT_TYPES as an upstream reference entity whose keys propagate into project reporting and page layout configuration across the Oracle Projects module.