Results for “okl_k_headers_full_uv”

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

Overview

OKL_K_HEADERS_FULL_UV is an APPS-owned database view within the Oracle Lease and Finance Management (OKL) module. It presents a consolidated, reporting-oriented projection of contract and lease header information, joining the base header table with its translation table so that descriptive text attributes are available alongside identifier and status columns.

The view is important because it exposes the header data model in a denormalized form suitable for inquiry screens, concurrent reports, and integration extracts. A defining characteristic of the view is its treatment of status and source columns: STS_CODE, SCS_CODE, and several related meaning columns are projected as TO_CHAR(NULL), meaning the code is carried forward while the human-readable meaning is not resolved within the view itself. This is the origin of the search term sts_code_meaning: implementers who need the status description must look up the code through a separate lookup or reference table rather than reading it directly from this view. The presence of OKC_UTIL in the referenced objects suggests the view text may use similar null-casting or utility-based expression patterns to support the "full" presentation of header data.

Underlying Base Objects

The documented metadata lists four referenced objects under the APPS schema:

• OKC_K_HEADERS_B (SYNONYM) — the base header table, supplying core columns such as IDs, organization, contract number, status code, dates, and amounts.
• OKC_K_HEADERS_TL (SYNONYM) — the translation table, supplying descriptive attributes including SHORT_DESCRIPTION, DESCRIPTION, COGNOMEN, and NON_RESPONSE_REASON.
• OKC_UTIL (PACKAGE) — a utility package used within the view definition, likely for null handling or value conversion.
• OKL_K_HEADERS (SYNONYM) — a Lease Management header synonym, providing the OKL-specific naming layer over the shared OKC contract header structures.

The view aliases the base and translation tables as CHRB and CHRT respectively, joining them to produce one row per header with its translated text. Because the base objects are the shared OKC contract headers, the view represents the OKL view of the common contract header foundation, with columns mapped using the OKL_ naming convention.

Key Columns

Important columns exposed by the view include:

• ID, OBJECT_VERSION_NUMBER — primary identifier and optimistic locking version, converted to character for reporting.
• STS_CODE, SCS_CODE, STS_CODE_MEANING, SCS_CODE_MEANING — status and source codes, with the meaning columns returned as NULL.
• CONTRACT_NUMBER, CONTRACT_NUMBER_MODIFIER, ORG_ID, INV_ORGANIZATION_ID, AUTHORING_ORG_ID — contract identity and organizational context.
• CHR_TYPE, RFP_TYPE, TRN_CODE, BUY_OR_SELL, ISSUE_OR_RECEIVE — classification and direction attributes.
• START_DATE, END_DATE, DATE_APPROVED, DATE_SIGNED, DATE_TERMINATED, DATE_RENEWED — lifecycle dates.
• ESTIMATED_AMOUNT, ESTIMATED_AMOUNT_RENEWED, CURRENCY_CODE — financial summary fields.
• Descriptive columns SHORT_DESCRIPTION, DESCRIPTION, COGNOMEN, NON_RESPONSE_REASON sourced from the translation table.

Common Use Cases and Queries

The view is typically used for lease header inquiry and extraction, and for reporting where readable descriptions are required. A representative query:

• SELECT id, contract_number, sts_code, chr_type, start_date, end_date FROM okl_k_headers_full_uv WHERE org_id = :p_org_id ORDER BY contract_number;
• SELECT h.id, h.contract_number, fl.meaning FROM okl_k_headers_full_uv h, fnd_lookup_values fl WHERE fl.lookup_type = :sts_lookup AND fl.lookup_code = h.sts_code; — the standard pattern used to resolve sts_code_meaning, since the view returns that column as NULL.

Because NULL meaning columns are intentional, developers expecting resolved values must perform their own lookup join rather than assuming incomplete view definition.