Search Results report_code




Overview
Explore in AI Chat

Overview

PAY_US_TAX_REPORT_DIMENSIONS is a reference table in the Oracle E-Business Suite Payroll (PAY) module, owned by the HR schema. Its documented purpose is to hold the balance dimensions used by the US Payroll Tax Summary Listing report. In practical terms, the table acts as a configuration and lookup layer that drives which balance dimensions are gathered, aggregated, or displayed when the US Payroll Tax Summary Listing report is executed. By externalizing the mapping between a report and its dimensions, Oracle allows the report content to be controlled through data rather than through hard-coded logic in the report definition.

The table is a small, static reference object. In Oracle EBS 12.1.1 and 12.2.2 the structure is identical, consisting of only two columns and one unique index. Because the metadata classifies this object heuristically as standalone under the Data Vault model, it is best modeled as a reference or lookup table rather than as a hub, link, or satellite. There are no foreign key relationships documented, so the table does not participate in an enforced parent-child dependency chain; its integrity is maintained by its composite primary key.

Key Information Stored

The documented physical schema for this table in ETRM 12.2.2 contains exactly two columns:

  • REPORT_CODE — The business identifier of the report that consumes the dimension mapping. For the US Payroll Tax Summary Listing, this code identifies the specific report definition against which the dimension list applies.
  • DIMENSION_CODE — The balance dimension identifier, referencing a payroll balance dimension that the report is expected to include. This corresponds to the dimension names used elsewhere in the payroll balance architecture.

The primary key is defined by the unique index PAY_US_TAX_REPORT_DIMENSIO_PK, which spans (REPORT_CODE, DIMENSION_CODE). This composite structure means neither column is unique on its own: multiple dimensions may be associated with a single report code, and a single dimension may appear under several report codes. The combination of the two columns forms the business key, and no separate surrogate key column is documented. Any application logic that needs to resolve which dimensions belong to a given report must therefore use the composite key rather than a single-column lookup.

Because the table holds only keys and no descriptive or date-effective attributes, it functions purely as a many-to-many join between reports and dimensions rather than carrying its own descriptive payload.

Common Use Cases and Queries

The primary use case is determining, for a specified report code, the complete set of balance dimensions that the report will process. A typical query filters on REPORT_CODE:

  • SELECT REPORT_CODE, DIMENSION_CODE FROM HR.PAY_US_TAX_REPORT_DIMENSIONS WHERE REPORT_CODE = :p_report_code; — retrieves the dimension list for a single report.
  • SELECT DIMENSION_CODE, COUNT(*) FROM HR.PAY_US_TAX_REPORT_DIMENSIONS GROUP BY DIMENSION_CODE ORDER BY 2 DESC; — identifies which dimensions are shared across the most reports, useful when assessing the impact of a dimension change.
  • SELECT DISTINCT REPORT_CODE FROM HR.PAY_US_TAX_REPORT_DIMENSIONS; — enumerates all report codes that have dimension configurations defined.

Additional scenarios include validating that a newly defined report code has the expected dimensions loaded, auditing configuration differences between environments, and troubleshooting why a tax summary report is omitting or duplicating balance output. Because the table is read by report execution logic, changes to its rows should be treated as functional configuration changes and tested against the tax reporting cycle.

Related Objects

The metadata documents no foreign keys for this table; the Data Vault classification confirms it is standalone. The following objects are the most significant logical dependencies:

When extending or diagnosing the US Payroll Tax Summary Listing, these objects should be reviewed together to confirm that report codes, dimensions, and balance definitions remain consistent with the configured mapping in PAY_US_TAX_REPORT_DIMENSIONS.