Search Results orig_system_source_code




Overview
Explore in AI Chat

Overview

OKC_K_LINES_V is a seeded, VALID view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKC — Contracts Core product. It presents contract line information maintained in the Contracts (OKC) module and functions as the principal read-only interface for contract line data in Oracle EBS 12.1.1 and 12.2.2. The view is defined over the contract line base table and its translation table, joining the two so that a single row exposes both transactional attributes (dates, prices, status, currency) and the descriptive, language-dependent text fields (name, comments, item description). Because it resolves the underlying _B and _TL objects into one flattened structure, it is the object most commonly referenced by reports, concurrent programs, Oracle Discoverer workbooks, and external integrations that need contract line detail without navigating the multi-table schema directly.

Underlying Base Objects

The documented metadata identifies the referenced base objects as OKC_K_LINES_B (SYNONYM) and OKC_K_LINES_TL (SYNONYM), which resolve to the APPS synonyms for OKC_CONTRACT_LINES_B and its translation table. The view joins the "B" (base) table and the "TL" (translation) table on the line identifier (CLE_ID) and on the line's language. The base table holds all transactional, numeric, and date columns, while the translation table supplies NAME, COMMENTS, ITEM_DESCRIPTION, BLOCK23TEXT, and the SFWT_FLAG. The view selects from CLEB (base) and CLET (translation) aliases and exposes the base table ROWID as ROW_ID. Only the currently effective translation row for the session language is returned, so callers see a single, denormalized record per contract line.

Key Columns

Common Use Cases and Queries

Typical reporting scenarios include listing all active lines for a contract, extracting priced lines by currency for financial reconciliation, and joining contract lines to headers for consolidated contract inventories.

SELECT l.chr_id,
       l.line_number,
       l.name,
       l.sts_code,
       l.start_date,
       l.end_date,
       l.price_negotiated,
       l.currency_code
  FROM okc_k_lines_v l
 WHERE l.chr_id = :p_contract_id
   AND l.sts_code = 'ACTIVE'
 ORDER BY l.display_sequence;

Because the view is the documented access path for OKC_CONTRACT_LINES_B, integration extracts should select from OKC_K_LINES_V rather than the base tables, ensuring translation text and standard audit columns are returned consistently across both 12.1.1 and 12.2.2 environments.