Search Results ship_set




Overview
Explore in AI Chat

Overview

The view APPS.OE_AK_SHIP_SETS_V is a filtered projection of the Oracle Order Management shipping set repository. It exposes a single subset of the records stored in OE_SETS — specifically those rows where SET_TYPE = 'SHIP_SET'. In Oracle EBS, a shipping set is a named grouping of order lines that must be shipped together from the same warehouse, to the same destination, on the same scheduled dates, and via the same carrier and shipping method. Collectively these attributes define an "arrival set" or "ship set" constraint that the shipping and scheduling engine enforces during pick release and ship confirmation.

Because the underlying table OE_SETS serves multiple set types (for example, ship sets and arrival sets), the view functions primarily as a convenience and security layer: it spares report developers and integration interfaces from repeatedly coding the SET_TYPE predicate and it presents a stable, human-readable column list that maps directly to the business concept of a ship set. It is therefore widely referenced in Order Management and Shipping Execution reporting, in custom concurrent programs, and in inbound or outbound interfaces that must resolve the set identifier associated with a group of lines. The view is owned by APPS and is normally granted to responsibility-level users through the standard EBS synonym and grant model.

Underlying Base Objects

The documented base object is OE_SETS, accessed through a synonym in the APPS schema. OE_SETS stores the header-level definition of all order sets. Each record is identified by SET_ID and qualified by SET_TYPE. The view applies the constant filter WHERE SET_TYPE = 'SHIP_SET', so every row returned by OE_AK_SHIP_SETS_V represents a ship set definition and no arrival-only or other set type will appear.

Note that the view is a read-only projection. It contains no joins, aggregations, or lookups to OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, or the shipping tables; the association between a ship set and its member lines is held separately in the line-level set columns. Consequently, the view should be treated as a dimension of ship set headers rather than as a complete picture of set membership.

Key Columns

  • SET_ID — Primary identifier of the ship set. This value is the foreign key referenced by order lines that belong to the set.
  • SHIP_FROM_ORG_ID — Inventory organization from which all lines in the set must ship.
  • SHIP_TO_ORG_ID — Destination organization or party site for the set.
  • SCHEDULE_SHIP_DATE — Date on which the set is scheduled to leave the warehouse; all member lines share this date.
  • SCHEDULE_ARRIVAL_DATE — Date on which the set is scheduled to arrive at the destination.
  • FREIGHT_CARRIER_CODE — Carrier assigned to the set.
  • SHIPPING_METHOD_CODE — Shipping method or service level applied to the set.
  • SHIPMENT_PRIORITY_CODE — Priority used by the shipping engine when sequencing the set.

Because the view inherits these columns directly from OE_SETS, code values follow the same validation and lookup conventions (FND_LOOKUPS, ORG_FREIGHT, and inventory organization definitions) applied elsewhere in Order Management.

Common Use Cases and Queries

Typical uses include validating set consistency before pick release, reporting on scheduled ship and arrival dates by carrier or destination, and supplying set identifiers to integration processes that create or update order lines. The following query lists ship sets by scheduled ship date and shipping method.

  • SELECT set_id, ship_from_org_id, ship_to_org_id, schedule_ship_date, freight_carrier_code FROM oe_ak_ship_sets_v WHERE schedule_ship_date >= TRUNC(SYSDATE) ORDER BY schedule_ship_date;
  • SELECT set_id, shipping_method_code, shipment_priority_code FROM oe_ak_ship_sets_v WHERE ship_from_org_id = :org_id;
  • SELECT COUNT(*) FROM oe_ak_ship_sets_v WHERE schedule_arrival_date BETWEEN :from_date AND :to_date;

When joining to order lines, the analyst must use the line-level set column or the shipping set assignment table; the view alone does not expose membership. All queries should be run with the standard EBS APPS initialization or via a secured synonym granted to the reporting schema.