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:
- DELIVERABLE_ID — Surrogate primary key defined by
OKE_K_DELIVERABLES_PK, and also the unique indexOKE_K_DELIVERABLES_U1. It is the identifier referenced by nearly every child table. - K_HEADER_ID, K_LINE_ID, DELIVERABLE_NUM — The business-key candidate defined by unique index
OKE_K_DELIVERABLES_U2. A deliverable is uniquely identified within the context of its contract header and contract line by its deliverable number. - PROJECT_ID, TASK_ID — Foreign keys to
PA_PROJECTS_ALLandPA_TASKS, tying the deliverable to the project and task used for cost collection and billing. - STATUS_CODE, STATUS_DATE — The current workflow status of the deliverable and the date that status was assigned.
- DELIVERY_DATE, NEED_BY_DATE, EXPECTED_SHIPMENT_DATE, PROMISED_SHIPMENT_DATE — Contractual and planning dates used to schedule and track fulfillment.
- QUANTITY, UOM_CODE, UNIT_PRICE, CURRENCY_CODE, VOLUME, WEIGHT — Commercial and physical quantity attributes used for pricing, shipping, and billing calculations.
- SHIPPING_REQUEST_ID — Foreign key to
WSH_DELIVERY_DETAILS, linking the deliverable to its shipping/delivery detail record. - BILLING_EVENT_ID and the BILL_* columns — Billing attributes (event type, date, item, line, rate, exchange rate, amount, quantity) populated when the deliverable is invoiced.
- ITEM_ID, INVENTORY_ORG_ID — References to the shipped or procured inventory item.
- ATTRIBUTE_CATEGORY through ATTRIBUTE1–15 — The standard EBS descriptive flexfield columns for client-specific extensions.
- SUBCONTRACTED_FLAG, BILLABLE_FLAG, DEPENDENCY_FLAG, COMPLETED_FLAG, READY_TO_BILL, READY_TO_PROCURE — Workflow and eligibility flags driving downstream processing.
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_ALLandPA_TASKSonPROJECT_IDandTASK_ID. - Billing reconciliation: join
BILLING_EVENT_IDtoOKE_K_BILLING_EVENTSto compare billed amounts againstUNIT_PRICEandQUANTITY. - Open deliverables report: filter on
STATUS_CODEandCOMPLETED_FLAG = 'N'. - Shipped-but-not-billed analysis: join
SHIPPING_REQUEST_IDtoWSH_DELIVERY_DETAILSand checkREADY_TO_BILL.
Related Objects
- OKE_K_HEADERS and OKE_K_LINES — Parent contract header and line records (joined on
K_HEADER_IDandK_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_IDandDEPENDENT_ID. - OKE_K_BILLING_EVENTS — Billing event records referencing
DELIVERABLE_ID. - PA_PROJECTS_ALL and PA_TASKS — Project and task masters joined on
PROJECT_IDandTASK_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.
-
This table stores all deliverable information for Project Contracts
-
View: OKE_K_DELIVERABLES_VLH 12.2.2
Contract deliverable infomation history view
APPS.OKE_K_DELIVERABLES_VLH·↳ OKC_STATUSES_V·↳ OKE_K_DELIVERABLES_BH·↳ OKE_K_DELIVERABLES_TLH·Explore OKE module →
-
Historical Contract Deliverable information
-
Historical Contract Deliverable information
-
View: OKE_K_DELIVERABLES_VL 12.2.2
Contract deliverable infomation view
APPS.OKE_K_DELIVERABLES_VL·↳ OKC_STATUSES_V·↳ OKE_K_DELIVERABLES_B·↳ OKE_K_DELIVERABLES_TL·Explore OKE module →
-
View: OKE_K_DELIVERABLES_VLH 12.1.1
Contract deliverable infomation history view
APPS.OKE_K_DELIVERABLES_VLH·↳ OKC_STATUSES_V·↳ OKE_K_DELIVERABLES_BH·↳ OKE_K_DELIVERABLES_TLH·Explore OKE module →
-
View: OKE_K_DELIVERABLES_VL 12.1.1
Contract deliverable infomation view
APPS.OKE_K_DELIVERABLES_VL·↳ OKC_STATUSES_V·↳ OKE_K_DELIVERABLES_B·↳ OKE_K_DELIVERABLES_TL·Explore OKE module →
-
This table stores all deliverable information for Project Contracts
-
eTRM - OKE Tables and Views 12.1.1
This table stores the version comparison results.
-
eTRM - OKE Tables and Views 12.2.2
This table stores the version comparison results.