Results for “okl_bpd_pay_terms_v”

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

Overview

OKL_BPD_PAY_TERMS_V is a lightweight, read-only view in the Oracle Lease and Finance Management (OKL) module, owned by the APPS schema. Its purpose is to expose the set of active, enabled payment terms maintained in Oracle Payables so that the OKL billing and payment (BPD) subsystems can present a validated list of terms without querying the underlying Payables dictionary directly. The view acts as a curated lookup layer: rather than returning every term defined in the payables setup, it restricts output to terms whose ENABLED_FLAG equals 'Y', thereby eliminating obsolete or disabled terms from downstream selection lists, reporting queries, and integration payloads.

In the ETRM 12.2.2 documentation this object carries a status of VALID and is classified as a VIEW. It is significant to the OKL module because lease contracts, billing schedules, and finance-related payment arrangements depend on consistent, current payment-term definitions that originate in the Payables application. By encapsulating the filter and column projection, the view provides a stable interface that insulates OKL components from changes in the AP_TERMS_V definition and from the multi-org and language-dependent behavior underlying the Payables terms model.

Underlying Base Objects

The documented base object referenced by OKL_BPD_PAY_TERMS_V is a single view:

• AP_TERMS_V (VIEW) — the Payables payment terms view, itself typically defined over AP_TERMS_TL (the translated terms table) and related entities such as AP_TERMS_B. When a term is defined, Payables stores the base attributes and the language-specific name; AP_TERMS_V resolves these into a single enabled-terms view for consumption by other products.

The view text is straightforward. It selects TERM_ID and NAME from AP_TERMS_V, aliasing NAME as TERMS, and applies the predicate ENABLED_FLAG = 'Y':

• SELECT APT.TERM_ID TERM_ID, APT.NAME TERMS FROM AP_TERMS_V APT WHERE ENABLED_FLAG = 'Y'

Because the source is a view rather than a table, no distinct storage or index exists on OKL_BPD_PAY_TERMS_V; all access is resolved at runtime against AP_TERMS_V, which in turn reads the Payables base and translation tables. Any performance characteristics therefore derive entirely from the base objects and their indexes.

Key Columns

The view exposes exactly two columns, matching the documented structure:

• TERM_ID — the numeric identifier of the payment term. This is the primary key value from the Payables terms definition and serves as the foreign key used by OKL records that reference a payment term. It is the column that should be stored on transactional and setup records; the name is presentational only.
• TERMS — the user-facing name of the payment term (aliased from NAME in AP_TERMS_V). This is the descriptive label presented to users, such as "Net 30" or "Immediate". Because names are language-dependent in Payables, the values returned reflect the session's language environment.

The implicit filter column, ENABLED_FLAG, is not projected. Consequently, every row returned by this view can be treated as selectable; callers do not need to test status themselves.

Common Use Cases and Queries

The view is most often used to populate list-of-values (LOV) queries, validation routines, and reports that present payment-term choices to OKL users. A typical lookup joins the view to OKL transaction data to obtain the term name for display:

• Populating an LOV: SELECT TERMS, TERM_ID FROM APPS.OKL_BPD_PAY_TERMS_V ORDER BY TERMS
• Resolving a term name for a stored ID: SELECT TERMS FROM APPS.OKL_BPD_PAY_TERMS_V WHERE TERM_ID = :p_term_id
• Joining to OKL contract or billing records to report terms alongside lease data, using TERM_ID as the join key to the OKL side and retrieving TERMS for presentation.

Because the view restricts to enabled terms, it is also convenient for integration and interface programs that must validate an incoming payment-term reference before accepting it. Callers should note that disabled terms intentionally do not appear, so a missing TERM_ID in the view does not necessarily mean the identifier is invalid — only that the corresponding term is not currently enabled. Filtering logic should be applied with that distinction in mind.