Search Results pay_magnetic_procedures




Overview

HR.PAY_REPORT_MAGNETIC_PROCEDURES is a configuration and extensibility table within the Oracle E-Business Suite Payroll (PAY) schema. It functions as a hook that localizations can use to inject localization-specific XML content into the core delivered XML generation procedures used for magnetic media reporting. Magnetic media reports — such as statutory year-end tax files, bank transfer files, and government-required payroll submissions — are generated through a combination of seeded report definitions and localization extensions. This table provides the mapping that binds a specific localization procedure to a magnetic block and report group, allowing the standard XML generation engine to call the appropriate localized routine at the correct point in the output sequence.

Under the heuristic Data Vault classification mined from the foreign key structure, this object is modeled as standalone. That classification is a modeling suggestion only; in practice the table sits between the magnetic report configuration tables and the localization code layer, and its two outgoing foreign keys to PAY_MAGNETIC_BLOCKS and PAY_REPORT_GROUPS give it the character of a link-style association table despite the heuristic label.

Key Information Stored

The table holds seven documented columns. The surrogate primary key is REPORT_MAGNETIC_PROCEDURE_ID, a NUMBER(15) unique key. Note that the documented unique index PAY_REPORT_MAGNETIC_PROC_PK is defined over two columns — REPORT_MAGNETIC_PROCEDURE_ID and ZD_EDITION_NAME — rather than the surrogate key alone. ZD_EDITION_NAME is a VARCHAR2(30) column used in the editioning model to distinguish rows across editions.

  • REPORT_MAGNETIC_PROCEDURE_ID — Surrogate identifier and the documented primary key column for the table.
  • MAGNETIC_BLOCK_ID — Foreign key to PAY_MAGNETIC_BLOCKS, identifying the magnetic block context in which the localization procedure executes.
  • REPORT_GROUP_ID — Foreign key to PAY_REPORT_GROUPS, linking the procedure to the report group that drives the submission run.
  • PROCEDURE_NAME — VARCHAR2(240) holding the name of the localization-specific procedure invoked to append or generate XML.
  • LEGISLATION_CODE — VARCHAR2(240) identifying the legislation (country) for which the procedure applies.
  • SEQUENCE — NUMBER(15) controlling the ordering in which multiple procedures execute within a block.
  • ZD_EDITION_NAME — Editioning discriminator included in the unique index.

Common Use Cases and Queries

The primary use case is diagnostics and extension auditing: identifying which localization procedures are registered against a given magnetic block or report group, and verifying the execution order. A second use case is impact analysis when a localization procedure is renamed or retired.

  • Listing all procedures for a legislation: SELECT * FROM HR.PAY_REPORT_MAGNETIC_PROCEDURES WHERE LEGISLATION_CODE = :leg_code ORDER BY REPORT_GROUP_ID, SEQUENCE;
  • Joining to the block definition to trace output structure: query PAY_MAGNETIC_BLOCKS on MAGNETIC_BLOCK_ID to see block names alongside PROCEDURE_NAME.
  • Confirming unique registration: the PAY_REPORT_MAGNETIC_PROC_PK index guarantees that a given procedure ID and edition combination appears once.
  • Reporting registered extensions by report group for release upgrade readiness checks prior to applying a patch.

Related Objects

The documented dependency metadata confirms that this table references no database object directly, but it is referenced by HR.PAY_REPORT_MAGNETIC_PROCEDURE#. The most significant related objects are:

  • HR.PAY_MAGNETIC_BLOCKS — joined on MAGNETIC_BLOCK_ID.
  • HR.PAY_REPORT_GROUPS — joined on REPORT_GROUP_ID.
  • HR.PAY_REPORT_MAGNETIC_PROCEDURE# — dependent object referencing this table.
  • HR.PAY_MAGNETIC_PROCEDURES — the parent magnetic-procedure definition referenced by REPORT_MAGNETIC_PROCEDURE_ID per the column comment.
  • HR.PAY_REPORT_MAGNETIC_PROCEDURES — no direct self-reference is documented; treat as the transactional counterpart consulted during XML generation.