Search Results okl_la_payment_structure

Overview

APPS.OKL_OR_PAYMENT_HEADER_UV is a reporting and integration view in the Oracle EBS Lease Management (OKL) module. Its name follows the OKL standard convention, where the "OR" prefix denotes an operational reporting view, and the "_UV" suffix identifies it as a user-facing view intended for queries, extracts, and interfaces rather than for direct inserts or updates. The view consolidates payment header information derived from the lease and contract rule model, joining lease header data with the rule hierarchies that define payment structures, frequencies, and arrears behaviour.

The view is a header-level construct: it exposes one row per payment rule header (a rule belonging to rule category LASLH) combined with its associated structure-line rule (category LASLL). Because the underlying rule model stores administrative attributes—such as payment structure code, frequency, and arrears indicator—as rule information attributes rather than dedicated columns, the view decodes these codes into descriptive names using the OKL_LLA_UTIL_PVT lookup utility, making the output directly consumable by reports and downstream systems.

Underlying Base Objects

The view is defined over the following documented base objects, accessed through APPS synonyms:

• OKC_RULE_GROUPS_B — provides the rule group RGP_LALEVL (rgd_code = 'LALEVL'), the container that anchors the lease-level payment rules to a contract.
• OKC_RULES_B — appears twice: as RUL_LASLH (the payment header rule, rule_information_category = 'LASLH') and as RUL_LASLL (the payment structure line rule, rule_information_category = 'LASLL'). The two are related via the rule group and the object2_id1/object2_id2 linkage.
• OKC_K_HEADERS_B — supplies contract header attributes, notably start_date.
• OKL_K_HEADERS — supplies lease-specific header attributes, notably term_duration, and is joined to OKC_K_HEADERS_B on id.
• OKL_STRM_TYPE_TL — the stream type translation table, providing the stream type name (sty_name) for the language returned by USERENV('LANG').
• OKL_LLA_UTIL_PVT — a package whose get_lookup_meaning function translates structure, frequency, and yes/no codes into display names.

The core join path is: contract header to rule group to LASLH rule to LASLL rule, with the stream type and lease header joined in for descriptive attributes, and the language-sensitive condition ensuring only the current session language row is returned.

Key Columns

• start_date and term_duration — contract and lease header attributes giving the commencement and length of the agreement.
• rgp_lalevl_id, rgp_lalevl_rgd_code, dnz_chr_id, cle_id — identifiers of the rule group, its code, the owning contract header, and the contract line if applicable.
• rul_laslh_id, rul_laslh_rule_info_cat, rul_laslh_object1_id1, rul_laslh_object1_id2, rul_laslh_jtot_object1_code — the LASLH payment header rule identity and its object references.
• sty_name — the stream type name associated with the rule's object1_id1.
• structure_code and structure_name — the payment structure (from rule_information5) and its decoded meaning.
• frequency_code and frequency_name — the payment frequency (from object1_id1) and its decoded meaning.
• arrears_yn and arrears_yn_name — the arrears indicator, NVL'd to 'N', and its decoded name.
• service_fee_cle_id, service_fee_name, asset_cle_id, asset_number, asset_description — reserved columns returned as NULL in this version, retaining a stable interface shape.

Common Use Cases and Queries

Typical uses include lease payment stream reporting, validation of payment setup against contractual terms, and data extraction for billing reconciliation or external interfaces.

• List payment headers for a contract: SELECT rgp_lalevl_id, rul_laslh_id, structure_name, frequency_name, arrears_yn_name FROM apps.okl_or_payment_header_uv WHERE dnz_chr_id = :p_chr_id;
• Identify arrears arrangements: SELECT dnz_chr_id, rul_laslh_id FROM apps.okl_or_payment_header_uv WHERE arrears_yn = 'Y';
• Aggregate by payment frequency: SELECT frequency_name, COUNT(*) FROM apps.okl_or_payment_header_uv GROUP BY frequency_name;

Because the view resolves rule information into codes and decoded names, it is the preferred access point for reporting on lease payment headers without navigating the underlying OKC rule tables directly.