Results for “oks_sts_code”

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

Overview

The view APPS.OKL_OKS_CONTRACTS_ALL_UV is a reporting construct within the Oracle E-Business Suite OKL – Lease and Finance Management product module. Its documented purpose is to present a consolidated list of Lease contracts that are linked to Service contracts. The view straddles two distinct contract domains: lease agreements held in the OKL schema family and service agreements managed by the OKS (Service Contracts) tables accessed through OKC common contract infrastructure. Because it resolves relationship records into a single denormalised row spanning both contracts, the view functions primarily as a reporting and integration artifact rather than a transactional entity. It is defined with status VALID in the APPS schema and is available in both Oracle EBS 12.1.1 and 12.2.2 environments.

Underlying Base Objects

The documented referenced base objects are:

• OKC_K_HEADERS_ALL_V (VIEW) – the service contract header source, supplying contract number, status code, dates and description.
• OKC_K_REL_OBJS_V (VIEW) – the relationship object view that links a lease contract header (CHR_ID) to a service contract (OBJECT1_ID1).
• OKL_K_HEADERS_FULL_ALL_V (VIEW) – the lease contract header view, providing the lease contract number.
• OKC_STATUSES_TL (SYNONYM) – the translatable status lookup supplying status meaning for the service contract.
• FND_LOOKUP_VALUES_VL (VIEW) – the lookup source used to derive the CONTRACT_TYPE description from the OKL_CONTRACT_CATEGORY lookup type.
• OKC_UTIL (PACKAGE) – the contract utility package referenced in the resolution of relationship type and object codes (RTY_CODE, JTOT_OBJECT1_CODE).

The joins establish a strict filter: relationship records with RTY_CODE of 'OKLSRV' or 'OKLUBB', no CLE_ID, and JTOT_OBJECT1_CODE equal to 'OKL_SERVICE'. This ensures only genuine lease-to-service linkages are returned.

Key Columns

• OKL_CHR_ID – lease contract header identifier (from RELO.CHR_ID).
• OKL_CONTRACT_NUMBER – the lease contract number.
• OKS_CHR_ID – the linked service contract identifier.
• OKS_CONTRACT_NUMBER – the service contract number.
• CONTRACT_TYPE – a derived literal returned by a scalar subquery against FND_LOOKUP_VALUES_VL for lookup code 'SERVICE' in the OKL_CONTRACT_CATEGORY lookup type; it always resolves to the "Service" category meaning.
• OKS_STS_CODE – the translated status meaning of the service contract.
• OKS_START_DATE / OKS_END_DATE – the effective period of the service contract.
• OKS_SHORT_DESCRIPTION – a brief description of the service contract.

Common Use Cases and Queries

A frequent requirement is to enumerate every lease contract and its associated service contract, filtering on the CONTRACT_TYPE column that the user searched for ("contract_type"). Because the view exposes only the 'SERVICE' category, filtering on CONTRACT_TYPE returns all rows, but it remains useful as a display column or for joins to other category-annotated datasets.

• Reporting all lease-to-service mappings for reconciliation between OKL and OKS.
• Identifying lease contracts whose service contracts start or expire within a given window.
• Feeding downstream integrations that must align lease and service coverage periods.

Sample query:

• SELECT OKL_CONTRACT_NUMBER, OKS_CONTRACT_NUMBER, CONTRACT_TYPE, OKS_STS_CODE, OKS_START_DATE, OKS_END_DATE FROM APPS.OKL_OKS_CONTRACTS_ALL_UV WHERE CONTRACT_TYPE = 'Service' ORDER BY OKS_END_DATE;
• SELECT OKL_CHR_ID, COUNT(OKS_CHR_ID) FROM APPS.OKL_OKS_CONTRACTS_ALL_UV GROUP BY OKL_CHR_ID HAVING COUNT(OKS_CHR_ID) > 1;

Consult the ETRM documentation for the authoritative view text, as columns and filters are governed by the documented definition above.