Search Results pay_monetary_units_tl_pk




Overview
Explore in AI Chat

Overview

The HR.PAY_MONETARY_UNITS_TL table is a core translation table within the Oracle E-Business Suite Human Resources and Payroll modules, specifically for versions 12.1.1 and 12.2.2. It functions as the multilingual repository for the names of monetary units, such as currencies or other units of payment defined within the system. This table implements the standard Oracle Applications (EBS) translation architecture, enabling a single installation to support multiple languages by storing user-facing text in a language-specific format. Its primary role is to provide the localized name for a monetary unit based on the user's session language, ensuring that payroll and compensation data is presented correctly in global deployments.

Key Information Stored

The table's structure is designed to manage translated text with standard auditing columns. The key columns are:

  • MONETARY_UNIT_ID: A mandatory NUMBER that serves as the foreign key to the base table (PAY_MONETARY_UNITS), linking the translation to the specific monetary unit entity.
  • LANGUAGE: A mandatory VARCHAR2 column storing the language code (e.g., 'US', 'FR') for the translation. Together with MONETARY_UNIT_ID, it forms the primary key PAY_MONETARY_UNITS_TL_PK, ensuring a unique translation per language per unit.
  • MONETARY_UNIT_NAME: A VARCHAR2(80) column holding the actual translated name of the monetary unit as it should appear in the application for the specified language.
  • SOURCE_LANG: A VARCHAR2 column indicating the original language in which the row's data was created, which is critical for the translation synchronization process.
  • Standard Who Columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN for audit trail purposes.

Common Use Cases and Queries

This table is primarily accessed indirectly by the application's runtime to display localized content. Direct queries are common for data validation, migration scripts, and custom reports requiring multilingual support. A typical use case is retrieving the translated name for a set of monetary units for a report in a specific language. The sample query pattern, as indicated in the metadata, is fundamental:

SELECT MONETARY_UNIT_ID, MONETARY_UNIT_NAME, LANGUAGE, SOURCE_LANG FROM HR.PAY_MONETARY_UNITS_TL WHERE LANGUAGE = userenv('LANG');

Another critical pattern involves joining this table with its base table, PAY_MONETARY_UNITS, to get a complete set of monetary unit details with translations. Developers must always filter by the LANGUAGE column (or SOURCE_LANG) to avoid duplicate rows when joining, leveraging the non-unique index PAY_MONETARY_UNITS_TL_N2 on (LANGUAGE, MONETARY_UNIT_NAME) for performance.

Related Objects

The table's relationships are defined by its primary and foreign keys. As per the provided metadata:

  • Primary Key: The table is uniquely identified by the PAY_MONETARY_UNITS_TL_PK constraint on the columns (MONETARY_UNIT_ID, LANGUAGE).
  • Base Table Relationship: The MONETARY_UNIT_ID column is a foreign key referencing the PAY_MONETARY_UNITS base table (likely via a column of the same name), which holds the non-translatable attributes of a monetary unit. This is a classic parent-child (base-translation) relationship in the EBS data model.
  • Dependencies: The table is referenced by synonym structures (APPS.PAY_MONETARY_UNITS_TL and PUBLIC.PAY_MONETARY_UNITS_TL) for public access. It is also referenced by a trigger object named PAY_MONETARY_UNITS_T041422_WHO, which is likely a standard *"_WHO* trigger for populating the "Who" audit columns automatically.