Results for “overflow_mode”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

HR_S_MAGNETIC_RECORDS is a Payroll (PAY) module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a configuration and sequencing table that governs how magnetic tape or magnetic media output files are assembled during payroll processing. Each row represents one processing step, or "record," within a magnetic block — defining the order in which records are written, their layout formula, overflow behavior, and the frequency at which they are executed. This table is central to the legacy magnetic media (mag tape) generation used for direct deposit, third-party payments, and regulatory file extracts, and it underpins the "magnetic records" that appear in payroll payment and payslip interfaces.

Based on the heuristic Data Vault classification mined from its foreign key structure, HR_S_MAGNETIC_RECORDS is modeled as a standalone table. In Data Vault terms this suggests it behaves as a self-contained reference/configuration object rather than a classic hub, link, or satellite, though its MAGNETIC_BLOCK_ID foreign key does establish a parent-child dependency on PAY_MAGNETIC_BLOCKS.

Key Information Stored

The table contains seven documented columns. The most significant are:

• MAGNETIC_BLOCK_ID — Foreign key to PAY_MAGNETIC_BLOCKS. Identifies the magnetic block (the logical file/format group) to which the record belongs. This is the principal business-key relationship.
• FORMULA_ID — References the FastFormula or formula definition used to construct the record's content at runtime.
• SEQUENCE — Determines the ordinal position of the record within its block, controlling output file ordering.
• NEXT_BLOCK_ID — Identifies the block executed after the current one, enabling chained/sequential block processing.
• OVERFLOW_MODE — Controls how records are handled when a block exceeds its allocated space or record limit.
• FREQUENCY — Defines the execution frequency or recurrence for the record within the magnetic run.
• LAST_RUN_EXECUTED_MODE — Records the mode (e.g., test versus production) used during the most recent execution.

MAGNETIC_BLOCK_ID and SEQUENCE together act as the practical composite business key, since a block's ordering is defined by sequence. The metadata does not document an explicit surrogate primary key column, though the parent FK relationship implies MAGNETIC_BLOCK_ID participates in uniqueness constraints.

Common Use Cases and Queries

Developers and payroll analysts query this table to trace how magnetic files and associate pay-slip/payment extracts are assembled, to debug record ordering, and to audit the last execution mode. Typical patterns include auditing record ordering per block and joining to the parent block table, for example:

• Record listing: SELECT magnetic_block_id, sequence, formula_id, frequency FROM hr.hr_s_magnetic_records WHERE magnetic_block_id = :block_id ORDER BY sequence;
• Join to block definitions: SELECT m.magnetic_block_id, m.sequence, m.overflow_mode, b.* FROM hr.hr_s_magnetic_records m, pay.pay_magnetic_blocks b WHERE m.magnetic_block_id = b.magnetic_block_id;
• Last-run audit: filtering on LAST_RUN_EXECUTED_MODE to distinguish test from production runs.
• Overflow analysis: grouping by OVERFLOW_MODE to identify blocks configured to spill into next blocks.

Reporting use cases include documenting the magnetic file layout for compliance, verifying formula assignments per record, and validating sequence gaps before a payroll run.

Related Objects

• PAY_MAGNETIC_BLOCKS — Parent table referenced by MAGNETIC_BLOCK_ID; defines the magnetic block header.
• FF_FORMULAS / FF_FORMULA_TYPES — Formula definitions referenced via FORMULA_ID.
• PAY_MAGNETIC_BLOCK_RULES and other magnetic-media configuration tables.
• PAY_ACTION_INFORMATION / PAY_RUN_RESULTS — Runtime results feeding the magnetic extract.
• PAY_PAYROLL_ACTIONS — The payroll run that triggers magnetic record execution.
• Third-party direct deposit and payment file APIs that consume the generated magnetic output.

Because the table is classified as standalone, its relationships are predominantly reference-driven rather than transactional, reinforcing its role as configuration metadata for payroll magnetic media generation.