Results for “okl_la_payments_uv”

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

Overview

OKL_LA_PAYMENTS_UV is a user interface (UI) view owned by the APPS schema within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment. It belongs to the OKL product family — Oracle Lease and Finance Management — and is documented as a valid, enabled database object of type VIEW. Its stated purpose in the ETRM metadata is to serve as the "User Interface view for payments page," meaning it is the curated data source behind the Lease Management payments screen rather than a general-purpose reporting view. As a UI view, it exposes a controlled projection of lease payment rule data so that the OAF-based payments page can display schedule information — start dates, end dates, rule identifiers, and descriptive rule attributes — without querying the underlying contract and rule tables directly.

Underlying Base Objects

The view is defined over OKC_RULES_V, a view in the Oracle Contracts (OKC) module that presents lease and contract rules. The filter RULE_INFORMATION_CATEGORY = 'LASLL' restricts output to lease schedule (LASLL) rules, separating payment lines from other rule categories. The SELECT list references several supporting objects:

• OKC_RULES_V (VIEW) — primary driving object, aliased RL, supplying ID, RGP_ID, DNZ_CHR_ID, the JTOT_OBJECTn_CODE / OBJECTn_IDn pairs, and the fifteen RULE_INFORMATIONn columns plus RULE_INFORMATION_CATEGORY.
• OKC_K_HEADERS_B (SYNONYM) — a correlated scalar subquery retrieves END_DATE from the contract header where ID equals RL.DNZ_CHR_ID, providing the authoritative contract termination date.
• OKL_LA_PAYMENTS_PVT (PACKAGE) — supplies GET_DISPLAY_END_DATE and GET_START_DAY functions used to derive the computed END_DATE and start-day calculations.
• OKL_LLA_UTIL_PVT (PACKAGE) — supplies GET_DISPLAY_DATE, applied to RULE_INFORMATION2 to render a display-formatted date.
• FND_DATE (PACKAGE) — supplies CANONICAL_TO_DATE, converting the canonical RULE_INFORMATION2 string into the START_DATE value used for ordering.

Key Columns

• ID — the rule identifier inherited from OKC_RULES_V.
• RGP_ID / DNZ_CHR_ID — rule group identifier and contract header identifier, linking the payment line to its contract.
• OBJECT1_ID1, OBJECT2_ID1, OBJECT3_ID1 and matching _ID2 / JTOT_OBJECT_CODE columns — the generic object reference triplets that qualify the rule's associations, used by the UI to resolve the linked entities.
• RULE_INFORMATION1 through RULE_INFORMATION15 — the descriptive-flex attribute set; entries such as RULE_INFORMATION2 (start date), RULE_INFORMATION3 (payment frequency), and RULE_INFORMATION7 (term-related) carry schedule semantics.
• START_DATE — the canonical date derived via FND_DATE.CANONICAL_TO_DATE on RULE_INFORMATION2; the query is ordered by this column.
• CNL_START_DATE — the raw RULE_INFORMATION2 alias, retained for comparison or canonical display.
• END_DATE — computed by OKL_LA_PAYMENTS_PVT.GET_DISPLAY_END_DATE using start date, RULE_INFORMATION7, object references, and the contract header END_DATE.

Common Use Cases and Queries

Because the view already applies the LASLL category filter and date-conversion logic, it is the preferred source for payment schedule listings. A standard call takes the form:

• SELECT id, rgp_id, dnz_chr_id, start_date, end_date FROM okl_la_payments_uv WHERE dnz_chr_id = :contract_id ORDER BY start_date; — retrieve ordered payment lines for one lease contract.
• SELECT object1_id1, rule_information1, rule_information3, end_date FROM okl_la_payments_uv WHERE rgp_id = :rule_group_id; — inspect scheduling detail for a specific rule group.
• Reconciliation queries joining DNZ_CHR_ID to OKC_K_HEADERS_B for contract-level reporting, or extracting RULE_INFORMATION2 and END_DATE for period-based payment analysis.

Direct DML against the view is not supported; it is read-only and intended for display, so any data correction must target OKC_RULES_V's base tables.