Results for “ra_terms_tl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

RA_TERMS_TL is the multi-lingual support (MLS) table for Payment Terms within the Oracle Receivables (AR) module. In Oracle EBS 12.1.1 and 12.2.2, payment terms define the conditions under which customers are expected to pay invoices, including due dates, discount periods, and installment schedules. Because EBS supports multiple installed languages, the translatable attributes of a payment term — specifically its user-facing NAME and DESCRIPTION — are not stored in the base RA_TERMS table. Instead, they are held in RA_TERMS_TL, one row per language, while the base table RA_TERMS retains the language-independent business and calculation attributes.

The table is owned by the AR schema and resides in the APPL_TOP database tier. Its primary key is RA_TERMS_TL_PK, defined on the composite of TERM_ID and LANGUAGE, which enforces exactly one translated record per term per installed language. From a heuristic Data Vault modeling perspective, this object classifies as a satellite: it is a descriptive, language-dependent child of the TERM_ID hub represented by the base RA_TERMS table. It carries no independent business identity of its own — every row exists only to describe an existing payment term in a specific language. The uniqueness constraint RA_TERMS_TL_U1 (TERM_ID, LANGUAGE, ZD_EDITION_NAME) further refines this relationship under the Editioning model introduced in 12.2.x.

Key Information Stored

The documented physical schema contains eleven columns. The most significant are:

• TERM_ID — Surrogate foreign key to RA_TERMS.TERM_ID; the component that links the translation to its parent payment term.
• LANGUAGE — The NLS language code (for example, US or AR) identifying which installed language this row translates.
• NAME — The translated, user-visible name of the payment term (for example, "Net 30" rendered in an alternate language).
• DESCRIPTION — The translated free-text description displayed to users in the relevant language.
• SOURCE_LANG — The language in which the term was originally created; used to flag whether a given translation is the source or a derived version.
• ZD_EDITION_NAME — The Editioning column present in 12.2.x, enabling online patching by allowing multiple editions of the same term/language row to coexist.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS Who columns providing audit and concurrency control.

The surrogate primary key is RA_TERMS_TL_PK on (TERM_ID, LANGUAGE). The unique index RA_TERMS_TL_U1 on (TERM_ID, LANGUAGE, ZD_EDITION_NAME) functions as the business-key candidate in 12.2.x, guaranteeing that for any term, language, and edition combination there is precisely one active row. Note that the surrogate key is not TERM_ID alone but the composite with LANGUAGE, reflecting the internationalization requirement.

Common Use Cases and Queries

Typical scenarios include retrieving the localized name of a payment term for a report, validating translation completeness across installed languages, and joining translated descriptions to invoice or customer records.

A standard lookup for a term in the current session language:

SELECT t.term_id, tl.name, tl.description
FROM   ra_terms t, ra_terms_tl tl
WHERE  t.term_id = tl.term_id
AND    tl.language = USERENV('LANG');

Identifying terms missing a translation for a specific language is a common data-quality check:

SELECT t.term_id
FROM   ra_terms t
WHERE  NOT EXISTS (SELECT 1 FROM ra_terms_tl tl
                   WHERE tl.term_id = t.term_id
                   AND tl.language = 'AR');

Reporting queries frequently join RA_TERMS_TL to RA_TERMS to present the localized name alongside the term's due-date and discount rules, which are stored in the base table.

Related Objects

The following objects are most significant to RA_TERMS_TL:

• RA_TERMS — Parent base table joined on TERM_ID; holds language-independent attributes.
• RA_TERMS_B — The 12.2.x editioning variation of the base table, also joined on TERM_ID.
• RA_CUSTOMERS — References payment terms via TERM_ID for receivables profile assignment.
• RA_CUST_RECEIPT_METHODS — Links payment terms to receipt methods in receipt configuration.
• AR_PAYMENT_SCHEDULES — Uses terms to derive installment due dates and discount eligibility.
• RA_INTEREST_RATES / AR_INTEREST_RATES — Associated with late-charge configurations tied to terms.
• FND_LANGUAGES — Provides validation of the LANGUAGE column against installed languages.
• FND_FLEX_VALUES / AR_LOOKUPS — Supporting reference data used in payment-terms setup screens.

Together these objects form the payment-terms reference submodel consumed throughout Receivables, Order Management, and Advanced Collections.