Search Results pay_report_groups_pk

Overview

PAY_REPORT_GROUPS is a Payroll (PAY) module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It defines report groups, which serve as the top-level grouping mechanism used to organize and categorize payroll reports and report categories within the Oracle Payroll reporting framework. Each row represents a named report group scoped to a specific legislation and, optionally, a business group, allowing implementations to segment reporting configuration by legislative and organizational boundaries.

From a dimensional modeling perspective, the metadata's heuristic Data Vault classification places this object as a standalone table. No foreign keys are defined from PAY_REPORT_GROUPS outward to parent tables in the documented relationship data, though three downstream tables reference it. This suggests the table functions as a master/reference entity within the reporting configuration domain, and a Data Vault implementation could model it as a hub keyed on REPORT_GROUP_ID, with dependent descriptive attributes carried in a satellite.

Key Information Stored

The table contains 18 documented columns. The most significant include:

• REPORT_GROUP_ID — the surrogate primary key, populated by the PAY_REPORT_GROUPS_PK sequence/trigger mechanism.
• REPORT_GROUP_NAME — the descriptive name of the report group, presented to users when selecting or assigning reports.
• SHORT_NAME — an abbreviated identifier used in constrained UI contexts and reports.
• LEGISLATION_CODE — the legislative context (for example, US, CA, GB) that scopes the group's applicability.
• BUSINESS_GROUP_ID — the business group partition, enabling multi-organization security and isolation.
• REPORT_FORMAT_MAPPING_ID — links the group to a report format mapping definition.
• REPORT_LEVEL and THREAD_LEVEL — control the reporting hierarchy and concurrency/processing level.
• QUALIFYING_PROCEDURE — a PL/SQL procedure that determines whether a report qualifies for inclusion in the group.
• ASG_MAGNETIC_BLOCK_ID — associates an assignment-level magnetic block used in magnetic media reporting.
• REPORT_ON_FULL_XML — a flag controlling whether reporting is performed against the full XML payload.
• ZD_EDITION_NAME — the editioning column supporting EBS 12.2 online patching (Edition-Based Redefinition), enabling non-disruptive upgrades.
• Standard audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — capture who created and modified each row, support optimistic locking, and aid in change tracking.

The documented unique index, PAY_REPORT_GROUPS_PK, covers (REPORT_GROUP_ID, ZD_EDITION_NAME), making REPORT_GROUP_ID the surrogate key and confirming the edition name as part of the physical uniqueness constraint.

Common Use Cases and Queries

Typical uses include enumerating the report groups configured for a given legislation or business group, validating that reports are correctly grouped before running a payroll reporting cycle, and auditing changes to group definitions. A representative query is:

• SELECT report_group_id, report_group_name, short_name, legislation_code, business_group_id FROM pay_report_groups WHERE legislation_code = :leg AND business_group_id = :bg ORDER BY report_group_name;
• Joining to dependent tables, for example: SELECT g.report_group_name, c.category_name FROM pay_report_groups g, pay_report_categories c WHERE g.report_group_id = c.report_group_id AND g.legislation_code = :leg;
• Audit query: SELECT report_group_id, last_updated_by, last_update_date, object_version_number FROM pay_report_groups ORDER BY last_update_date DESC;

Reporting use cases include generating a catalog of report groups per legislation, reconciling group membership, and tracing which magnetic-media procedures are tied to which groups. Because of the ZD_EDITION_NAME column, queries executed in a 12.2 environment should be edition-aware, and EBS 12.2 online patching will maintain separate editions of the rows during upgrades.

Related Objects

The following documented tables reference PAY_REPORT_GROUPS via REPORT_GROUP_ID, forming the principal join relationships:

• PAY_REPORT_CATEGORIES — categories belonging to each report group (REPORT_GROUP_ID foreign key).
• PAY_REPORT_DEFINITIONS — individual report definitions assigned to a group (REPORT_GROUP_ID foreign key).
• PAY_REPORT_MAGNETIC_PROCEDURES — magnetic-media procedures linked to a group (REPORT_GROUP_ID foreign key).

Additional related objects include the PAY_REPORT_GROUPS_PK index and the standard HR schema reporting views and Oracle Payroll reporting APIs that consume these group definitions. Together these objects form the reporting configuration layer that drives Oracle Payroll's report generation, formatting, and magnetic-media processing across both 12.1.1 and 12.2.2 environments.