Search Results pay_report_category_components




Overview
Explore in AI Chat

Overview

The PAY_REPORT_CATEGORY_COMPONENTS table, owned by the HR schema within the Oracle E-Business Suite Payroll (PAY) module, defines the component-level composition of payroll report categories. It serves as the association layer that binds individual report definitions to a parent report category, determining the order in which reports appear, the breakout variables that drive their content, and the style sheets applied to their output. In practice, the table underpins the configurable reporting framework that payroll administrators use to organize and render statutory and management reports.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. Under a Data Vault modeling approach, this suggests the table behaves as an independent construct rather than a hub, link, or satellite. This is consistent with its role as a configuration or cross-reference table that carries its own surrogate identity and lifecycle rather than participating in a strictly normalized hub-and-link topology. It should be treated as a reference table whose rows are managed by setup and maintenance activities.

Key Information Stored

The table contains fifteen documented columns. The most significant are outlined below.

Note that the business-key candidate is documented as the composite of REPORT_CATEGORY_COMP_ID and ZD_EDITION_NAME, while the surrogate primary key is REPORT_CATEGORY_COMP_ID alone.

Common Use Cases and Queries

Typical scenarios involve resolving the reports that constitute a given category, or determining how a particular report is configured within categories.

To list components for a category:

  • SELECT report_definition_id, breakout_variable_id, order_by_variable_id FROM pay_report_category_components WHERE report_category_id = :category_id;

To find all categories containing a specific report definition:

  • SELECT report_category_id FROM pay_report_category_components WHERE report_definition_id = :report_def_id;

Reporting use cases include auditing which breakout and order-by variables are assigned across categories, verifying style sheet assignments for legislative compliance, and reconciling configuration between environments. Joining to PAY_REPORT_CATEGORIES and PAY_REPORT_DEFINITIONS produces a readable inventory of category-to-report mappings.

Related Objects

The following objects are most significant in relation to this table.

  • PAY_REPORT_CATEGORIES — Parent table referenced via REPORT_CATEGORY_ID; supplies category metadata such as name and legislative context.
  • PAY_REPORT_DEFINITIONS — Referenced via REPORT_DEFINITION_ID; defines the individual reports placed within categories.
  • PAY_REPORT_CATEGORY_COMP_PK — The unique index enforcing the primary key and business-key candidate.
  • Payroll reporting concurrent programs — The report generation setup that consumes these component rows to determine breakout, ordering, and styling at runtime.
  • Legislation and business-group configuration tables — Provide the context referenced by LEGISLATION_CODE and BUSINESS_GROUP_ID.