Search Results pqp_exception_reports_tl_pk

Overview

HR.PQP_EXCEPTION_REPORTS_TL is the translation (MLS) table for Oracle EBS exception report definitions used by the Payroll process and related HR reporting infrastructure. In Oracle EBS Release 12.1.1 and 12.2.2, it stores the language-specific, user-facing name of each exception report so that the same report definition can be presented in multiple installed languages. The base (non-translated) record resides in HR.PQP_EXCEPTION_REPORTS, while this table carries the localized text keyed by report and language.

The object is classified in the ETRM design data as PQP.PQP_EXCEPTION_REPORTS_TL, with owner/schema HR and status VALID. It resides in the APPS_TS_TX_DATA tablespace. From a Data Vault modeling perspective, the metadata heuristic classifies this object as standalone; that is, it is best modeled as a satellite-like descriptive table attached to the exception report hub (the base table), because it carries descriptive, language-dependent attributes rather than its own independent business entity or explicit foreign-key link settlement.

Key Information Stored

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

• EXCEPTION_REPORT_ID (NUMBER) — Surrogate identifier inherited from the base table PQP_EXCEPTION_REPORTS; it is the report's primary key in the parent table.
• LANGUAGE (VARCHAR2) — The language in which the report name is translated; part of the composite primary key.
• EXCEPTION_REPORT_NAME (VARCHAR2, 80) — The translated, display-facing exception report name.
• SOURCE_LANG (VARCHAR2) — The source language from which the name was translated; supports the MLS translation workflow.
• LAST_UPDATE_DATE (DATE) — Standard WHO audit column recording the last modification timestamp.
• LAST_UPDATED_BY (NUMBER, 15) — Standard WHO audit column identifying the user who last updated the row.
• LAST_UPDATE_LOGIN (NUMBER, 15) — Standard WHO audit column capturing the login session of the last update.
• CREATION_DATE (DATE) — Standard WHO audit column recording row creation timestamp.
• CREATED_BY (NUMBER, 15) — Standard WHO audit column identifying the creating user.

The documented primary key is PQP_EXCEPTION_REPORTS_TL_PK, defined on the composite of EXCEPTION_REPORT_ID and LANGUAGE. The unique index PQP_EXCEPTION_REPORTS_TL_PK on the same two columns is the business-key candidate, enforcing one translated name per report per language across tablespace APPS_TS_TX_IDX. The dependence on EXCEPTION_REPORT_ID as the sole non-language key element distinguishes the surrogate import from the composite business key.

Common Use Cases and Queries

Typical reporting and configuration tasks involve joining the translation table to the base table and filtering by the session or requested language. A common pattern resolves the localized name for a given report:

• Lookup by report and language: SELECT exception_report_name FROM hr.pqp_exception_reports_tl WHERE exception_report_id = :id AND language = USERENV('LANG');
• Listing all translations for a report: query by EXCEPTION_REPORT_ID and order by LANGUAGE.
• Identifying untranslated rows: compare rows in the base table against this table filtered by SOURCE_LANG and target LANGUAGE.
• Audit reporting: use CREATED_BY, CREATION_DATE, LAST_UPDATED_BY and LAST_UPDATE_DATE to track translation changes.

A canonical query joins the base and translation tables: SELECT b.exception_report_id, t.exception_report_name FROM hr.pqp_exception_reports b, hr.pqp_exception_reports_tl t WHERE b.exception_report_id = t.exception_report_id AND t.language = USERENV('LANG'); This supports Payroll exception-detection reporting, where administrators must see report labels in their operating language.

Related Objects

The ETRM dependency information states that HR.PQP_EXCEPTION_REPORTS_TL does not reference any database object directly, but it is referenced by HR and by the view or synonym construct PQP_EXCEPTION_REPORTS_TL#. The principal related objects are:

• HR.PQP_EXCEPTION_REPORTS — The base translation-source table sharing EXCEPTION_REPORT_ID as primary key; the logical join key.
• PQP_EXCEPTION_REPORTS_TL# — Documented dependent object referencing the translation table within the HR schema.
• HR.PQP_EXCEPTION_REPORTS_TL_PK — The unique index underpinning the composite primary key.
• Oracle HRMS / Payroll concurrent programs — Consume the localized exception report names during payroll exception reporting runs.
• FND Design Data registration (PQP.PQP_EXCEPTION_REPORTS_TL) — Governs the object's registration and MLS behavior in the EBS repository.

Because the table is a dependent translation satellite, change management should treat it as a consumer of base-table identifiers rather than an independently mastered entity.