Search Results customized_restriction_id




Overview
Explore in AI Chat

Overview

The PAY_CUSTOM_RESTRICTIONS_TL table is a translation table within the Oracle E-Business Suite (EBS) Payroll module. It is a core component of the application's multi-language architecture, specifically designed to store translated text for the base table PAY_CUSTOMIZED_RESTRICTIONS. This table enables the localization of user-facing descriptions and messages associated with custom payroll restrictions, allowing the system to display content in the user's preferred language. Its role is critical for global implementations of Oracle EBS Payroll, ensuring compliance and usability across different linguistic regions in both versions 12.1.1 and 12.2.2.

Key Information Stored

The table's primary function is to hold language-specific versions of textual data. Its structure is defined by a composite primary key that links each translation to its source record and target language. The most significant columns include:

  • CUSTOMIZED_RESTRICTION_ID: A foreign key column that uniquely identifies the source record in the PAY_CUSTOMIZED_RESTRICTIONS table. This is the link to the entity being translated.
  • LANGUAGE: The language code (e.g., 'US' for American English, 'F' for French) for which the translated text is stored. This column, combined with CUSTOMIZED_RESTRICTION_ID, forms the table's primary key.
  • SOURCE_LANG: A system column indicating the original language in which the data was entered, facilitating synchronization of translations.
  • Translated Text Columns: While the exact column names are not detailed in the provided metadata, translation tables typically include columns such as DESCRIPTION, USER_DEFINED_NAME, or MESSAGE_TEXT to hold the actual translated strings for the custom restriction.

Common Use Cases and Queries

This table is primarily accessed by the Oracle application's internal translation engine to serve language-specific content to forms, reports, and self-service pages. Common operational and reporting scenarios include extracting user-friendly restriction descriptions for multi-language reports or auditing translation completeness. A typical query pattern involves joining the translation table to its base table while filtering for the session language.

SELECT b.restriction_code,
       t.description AS translated_description
FROM   pay_customized_restrictions b,
       pay_custom_restrictions_tl t
WHERE  b.customized_restriction_id = t.customized_restriction_id
AND    t.language = USERENV('LANG')
AND    b.effective_date BETWEEN SYSDATE-30 AND SYSDATE;

This query retrieves the active custom restrictions with their descriptions in the current user's language for reporting purposes.

Related Objects

PAY_CUSTOM_RESTRICTIONS_TL has a direct and dependent relationship with its base table. The documented primary key indicates the following critical relationship:

  • Base Table: PAY_CUSTOMIZED_RESTRICTIONS. The PAY_CUSTOM_RESTRICTIONS_TL table exists solely to provide translations for records in this table. The CUSTOMIZED_RESTRICTION_ID column in the TL table is a foreign key referencing the primary key of PAY_CUSTOMIZED_RESTRICTIONS.

This relationship ensures that for every translatable custom restriction, there can be multiple rows in the TL table—one for each supported language—while maintaining referential integrity with the core business data.