Results for “okl_cs_oks_contracts_uv”

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

Overview

OKL_CS_OKS_CONTRACTS_UV is an APPS-owned reporting view within the Oracle Lease and Finance Management (OKL) module. Its documented purpose is to present a list of Lease contracts that are linked to Service contracts, providing a consolidated read-only projection that bridges the OKL (Lease and Finance Management) and OKS (Service) contract schemas. The view is a classic integration/reporting object: rather than requiring a developer to join the OKC relationship, header, and status tables manually, the view exposes the lease-to-service linkage in a single, denormalized result set.

Because a valid EBS 12.1.1 / 12.2.2 instance maintains this view as VALID, it can be queried directly by custom reports, BI Publisher data templates, concurrent programs, or ad hoc SQL. Users searching for the related object name "okc_k_rel_objs_v" typically arrive here because OKC_K_REL_OBJS_V is one of the view's core underlying objects; the relationship view is the mechanism through which lease and service contracts are associated.

Underlying Base Objects

The documented view definition joins the following objects, all under the APPS schema:

• OKC_K_REL_OBJS_V (VIEW) — aliased RELO. This is the relationship object view that carries the contract relationship records, including RTY_CODE, JTOT_OBJECT1_CODE, OBJECT1_ID1, CLE_ID, and CHR_ID. It is the central intersection point linking a lease contract header to its associated service contract.
• OKC_K_HEADERS_V (VIEW) — aliased OKCH. Supplies the service contract header attributes such as CONTRACT_NUMBER, STS_CODE, START_DATE, END_DATE, and SHORT_DESCRIPTION. Joined on OKCH.ID = RELO.OBJECT1_ID1.
• OKL_K_HEADERS_FULL_V (VIEW) — aliased OKLH. Supplies the lease contract header, joined on OKLH.ID = RELO.CHR_ID, yielding the OKL contract number.
• OKC_STATUSES_TL (SYNONYM) — aliased STST. Provides the translated status meaning (MEANING) for the service contract status code, filtered by the user's session language.
• FND_LOOKUP_VALUES_VL (VIEW) — used in a scalar subquery to return the CONTRACT_TYPE meaning from the OKL_CONTRACT_CATEGORY lookup for the 'SERVICE' code.
• OKC_UTIL (PACKAGE) — a documented referenced base object, typically invoked in the relationship logic underpinning OKC_K_REL_OBJS_V.

Key Columns

• OKL_CHR_ID — the lease contract header identifier (RELO.CHR_ID).
• OKL_CONTRACT_NUMBER — the lease contract number from OKL_K_HEADERS_FULL_V.
• OKS_CHR_ID — the service contract header identifier (RELO.OBJECT1_ID1).
• OKS_CONTRACT_NUMBER — the service contract number from OKC_K_HEADERS_V.
• CONTRACT_TYPE — a constant-style value resolved from the OKL_CONTRACT_CATEGORY lookup for code 'SERVICE'.
• OKS_STS_CODE — the translated status meaning of the service contract via OKC_STATUSES_TL.
• OKS_START_DATE / OKS_END_DATE — the service contract effective date range.
• OKS_SHORT_DESCRIPTION — the service contract description.

Common Use Cases and Queries

Typical scenarios include reconciling which service contracts are attached to a lease, auditing contract coverage windows, and feeding integration extracts that must map lease identifiers to service identifiers.

• Listing all service contracts for a given lease number.
• Identifying service contracts whose end date precedes a lease end date (coverage gaps).
• Extract for downstream systems needing OKL_CHR_ID / OKS_CHR_ID pairs.

Sample query:

SELECT OKL_CONTRACT_NUMBER,
       OKS_CONTRACT_NUMBER,
       OKS_STS_CODE,
       OKS_START_DATE,
       OKS_END_DATE
FROM   OKL_CS_OKS_CONTRACTS_UV
WHERE  OKL_CONTRACT_NUMBER = :lease_number
ORDER BY OKS_START_DATE;

Filters on RTY_CODE IN ('OKLSRV','OKLUBB'), CLE_ID IS NULL, and JTOT_OBJECT1_CODE = 'OKL_SERVICE' are already applied internally, so callers need only add their own predicates.