Results for “book_class_code”

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

Overview

OKL_SEC_BUYBACK_CONTRACTS_UV is an APPS-owned database view in Oracle E-Business Suite 12.1.1 and 12.2.2, delivered as part of the OKL — Leasing and Finance Management product family. It exists to support the securitization buyback contracts user interface, exposing a denormalized, query-ready projection of lease and finance contracts that have been flagged for securitized buyback treatment. Unlike a base table, the view provides no storage of its own; it consolidates columns from contract header, party, product, and lookup sources so that application UI regions and reporting tools can retrieve buyback contract data with a single, join-free query.

The view is particularly relevant to the term book_class, because it derives the BOOK_CLASS and BOOK_CLASS_CODE columns from the contract's deal type, translated through the OKL_BOOK_CLASS lookup type in FND_LOOKUPS. This makes the view the natural reporting surface whenever buyback contracts must be grouped, filtered, or reconciled by accounting book class. Only contracts appearing in an active pool are returned, which aligns the view with securitization processing rather than general contract inquiry.

Underlying Base Objects

According to the documented ETRM metadata, the view is defined over the following base objects, all referenced through APPS-owned synonyms except the package and lookup view:

• OKC_K_HEADERS_B — core contract header, supplying contract number, start date, end date, currency, and operating unit (ORG_ID).
• OKC_K_HEADERS_TL — translated header attributes, providing SHORT_DESCRIPTION subject to the session language.
• OKC_K_PARTY_ROLES_B — contract party role assignments, filtered to the LESSEE role with OBJECT1_ID2 = '#' to isolate the primary party.
• HZ_PARTIES — the Trading Community Architecture party registry, supplying the lessee name and party identifier.
• OKL_K_HEADERS — the OKL-specific header extension, contributing DEAL_TYPE (used as BOOK_CLASS_CODE) and the product identifier.
• OKL_PRODUCTS — product definition, yielding the PRODUCT name for each contract.
• FND_LOOKUPS — the lookup view, translating DEAL_TYPE into a user-facing BOOK_CLASS meaning via the OKL_BOOK_CLASS lookup type.
• OKL_POOL_CONTENTS — pool membership, joined in an EXISTS subquery restricted to STATUS_CODE = 'ACTIVE'.

The join architecture is contract-centric: OKC_K_HEADERS_B anchors the query and is joined by ID to its translation row, its OKL extension row, its lessee role row, and its product row. The EXISTS clause against OKL_POOL_CONTENTS is the filter that distinguishes this view from a generic contract listing.

Key Columns

• CUST_OBJECT1_ID1 — the party identifier of the lessee, derived from HZ_PARTIES.PARTY_ID.
• LESSEE — the party name of the lessee from HZ_PARTIES.PARTY_NAME.
• DNZ_CHR_ID — the contract header identifier (CHRB.ID), the primary key for joining to other OKC/OKL objects.
• CONTRACT_NUMBER — the human-readable contract number from OKC_K_HEADERS_B.
• SHORT_DESCRIPTION — the translated contract description from OKC_K_HEADERS_TL.
• BOOK_CLASS_CODE — the raw deal type value from OKL_K_HEADERS.DEAL_TYPE.
• BOOK_CLASS — the decoded meaning from FND_LOOKUPS for lookup type OKL_BOOK_CLASS.
• PDT_ID / PRODUCT — the product identifier and name from OKL_PRODUCTS.
• START_DATE / END_DATE — the contract term boundaries.
• CURRENCY_CODE — the contract currency.
• ORG_ID — the operating unit, enabling Multi-Org secured access.

Common Use Cases and Queries

Typical uses include: listing active securitized buyback contracts by book class; reconciling lessee and product detail for pool reporting; and feeding downstream extracts that require the decoded book class rather than the raw deal type code. A representative query filtering on book class is:

• SELECT contract_number, lessee, product, book_class_code, book_class, start_date, end_date FROM okl_sec_buyback_contracts_uv WHERE book_class = 'FINANCE LEASE' AND org_id = :p_org_id ORDER BY contract_number;
• SELECT book_class, COUNT(*) FROM okl_sec_buyback_contracts_uv GROUP BY book_class;
• SELECT c.contract_number, c.lessee, c.product FROM okl_sec_buyback_contracts_uv c WHERE c.dnz_chr_id IN (SELECT khr_id FROM okl_pool_contents WHERE status_code = 'ACTIVE');

Because the view already restricts output to contracts with an active pool membership, additional pool joins are typically redundant, though the pool identifier may be resolved separately through OKL_POOL_CONTENTS using DNZ_CHR_ID. Multi-Org security should be applied explicitly through ORG_ID in custom reports, since the view itself does not enforce row-level security beyond what the owning schema provides.