Results for “ship_to_address1”

50+ results




Overview
Explore in AI Chat

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

Overview

The ASO_SHIPMENTS_BALI_V view is a reporting and integration object owned by the APPS schema within the ASO (Order Capture) product family of Oracle E-Business Suite, applicable to releases 12.1.1 and 12.2.2. It is a denormalized, read-only projection that consolidates shipment-level detail from Oracle Quoting with customer ship-to address information and shipping method reference data. The view presents one row per shipment line, joining each shipment record to its originating quote header for currency context, to the customer's ship-to address for geographic detail, and to a shipping method view for a descriptive carrier or service name.

Its principal role is to support reporting and downstream integration scenarios in which a flat, human-readable picture of quote shipment data is required without traversing the normalized Quoting and Trading Community Architecture (TCA) relationships at runtime. Because the view is defined entirely with outer joins for the address and shipping-method branches, shipment rows are preserved even when the associated ship-to site or method description is unavailable, making it suitable for exception-driven reporting.

Underlying Base Objects

The documented ETRM metadata identifies the referenced base objects as follows:

The joins to HZ_PARTY_SITES, HZ_LOCATIONS, and ASO_I_SHIPPING_METHODS_V are outer joins (marked with the (+) operator), while the join to ASO_QUOTE_HEADERS_ALL is an inner join on QUOTE_HEADER_ID. Consequently, a qualifying quote header is mandatory, whereas address and shipping method attributes are optional.

Key Columns

  • SHIPMENT_ID — Unique identifier of the shipment row from ASO_SHIPMENTS; the view's primary granularity.
  • QUOTE_HEADER_ID — Foreign key linking the shipment to its parent quote header; drives the currency join.
  • QUOTE_LINE_ID — Identifies the quote line associated with the shipment.
  • QUANTITY — Shipped or quoted quantity for the shipment line.
  • SHIP_TO_ADDRESS1, SHIP_TO_CITY, SHIP_TO_STATE — Flattened address attributes sourced from HZ_LOCATIONS via HZ_PARTY_SITES.
  • SHIP_METHOD_CODE — Shipping method code recorded on the shipment, used as the join key to the shipping method view.
  • SHIP_QUOTE_PRICE — Quoted shipping price for the shipment.
  • CURRENCY_CODE — Transaction currency of the parent quote header.
  • SHIPPING_METHOD — Descriptive name of the shipping method (note: documented as column heading "SHPPPING_METHOD").

Common Use Cases and Queries

Typical uses include auditing shipment pricing against quotes, reconciling ship-to addresses for fulfillment, and feeding external logistics or analytics systems with flattened shipment data.

Retrieve all shipments for a given quote, including ship-to address detail:

  • SELECT shipment_id, quote_line_id, quantity, ship_to_address1, ship_to_city, ship_to_state, shipping_method, ship_quote_price, currency_code FROM apps.aso_shipments_bali_v WHERE quote_header_id = :p_quote_header_id;

Aggregate quoted shipping charges by shipping method and currency:

  • SELECT shipping_method, currency_code, COUNT(*) shipment_count, SUM(ship_quote_price) total_price FROM apps.aso_shipments_bali_v GROUP BY shipping_method, currency_code ORDER BY total_price DESC;

Identify shipments lacking a resolvable ship-to address or method description, exploiting the outer joins:

  • SELECT shipment_id, quote_header_id, ship_method_code, shipping_method FROM apps.aso_shipments_bali_v WHERE ship_to_address1 IS NULL OR shipping_method IS NULL;

Because the view references multi-org and TCA objects, queries should be issued with an appropriate responsibility and, where applicable, operating unit context to ensure correct data visibility.