Results for “ap_terms_tl”

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

Overview

AP_TERMS_TL is the translation-enabled intersection table that stores the language-specific descriptive attributes of payment terms in Oracle Payables (AP). In an Oracle E-Business Suite 12.1.1 or 12.2.2 environment, payment terms define the due date calculation and discount rules that govern supplier invoices. Because users in a multi-language installation must see term names and descriptions in their own language, Oracle separates the language-neutral attributes into AP_TERMS (the base table) and the translatable text attributes into AP_TERMS_TL. The _TL suffix identifies this as a Translation (TL) table, which is validated against the language definitions held in FND_LANGUAGES.

From a dimensional modeling perspective, the source metadata classifies this object heuristically as a link table. This is a reasonable modeling suggestion: AP_TERMS_TL does not store a standalone business entity but rather associates a term identifier with a language, forming a bridge between the AP_TERMS entity and the FND_LANGUAGES reference set. Practitioners building a data vault or reporting layer should treat it as a translated descriptive satellite linked to the term hub, filtered on the user's session language.

Key Information Stored

The most significant columns in AP_TERMS_TL are:

• TERM_ID and LANGUAGE — Together these form the primary key AP_TERMS_PK. TERM_ID is the surrogate key inherited from AP_TERMS; LANGUAGE is the ISO language code from FND_LANGUAGES.
• NAME — The user-facing name of the payment term, which is the primary business attribute displayed in the Payables Terms window and on invoice headers.
• DESCRIPTION — The longer free-text explanation of the term's purpose and calculation behavior.
• ENABLED_FLAG — Indicates whether the term is active and selectable when entering invoices or supplier sites.
• DUE_CUTOFF_DAY — The day of the month after which the due date is pushed to the following period for terms with cutoff logic.
• TYPE — Classifies the term as a discount or due-date term, driving which validation path Invoice Workbench applies.
• START_DATE_ACTIVE and END_DATE_ACTIVE — Effective-dating bounds that control whether a term is available for assignment at a given time.
• RANK — Controls the display or processing order of terms, particularly where multiple terms are stacked on one invoice.
• SOURCE_LANG — The source language from which this row was derived; also validated against FND_LANGUAGES.
• ATTRIBUTE_CATEGORY through ATTRIBUTE15 — The standard Oracle descriptive flexfield (DFF) columns reserved for customer-defined extensions.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN support standard "who/when" tracking.

AP_TERMS_TL_U1 is a unique index on (TERM_ID, LANGUAGE) and is effectively a business-key candidate, mirroring the primary key. The true business identifier desired by users is NAME, but NAME is not guaranteed unique and must be scoped by LANGUAGE.

Common Use Cases and Queries

Reporting on payment terms almost always requires filtering by language to avoid duplicate rows, since each term appears once per translated language. A typical query joining to the base table looks like this:

SELECT t.term_id, tl.name, tl.description, t.enabled_flag
FROM   ap_terms t, ap_terms_tl tl
WHERE  t.term_id = tl.term_id
AND    tl.language = USERENV('LANG');

Common scenarios include validating that a supplier site's default term is enabled (ENABLED_FLAG = 'Y') and within its START_DATE_ACTIVE/END_DATE_ACTIVE range; populating an invoice register with term names; and auditing which terms have DFF attribute values populated for a specific ATTRIBUTE_CATEGORY. A typical reporting use case is a payment-terms listing for a specific operating unit, joined through AP_TERMS to supplier site assignments. Because DFF columns reside in this table for term-level meaning, any flexfield extract must reference AP_TERMS_TL rather than AP_TERMS.

Related Objects

• AP_TERMS — The base, language-neutral term table joined on TERM_ID; the parent of the surrogate key.
• FND_LANGUAGES — Referenced by both LANGUAGE and SOURCE_LANG; defines the installed languages and their ISO codes.
• AP_TERMS_SCHEDULES (and installment tables) — Consume TERM_ID to compute invoice installment due dates.
• PO_VENDOR_SITES_ALL / AP_SUPPLIER_SITES_ALL — Assign default payment terms to supplier sites via TERM_ID.
• AP_INVOICES_ALL — Stores TERMS_ID/TERM_ID on invoices created against a term.
• AP_PAYMENT_TERMS (view) — A translated reporting view that typically masks the underlying TL join.

Together these objects provide the full lifecycle view: term definition in AP_TERMS/AP_TERMS_TL, assignment through supplier sites, and application on invoices and installments.