Results for “ap_terms_vl”

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

Overview

AP_TERMS_VL is a Payables (AP) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes payment term definitions maintained in the Oracle Payables module and represents the language-specific ("VL," or view language) presentation of payment terms data. Payment terms drive the calculation of due dates, discount dates, discount percentages, installment schedules, and due-date cutoffs applied to supplier invoices, credit memos, and recurring payment schedules. Because payment terms are translatable reference data, Oracle stores them in a pair of tables — a translation table holding the descriptive columns and a base table holding the non-translatable attributes — and publishes AP_TERMS_VL as the reporting and integration surface for that data.

The view is defined over the translation table AP_TERMS_TL and adds a WHERE predicate restricting rows to the session language via USERENV('LANG'). This design means AP_TERMS_VL returns only the term names and descriptions relevant to the current runtime language, which is the behavior expected by Oracle Forms, concurrent programs, and OAF-based pages. The object is documented as VALID in the ETRM and is a supported read interface for reporting and integration; it is not intended as a direct data-entry target.

Underlying Base Objects

Per the ETRM metadata, AP_TERMS_VL is defined over a single referenced base object, AP_TERMS_TL, accessed in the source query through a synonym. The view text is a straightforward projection of the translation table's columns:

• AP_TERMS_TL — the translation table supplying NAME and DESCRIPTION along with the shared term attributes (TERM_ID, TYPE, ENABLED_FLAG, DUE_CUTOFF_DAY, RANK, START_DATE_ACTIVE, END_DATE_ACTIVE, and the ATTRIBUTE1–15 flexfield columns).
• Synonym reference — the query selects from AP_TERMS_TL by way of the synonym visible in the documented definition, with the alias B applied to every projected column.

Notably, the view text as documented selects directly from AP_TERMS_TL with a language filter and does not perform a join to a separate non-translated AP_TERMS_B table. All 28 documented columns — beginning with ROW_ID and TERM_ID and ending with NAME and DESCRIPTION — are sourced from that translation table.

Key Columns

• ROW_ID — the ROWID of the underlying translation row; used for row identification in Forms and for certain updates.
• TERM_ID — the primary key and foreign key reference used throughout Payables (for example, on AP_INVOICES_ALL and AP_SUPPLIERS) to link an invoice or supplier to its payment terms.
• NAME / DESCRIPTION — the translated term name and description, filtered to the session language.
• TYPE — the term basis (for example, a fixed number of days, a specific day of the month, or a proximity/day-of-month rule).
• DUE_CUTOFF_DAY — the cutoff day configuration governing how due dates are calculated.
• ENABLED_FLAG — indicates whether the term is active and selectable.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range for the term.
• RANK — the display/sort ranking for the term list of values.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield columns reserved for customer extensions.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

AP_TERMS_VL is commonly joined to invoice and supplier tables to resolve human-readable term names in reports and extracts. A typical query returning active terms for the current language is:

SELECT term_id, name, description, type, due_cutoff_day, enabled_flag FROM ap_terms_vl WHERE enabled_flag = 'Y' ORDER BY rank, name;

To resolve the terms assigned to invoices, the view is joined on TERM_ID:

SELECT i.invoice_num, i.invoice_date, t.name term_name, t.due_cutoff_day FROM ap_invoices_all i, ap_terms_vl t WHERE i.term_id = t.term_id AND i.org_id = :p_org_id;

Because the view enforces a USERENV('LANG') filter, queries executed in a multilingual environment return only the rows matching the session language; reporting tools that require all languages must query the base AP_TERMS_TL table directly. The view remains the preferred, supported interface for standard reporting and integration against Payables payment terms.