Results for “sub_ref_id”

28 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKE_K_DELIVERABLES_B is the base table within the OKE (Project Contracts) schema that stores all deliverable information associated with Oracle Project Contracts in Oracle E-Business Suite 12.1.1 and 12.2.2. Deliverables in this context represent the discrete, contractually obligated items, submissions, documents, or goods that a contractor must produce, transmit, or supply to a customer under the terms of an awarded project contract. This table is the central repository for the commercial, logistical, scheduling, and billing attributes of each deliverable line, and it acts as the parent object for numerous dependent child tables across the Project Contracts and adjacent modules.

From a data modeling perspective, the heuristic Data Vault classification mined from the foreign key structure indicates this table behaves as a hub. The DELIVERABLE_ID surrogate key serves as the unique business identifier that links satellite-style descriptive attributes (physical columns in this table) and multiple dependent link relationships (dependencies, billing events, communications, holds, standard notes). This classification is a modeling suggestion; in native EBS terms the table functions as the primary master record for the deliverable entity.

Key Information Stored

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

Common Use Cases and Queries

Typical reporting and integration scenarios include retrieving all deliverables for a given contract header and line, tracking deliverables approaching their need-by or promised shipment dates, and reconciling deliverables against billing events.

  • Deliverables by contract: SELECT deliverable_id, deliverable_num, status_code, delivery_date FROM oke_k_deliverables_b WHERE k_header_id = :header_id;
  • Deliverables with project context: join to PA_PROJECTS_ALL and PA_TASKS on PROJECT_ID and TASK_ID.
  • Billing reconciliation: join BILLING_EVENT_ID to OKE_K_BILLING_EVENTS to compare billed amounts against UNIT_PRICE and QUANTITY.
  • Open deliverables report: filter on STATUS_CODE and COMPLETED_FLAG = 'N'.
  • Shipped-but-not-billed analysis: join SHIPPING_REQUEST_ID to WSH_DELIVERY_DETAILS and check READY_TO_BILL.

Related Objects

  • OKE_K_HEADERS and OKE_K_LINES — Parent contract header and line records (joined on K_HEADER_ID and K_LINE_ID).
  • OKE_K_DELIVERABLES_TL — Translation table keyed on DELIVERABLE_ID, holding language-specific descriptive text.
  • OKE_DEPENDENCIES — Stores predecessor/successor relationships through DELIVERABLE_ID and DEPENDENT_ID.
  • OKE_K_BILLING_EVENTS — Billing event records referencing DELIVERABLE_ID.
  • PA_PROJECTS_ALL and PA_TASKS — Project and task masters joined on PROJECT_ID and TASK_ID.
  • WSH_DELIVERY_DETAILS — Shipping detail records joined on SHIPPING_REQUEST_ID.
  • OKE_K_HOLDS and OKE_K_STANDARD_NOTES_B — Holds and standard notes attached to a deliverable.