Results for “contract_number_modifier”

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

Overview

OKS_APPROVED_CONTRACTS_V is a reporting view owned by the APPS schema within the OKS - Service Contracts module of Oracle E-Business Suite (available in both 12.1.1 and 12.2.2). As its documented description states, it is a "View for Approved Contracts." Its purpose is to expose only those service contract lines whose status has reached an approved milestone, thereby giving downstream reports, integrations, and concurrent programs a pre-filtered data set that excludes draft, cancelled, or otherwise unapproved agreements.

The view is significant for users who search on the term "customer_product_id." That identifier is the leading column of the view and is derived from the item-level reference in OKC_K_ITEMS, allowing a customer product instance to be linked back to the contract and its active coverage period. In this manner the view functions as a bridge between installed-base product records and the service contracts that cover them, a pattern common in service contract reporting, entitlement validation, and third-party integration extracts.

Underlying Base Objects

The view is defined over three documented base tables, each accessed through an APPS synonym:

• OKC_K_HEADERS_B (SYNONYM) — the contract header, supplying the contract identity.
• OKC_K_LINES_B (SYNONYM) — the contract lines, aliased twice in the view text as SVCKLINE (the service line) and CLVLLINE (the line-value or coverage line).
• OKC_K_ITEMS (SYNONYM) — the item-level detail, aliased NKITM, which carries the customer product reference.

The joins are anchored on the header: NHDR.ID equals SVCKLINE.DNZ_CHR_ID. The service line is then joined to the coverage line on SVCKLINE.ID = CLVLLINE.CLE_ID, the coverage line is restricted to LSE_ID = 25, and finally CLVLLINE.ID = NKITM.CLE_ID with NKITM.JTOT_OBJECT1_CODE = 'OKX_CUSTPROD'. This last predicate ensures that only item rows referencing a customer product object are returned.

Key Columns

• CUSTOMER_PRODUCT_ID — sourced from NKITM.OBJECT1_ID1. Identifies the customer product instance associated with the approved contract line; the primary search target for this view.
• START_DATE — from SVCKLINE.START_DATE. The effective start of the covered service line.
• END_DATE — from SVCKLINE.END_DATE. The effective end of the covered service line.
• CONTRACT_NUMBER — from NHDR.CONTRACT_NUMBER. The human-readable contract identifier.
• CONTRACT_NUMBER_MODIFIER — from NHDR.CONTRACT_NUMBER_MODIFIER. The version or modifier suffix distinguishing contract revisions.
• CONTRACT_ID — from NHDR.ID. The internal surrogate key for the contract header, used for joins to other OKC tables.

The status filter is embedded in the view: only lines with SVCKLINE.STS_CODE in ('SIGNED', 'ACTIVE') qualify, so consumers need not repeat that predicate.

Common Use Cases and Queries

Typical scenarios include verifying that a given customer product has active service coverage, building entitlement extracts for external systems, and reconciling contract coverage windows against installed-base assets. A minimal lookup by customer product is shown below:

• SELECT customer_product_id, contract_number, contract_number_modifier, start_date, end_date FROM oks_approved_contracts_v WHERE customer_product_id = :p_customer_product_id;
• SELECT contract_id, contract_number, start_date, end_date FROM oks_approved_contracts_v WHERE TRUNC(SYSDATE) BETWEEN start_date AND end_date;
• SELECT customer_product_id, COUNT(*) FROM oks_approved_contracts_v GROUP BY customer_product_id;

Because the view already restricts to SIGNED and ACTIVE lines and to customer product items, reports built on it are simpler and less error-prone than equivalent joins written directly against OKC_K_HEADERS_B, OKC_K_LINES_B, and OKC_K_ITEMS.