Search Results pay_report_format_mappings_f




Overview
Explore in AI Chat

Overview

PAY_REPORT_FORMAT_MAPPINGS_F is a Payroll (PAY) module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to map a report for a given jurisdiction to the fixed format defined for the magnetic tape. In practice, this table stores the configuration that tells Oracle Payroll and Oracle HRMS statutory reporting processes which report format layout should be used when producing magnetic media files — such as tape-based submissions — for a specific legislative jurisdiction and report type. Each row binds a report identity (type, qualifier, and category) to a report format and a set of processing codes that govern how the output is generated, archived, initialized, and de-initialized.

The object is date-tracked: it carries EFFECTIVE_START_DATE and EFFECTIVE_END_DATE, and it appears in the ETRM physical schema with a ZD_EDITION_NAME column, indicating it is an edition-enabled (ZD) table. The ETRM metadata classifies this object heuristically as standalone under the Data Vault model. As a modeling suggestion, the absence of documented foreign-key relationships means this table is best treated as an independent configuration reference rather than a hub or link; its natural role is closer to that of a reference or lookup satellite, since it describes attributes of a report-to-format mapping over effective-dated periods.

Key Information Stored

The 26 documented columns capture report identification, format assignment, processing behavior, and standard audit fields. The most important columns are:

The unique index PAY_REPORT_FORMAT_MAPPINGS_PK is defined on REPORT_TYPE, REPORT_QUALIFIER, REPORT_CATEGORY, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, and ZD_EDITION_NAME; the primary key constraint PAY_REPORT_FORMAT_MAPPINGS_PK is documented on the first five of these. The surrogate REPORT_FORMAT_MAPPING_ID provides a stable single-column handle for downstream references.

Common Use Cases and Queries

Typical usage centers on statutory magnetic media reporting. A common query retrieves the active mapping for a jurisdiction and report type at a point in time:

  • SELECT report_type, report_qualifier, report_category, report_format, legislation_code FROM pay_report_format_mappings_f WHERE legislation_code = :leg_code AND report_type = :type AND SYSDATE BETWEEN effective_start_date AND effective_end_date;

Analysts also use the table to audit which formats are configured per legislative jurisdiction, to compare format assignments across effective-dated revisions, and to validate that a report name maps to the expected format before running a submission. Joins to report definitions and to payroll action/processing tables are performed on REPORT_TYPE, REPORT_CATEGORY, LEGISLATION_CODE, and REPORT_FORMAT_MAPPING_ID, since no formal foreign keys are documented.

Related Objects

Because the ETRM metadata classifies this table as standalone with no documented foreign keys, related objects are established primarily through shared business keys rather than enforced constraints. The most significant are:

  • PAY_REPORT_FORMAT_MAPPINGS_F itself in its _F (date-tracked) form, paired with its associated _TL and _B/date-tracked variants where localization and translation exist.
  • Payroll report and magnetic-media report definition tables referenced via REPORT_TYPE and REPORT_CATEGORY.
  • Legislative jurisdiction and legislation tables joined on LEGISLATION_CODE.
  • Business group reference tables joined on BUSINESS_GROUP_ID.
  • Payroll action and processing configuration tables referenced through ASSIGNMENT_ACTION_CODE, INITIALIZATION_CODE, and DEINITIALIZATION_CODE.
  • Standard HRMS date-tracked infrastructure (ZD_EDITION_NAME and effective-date ranges) that governs row visibility in the edition-enabled schema.

These joins are business-key based; DBA review of the HR schema is recommended to confirm referenced table names for any specific release.