Results for “okl_contract_category”

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

Overview

APPS.OKL_OKS_CONTRACTS_ALL_UV is a read-only view in the Oracle E-Business Suite Contracts (OKL / OKC) module that correlates Oracle Lease Management service contracts with their parent contract relationships. It belongs to the ETRM (Enterprise Transaction and Reference Model) family of objects and is defined with the suffix _UV, indicating a "user view" intended for reporting, inquiry, and integration consumption rather than for direct DML. The view exposes a single, denormalized record set that joins contract header information from both the OKC and OKL schemas and resolves the contract category through the FND lookup mechanism.

The object is particularly relevant when users query for OKL_CONTRACT_CATEGORY. The view's inline scalar subquery resolves the lookup meaning for the OKL_CONTRACT_CATEGORY lookup type with lookup_code = 'SERVICE'. This means the view is hard-coded to return the SERVICE contract category in the CONTRACT_TYPE column, and it serves as a convenient reporting source for identifying service-related lease contracts and their associated contract programs.

Underlying Base Objects

The documented metadata identifies the following base objects referenced by the view:

• OKC_K_HEADERS_ALL_V (VIEW) — aliased as OKCH, supplies the service contract header, contract number, start/end dates, short description, and status code.
• OKC_K_REL_OBJS_V (VIEW) — aliased as RELO, provides the relationship between the OKL contract (chr_id) and the referenced OKS service contract (object1_id1).
• OKC_STATUSES_TL (SYNONYM) — aliased as STST, translates the status code into a language-specific meaning.
• OKL_K_HEADERS_FULL_ALL_V (VIEW) — aliased as OKLH, supplies the OKL contract number (contract_number) for the parent lease contract.
• FND_LOOKUP_VALUES_VL (VIEW) — drives the CONTRACT_TYPE column by returning the meaning for the OKL_CONTRACT_CATEGORY / SERVICE lookup.
• OKC_UTIL (PACKAGE) — referenced indirectly through the API or view logic that supports the OKC header views.

The join topology connects RELO.CHR_ID to OKLH.ID (the OKL lease contract), and RELO.OBJECT1_ID1 to OKCH.ID (the OKS service contract), yielding one row per qualifying relationship.

Key Columns

• OKL_CHR_ID — Identifier of the parent OKL lease contract header.
• CONTRACT_NUMBER — Contract number of the parent OKL lease contract.
• OKS_CHR_ID — Identifier of the linked OKS service contract header.
• OKS_CONTRACT_NUMBER — Contract number of the linked service contract.
• CONTRACT_TYPE — Hard-coded lookup meaning for OKL_CONTRACT_CATEGORY / SERVICE.
• OKS_STS_CODE — Language-specific status meaning of the service contract.
• OKS_START_DATE / OKS_END_DATE — Validity period of the service contract.
• OKS_SHORT_DESCRIPTION — Descriptive text for the service contract.

Common Use Cases and Queries

Typical usage includes identifying which lease contracts have associated service contracts, monitoring service contract validity windows, and validating contract category assignments. The view filters on relationship types 'OKLSRV' and 'OKLUBB', excludes rows where cle_id is not null, and requires jtot_object1_code = 'OKL_SERVICE'.

SELECT okl_chr_id, contract_number,
       oks_contract_number, oks_sts_code,
       oks_start_date, oks_end_date
FROM   apps.okl_oks_contracts_all_uv
WHERE  oks_end_date >= SYSDATE;

SELECT contract_type, COUNT(*)
FROM   apps.okl_oks_contracts_all_uv
GROUP  BY contract_type;

Because CONTRACT_TYPE is resolved from FND_LOOKUP_VALUES_VL restricted to language = USERENV('LANG') behavior on dependent views, the second query returns the SERVICE category for all rows. The view is well suited as a data source for concurrent programs and BI Publisher lease-service reconciliation reports.