Search Results okc_deliverables




Overview
Explore in AI Chat

Overview

The OKC_DELIVERABLES table is a core data object within the Oracle E-Business Suite (EBS) Contracts Core (OKC) module. It serves as the primary repository for recording deliverables and their amendments associated with contractual agreements. A deliverable is a tangible or intangible item, such as a report, product, or service milestone, that a party is obligated to provide under the terms of a contract. This table is fundamental for tracking the lifecycle, obligations, and fulfillment status of these contractual components, enabling structured contract management and compliance monitoring across the enterprise.

Key Information Stored

The table's primary key is DELIVERABLE_ID, which uniquely identifies each deliverable record. While the provided metadata does not list all columns, the foreign key relationships reveal critical data points. The table stores event-driven scheduling information through columns like RELATIVE_ST_DATE_EVENT_ID and RELATIVE_END_DATE_EVENT_ID, which link to business document events (OKC_BUS_DOC_EVENTS_B) to define start and end dates. It also manages communication alerts via the PRINT_DUE_DATE_MSG_NAME column, which references predefined message templates (OKC_DEL_MESSAGES) for notifications. Typical data stored includes deliverable descriptions, status, due dates, fulfillment dates, associated contract lines, and amendment history.

Common Use Cases and Queries

A primary use case is generating reports on outstanding contractual obligations. For instance, a query can list all deliverables due within a specific period for a set of contracts, aiding in workload management and risk assessment. Another common scenario involves tracking amendment history to audit changes in deliverable scope or timelines. Sample SQL often joins OKC_DELIVERABLES with the main contracts header table (OKC_K_HEADERS_B) and lines table (OKC_K_LINES_B) to provide context. For example:

  • SELECT d.deliverable_id, d.description, k.contract_number FROM okc_deliverables d, okc_k_lines_b l, okc_k_headers_b k WHERE d.line_id = l.id AND l.dnz_chr_id = k.id AND d.status = 'PENDING';

This pattern supports operational dashboards and compliance audits.

Related Objects

OKC_DELIVERABLES has documented foreign key relationships with several key tables in the Contracts Core schema, as per the provided metadata:

  • OKC_DEL_MESSAGES: Joined via OKC_DELIVERABLES.PRINT_DUE_DATE_MSG_NAME. This relationship links a deliverable to the message template used for notifications regarding its due date.
  • OKC_BUS_DOC_EVENTS_B (two relationships):
    • Joined via OKC_DELIVERABLES.RELATIVE_ST_DATE_EVENT_ID to define the event triggering the deliverable's start date.
    • Joined via OKC_DELIVERABLES.RELATIVE_END_DATE_EVENT_ID to define the event triggering the deliverable's end or due date.

These relationships are critical for the event-driven scheduling and alerting mechanisms within the Contracts module. The table is also intrinsically linked to core contract entities like OKC_K_HEADERS_B (contract headers) and OKC_K_LINES_B (contract lines), typically through foreign keys not listed in the excerpt but central to its function.