Results for “delivery_date”

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

Overview

OKE_DTS_SUBCONTRACTS_V is an APPS-owned database view in Oracle E-Business Suite, defined within the OKE – Project Contracts product family. Its documented purpose is to expose subcontract data related to contract deliverables. In the Oracle EBS 12.1.1 and 12.2.2 releases, the view operates as a read-only reporting and integration interface over the deliverable and subcontract structures maintained by Oracle Contracts Core and Oracle Project Contracts.

The view is significant because subcontract deliverables are not stored as independent records in a dedicated subcontract table. Instead, a parent deliverable row in OKE_K_DELIVERABLES_B references a second deliverable row through the SUB_REF_ID column, and that referenced row represents the subcontract side of the relationship. OKE_DTS_SUBCONTRACTS_V resolves this self-referential linkage and joins it to contract header, line, type, and status information so that both the owning deliverable and its associated subcontract deliverable can be reported side by side.

Underlying Base Objects

The documented base objects are OKE_K_DELIVERABLES_B, OKE_K_HEADERS_V, OKE_K_LINES_V, OKE_K_TYPES_VL, and OKC_STATUSES_V. In ETRM 12.2.2, OKE_K_DELIVERABLES_B is referenced as a synonym, while the remaining four are views.

• OKE_K_DELIVERABLES_B — the core deliverable table, aliased twice (D and SKD) to produce the owning deliverable and the subcontract deliverable in a single row.
• OKE_K_HEADERS_V / OKE_K_LINES_V — supply subcontract header and line context, including K_NUMBER_DISP and LINE_NUMBER.
• OKE_K_TYPES_VL — supplies the contract type name through KT.K_TYPE_NAME.
• OKC_STATUSES_V — supplies the translated status meaning through STS.MEANING.

The join conditions are fixed: D.SUB_REF_ID equals SKD.DELIVERABLE_ID, SKL.K_LINE_ID equals SKD.K_LINE_ID, SKH.K_HEADER_ID equals SKD.K_HEADER_ID, KT.K_TYPE_CODE equals SKH.K_TYPE_CODE, and STS.CODE equals SKH.STATUS_CODE.

Key Columns

• K_HEADER_ID, K_LINE_ID, DELIVERABLE_ID — identifiers of the owning contract deliverable.
• SUBK_HEADER_ID, SUBK_LINE_ID, SUBK_DELIVERABLE_ID — identifiers of the linked subcontract deliverable.
• SUBCONTRACT_NUMBER, SUBCONTRACT_LINE_NUMBER, SUBCONTRACT_DELIVERABLE_NUM — displayable subcontract identification values.
• SUBCONTRACT_K_TYPE, SUBCONTRACT_STATUS — contract type name and status meaning for the subcontract.
• QUANTITY — delivered or contracted quantity on the subcontract deliverable.
• DELIVERY_DATE — the scheduled delivery date for the subcontract deliverable. This is the column most commonly targeted when users search for delivery_date.
• NEED_BY_DATE — the required-by date, enabling comparison of scheduled delivery against demand.

Common Use Cases and Queries

Typical uses include subcontract deliverable tracking, delivery schedule reporting, and discrepancy analysis comparing DELIVERY_DATE against NEED_BY_DATE. A representative query is:

• SELECT subcontract_number, subcontract_line_number, subcontract_deliverable_num, quantity, delivery_date, need_by_date FROM oke_dts_subcontracts_v WHERE delivery_date BETWEEN :p_start AND :p_end ORDER BY delivery_date;
• SELECT subcontract_number, subcontract_status, delivery_date, need_by_date FROM oke_dts_subcontracts_v WHERE need_by_date < delivery_date;
• SELECT subcontract_k_type, COUNT(*) FROM oke_dts_subcontracts_v GROUP BY subcontract_k_type;

Because the view is read-only and joins secured contract entities, access depends on the APPS schema and standard OKE responsibility grants.