Search Results payout_basis_name

Overview

OKL_LA_PASSTHROUGH_HDR_UV is a user interface view owned by the APPS schema within the OKL (Leasing and Finance Management) product family. It presents passthrough fee header information in a denormalized, presentation-ready form suitable for concurrent programs, OAF pages, and ad hoc reporting. The view captures the basic attributes of a passthrough arrangement — the contract or clearing line it belongs to, its start date, effective dating, term, payout basis, and associated stream type — and resolves coded values into their translatable lookup meanings so that users and downstream processes are not required to join to FND_LOOKUPS independently.

The "_UV" suffix marks this as a user-facing view rather than a table of record; the underlying stored data resides in OKL_PARTY_PAYMENT_HDR. Because the view exposes the resolved PAYOUT_BASIS_NAME column derived from FND_LOOKUPS, it is the natural access point when a query or report must display the human-readable payout basis (for example, "Actual", "Straight-line", or other seeded OKL_PAYOUT_BASIS values) alongside the passthrough header record.

Underlying Base Objects

The view is defined over the following documented objects:

• OKL_PARTY_PAYMENT_HDR (SYNONYM) — the primary passthrough fee header table, aliased PPH. It supplies the header identifier, the originating contract and clearing line references, effective dating, term, the payout basis code and formula, and the passthrough stream type identifier.
• OKL_STRM_TYPE_TL (SYNONYM) — the translatable stream type table, aliased STYT. It is joined on an outer-join (STYT.ID (+) = PPH.PASSTHRU_STREAM_TYPE_ID) and filtered by the session language (STYT.LANGUAGE (+) = USERENV('LANG')) to return the translated stream type name.
• FND_LOOKUPS (VIEW) — the standard Oracle lookup view, aliased LKP_PYT_BASIS. It is outer-joined on LOOKUP_CODE = PPH.PAYOUT_BASIS with LOOKUP_TYPE constrained to 'OKL_PAYOUT_BASIS', yielding the MEANING column exposed as PAYOUT_BASIS_NAME.
• FND_GLOBAL (PACKAGE) — referenced through USERENV('LANG') to resolve the runtime language for the translatable stream type join.

Because the lookup and stream type joins are outer joins, records in OKL_PARTY_PAYMENT_HDR are preserved even when no matching lookup code or stream type translation exists. The view therefore behaves as a header-driven projection rather than a filtered subset.

Key Columns

• ID — the passthrough header identifier, uniquely identifying the arrangement.
• CLE_ID — the associated clearing line identifier, linking the passthrough to its contract-clearing context.
• DNZ_CHR_ID — the contract header identifier (denormalized), tying the passthrough to the originating lease or finance contract.
• PASSTHRU_START_DATE — the date on which the passthrough arrangement begins.
• PAYOUT_BASIS — the stored lookup code describing how the payable is to be paid out.
• PAYOUT_BASIS_NAME — the resolved FND_LOOKUPS meaning for the payout basis; this is the column users typically require when searching on "payout basis name".
• EFFECTIVE_FROM / EFFECTIVE_TO — the date range during which the record is active.
• PASSTHRU_TERM — the term or duration defined for the passthrough.
• PAYOUT_BASIS_FORMULA — the formula or expression governing calculation under the selected payout basis.
• PASSTHRU_STREAM_TYPE_ID and NAME — the stream type identifier and its session-language name.

Common Use Cases and Queries

Typical uses include extracting passthrough fee headers for reconciliation, validating that every stored PAYOUT_BASIS resolves to a seeded lookup meaning, and feeding OAF or BI Publisher layouts that must render the stream type name in the user's language. A representative query returning the readable payout basis for a given contract follows:

• SELECT id, dnz_chr_id, passthru_start_date, payout_basis, payout_basis_name, passthru_term, name FROM okl_la_passthrough_hdr_uv WHERE dnz_chr_id = :p_chr_id;
• SELECT payout_basis, payout_basis_name, COUNT(*) FROM okl_la_passthrough_hdr_uv GROUP BY payout_basis, payout_basis_name;
• SELECT id, cle_id, payout_basis_name, passthru_stream_type_id, name FROM okl_la_passthrough_hdr_uv WHERE effective_from >= :p_from_date AND NVL(effective_to, SYSDATE) <= :p_to_date;

Because the view is a read-only projection, it is safe for concurrent reporting use; no DML should be issued against it. In 12.1.1 and 12.2.2 the definition is identical, and the APPS schema grants determine visibility to reporting and integration accounts.