Results for “planned_flag”

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

Overview

OKE_DTS_SHIPPING_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the OKE – Project Contracts product family. Its stated purpose is to expose shipping data related to contract deliverables. Functionally, it consolidates delivery header, delivery detail, delivery assignment, packing slip, delivery leg, and document instance information from the Oracle Shipping (WSH) tables into a single, denormalized projection that is keyed to the OKE deliverable structure.

In practice, the view serves as the shipping-side companion to the OKE deliverable and billing tables. It allows contract-facing reporting, inquiry screens, and integration extracts to retrieve the physical fulfillment status of a contract deliverable — what was requested, what was shipped, what was delivered, and what was cancelled — along with carrier, waybill, tracking, and packing slip references, without joining the WSH tables directly. Because delivery status is resolved through the FND_LOOKUP_VALUES_VL lookup on the DELIVERY_STATUS lookup type, the view presents human-readable status values rather than raw codes.

Underlying Base Objects

The view is defined with an explicit filter on WSH_DELIVERY_DETAILS (DLVDTL) restricting rows to SOURCE_CODE = 'OKE', which is the predicate that ties shipping records back to Project Contracts deliverables. It is built from the following documented base objects:

• WSH_NEW_DELIVERIES (DLV) — delivery header attributes including NAME, INITIAL_PICKUP_DATE, PLANNED_FLAG, WAYBILL, and STATUS_CODE.
• WSH_DELIVERY_ASSIGNMENTS (DLVASGN) and WSH_DELIVERY_DETAILS (DLVDTL) — the link between deliveries and delivery details, supplying the quantity and date columns.
• FND_LOOKUP_VALUES_VL (DLVSTAT) — resolves DLV.STATUS_CODE into a meaningful status DESCRIPTION; defaults to 'OP' when the status code is null.
• WSH_PACKING_SLIPS_DB_V (PACK) — supplies PACKING_SLIP_NUMBER.
• WSH_DELIVERY_LEGS (LEG) and WSH_DOCUMENT_INSTANCES (INS) — supply bill of lading and document sequence information; cancelled document instances are excluded (INS.STATUS <> 'CANCELLED').
• OKE_UTILS — a package whose GET_LOCATION_DESCRIPTION function translates SHIP_FROM_LOCATION_ID and SHIP_TO_LOCATION_ID into descriptive location text.
• OKE_K_FORM_HEADERS and OKE_K_FORM_LINES (synonyms) — the contract header and line sources referenced in the delivery detail relationship.

Most joins are outer joins, so deliverables without a shipment or without packing slip and document instance records still return rows.

Key Columns

The most frequently referenced columns include:

• DELIVERED_QUANTITY — the quantity actually delivered for the contract deliverable, distinct from REQUESTED_QUANTITY and SHIPPED_QUANTITY. This is the column most often searched for reconciliation and revenue recognition purposes.
• SHIPPED_QUANTITY and CANCELLED_QUANTITY — supporting quantity measures for fulfillment and shortfall analysis; REQUESTED_QUANTITY_UOM provides the unit of measure.
• SOURCE_HEADER_ID / SOURCE_LINE_ID / DELIVERABLE_ID — the OKE contract header, line, and deliverable keys used to join back to the contract tables.
• DATE_REQUESTED, DATE_SCHEDULED, INITIAL_PICKUP_DATE — the request, schedule, and pickup dates that drive on-time delivery reporting.
• STATUS, PLANNED_FLAG, TRACKING_NUMBER, WAYBILL — shipment state, planning indicator, and carrier references.
• SHIP_FROM_LOCATION and SHIP_TO_LOCATION — descriptive locations derived via OKE_UTILS.
• PACKING_SLIP_NUMBER, BILL_OF_LADING_NUMBER — documentation references for shipment verification.

Common Use Cases and Queries

A typical use is to track delivered versus requested quantities per deliverable, which supports progress billing, milestone verification, and open quantity analysis. A representative query follows:

• SELECT deliverable_id, delivered_quantity, requested_quantity, status FROM oke_dts_shipping_v WHERE source_header_id = :header_id;
• SELECT deliverable_id, delivered_quantity - requested_quantity shortfall FROM oke_dts_shipping_v WHERE cancelled_quantity > 0;
• SELECT deliverable_id, status, waybill, packing_slip_number FROM oke_dts_shipping_v WHERE status = 'Delivered' AND date_scheduled BETWEEN :from AND :to;

Because the view resolves status codes through the lookup view and locations through OKE_UTILS, queries are self-contained and suitable for concurrent programs, OBIEE extracts, and integration interfaces. Reports should filter on SOURCE_HEADER_ID or DELIVERABLE_ID to avoid full-table scans, since the WSH base objects are among the largest in the EBS data model.