Search Results ra_terms_tl

Overview

The RA_TERMS_TL table is a core Oracle E-Business Suite (EBS) data object within the Receivables (AR) module, specifically designed to provide multi-lingual support (MLS) for Payment Terms. It functions as a translation table, storing language-specific descriptive text for payment terms defined in the base table, RA_TERMS_B. This structure is a standard Oracle Applications pattern, enabling a single set of payment term definitions to be presented to users in their preferred language, which is critical for global deployments. The table's existence is fundamental to the application's internationalization capabilities, ensuring that terms like "Net 30" or "2% 10, Net 30" can be displayed correctly across different language installations.

Key Information Stored

The table's primary purpose is to store translated names and descriptions. Its structure is defined by a composite primary key linking a term identifier to a language code. The most critical columns include:

• TERM_ID: The foreign key that links to the RA_TERMS_B.TERM_ID, uniquely identifying the payment term.
• LANGUAGE: The ISO code for the language of the translated text (e.g., 'US' for American English, 'KO' for Korean).
• NAME: The translated name of the payment term as it should appear in the user interface.
• DESCRIPTION: The translated detailed description of the payment term.
• SOURCE_LANG: A column typically indicating the original language in which the record was created.

Common Use Cases and Queries

This table is primarily accessed by the application runtime to display localized term descriptions on invoices, transaction entry forms, and reports. A common reporting need is to extract payment term details for a specific language. For instance, to list all active payment terms in French, one might join with the base table:

SELECT rt.name, rtl.description
FROM ra_terms_b rt, ra_terms_tl rtl
WHERE rt.term_id = rtl.term_id
AND rtl.language = 'F'
AND rt.status = 'A'
AND SYSDATE BETWEEN rt.start_date_active AND NVL(rt.end_date_active, SYSDATE);

Another critical use case is during data migration or setup, where translated values must be populated for each installed language. Developers also reference this table when creating custom reports that need to respect the user's session language, typically using the USERENV('LANG') function or joining via the FND_LANGUAGES table.

Related Objects

RA_TERMS_TL has direct dependencies with several key Receivables objects. Its primary relationship is with the base table RA_TERMS_B, which holds the non-translatable attributes and rules for payment terms. The view RA_TERMS_V (or similarly named) often serves as a public interface, combining data from both _B and _TL tables based on the current session language. The table is also referenced by transaction tables like RA_CUSTOMER_TRX_ALL (via TERM_ID) to store the terms applicable to an invoice. For programmatic access, the standard Payment Terms API (likely AR_TERMS_PUB) would handle the creation and maintenance of records in this translation table.