Search Results hr_s_magnetic_blocks




Overview
Explore in AI Chat

Overview

The HR.HR_S_MAGNETIC_BLOCKS table is a Payroll (PAY) module data object residing in the HR schema within Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a seed or setup table that defines the magnetic block structures used in magnetic media reporting — the mechanism by which Oracle Payroll produces statutory reports (such as tax, social insurance, and year-end filings) to tape, diskette, or file formats required by revenue authorities and government agencies. Each row describes a logical magnetic block that groups one or more report elements into a coherent output structure, providing the metadata layer that drives the Payroll magnetic media generator.

Under the heuristic Data Vault classification mined from the foreign-key structure, this object is best modeled as a satellite. Its sole foreign key (MAGNETIC_BLOCK_ID) references PAY_MAGNETIC_BLOCKS, and the remaining attributes are descriptive, non-key characteristics of the referenced magnetic block. This suggests the table carries contextual detail about a parent magnetic-block entity rather than acting as an independent hub or a relationship link in its own right.

Key Information Stored

The documented physical schema for 12.2.2 confirms the object is owned by HR and contains six columns. The most significant columns and their contents are:

  • MAGNETIC_BLOCK_ID — the numeric surrogate identifier and the sole documented foreign key, joining to PAY_MAGNETIC_BLOCKS.MAGNETIC_BLOCK_ID. It anchors each row to its parent magnetic-block definition.
  • BLOCK_NAME — the descriptive, human-readable label for the magnetic block. This is the strongest business-key candidate, since users identify blocks by name in setup and reporting screens.
  • MAIN_BLOCK_FLAG — a Yes/No indicator marking whether the block is the primary (main) block in a magnetic media layout, distinguishing the header or principal record from subordinate blocks.
  • REPORT_FORMAT — defines the physical or logical format in which the block is emitted (for example, fixed-width, delimited, or a specific government-specified layout).
  • CURSOR_NAME — names the database cursor or SQL construct used to fetch the data that populates the block, linking the block definition to its extraction logic.
  • NO_COLUMN_RETURNED — a control attribute indicating that the associated cursor returns no columns (a header, trailer, or purely structural block), useful when formatting records with no data payload.

No unique index beyond the primary key is documented in the supplied metadata; MAGNETIC_BLOCK_ID should be treated as the surrogate primary key, and BLOCK_NAME validated as a natural business-key candidate during implementation.

Common Use Cases and Queries

Typical scenarios include auditing magnetic media definitions, identifying main versus subordinate blocks, and tracing which cursor supplies a block's data during payroll report generation. A representative query joining the parent definition is:

  • SELECT mb.magnetic_block_id, mb.block_name, mb.main_block_flag, mb.report_format, mb.cursor_name, mb.no_column_returned FROM hr.hr_s_magnetic_blocks mb WHERE mb.main_block_flag = 'Y';
  • Joining to the parent to compare block-level attributes: SELECT p.magnetic_block_id, mb.block_name, mb.report_format FROM hr.hr_s_magnetic_blocks mb, hr.pay_magnetic_blocks p WHERE mb.magnetic_block_id = p.magnetic_block_id;
  • Filtering structural (no-data) blocks: SELECT block_name FROM hr.hr_s_magnetic_blocks WHERE no_column_returned = 'Y';

These patterns support setup validation, report-format troubleshooting, and documentation of statutory reporting configurations.

Related Objects

The most significant related objects, grounded in the documented foreign key, are:

  • PAY_MAGNETIC_BLOCKS — parent table; join on MAGNETIC_BLOCK_ID.
  • PAY_MAGNETIC_BLOCK_RULES / magnetic media definition tables — define the overall report and consume block definitions.
  • PAY_MAGNETIC_MEDIA — the magnetic media entity that organizes blocks into a complete submission.
  • HR_S_MAGNETIC_BLOCKS views and Payroll magnetic media generator programs — read block metadata at run time.
  • Payroll reporting APIs and concurrent programs — depend on CURSOR_NAME and REPORT_FORMAT to emit records.