Search Results zx_recovery_types_tl




Overview
Explore in AI Chat

Overview

The ZX_RECOVERY_TYPES_TL table is a core component of the Oracle E-Business Tax (ZX) module within Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It functions as a translation table, providing multilingual support (MLS) for tax recovery type definitions. Its primary role is to enable the storage and display of user-defined recovery type names and descriptions in multiple languages, ensuring that tax-related data can be accurately presented and printed in a global enterprise's local languages. This table is integral to the internationalization features of E-Business Tax, separating translatable descriptive data from the base transactional and setup information.

Key Information Stored

The table stores language-specific translations for each tax recovery type. Its structure is typical of EBS translation tables, combining a key identifier with a language code. The most critical columns include:

  • RECOVERY_TYPE_ID: The primary foreign key that links each row to its corresponding base definition in the ZX_RECOVERY_TYPES_B table. This ID uniquely identifies the specific tax recovery rule.
  • LANGUAGE: The language code (e.g., 'US' for American English, 'KO' for Korean) for the translated text. Together with RECOVERY_TYPE_ID, this column forms the table's primary key.
  • RECOVERY_TYPE_NAME: The translated name of the recovery type as it should appear in the user interface and reports for the specified language.
  • DESCRIPTION: A more detailed explanation of the recovery type in the specified language.
  • Standard MLS columns such as SOURCE_LANG, CREATED_BY, and LAST_UPDATE_DATE to track the origin language of the data and audit changes.

Common Use Cases and Queries

This table is primarily accessed by the E-Business Tax engine during application runtime to retrieve the appropriate descriptive text based on the user's session language. Common use cases include generating multilingual tax reports, displaying setup data in the Tax Manager UI, and supporting data migration for multilingual implementations. A typical query to retrieve all translations for a specific recovery type would join the base and translation tables:

SELECT b.RECOVERY_TYPE_CODE, tl.LANGUAGE, tl.RECOVERY_TYPE_NAME, tl.DESCRIPTION
FROM ZX_RECOVERY_TYPES_B b, ZX_RECOVERY_TYPES_TL tl
WHERE b.RECOVERY_TYPE_ID = tl.RECOVERY_TYPE_ID
AND b.RECOVERY_TYPE_CODE = '<YOUR_CODE>';

For reporting, a query might filter on the session language to get the user-relevant description:
SELECT RECOVERY_TYPE_NAME, DESCRIPTION
FROM ZX_RECOVERY_TYPES_TL
WHERE RECOVERY_TYPE_ID = :p_recovery_type_id
AND LANGUAGE = userenv('LANG');

Related Objects

The ZX_RECOVERY_TYPES_TL table has a direct, dependent relationship with the base table that holds the core definition of tax recovery types. The documented foreign key relationship is:

  • Primary Key (ZX_RECOVERY_TYPES_TL_PK): RECOVERY_TYPE_ID, LANGUAGE.
  • Foreign Key to ZX_RECOVERY_TYPES_B: The RECOVERY_TYPE_ID column in ZX_RECOVERY_TYPES_TL references the RECOVERY_TYPE_ID column in ZX_RECOVERY_TYPES_B. This is a mandatory relationship, meaning every translation record must correspond to a valid base record. The base table (ZX_RECOVERY_TYPES_B) stores the non-translatable attributes like the recovery type code and effective dates.

This table is also typically accessed through standard MLS views provided by Oracle, which automatically handle language filtering based on the session context.