Search Results oks_k_order_details




Overview
Explore in AI Chat

Overview

The OKS_K_ORDER_DETAILS table is a core data object within the Oracle E-Business Suite Service Contracts (OKS) module, specifically for releases 12.1.1 and 12.2.2. Its primary function is to capture and store detailed service contract information that is generated when a service is ordered through the Order Management module. This table serves as a critical integration point, linking transactional order data from Order Management with the contractual service terms and structures defined in Service Contracts. It acts as a child table to the primary contract header and line entities, enabling the detailed configuration of service deliverables tied to a sales order.

Key Information Stored

While the provided metadata does not list specific columns, the foreign key relationships define the critical linkages the table manages. The primary key is the ID column, constrained by OKS_K_ORDER_DETAILS_PK. The most significant columns are the foreign keys that establish relationships with other core contract entities. The CHR_ID and CLE_ID columns link the record directly to a parent contract header (OKC_K_HEADERS_B) and contract line (OKC_K_LINES_B), respectively. The LINK_CHR_ID and LINK_CLE_ID columns provide references to other contract headers and lines, which are essential for modeling complex service contract structures, such as linked or master-detail agreements. The COD_ID column facilitates a recursive relationship within the table itself, allowing for hierarchical detailing of order-level service information.

Common Use Cases and Queries

This table is central to processes where service contracts are generated or modified from sales orders. A common use case is tracing the complete service contract lineage back to its originating order lines for audit or fulfillment purposes. Technical consultants often query this table to diagnose integration issues between Order Management and Service Contracts or to build custom reports on service orders. A typical SQL pattern involves joining OKS_K_ORDER_DETAILS to the core contract tables to retrieve a consolidated view of ordered services.

SELECT okod.id, okh.contract_number, okl.line_number, okod.link_chr_id
FROM oks_k_order_details okod,
     okc_k_headers_b okh,
     okc_k_lines_b okl
WHERE okod.chr_id = okh.id
  AND okod.cle_id = okl.id
  AND okh.contract_number = '<CONTRACT_NUM>';

Related Objects

The table maintains extensive relationships with other Service Contracts entities, as documented in the foreign key metadata.

  • Primary Key Reference: OKS_K_ORDER_DETAILS_PK on column ID.
  • Foreign Keys (This Table References):
    • OKC_K_HEADERS_B: Via CHR_ID and LINK_CHR_ID columns. This links the order detail to the main contract header and potentially a linked contract header.
    • OKC_K_LINES_B: Via CLE_ID and LINK_CLE_ID columns. This links the order detail to the specific contract line item and potentially a linked contract line.
    • OKS_K_ORDER_DETAILS (Self-Reference): Via COD_ID column, enabling hierarchical data within the table.
  • Foreign Keys (Tables Referencing This Table):
    • OKS_K_ORDER_CONTACTS: Via COD_ID. This indicates that contact information specific to the order detail is stored in a separate child table.
    • OKS_K_ORDER_DETAILS (Self-Reference): Via COD_ID, completing the recursive relationship for hierarchy management.