Results for “okc_k_lines_b”

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

Overview

OKC_K_LINES_B is the base table for contract lines in Oracle E-Business Suite Contracts Core (OKC), the foundation module shared by Service Contracts (OKS), Lease Management (OKL/OKE), and Procurement Contracts. Each row represents a deliverable line item grouped into a logical set—typically defined by unitary price, delivery schedule, or another classification—that belongs to a contract header. Contract lines are the transactional backbone of the contracts suite: pricing, billing, renewals, tax, accounting, and fulfillment all attach to a line rather than to the header itself.

Functionally, the table sits between the header (OKC_K_HEADERS_B) and the item/deliverable layer (OKC_K_ITEMS). It carries commercial terms such as currency, negotiated price, price basis, payment terms, invoicing rules, price-list references, quantity-break pricing attributes, and configuration pointers. It also manages lifecycle state: status, termination, renewal (inbound and outbound links), and cancellation. The table is partitioned conceptually by contract type through the CLE_ID column, which references the contract-type definitions that determine which data-entry pages and validation rules apply.

The ETRM metadata classifies this object heuristically as a Data Vault hub. That is a modeling suggestion rather than an EBS fact: OKC_K_LINES_B functions as the central business-key anchor (contract line) around which many dependent satellites and links cluster. Architects building a vault or warehouse model should treat CLE_ID/ID as the durable line key, with pricing, status, and renewal attributes sourced from satellite-style history tables such as OKC_K_HISTORY_B.

Key Information Stored

The physical table contains 94 columns. The surrogate primary key is ID, enforced by unique index OKC_K_LINES_B_U1 and the constraint OKC_K_LINES_B_PK. A separate unique index, CLE_CLE1_UK, covers CHR_ID, CLE_ID, and LINE_NUMBER, making the combination of contract header, contract line, and line number the principal business-key candidate. The most significant columns are:

• ID – surrogate primary key; the row-level identity used by most foreign keys.
• CLE_ID – the contract line identifier; self-referencing and referenced by nearly every dependent OKC/OKS/OKL/OKE table.
• CHR_ID – the owning contract header; foreign key to OKC_K_HEADERS_B.
• LINE_NUMBER – ordering and uniqueness of lines within a header, part of the CLE_CLE1_UK business key.
• STS_CODE – line status; foreign key to OKC_STATUSES_B, governs workflow and eligibility for billing or renewal.
• TRN_CODE – transaction type controlling processing rules for the line.
• LSE_ID – line style; foreign key to OKC_LINE_STYLES_B, defines behavior for the contract line type.
• PRICE_NEGOTIATED, CURRENCY_CODE, PRICE_TYPE, PRICE_UNIT – core commercial terms captured per line.
• PRICE_LIST_ID, PRICE_LIST_LINE_ID, LINE_LIST_PRICE, PRICING_DATE – list-price context and the price actually applied.
• PH_QP_REFERENCE_ID, PH_PRICING_TYPE, PH_PRICE_BREAK_BASIS, PH_MIN_QTY, PH_MIN_AMT – price-break/price-hold attributes linked to Oracle Advanced Pricing lists (QP_LIST_HEADERS_B/QP_LIST_LINES).
• PAYMENT_TERM_ID, INV_RULE_ID – payment terms and inventory picking rules that drive invoicing and fulfillment.
• CLE_ID_RENEWED, CLE_ID_RENEWED_TO, DATE_RENEWED – self-referencing renewal lineage.
• START_DATE, END_DATE, DATE_TERMINATED, DATE_CANCELLED – effective-dating and lifecycle control.
• CONFIG_HEADER_ID, CONFIG_TOP_MODEL_LINE_ID, CONFIG_ITEM_ID, CONFIG_COMPLETE_YN – configuration/ATO context.
• DNZ_CHR_ID, ORIG_SYSTEM_SOURCE_CODE, ORIG_SYSTEM_ID1 – denormalized header and source-system lineage.
• SECURITY_GROUP_ID, OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE – multi-tenant security and concurrency/audit columns.

Common Use Cases and Queries

Contract lines are queried for renewal pipelines, billing reconciliation, price-list analysis, and tax determination. Because OKL_TAX_SOURCES and OKL_TAX_SOURCES_T both carry a KLE_ID foreign key to OKC_K_LINES_B, the user search for "okl_tax_sources" almost certainly indicates tracing how tax is sourced from a contract line.

• Lines for a contract header — join CHR_ID to OKC_K_HEADERS_B (or use DNZ_CHR_ID) and filter on STS_CODE to exclude cancelled or terminated lines.
• Tax source traceability — SELECT t.* FROM okc_k_lines_b l, okl_tax_sources t WHERE t.kle_id = l.id to map taxable lines to their source records.
• Renewal chain analysis — self-join on CLE_ID = CLE_ID_RENEWED or CLE_ID_RENEWED_TO to reconstruct renewal history and renewal value.
• Active lines in a period — filter START_DATE <= :as_of AND NVL(END_DATE, :as_of+1) > :as_of AND DATE_TERMINATED IS NULL AND DATE_CANCELLED IS NULL.
• Price-break reporting — join PH_QP_REFERENCE_ID to QP_LIST_HEADERS_B and QP_LIST_LINES for Advanced Pricing tier data.
• Billing reconciliation — link CLE_ID to OKS_BILL_CONT_LINES, OKS_BILL_SUB_LINES, and OKL_SUPP_INVOICE_DTLS to reconcile billed versus contracted value.

All queries should be schema-qualified (OKC.OKC_K_LINES_B) and, given the table's size and FK density, indexed access via CHR_ID or CLE_ID is strongly preferred over full scans.

Related Objects

• OKC_K_HEADERS_B – parent contract header; joined on OKC_K_LINES_B.CHR_ID = OKC_K_HEADERS_B.ID.
• OKC_K_ITEMS – deliverable items within a line; joined on CLE_ID (and CLE_ID_FOR).
• OKC_K_HISTORY_B – historical/versioned line data; join on CLE_ID for change tracking.
• OKL_TAX_SOURCES / OKL_TAX_SOURCES_T – lease tax source records; join KLE_ID to OKC_K_LINES_B.ID.
• OKS_BILL_CONT_LINES, OKS_BILL_SUB_LINES, OKS_K_ORDER_DETAILS – billing and order detail lines; join on CLE_ID (and LINK_CLE_ID).
• OKC_PRICE_ADJUSTMENTS / OKC_PRICE_ATT_VALUES – price adjustments and pricing attributes attached to a line via CLE_ID.
• OKC_K_REL_OBJS, OKC_GOVERNANCES, OKC_ANCESTRYS – relationship, governance, and hierarchy links rooted at CLE_ID.
• RA_CUSTOMER_TRX_LINES_ALL / RA_INTERFACE_LINES_ALL – Receivables invoice lines referencing the contract line via CONTRACT_LINE_ID.
• AHL_UNIT_EFFECTIVITIES_B, CSD_REPAIRS, CS_INCIDENTS_ALL_B – service, repair, and incident records that depend on the service line.

Because nearly every Contracts module table carries a CLE_ID foreign key into OKC_K_LINES_B, it is best treated as the hub of the contracts data model, with OKL_TAX_SOURCES among the many dependent satellite tables referencing it through KLE_ID.