Results for “short_description”

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

Overview

OKS_CONTRACT_NUMBER_V is a database view owned by the APPS schema within the OKS – Service Contracts module of Oracle E-Business Suite. The view is documented as VALID in both ETRM 12.1.1 and 12.2.2. Its stated purpose is to support the Quote Printing list of values (LOV), presenting a distinct set of contract numbers for operator selection during quote generation and printing. Rather than exposing the full contract header record, the view narrows the result set to warranty-related service contracts and returns only the contract number together with its short description, which keeps the LOV efficient and free of duplicate rows.

Because the view is a read-only projection over the core contract tables, it plays a supporting role in reporting and integration: it offers a stable, pre-joined, pre-filtered interface for any concurrent program, Oracle Forms LOV, or custom report that needs a lightweight warranty contract list without embedding join logic against the base tables. The user search term "okc_k_headers_tl" reflects the common investigation path: developers tracing a contract number back to its translated header row discover that the translation table is queried indirectly through this view.

Underlying Base Objects

The documented view metadata lists two referenced base objects, both exposed in the APPS schema as synonyms:

• OKC_K_HEADERS_B — the base (non-translated) contract header table. It supplies the CONTRACT_NUMBER column and the SCS_CODE discriminator used to filter the rows.
• OKC_K_HEADERS_TL — the translated contract header table. It supplies SHORT_DESCRIPTION and is joined on the shared contract header ID.

The view definition joins the two tables on the condition CHRB.ID = CHRT.ID, restricting results to rows where CHRB.SCS_CODE = 'WARRANTY' and where CHRT.LANGUAGE matches the session language as returned by USERENV('LANG'). The DISTINCT keyword removes duplicate combinations of contract number and short description. Because the query resolves the session language at runtime, the description returned is always the translation appropriate to the user's current environment, which is the expected behavior for an LOV used in an interactive printing flow.

Key Columns

• CONTRACT_NUMBER — the business-facing contract number drawn from OKC_K_HEADERS_B. This is the value displayed in and returned from the quote printing LOV.
• SHORT_DESCRIPTION — the translated short description from OKC_K_HEADERS_TL for the user's session language, providing the descriptive text shown alongside the number.

The view intentionally exposes no other attributes. There is no contract ID, status, date, or currency column, so the view is unsuitable as a general-purpose contract header query; it is scoped to identification and display only.

Common Use Cases and Queries

The primary use case is population of the Quote Printing LOV, where the form issues a query against the view and the user selects from the returned warranty contracts. Secondary uses include ad-hoc reporting on warranty contract numbering and validation routines that must confirm a contract number exists and is of type WARRANTY. A simple retrieval follows:

• SELECT contract_number, short_description FROM apps.oks_contract_number_v ORDER BY contract_number;
• SELECT contract_number FROM apps.oks_contract_number_v WHERE contract_number LIKE :p_prefix || '%'; — supports LOV wildcard entry.
• SELECT COUNT(*) FROM apps.oks_contract_number_v; — quick population check for a warranty contract list.

Because the underlying join depends on USERENV('LANG'), queries executed from concurrent programs or external clients should ensure the session language is initialized; otherwise SHORT_DESCRIPTION may return no rows for the chosen language. For non-warranty contract types, developers must query OKC_K_HEADERS_B and OKC_K_HEADERS_TL directly, since this view filters exclusively on SCS_CODE = 'WARRANTY'.