Search Results ship_partial_flag




Overview
Explore in AI Chat

Overview

OKX_QTE_SHIPMENTS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite. It belongs to the OKX – Contracts Integration product family, which provides the integration layer between Oracle Quoting (ASO) and downstream order fulfillment flows in Oracle Order Management. The view exposes shipment-level scheduling and fulfillment detail associated with quote lines, allowing quote headers and quote lines to be linked to the shipment records generated against them.

Because the object is a view rather than a table, no data is stored within it. Instead, it presents a horizontally projected, denormalized result set derived from the underlying Oracle Quoting shipment entity. Its purpose is to give reporting tools, concurrent programs, and integration interfaces a stable, APPS-owned access point to shipment information without requiring direct reads from the Oracle Quoting base schema. In EBS 12.1.1 and 12.2.2 the object retains a VALID status, and the documented metadata confirms it is defined over the ASO_SHIPMENTS base object exposed through a synonym.

Underlying Base Objects

The documented reference for this view is the base object ASO_SHIPMENTS, accessed through a synonym. ASO_SHIPMENTS is the Oracle Quoting shipment entity that stores shipment scheduling information for quote lines, including promise dates, ship-to parties, shipping and packing instructions, carrier and freight attributes, and reserved quantities. OKX_QTE_SHIPMENTS_V is a simple projection over that entity: the view text selects a defined list of columns directly FROM ASO_SHIPMENTS with no joins, unions, or aggregation.

As a consequence, each row in the view corresponds one-to-one with a row in ASO_SHIPMENTS. Row counts and cardinality therefore match the underlying shipment records. Any update, deletion, or insertion performed on the base shipment entity is immediately reflected when the view is queried. The view remains a dependent object of ASO_SHIPMENTS, so the underlying table must exist and be valid for the view to compile and return data.

Key Columns

Common Use Cases and Queries

The view is typically used to report on shipment scheduling attached to quotes, to feed integration programs that pass shipment detail downstream, and to reconcile quote lines with their resultant order lines. A common pattern joins the view back to the quote header and line entities using QUOTE_HEADER_ID and QUOTE_LINE_ID.

Example: retrieve scheduled shipments for a given quote line.

  • SELECT s.shipment_id, s.quote_line_id, s.promise_date, s.schedule_ship_date, s.quantity, s.reserved_quantity, s.ship_method_code, s.freight_carrier_code FROM apps.okx_qte_shipments_v s WHERE s.quote_line_id = :p_quote_line_id ORDER BY s.schedule_ship_date;

Example: list all open scheduled shipments with ship-to detail for a date range.

  • SELECT s.shipment_id, s.quote_header_id, s.ship_to_party_id, s.ship_to_party_site_id, s.ship_to_cust_account_id, s.freight_terms_code, s.fob_code FROM apps.okx_qte_shipments_v s WHERE s.schedule_ship_date BETWEEN :p_from_date AND :p_to_date;

Because the view performs no transformation, ad hoc queries can rely on the underlying column semantics matching Oracle Quoting documentation. Developers should avoid DML against the view and instead direct inserts and updates to the Oracle Quoting shipment APIs or the base entity, treating OKX_QTE_SHIPMENTS_V strictly as a query and reporting surface.