Results for “okl_pay_terms_uv”

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

Overview

OKL_PAY_TERMS_UV is a view owned by the APPS schema in Oracle E-Business Suite, registered within the OKL — Lease and Finance Management product family. Its documented status is VALID, and it is described in the ETRM repository as a "View for list of values of Funding request Payment Terms." The object therefore serves a narrow but well-defined purpose: supplying the selection list from which users choose payment terms when creating or maintaining funding requests in Lease and Finance Management. Rather than storing any data of its own, the view presents a filtered, orderable projection of the payment terms maintained in Oracle Payables, restricted to those terms that are currently enabled and within their effective date range.

Because it reads from AP_TERMS_V, OKL_PAY_TERMS_UV inherits the standard Payables payment terms definition and exposes it to the OKL funding request flow. This decoupling means that payment terms are maintained in a single place in Payables and consumed consistently by Lease and Finance Management without duplicating setup data.

Underlying Base Objects

The view is defined over a single referenced base object, AP_TERMS_V, described in the documented metadata as a VIEW. The view text is:

• SELECT APT.TERM_ID TERM_ID, APT.NAME TERMS, APT.DESCRIPTION FROM AP_TERMS_V APT
• WHERE ENABLED_FLAG = 'Y'
• AND TRUNC(SYSDATE) BETWEEN TRUNC(NVL(START_DATE_ACTIVE, SYSDATE)) AND TRUNC(NVL(END_DATE_ACTIVE, SYSDATE))
• ORDER BY TERMS

Two filtering rules are applied. First, only terms with an enabled flag of 'Y' are returned. Second, the current date, truncated to remove the time component, must fall between the truncated start and end active dates. The NVL functions substitute SYSDATE where a start or end date is null, effectively treating an open-ended date range as always valid. The result set is sorted alphabetically by the terms name.

Key Columns

The view exposes three columns:

• TERM_ID — The unique identifier of the payment term, sourced from TERM_ID on AP_TERMS_V. This is the value typically stored on the funding request record as the foreign key reference.
• TERMS — The payment term name as maintained in Payables. This is the user-facing value displayed in the list of values and is the column on which the ORDER BY clause sorts.
• DESCRIPTION — The free-text description of the payment term, useful for distinguishing between similarly named terms when presented alongside TERMS in a selection list.

Common Use Cases and Queries

The primary use case is populating the payment terms list of values on the funding request entry form in Lease and Finance Management. Queries against the view are typically validation or lookup operations rather than reporting joins.

A common pattern resolves a selected term name back to its identifier:

• SELECT TERM_ID, TERMS, DESCRIPTION FROM APPS.OKL_PAY_TERMS_UV WHERE TERMS = :term_name;

A second scenario validates that a stored TERM_ID still refers to an active, currently effective term before processing a funding request:

• SELECT TERM_ID, TERMS FROM APPS.OKL_PAY_TERMS_UV WHERE TERM_ID = :term_id;

A third pattern is confirming that a given term appears in the selection list by testing a term name or id against the view, using the same WHERE TERMS = :term_name predicate. Because the view applies date and enablement filtering at query time, results shift automatically as terms are enabled, disabled, or fall outside their active window. The filter makes the view unsuitable for historical reporting of expired terms; such reporting should query AP_TERMS_V directly. Where the user searched for "ap_terms_v", this view is the OKL-specific, filtered entry point to that Payables source.