Search Results pay_magnetic_blocks




Overview
Explore in AI Chat

Overview

PAY_MAGNETIC_BLOCKS is a Payroll module table owned by the HR schema that serves as the driving table for the fixed format version of the magnetic tape process. In Oracle EBS 12.1.1 and 12.2.2, the magnetic tape process generates fixed-format output files used for third-party payroll payments, such as bank transfers for direct deposit or electronic funds transfer. This table defines the logical blocks into which those output records are grouped, establishing the structural template and record sequencing rules that the concurrent program uses when materializing the physical file.

Based on the foreign key topology documented in ETRM, the object has a hub-leaning Data Vault classification. In a Data Vault model, this suggests that PAY_MAGNETIC_BLOCKS acts as a central hub of unique block identifiers, with dependent tables such as PAY_MAGNETIC_RECORDS and PAY_REPORT_RECORD_TEMPLATES functioning as satellites or link participants that attach descriptive detail and ordering metadata to each block.

Key Information Stored

The table contains seven documented columns. The most operationally significant are listed below.

  • MAGNETIC_BLOCK_ID – Surrogate primary key, defined by the unique index PAY_MAGNETIC_BLOCKS_PK, which is composed of MAGNETIC_BLOCK_ID and ZD_EDITION_NAME. This identifier is the anchor referenced by all child tables.
  • BLOCK_NAME – The user-facing name of the block, used to identify each grouping during configuration and reporting.
  • MAIN_BLOCK_FLAG – Indicates whether the block is the primary (main) block versus a subordinate block within the fixed-format layout.
  • REPORT_FORMAT – Defines the report or file format associated with the block, driving layout expectations during output generation.
  • CURSOR_NAME – Identifies the cursor or query logic that populates the block, linking the block definition to the extraction routine.
  • NO_COLUMN_RETURNED – Governs behavior when the underlying query returns no columns, controlling exception handling for empty blocks.
  • ZD_EDITION_NAME – The editioning column supporting Oracle E-Business Suite online patching (EDITIONABLE schema objects), included in the primary key to preserve edition isolation.

The primary key is surrogate, while the ZD_EDITION_NAME column functions as a technical business-key qualifier under editioning rather than a true natural business key.

Common Use Cases and Queries

The most frequent use case is diagnosing why a fixed-format magnetic tape file is misaligned or missing records. Administrators query the block definitions to confirm which blocks are marked as main, which format is expected, and which cursor supplies data.

SELECT b.magnetic_block_id,
       b.block_name,
       b.main_block_flag,
       b.report_format
  FROM hr.pay_magnetic_blocks b
 WHERE b.zd_edition_name = 'SET1'
 ORDER BY b.magnetic_block_id;

A second common pattern traces block-to-record populations: joining PAY_MAGNETIC_BLOCKS to PAY_MAGNETIC_RECORDS reconciles the logical block template against the actual records emitted, exposing blocks that produced no output or exceeded expected row counts. Reporting queries frequently join blocks to PAY_REPORT_DEFINITIONS or PAY_REPORT_RECORD_TEMPLATES to audit which report definition consumes each block.

Related Objects

The following objects reference or depend upon PAY_MAGNETIC_BLOCKS, joined on MAGNETIC_BLOCK_ID unless noted.

  • PAY_MAGNETIC_RECORDS – Child records within each block; joins on MAGNETIC_BLOCK_ID, and also holds NEXT_BLOCK_ID referencing this table for block chaining.
  • PAY_REPORT_RECORD_TEMPLATES – Templates that map record layouts to blocks; joins on MAGNETIC_BLOCK_ID.
  • PAY_REPORT_DEFINITIONS – Report definitions that consume blocks; joins on MAGNETIC_BLOCK_ID.
  • PAY_REPORT_MAGNETIC_PROCEDURES – Procedure registrations tied to blocks; joins on MAGNETIC_BLOCK_ID.
  • HR_S_MAGNETIC_BLOCKS – Secure/translated view mirroring blocks; joins on MAGNETIC_BLOCK_ID.
  • HR_S_MAGNETIC_RECORDS – Secure/translated record view referencing blocks; joins on MAGNETIC_BLOCK_ID.

Together these relationships establish PAY_MAGNETIC_BLOCKS as the structural hub of the fixed-format magnetic tape configuration model.