Search Results i_ship_addr

Overview

APPS.ASO_SHIPMENTS_V is a reporting and integration view in the Oracle E-Business Suite Order Management and Quoting modules (Oracle Advanced Pricing / Oracle Quoting — ASO schema). It exposes shipment scheduling and shipping detail information associated with quote lines, enriching the raw shipment record in ASO_SHIPMENTS with decoded party, contact, and address attributes. Rather than requiring callers to join several party and address views manually, ASO_SHIPMENTS_V pre-joins these lookups so that a single query returns a fully described shipping destination — including ship-to party name, contact names, and a complete postal address.

The view is commonly used for reporting, order-to-quote traceability extracts, and integration payloads where a flat, human-readable representation of the shipping destination is required. Because it flattens party and location data into the same row as the shipment scheduling attributes, it is well suited to feed custom reports, interfaces, and downstream systems without additional joins.

Underlying Base Objects

The documented view is defined over the following objects:

• ASO_SHIPMENTS (SYNONYM) — the driving table supplying shipment IDs, scheduling dates, quantities, shipping method codes, freight terms, FOB, instructions, and descriptive flexfield (DFF) attributes.
• ASO_I_PARTY_SITES_V (VIEW) — the ship-to address source, aliased I_SHIP_ADDR, joined on SHIP_TO_PARTY_SITE_ID.
• ASO_I_PARTIES_V (VIEW) — used twice: as I_SHIP_PARTIES for the ship-to party/contact names and as I_SHIP_CUST_PARTIES for the customer party name.
• ASO_I_COUNTRIES_V (VIEW) — participating in the join to resolve country data; it appears in the FROM clause though its columns are not explicitly projected in the excerpt.
• ASO_SHIPMENT_PVT (PACKAGE) — the underlying API package that maintains shipment records, referenced as a base object for the view.

The critical join is SHIP.SHIP_TO_PARTY_SITE_ID = I_SHIP_ADDR.PARTY_SITE_ID(+), an outer join ensuring shipments without a resolved party site are not dropped.

Key Columns

• SHIPMENT_ID, QUOTE_HEADER_ID, QUOTE_LINE_ID, ORDER_LINE_ID — identifiers linking the shipment to its quote and order context.
• PROMISE_DATE, REQUEST_DATE, SCHEDULE_SHIP_DATE — scheduling and commitment dates.
• SHIP_TO_PARTY_ID, SHIP_TO_PARTY_NAME, SHIP_TO_PARTY_SITE_ID — the destination party and site.
• SHIP_TO_ADDRESS1..ADDRESS4, SHIP_TO_CITY, SHIP_TO_STATE, SHIP_TO_PROVINCE, SHIP_TO_COUNTY, SHIP_TO_POSTAL_CODE, SHIP_TO_COUNTRY, SHIP_TO_COUNTRY_CODE — the decoded address components sourced from I_SHIP_ADDR.
• SHIP_TO_CONTACT_FIRST_NAME / MIDDLE_NAME / LAST_NAME — the ship-to contact names.
• SHIP_METHOD_CODE, FREIGHT_TERMS_CODE, FREIGHT_CARRIER_CODE, FOB_CODE, SHIP_PARTIAL_FLAG, SHIP_SET_ID — shipping terms and control flags.
• SHIPPING_INSTRUCTIONS, PACKING_INSTRUCTIONS — free-text handling instructions.
• QUANTITY, RESERVED_QUANTITY, RESERVATION_ID — quantities and reservation linkage.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1..ATTRIBUTE15 — the DFF columns.
• SHIP_FROM_ORG_ID, SHIP_TO_CUST_ACCOUNT_ID, SHIP_TO_CUST_PARTY_ID — organizational and customer party references.

Common Use Cases and Queries

A frequent requirement is extracting a shipment with its formatted ship-to address, which is exactly the column set the user searched for (i_ship_addr). For example:

• Reporting all shipments for a quote header with destination details.
• Feeding integrations that require a flat ship-to address block.
• Auditing promise dates against schedule ship dates.

SELECT shipment_id,
       quote_header_id,
       quote_line_id,
       promise_date,
       schedule_ship_date,
       ship_to_party_name,
       ship_to_contact_last_name,
       ship_to_address1,
       ship_to_city,
       ship_to_state,
       ship_to_postal_code,
       ship_to_country,
       ship_method_code,
       quantity
  FROM apps.aso_shipments_v
 WHERE quote_header_id = :p_quote_header_id

A second common query filters by destination to review shipments bound for a given party site:

SELECT shipment_id, quote_line_id, schedule_ship_date, ship_to_address1, ship_to_city
  FROM apps.aso_shipments_v
 WHERE ship_to_party_site_id = :p_site_id
   AND schedule_ship_date >= TRUNC(SYSDATE)

Because the view depends on party and address views that in turn rely on TCA (Trading Community Architecture) structures, results reflect the current decoded party site data. Callers should filter on QUOTE_HEADER_ID or SHIP_TO_PARTY_SITE_ID and avoid unconstrained full scans on high-volume environments.