Results for “okl_k_headers_full_all_v”

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

Overview

OKL_K_HEADERS_FULL_ALL_V is a consolidated header view owned by the APPS schema within the Oracle Lease and Finance Management (OKL) module. It presents a complete, denormalized picture of a contract header by combining the core contract attributes held in the Oracle Contracts (OKC) foundation tables with the lease- and finance-specific header attributes held in the OKL lease management tables. As the name implies, the "_FULL_" designation indicates that the view exposes the full set of columns from the component headers rather than a narrow subset, and the "_ALL_" suffix signals that the view is intended to span all header records reachable through the composite definition.

Because both the contract core and the lease management extension contribute columns to a single row, this view is the natural reporting and integration surface for consumers that need one flat, queryable structure describing a lease or finance contract. It spares developers from manually joining the bilingual (TL) and base (B) contract tables with the OKL counterpart, and it standardizes attribute naming across the two sources. In Oracle EBS 12.1.1 and 12.2.2 the object is reported as VALID, confirming that the underlying synonyms and package dependencies resolve correctly in a supported installation.

Underlying Base Objects

The view is defined over the following documented base objects:

• OKC_K_HEADERS_ALL_B (SYNONYM) — the base (language-independent) contract header table in Oracle Contracts.
• OKC_K_HEADERS_TL (SYNONYM) — the translation table supplying language-specific descriptive columns such as SHORT_DESCRIPTION, COMMENTS, DESCRIPTION, COGNOMEN, NON_RESPONSE_REASON, NON_RESPONSE_EXPLAIN, and SET_ASIDE_REASON.
• OKL_K_HEADERS (SYNONYM) — the lease and finance management extension table holding OKL-specific header attributes.
• OKC_UTIL (PACKAGE) — a Contracts utility package referenced by the view definition.

The view text selects ROWID from the base header table and joins the translation and OKL extension objects so that each row carries both the contract number, status, currency, and dates from the core and the lease-specific enrichment from the OKL table. The documented definition is described as a full view over OKC_K_HEADERS_B and OKL_K_HEADERS, combining the contracts core and lease management header attributes into one view.

Key Columns

The view exposes a broad set of header attributes. Notable columns include:

• ID and OBJECT_VERSION_NUMBER — the unique header identifier and the optimistic locking version.
• CONTRACT_NUMBER and CONTRACT_NUMBER_MODIFIER — the human-readable contract reference.
• STS_CODE and SCS_CODE — the contract status and status classification.
• CURRENCY_CODE, START_DATE, END_DATE — the commercial and effective-dating attributes.
• CHR_TYPE and RFP_TYPE — the contract header type and request-for-proposal classification used heavily in leasing and procurement flows.
• DATE_APPROVED, DATE_SIGNED, DATE_TERMINATED, DATE_RENEWED, DATETIME_CANCELLED, DATETIME_RESPONDED — lifecycle milestone dates.
• TEMPLATE_YN and TEMPLATE_USED — flags indicating whether the header is a template and which template it derives from.
• SHORT_DESCRIPTION, DESCRIPTION, COMMENTS, COGNOMEN — translated textual attributes drawn from the TL table.
• AUTHORING_ORG_ID, INV_ORGANIZATION_ID, BUY_OR_SELL — organizational and transactional orientation.
• DELETED_YN, ARCHIVED_YN, TEMPLATE_YN — record state and retention flags.

Common Use Cases and Queries

This view is commonly used in lease contract reporting, AR/GL reconciliation extracts, and integrations that require a single flat source for header data. A typical query filters by contract number and status:

• SELECT id, contract_number, sts_code, currency_code, start_date, end_date FROM okl_k_headers_full_all_v WHERE contract_number = :p_contract_number;
• SELECT contract_number, short_description, date_signed FROM okl_k_headers_full_all_v WHERE sts_code = 'ACTIVE' AND deleted_yn = 'N';
• SELECT contract_number, chr_type, rfp_type, date_approved FROM okl_k_headers_full_all_v WHERE template_yn = 'N' AND archived_yn = 'N';

Because the view joins base, translation, and lease extension objects, queries should always supply selective predicates on indexed header columns such as ID or CONTRACT_NUMBER to avoid full scans of the bilingual translation table. As with all APPS-owned views, it should be accessed read-only and never updated directly.