Search Results oe_ak_ship_sets_v




Overview
Explore in AI Chat

Overview

OE_AK_SHIP_SETS_V is a seeded Oracle E-Business Suite database view owned by the APPS schema within the Order Management (ONT) product family. It exposes a filtered, denormalized projection of shipping set definitions maintained in the Order Management foundation. The view is defined as a restricted SELECT over OE_SETS, returning only those records where SET_TYPE equals 'SHIP_SET'. Because it is a view rather than a table, it carries no storage of its own and imposes no additional locking behavior; it is a read-only access path intended for inquiry, reporting, and integration.

The "AK" prefix in the object name follows the historical Oracle Applications convention for attribute-and-key style interface views. In practice, OE_AK_SHIP_SETS_V is used by Order Management and its dependent modules to resolve the shipping attributes—source organization, destination organization, scheduled dates, freight carrier, shipping method, and shipment priority—associated with a given shipping set identifier. This makes it a convenient, low-cost source for reports, concurrent programs, and custom extensions that need shipping set attributes without querying the broader OE_SETS table directly. The column FREIGHT_CARRIER_CODE, which is the term the user searched for, is one of the principal shipping attributes exposed by this view.

Underlying Base Objects

The ETRM metadata documents a single referenced base object: OE_SETS, accessed through a public synonym in the APPS schema. OE_SETS is the Order Management foundation table that stores set definitions for multiple set types, of which shipping sets are only one. The view applies a constant predicate, SET_TYPE = 'SHIP_SET', so every row returned represents a shipping set rather than another set category such as a pick set or a configuration set.

Because the relationship is a one-view-to-one-table projection, each row in OE_AK_SHIP_SETS_V corresponds to exactly one row in OE_SETS with the shipping set type. No joins, unions, or aggregations are present in the view text, so the view adds no cardinality change and no derived columns. Any filtering or joining that consumers require—for example, to order headers, delivery lines, or carrier master data—must be supplied in the consuming query.

Key Columns

  • SET_ID — Primary identifier of the shipping set. This is the key used to correlate the view with order, delivery, and set-related records elsewhere in Order Management.
  • SHIP_FROM_ORG_ID — Organization identifier for the shipping warehouse or source organization from which goods are dispatched.
  • SHIP_TO_ORG_ID — Organization identifier for the receiving or destination location.
  • SCHEDULE_SHIP_DATE — Planned ship date for the set.
  • SCHEDULE_ARRIVAL_DATE — Planned arrival date at the destination.
  • FREIGHT_CARRIER_CODE — Code of the freight carrier assigned to the shipping set. This is the attribute most frequently searched in this context and is typically resolved against carrier master data to obtain carrier name and service details.
  • SHIPPING_METHOD_CODE — Code identifying the shipping method (for example, the mode or service level) associated with the set.
  • SHIPMENT_PRIORITY_CODE — Code indicating the handling priority assigned to the shipment.

Common Use Cases and Queries

Typical use cases include shipping set inquiry screens, freight carrier assignment audits, carrier utilization reporting, and interfaces that export scheduled ship and arrival dates to planning or transportation systems. The view is also useful for validating that shipping sets carry complete carrier and method assignments before release to shipping.

The following query lists shipping sets by freight carrier:

  • SELECT set_id, ship_from_org_id, ship_to_org_id, freight_carrier_code, shipping_method_code, shipment_priority_code, schedule_ship_date FROM oe_ak_ship_sets_v WHERE freight_carrier_code = :p_carrier ORDER BY schedule_ship_date;
  • SELECT freight_carrier_code, COUNT(*) FROM oe_ak_ship_sets_v GROUP BY freight_carrier_code;

Consumers should note that the view exposes only shipping set columns and no descriptive carrier or organization names; those must be obtained through additional lookups in the consuming query.