Search Results okc_k_items

Overview

The OKC_K_ITEMS table is a core data object within the Oracle E-Business Suite Contracts Core module (OKC). It serves as the primary repository for storing item-specific attributes associated with contract lines. This table is integral to the contract management lifecycle, enabling the detailed definition of products, services, or assets that are the subject of a contractual agreement. By linking item data to contract lines, it supports complex pricing, fulfillment, and revenue recognition scenarios, forming a critical junction between the Contracts module and other EBS product families like Order Management and Service.

Key Information Stored

The table's structure is designed to capture the relationship between a contract line and an item, along with associated metadata. Based on the provided metadata, key columns include the primary key ID and several critical foreign keys. The CHR_ID column links the item record to its parent contract header in the OKC_K_HEADERS_B table. The CLE_ID and CLE_ID_FOR columns establish the relationship with the contract line in the OKC_K_LINES_B table, likely differentiating between the primary line item and a related "for" item in certain configurations. The JTOT_OBJECT1_CODE column references the JTF_OBJECTS_B table, which manages trading community objects, suggesting this table can store items that are not just inventory items but also service or complex product models.

Common Use Cases and Queries

This table is central to queries that report on the specific items covered under contracts. A common use case is generating a detailed item listing for a given contract or set of contracts, which is essential for procurement, service delivery, and audit reports. For instance, to list all items for a specific contract, a query would join OKC_K_ITEMS to OKC_K_LINES_B and OKC_K_HEADERS_B. Another critical scenario involves integration with Order Management, where item details from this table are used to create sales orders or purchase orders linked to the contract. Analysts may also query this table to understand item usage patterns across the contract portfolio.

• Sample Query: Retrieve contract number and associated item details.
  SELECT hkr.contract_number, kle.line_number, kit.*
FROM okc_k_items kit,
okc_k_lines_b kle,
okc_k_headers_b hkr
WHERE kit.cle_id = kle.id
AND kle.chr_id = hkr.id
AND hkr.contract_number = '<CONTRACT_NUM>';

Related Objects

As indicated by its foreign keys, OKC_K_ITEMS has strong dependencies on several foundational Contracts Core tables. Its primary relationship is with OKC_K_LINES_B, the table for contract lines, and OKC_K_HEADERS_B, the table for contract headers. The link to JTF_OBJECTS_B provides access to the trading community model. Furthermore, the metadata shows that OKC_ITEM_PARTYS_B holds a foreign key reference back to OKC_K_ITEMS (via CIM_ID), indicating it stores party assignments for the items defined in this table. This network of relationships positions OKC_K_ITEMS as a key hub for enriching contract line data with detailed product information.