Search Results pay_report_record_templates




Overview
Explore in AI Chat

Overview

PAY_REPORT_RECORD_TEMPLATES 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 the record templates that govern how payroll report output is physically formatted for magnetic media and other structured report files. Each row associates a report variable with a magnetic block and a template name, thereby specifying the layout used when payroll data is written to that block. This table is a configuration and metadata object that supports the Payroll report generation and magnetic media delivery processes rather than transactional payroll data itself.

Under the heuristic Data Vault classification supplied in the ETRM metadata, this object is modeled as a standalone entity. Because no downstream tables reference it through foreign keys, it does not function as a hub or link in the mined relationship graph; in Data Vault terms it behaves more like a reference or definition satellite containing descriptive attributes of the report template. This classification should be treated as a modeling suggestion rather than a definitive architectural constraint.

Key Information Stored

The documented physical schema exposes four columns, of which the following are significant:

  • REPORT_VARIABLE_ID — Foreign key to PAY_REPORT_VARIABLES. Identifies the payroll report variable whose value is being formatted. This is one component of the table's business key.
  • MAGNETIC_BLOCK_ID — Foreign key to PAY_MAGNETIC_BLOCKS. Identifies the magnetic media block into which the templated record is written, defining the physical output segment. This is the second component of the business key.
  • SEQUENCE — Numeric ordering attribute that positions the templated element within the block or record. It determines the relative placement of fields during rendering.
  • TEMPLATE_NAME — The descriptive name that identifies the record template. This is the primary descriptive attribute of the row and is useful for reporting and maintenance.

The table has no documented single-column surrogate primary key; the identifying key is composite, formed by REPORT_VARIABLE_ID and MAGNETIC_BLOCK_ID, with SEQUENCE refining ordering. No unique index definitions were included in the available metadata, so the composite business key should be confirmed against the live data dictionary in a given instance.

Common Use Cases and Queries

Typical uses include diagnosing magnetic media output layouts, validating that every report variable referenced by a magnetic block has a template defined, and generating documentation of report file structures. A basic join lists the template definitions together with their block and variable context:

  • SELECT t.template_name, t.sequence, v.report_variable_name, b.magnetic_block_name FROM hr.pay_report_record_templates t, hr.pay_report_variables v, hr.pay_magnetic_blocks b WHERE t.report_variable_id = v.report_variable_id AND t.magnetic_block_id = b.magnetic_block_id ORDER BY t.magnetic_block_id, t.sequence;
  • Orphan detection: query rows in PAY_REPORT_VARIABLES that have no matching template for a given MAGNETIC_BLOCK_ID.
  • Sequencing audit: identify duplicate or missing SEQUENCE values within a block to detect layout conflicts.

These queries support implementation reviews, defect analysis on magnetic media reports, and post-patch verification of template configuration.

Related Objects

The following objects are most significant in relation to this table, based on documented foreign keys:

  • PAY_REPORT_VARIABLES — joined on REPORT_VARIABLE_ID; supplies the report variable definition for each template.
  • PAY_MAGNETIC_BLOCKS — joined on MAGNETIC_BLOCK_ID; supplies the magnetic media block definition and grouping.
  • Other PAY report definition tables and the Oracle Payroll magnetic media generation concurrent programs that consume template metadata at run time.

Because the object is classified as standalone, no dependent child tables were mined; any additional referencing objects should be verified in the specific environment.