Search Results okl_k_headers_full_v




Overview
Explore in AI Chat

Overview

OKL_K_HEADERS_FULL_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2. It belongs to the OKL product family, Oracle Leasing and Finance Management, and exists to consolidate contract header information that is otherwise distributed across the Oracle Contracts Core (OKC) and Oracle Leasing (OKL) data models. The view is documented as a "full view" on tables OKC_K_HEADERS_B and OKL_K_HEADERS, combining the contracts core header attributes with lease management header attributes into a single, denormalized row per contract header.

In practice, the view provides a convenient access path for developers, report authors, and integrators who require lease-related contract header details without writing multi-table joins against OKC and OKL base tables. Because it joins the core contract header to the lease extension, it reflects the EBS architecture in which leasing records extend a base contracts-core record rather than duplicating it. The view is marked VALID in the ETRM metadata, indicating that it compiles successfully against the referenced objects.

Underlying Base Objects

The ETRM metadata for Release 12.2.2 identifies the following referenced base objects:

  • OKC_K_HEADERS_B (SYNONYM) — the Contracts Core header base table, holding the primary contract header record keyed by ID.
  • OKC_K_HEADERS_TL (SYNONYM) — the translated (language) table supplying descriptive columns such as short description and comments.
  • OKL_K_HEADERS (SYNONYM) — the Leasing and Finance Management header extension table carrying lease-specific attributes.
  • OKC_UTIL (PACKAGE) — a Contracts utility package referenced by the view definition.

The view therefore sits on top of the core contracts header (base and translated) joined to the OKL lease header extension, exposing columns sourced from each. Column aliases in the view definition reflect this split: the ROWID, ID, OBJECT_VERSION_NUMBER, status, currency, contract number, and most business columns derive from the core header (CHRB), while translated descriptive text (SHORT_DESCRIPTION, COMMENTS, DESCRIPTION, COGNOMEN, NON_RESPONSE_REASON, SET_ASIDE_REASON) derives from the TL source (CHRT).

Key Columns

Common Use Cases and Queries

Typical uses include ad-hoc reporting on active lease contracts, integration extracts feeding downstream systems, and validation queries during data migration. A minimal query returns the current header population:

SELECT CONTRACT_NUMBER, CONTRACT_NUMBER_MODIFIER, STS_CODE, CURRENCY_CODE, START_DATE, END_DATE FROM APPS.OKL_K_HEADERS_FULL_V WHERE DELETED_YN = 'N';

To list active contracts by status with their short description:

SELECT CONTRACT_NUMBER, SHORT_DESCRIPTION, STS_CODE FROM APPS.OKL_K_HEADERS_FULL_V WHERE STS_CODE = 'ACTIVE' AND BUY_OR_SELL = 'SELL';

Because the view encapsulates the OKC-to-OKL join, it is well suited to reports that require both core contract metadata and lease extension flags without hand-coded joins. Queries should apply the relevant language and organization predicates where translation and multi-org coverage matter.