Search Results oke_k_lines_u1

Overview

OKE.OKE_K_LINES is the Project Contracts extension table that stores the contract line (CLIN) and sub-line (SLIN) information specific to the Oracle E-Business Suite Project Contracts module. It is a child of the Contracts Core base table OKC_K_LINES_B, sharing a strict one-to-one row relationship keyed on K_LINE_ID; translated attribute data resides in OKC_K_LINES_TL. In Oracle EBS 12.1.1 and 12.2.2, this table is central to contract authoring, deliverable tracking, billing events, funding allocations, and terms management for project and procurement contracts.

Contract lines are hierarchical. A line may have multiple children but belongs to at most one parent, identified by PARENT_LINE_ID. The topmost line (the "top line") has no parent and instead belongs to the Contract Header. Every line carries a Line Style that governs permissible child line styles — for example, an Item line style may reference inventory items via INVENTORY_ITEM_ID and MTL_CUSTOMER_ITEMS, whereas a Data Item line style supports data deliverable attributes such as CDRL_CATEGORY and DATA_ITEM_NAME.

Heuristic data vault classification (as mined from the foreign key structure) suggests this table behaves as a hub-leaning entity: it holds the durable K_LINE_ID business key, is referenced by numerous satellite-style child tables (deliverables, holds, terms, notes), and itself references PA_PROJECTS_ALL, PA_TASKS, and MTL_CUSTOMER_ITEMS. In practice, this means OKE_K_LINES can be modeled as the hub for contract-line identities, with dependent detail tables treated as satellites.

Key Information Stored

The table contains 103 documented columns. The most operationally significant are:

• K_LINE_ID — Surrogate primary key (OKE_K_LINES_PK) and the unique business-key candidate via index OKE_K_LINES_U1. It is the join key to OKC_K_LINES_B and virtually all dependent tables.
• PARENT_LINE_ID — Self-referencing FK defining the parent-child line hierarchy.
• PROJECT_ID / TASK_ID — Foreign keys to PA_PROJECTS_ALL and PA_TASKS, linking the line to a project and task for cost collection and billing.
• INVENTORY_ITEM_ID / CUSTOMER_ITEM_ID — References to MTL_CUSTOMER_ITEMS and inventory items for item-based lines.
• LINE_QUANTITY, UNIT_PRICE, UOM_CODE — Commercial quantity, pricing, and unit-of-measure data.
• BILLING_METHOD_CODE, BILLABLE_FLAG, SHIPPABLE_FLAG, DELIVERY_ORDER_FLAG — Billing and fulfillment controls.
• DELIVERY_DATE, PROPOSAL_DUE_DATE, DATE_MATERIAL_REQ — Schedule and milestone dates; DELIVERY_DATE is indexed (OKE_K_LINES_N4) for scheduling reports.
• LINE_VALUE, LINE_VALUE_TOTAL — Aggregated commercial value of the line.
• PREPAYMENT_AMOUNT, PROGRESS_PAYMENT_RATE, AWARD_FEE, FIXED_FEE — Contract financing and fee structures.
• COMPLETED_FLAG, SPLITED_FLAG, NSP_FLAG — Status and processing indicators.

Standard Who columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) support audit tracking. Additional non-unique indexes cover PROJECT_ID (OKE_K_LINES_N1), TASK_ID (OKE_K_LINES_N2), INVENTORY_ITEM_ID (OKE_K_LINES_N3), and DELIVERY_DATE (OKE_K_LINES_N4).

Common Use Cases and Queries

Typical scenarios include contract line listing per project, deliverable reconciliation, billing event sourcing, and funding allocation reporting.

Sample — lines for a project with their parent line:

SELECT l.k_line_id, l.parent_line_id, l.project_id, l.task_id,
       l.inventory_item_id, l.line_quantity, l.unit_price, l.line_value
FROM   oke.oke_k_lines l
WHERE  l.project_id = :project_id
ORDER BY l.parent_line_id NULLS FIRST, l.k_line_id;

Sample — joins to the core base table for descriptive attributes:

SELECT l.k_line_id, b.line_number, l.billable_flag, l.delivery_date
FROM   oke.oke_k_lines l, okc.okc_k_lines_b b
WHERE  l.k_line_id = b.k_line_id
AND    l.completed_flag = 'N';

Reporting use cases include open deliverables by delivery date, progress-payment lines with a non-null PROGRESS_PAYMENT_RATE, and lines pending customer approval (CUSTOMER_APPROVAL_REQ_FLAG = 'Y'). The APPS_TS_TX_DATA tablespace placement and APPS_TS_TX_IDX index placement indicate transactional, high-concurrency access patterns.

Related Objects

• OKC.K_LINES_B — Contracts Core parent table; one-to-one via K_LINE_ID.
• OKC.OKC_K_LINES_TL — Translated line (and header) text.
• PA.PA_PROJECTS_ALL — Project definition, joined via PROJECT_ID.
• PA.PA_TASKS — Task definition, joined via TASK_ID.
• MTL_CUSTOMER_ITEMS — Customer item catalog for item lines.
• OKE_K_DELIVERABLES_B / _TL / _TLH — Deliverable records per line.
• OKE_K_BILLING_EVENTS — Billing events tied to a line or bill line.
• OKE_K_FUND_ALLOCATIONS / _H — Funding allocation and history per line.
• OKE_K_HOLDS — Hold records applied to a line.
• OKE_K_TERMS — Contract terms attached to a line.

Collectively, these relationships confirm OKE_K_LINES as the hub within the Project Contracts subsystem, with dependent satellites providing deliverables, billing, funding, holds, and terms data.