Search Results arrears_yn_name

Overview

OKL_OR_PAYMENT_HEADER_UV is a reportable view in the OKL (Leasing and Finance Management) module of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2 and owned by the APPS schema. It presents payment header information for lease and finance contracts, resolving the raw rule and rule group identifiers stored in the Oracle Contracts (OKC) repository into business-meaningful values. Specifically, the view exposes the lease payment structure and payment frequency associated with a contract, along with arrears indicators and contract term attributes. Because it joins contract header data to the OKL stream header, it is suited to operational reporting, reconciliation, and integration extracts where the payment terms of a lease must be communicated in descriptive rather than coded form.

Underlying Base Objects

The view is defined over the following documented base objects:

• OKC_K_HEADERS_B — the contract header base table, supplying contract identity and start date.
• OKC_RULE_GROUPS_B — the rule group container, filtered to the rule group code 'LALEVL' (the lease payment rule group).
• OKC_RULES_B — referenced twice: once as RUL_LASLH for the rule information category 'LASLH' (structure header), which carries the stream type, and once as RUL_LASLL for the rule information category 'LASLL' (structure line), which carries the payment structure, frequency, and arrears attributes.
• OKL_K_HEADERS — the OKL contract header, supplying term duration.
• OKL_STRM_TYPE_TL — the stream type translation table, joined by language via USERENV('LANG') to return the translated stream type name.
• OKL_LLA_UTIL_PVT — a public package invoked through GET_LOOKUP_MEANING to convert lookup codes into their display meanings.

Joins are established on DNZ_CHR_ID and RGP_ID, ensuring that each structure line rule is correctly associated with its parent structure header rule and contract.

Key Columns

• START_DATE — contract start date from OKC_K_HEADERS_B.
• DURATION / TERM_DURATION — the lease term duration.
• DNZ_CHR_ID, CLE_ID — contract and line identifiers establishing the ownership chain.
• STY_NAME — the translated stream type name.
• STRUCTURE_CODE — the raw payment structure lookup value (RULE_INFORMATION5).
• STRUCTURE_NAME — the decoded payment structure meaning, returned by OKL_LLA_UTIL_PVT.GET_LOOKUP_MEANING against the OKL_LA_PAYMENT_STRUCTURE lookup type. This is the column most commonly targeted by users searching for "structure_name".
• FREQUENCY_CODE / FREQUENCY_NAME — the payment frequency code and its decoded meaning from the OKL_FREQUENCY lookup.
• ARREARS_YN / ARREARS_YN_NAME — the arrears indicator and its decoded OKL_YES_NO meaning, with NVL defaulting to 'N'.

Several columns, including SERVICE_FEE_CLE_ID and ASSET_CLE_ID, are defined as TO_CHAR(NULL) placeholders and therefore always return null in this view.

Common Use Cases and Queries

Typical usage includes reporting payment structures per contract, validating that decoded frequency and structure values reconcile with contract terms, and building integration extracts that require descriptive payment values. A representative query follows:

SELECT start_date, structure_code, structure_name, frequency_name, arrears_yn_name, sty_name FROM apps.okl_or_payment_header_uv WHERE dnz_chr_id = :contract_id;

Because STRUCTURE_NAME is resolved at runtime through a PL/SQL package call within the view text, performance may be affected on large result sets; filtering by DNZ_CHR_ID or START_DATE before invoking the view is advisable.