Results for “okl_ebiz_kheaders_v”

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

Overview

The OKL_EBIZ_KHEADERS_V view is an APPS-owned database object within the Oracle E-Business Suite OKL – Leasing and Finance Management module. Its primary purpose is to serve as the find grid for eBusiness Integration, presented on the Contracts tab of the eBusiness user interface. The view filters lease contracts by restricting the result set to records where SCS_CODE = 'LEASE', ensuring that only lease-classified contract headers are surfaced to the integration finder.

The view is integral to the eBusiness integration flow because it consolidates contract header attributes, status and subclass meanings, product and program details, private-label party information, and access-level computations into a single denormalized projection. The object is documented as VALID in the APPS schema and is available in both 12.1.1 and 12.2.2 environments.

Underlying Base Objects

OKL_EBIZ_KHEADERS_V is defined over a combination of synonyms, views, and packages that span the OKL, OKC, and HZ schemas. The documented base objects include:

• OKC_K_HEADERS_B – the base contract header table supplying the primary key ID, CONTRACT_NUMBER, currency, dates, and template flags.
• OKC_K_HEADERS_TL – the translated contract header table, providing SHORT_DESCRIPTION and COGNOMEN filtered by USERENV('LANG').
• OKL_K_HEADERS – the leasing-specific header extension supplying SYNDICATABLE_YN and ACCEPTED_DATE.
• OKC_STATUSES_TL and OKC_SUBCLASSES_TL – translated lookup tables yielding STS.MEANING and SC.MEANING.
• OKL_PRODUCTS and OKL_K_VENDOR_PROGRAMS_UV – supplying product name and program agreement.
• HZ_PARTIES (and indirectly HZ_CUST_ACCOUNTS) – providing the private-label party name.
• FND_LOOKUPS – delivering the book class meaning.
• OKL_CS_LC_CONTRACT_PVT and OKC_UTIL – PL/SQL packages invoked to compute the access level and related logic.
• FND_GLOBAL, IEX_LOOKUPS_V, IEX_CASE_OBJECTS, and OKC_K_PARTY_ROLES_B – supporting context and integration objects referenced in the transitive dependency chain.

Key Columns

The view exposes a broad set of columns, several of which are particularly significant for integration and reporting:

• SYNDICATABLE_YN – sourced from OKL_K_HEADERS; indicates whether the lease contract is eligible for syndication, a common filter in lease-finance reporting.
• CONTRACT_ID / CONTRACT_NUMBER – unique identifier and human-readable contract number.
• STATUS_MEANING and SUBCLASS_CODE / SUBCLASS_MEANING – translated status and subclass information; the view always restricts subclass to LEASE.
• USER_ACCESS_LEVEL – computed via OKL_CS_LC_CONTRACT_PVT.GET_K_ACCESS_LEVEL, enforcing function-security based on contract ID and subclass.
• OKL_PRODUCT, PROGRAM_AGREEMENT, PRIVATE_LABEL – descriptive integration attributes.
• BOOK_CLASS, ACCEPTED_DATE, DATE_SIGNED, DATE_TERMINATED, START_DATE, END_DATE – lifecycle and classification columns.
• DPAS_RATING, TEMPLATE_YN, TEMPLATE_USED, AUTO_RENEW_DAYS – operational lease attributes.

Common Use Cases and Queries

A frequent use case is identifying which lease contracts are syndicatable, and the search term syndicatable_yn surfaces that column directly from OKL_K_HEADERS. The following query illustrates a typical lookup:

• SELECT contract_number, okl_product, status_meaning, syndicatable_yn, user_access_level FROM okl_ebiz_kheaders_v WHERE syndicatable_yn = 'Y';

Other scenarios include populating the eBusiness find grid with accessible lease contracts for a given user, and joining to additional OKC or OKL tables for integration extraction. Note that the view does not expose a literal column mapped solely to syndicatable_yn as a filter predicate—it must be applied by the calling query—and the grid itself is scoped by subclass and access level.