Results for “okl_pool_contracts_uv”

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

Overview

OKL_POOL_CONTRACTS_UV is a seeded APPS-owned database view within the Oracle E-Business Suite Leasing and Finance Management (OKL) module. It is classified as a UI view, meaning it exists primarily to supply the Securitization Pool Contracts page with the contract-level data required to display, select, and process lease and loan contracts that participate in a securitization pool. The view carries a VALID status in both release 12.1.1 and 12.2.2 and is therefore safe to reference from custom reports, integrations, and extensions, provided the standard caution regarding unsupported direct modification of seeded objects is observed.

From a reporting perspective, the view consolidates attributes that normally require joins across the contract header tables and the rules framework. It exposes securitization-relevant fields such as the pre-tax yield, the book classification, and the assignability flag, allowing downstream consumers to evaluate which contracts qualify for pool assignment without reconstructing the underlying rule model themselves.

Underlying Base Objects

The view is defined over four documented base objects, all accessed through APPS synonyms:

• OKC_K_HEADERS_B — the core contract headers table, aliased CHRB, supplying the contract identifier, contract number, status, start and end dates, authoring organization, and currency.
• OKL_K_HEADERS — the OKL extension of the contract header, aliased KHRB, supplying leasing-specific attributes including pre-tax yield, deal type, product identifier, and the assignability flag.
• OKC_RULE_GROUPS_B — the rule group header, aliased RGPB, linked on DNZ_CHR_ID to the contract header.
• OKC_RULES_B — the individual rule records, aliased RULB, linked to the contract and to the rule group, filtered to the LATOWN rule information category.

The joins are driven by the shared contract identifier (CHRB.ID), creating a one-to-many relationship between the contract and its rule rows that is narrowed by the RULE_INFORMATION_CATEGORY predicate. Because the LATOWN category is used to derive the tax owner, the view returns one row per qualifying rule record per contract.

Key Columns

• DNZ_CHR_ID — the internal contract identifier inherited from OKC_K_HEADERS_B.ID; the primary join key for all related entities.
• CONTRACT_NUMBER — the user-visible contract number used for identification on the pool contracts page.
• PRE_TAX_YIELD — the yield obtained from the leasing header, used in securitization yield calculations.
• BOOK_CLASSIFICATION — sourced from KHRB.DEAL_TYPE, indicating whether the contract is treated as a lease, loan, or comparable classification.
• PDT_ID — the product identifier to which the contract belongs.
• ASSIGNABLE_YN — the flag that determines whether a contract may be assigned into a securitization pool; this is the column most frequently referenced by users searching for assignability information.
• STS_CODE — the current contract status code.
• START_DATE / END_DATE — the contract term boundaries.
• OPERATING_UNIT / AUTHORING_ORG_ID — both map to CHRB.AUTHORING_ORG_ID, identifying the owning organization and supporting multi-org security.
• CURRENCY_CODE — the contract currency.
• TAX_OWNER — derived from RULB.RULE_INFORMATION1 for rules in the LATOWN category.

Common Use Cases and Queries

The view supports identification of assignable contracts, reconciliation of pool membership, and yield or tax-owner reporting. A representative query filters on the assignability flag and status:

• SELECT contract_number, pre_tax_yield, book_classification, assignable_yn, currency_code, tax_owner FROM okl_pool_contracts_uv WHERE assignable_yn = 'Y' AND sts_code = 'BOOKED'
• SELECT operating_unit, book_classification, COUNT(*) FROM okl_pool_contracts_uv GROUP BY operating_unit, book_classification
• SELECT contract_number, start_date, end_date, tax_owner FROM okl_pool_contracts_uv WHERE start_date >= :p_from_date

Because rows are multiplied by the LATOWN rule join, consumers should de-duplicate on DNZ_CHR_ID when a single row per contract is required. Custom code should treat the view as read-only and avoid relying on the internal aliases or column ordering, which are subject to change across patches.