Search Results pay_report_format_mappings




Overview
Explore in AI Chat

Overview

PAY_REPORT_FORMAT_MAPPINGS is a date-effective view owned by the APPS schema in the Oracle E-Business Suite Payroll (PAY) product. It presents configuration data that controls how payroll reports and magnetic media files are formatted, initialized, archived, and deinitialized at runtime. The view is defined over the date-effective table PAY_REPORT_FORMAT_MAPPINGS_F and filters rows against the effective date of the current user session, exposing only the record versions valid as of that date. This pattern is standard across Oracle EBS date-tracked (datetrack) entities and guarantees that concurrent users see the correct configuration version for their session context.

The view plays a supporting role in payroll reporting and third-party integration. Report format mappings determine which report format, initialization code, archive code, magnetic media code, and deinitialization code are applied for a given report type and qualifier. The column DEINITIALIZATION_CODE, referenced in the user's search, is the element that names the routine or program invoked to deinitialize the reporting environment after a report format completes execution — the logical counterpart to INITIALIZATION_CODE.

Underlying Base Objects

The view is defined exclusively over PAY_REPORT_FORMAT_MAPPINGS_F, accessed through a synonym. Its WHERE clause references FND_SESSIONS, also accessed through a synonym, in two scalar subqueries. The date filter compares EFFECTIVE_START_DATE and EFFECTIVE_END_DATE against the EFFECTIVE_DATE of the FND_SESSIONS row matching the current USERENV('SESSIONID'). As a result, the view is session-aware and returns a single effective version of each report format mapping for the duration of the user's session.

  • PAY_REPORT_FORMAT_MAPPINGS_F — the datetracked base table holding the full history of report format configuration rows.
  • FND_SESSIONS — the application session table supplying the effective date used to resolve the currently valid row version.

Because the filter is applied at query time rather than through a stored column, no derived or denormalized attributes are introduced; every view column maps one-to-one to a base-table column.

Key Columns

  • REPORT_TYPE — identifies the category of report to which the mapping applies.
  • REPORT_QUALIFIER — narrows the mapping within a report type.
  • REPORT_FORMAT — the format definition used to render the report.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the datetrack bounds of the row version.
  • RANGE_CODE — controls the range of data selected for the report.
  • ASSIGNMENT_ACTION_CODE — links the format to a payroll assignment action.
  • INITIALIZATION_CODE — routine executed to initialize the report environment before the report runs.
  • DEINITIALIZATION_CODE — routine executed to deinitialize (tear down) the report environment after the report completes.
  • ARCHIVE_CODE — controls archiving behavior for generated output.
  • MAGNETIC_CODE — governs magnetic media (tape/file) generation parameters.
  • REPORT_CATEGORY, REPORT_NAME — descriptive identification of the report.
  • SORT_CODE — controls the ordering of report records.
  • UPDATABLE_FLAG — indicates whether the mapping may be modified by the user.

Common Use Cases and Queries

Typical scenarios include identifying the initialization and deinitialization routines configured for a report, auditing effective-dated changes to report formats, and driving custom reporting or integration logic. A basic query isolating the initialization and deinitialization behavior is:

SELECT report_type, report_qualifier, report_format, initialization_code, deinitialization_code FROM pay_report_format_mappings WHERE initialization_code IS NOT NULL OR deinitialization_code IS NOT NULL;

To inspect all mappings for a specific report category:

SELECT report_name, report_type, report_qualifier, report_format, archive_code, magnetic_code FROM pay_report_format_mappings WHERE report_category = :p_category ORDER BY sort_code;

Because the view resolves to the session effective date, the same query executed under different FND_SESSIONS effective dates may return different row versions — a key consideration when comparing historical and current configuration. For full datetrack history, query the base table PAY_REPORT_FORMAT_MAPPINGS_F with an explicit AS OF or date-range predicate rather than the view.