Search Results oke_k_deliverables_vl




Overview
Explore in AI Chat

Overview

OKE_K_DELIVERABLES_VL is a multi-lingual (VL) view owned by the APPS schema in Oracle E-Business Suite, defined in the OKE – Project Contracts module. Its documented purpose is to present contract deliverable information maintained against project contracts, exposing both the operational attributes of a deliverable and the descriptive, translated text associated with it. The VL designation indicates that the view joins a base table to its translation table, so each row carries the language-specific description and comments for the deliverable in addition to the transactional data.

In EBS 12.1.1 and 12.2.2 the view serves reporting, inquiry, and integration consumers that need deliverable-level detail without navigating the underlying base and translation tables directly. Deliverables represent the items, submittals, and contractual artifacts that must be delivered under a project contract, and this view materialises the full lifecycle state of each one — from scheduling and shipping attributes through billing and procurement readiness — together with project and task context resolved from the Projects module.

Underlying Base Objects

The documented base objects for this view are:

The view is therefore a join of contract deliverable data to Projects entities, status lookup, version information, and translation rows, producing a denormalised result set suited to direct querying.

Key Columns

Identity and classification columns include DELIVERABLE_ID, DELIVERABLE_NUM, K_HEADER_ID, and K_LINE_ID, tying the deliverable to its contract header and line. PROJECT_ID, TASK_ID, SEGMENT1, NAME, TASK_NAME, and TASK_NUMBER provide the project and task context. Scheduling columns include DELIVERY_DATE, START_DATE, END_DATE, NEED_BY_DATE, EXPECTED_SHIPMENT_DATE, INITIATE_SHIPMENT_DATE, PROMISED_SHIPMENT_DATE, and AS_OF_DATE.

Logistics and shipping attributes include SHIP_TO_ORG_ID, SHIP_TO_LOCATION_ID, SHIP_FROM_ORG_ID, SHIP_FROM_LOCATION_ID, INVENTORY_ORG_ID, SHIPPABLE_FLAG, AVAILABLE_FOR_SHIP_FLAG, DROP_SHIPPED_FLAG, MPS_TRANSACTION_ID, and SHIPPING_REQUEST_ID. The SHIPPING_REQUEST_ID column is of particular interest to users searching for it: it links the deliverable to the shipping request generated for it, enabling reconciliation between contract deliverables and outbound shipment activity.

Commercial and billing columns include CURRENCY_CODE, UNIT_PRICE, UOM_CODE, QUANTITY, BILLABLE_FLAG, BILLING_EVENT_ID, and READY_TO_BILL. Workflow and processing columns include STATUS_CODE, MEANING, WF_ITEM_KEY, IN_PROCESS_FLAG, DEFAULTED_FLAG, and COMPLETED_FLAG. Export control fields include EXPORT_FLAG, EXPORT_LICENSE_NUM, and EXPORT_LICENSE_RES, while SUBMISSION_FLAG, FREQUENCY, TOTAL_NUM_OF_COPIES, CDRL_CATEGORY, and DATA_ITEM_NAME support contractual submittal tracking. Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and ATTRIBUTE1–15 complete the row. Note the view text lists VOLUME twice, a documented quirk of the definition.

Common Use Cases and Queries

Typical uses include deliverable status reporting, shipment reconciliation via SHIPPING_REQUEST_ID, billing readiness analysis, and export-control review.

  • List deliverables for a project with task and status meaning.
  • Find deliverables tied to a specific shipping request.
  • Identify billable deliverables ready to bill.

Sample queries:

SELECT deliverable_num, name, task_name, delivery_date, meaning FROM apps.oke_k_deliverables_vl WHERE project_id = :project_id ORDER BY deliverable_num;

SELECT deliverable_id, deliverable_num, k_header_id, k_line_id, shipping_request_id, ship_to_org_id, expected_shipment_date FROM apps.oke_k_deliverables_vl WHERE shipping_request_id IS NOT NULL AND shipping_request_id = :shipping_request_id;

SELECT deliverable_num, project_id, unit_price, quantity, currency_code FROM apps.oke_k_deliverables_vl WHERE billable_flag = 'Y' AND ready_to_bill = 'Y';