Search Results in_process_flag




Overview

OKE_DTS_SEARCH_LOV_V is a VALID database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKE – Project Contracts product family. It functions as a denormalized search and list-of-values (LOV) source for deliverable, task, and shipment scheduling data maintained by the Oracle Contract Deliverables (DTS) subsystem. Rather than exposing a single base table, the view consolidates deliverable rows from OKE_K_DELIVERABLES_VL with descriptive attributes drawn from contracts, projects, tasks, items, organizations, and lookup definitions, so that forms, concurrent programs, and integrations can query a single flattened result set.

The name and column layout indicate that this view backs search windows and value-selection lists in the Project Contracts and related shipping/deliverable flows. Fields such as SHIPPABLE_FLAG, BILLABLE_FLAG, DEPENDENCY_FLAG, and READY_TO_PROCURE are presented directly from the deliverable record, enabling the calling UI to filter candidate rows without joining back to the base tables. Because the view is a stored definition rather than a materialized object, it always reflects current transactional data.

Underlying Base Objects

The documented definition references the following objects, all resolved through the APPS schema:

The view therefore joins contractual deliverable data to project, task, item, and organization reference data, which is why it appears as a reporting-friendly surface over the transactional DTS tables.

Key Columns

Common Use Cases and Queries

The view is typically queried from forms and reports that require a user-selectable list of deliverables for a project or contract. A representative query filters on dependency and readiness flags:

  • SELECT deliverable_num, project_number, task_number, dependency_flag, ready_to_bill FROM oke_dts_search_lov_v WHERE project_id = :p_project_id AND dependency_flag = 'Y';
  • SELECT deliverable_id, data_item_name, delivery_date FROM oke_dts_search_lov_v WHERE k_header_id = :p_header_id ORDER BY deliverable_num;

Because the view restricts rows through its join conditions, consumers should supply contract or project predicates to keep result sets selective. It is not intended for high-volume batch extraction; for such workloads, joining the base objects directly is preferable.