Search Results base_fee




Overview
Explore in AI Chat

Overview

OKE_K_LINES is the core extension table for project contract lines in the Oracle E-Business Suite Project Contracts (OKE) module. It is owned by the OKE schema and stores extended, contract-specific attribute information for individual contract lines that originate in the common contract core. While its parent table OKC_K_LINES_B holds the shared contract line structure used across all Oracle Contracts applications, OKE_K_LINES captures the project-contracts-specific details required for contract fulfillment, billing, deliverables, funding, and pricing.

The table is defined with 103 columns and centers on the surrogate primary key K_LINE_ID, enforced by the OKE_K_LINES_PK constraint and the unique index OKE_K_LINES_U1. Based on the foreign key structure, the object exhibits hub-leaning characteristics under a heuristic Data Vault classification; that is, it behaves as a central hub entity around which numerous satellite-style child tables cluster. It also contains a self-referencing parent relationship through PARENT_LINE_ID, allowing hierarchical line structures. In Oracle EBS 12.1.1 and 12.2.2, OKE_K_LINES remains a VALID object and is integral to how project contracts are modeled and processed.

Key Information Stored

The most significant columns fall into several functional groups:

The surrogate key K_LINE_ID also serves as the documented business-key candidate through the unique index OKE_K_LINES_U1.

Common Use Cases and Queries

OKE_K_LINES is typically queried when reporting on contract line details, pricing terms, deliverables, or project associations. A common pattern joins the table to its parent contract core and project tables:

  • Retrieving all lines for a contract by joining OKC_K_LINES_B via K_LINE_ID and filtering on the contract header.
  • Reporting project-linked contract value by joining PROJECT_ID to PA_PROJECTS_ALL and TASK_ID to PA_TASKS.
  • Identifying hierarchical structures using a self-join on PARENT_LINE_ID to reconstruct parent-child line relationships.
  • Auditing billing and funding by joining to OKE_K_BILLING_EVENTS and OKE_K_FUND_ALLOCATIONS on K_LINE_ID.

A representative query might select K_LINE_ID, PROJECT_ID, LINE_QUANTITY, UNIT_PRICE, and LINE_VALUE from OKE_K_LINES where PROJECT_ID equals a given project. Because the table is central, it is frequently the driving table in contract line extracts and reconciliation reports.

Related Objects

The following objects have the most significant relationships to OKE_K_LINES:

  • OKC_K_LINES_B — Parent contract core line table; OKE_K_LINES.K_LINE_ID references it.
  • PA_PROJECTS_ALL and PA_TASKS — Project and task masters joined via PROJECT_ID and TASK_ID.
  • MTL_CUSTOMER_ITEMS — Customer item master joined via CUSTOMER_ITEM_ID.
  • OKE_K_BILLING_EVENTS — Billing event records referencing K_LINE_ID; also joined via BILL_LINE_ID.
  • OKE_K_DELIVERABLES_B — Deliverable definitions tied to contract lines.
  • OKE_K_FUND_ALLOCATIONS and OKE_K_TERMS — Funding and terms data linked by K_LINE_ID.
  • OKE_K_LINES_H — History/audit table for OKE_K_LINES.
  • OKE_K_USER_ATTRIBUTES and OKE_K_HOLDS — User-defined attributes and holds associated with each line.