Search Results i_ship_site

Overview

APPS.ASO_PVT_SHIPMENTS_V is a reporting and integration view in the Oracle EBS Order Capture (ASO) module. It presents shipment-level records from the ASO_SHIPMENTS table enriched with customer, party site, and address attributes drawn from the Oracle Trading Community Architecture (TCA) and FND reference data. The view is prefixed "PVT," which in Oracle Applications convention typically denotes a private or internal object; nevertheless, it is exposed under the APPS schema and is frequently reached by custom reports, extracts, and interfaces that need a denormalized shipment record without hand-joining TCA tables. Its role is to supply quote-to-order shipping data—promise dates, schedule ship dates, ship-to party and site, freight and FOB terms, reserved quantities, and flexible attribute columns—together with resolved customer names, account numbers, and shipping addresses.

The view is documented in ETRM under Oracle EBS 12.2.2 metadata (owner APPS) and is equally applicable to 12.1.1, since the underlying ASO, HZ, and FND objects share compatible structures across both releases. Interest in this view commonly arises when searching for the i_cust_parties alias, which is the HZ_PARTIES join that resolves the ship-to customer name and customer type.

Underlying Base Objects

The view is defined over the following documented base objects:

• ASO_SHIPMENTS (SYNONYM) — the driving table, supplying all shipment header attributes, quantity and reservation data, and descriptive flexfield columns.
• HZ_PARTY_SITES (SYNONYM) — aliased I_SHIP_SITE, joined on SHIP.SHIP_TO_PARTY_SITE_ID = I_SHIP_SITE.PARTY_SITE_ID.
• HZ_LOCATIONS (SYNONYM) — aliased I_SHIP_ADDR, joined to the party site to supply address components.
• HZ_RELATIONSHIPS (SYNONYM) — aliased I_PARTY_REL, linking party sites to parties.
• HZ_PARTIES (SYNONYM) — appears twice: as I_PARTY_REL_PARTY (party name for the relationship) and as I_CUST_PARTIES (customer name and customer type).
• HZ_CUST_ACCOUNTS (SYNONYM) — aliased I_CUST, supplying the account number.
• FND_TERRITORIES_VL (VIEW) — resolves the country code into a territory short name.

Because the view joins TCA entities, its output reflects the current state of customer and address records rather than a historical snapshot.

Key Columns

• SHIPMENT_ID, QUOTE_HEADER_ID, QUOTE_LINE_ID, ORDER_LINE_ID, RESERVATION_ID — primary and foreign identifiers tying the shipment to its quote, order line, and inventory reservation.
• PROMISE_DATE, REQUEST_DATE, SCHEDULE_SHIP_DATE — the key scheduling and commitment dates for the shipment.
• SHIP_TO_PARTY_ID, SHIP_TO_CUST_ACCOUNT_ID, SHIP_TO_CUST_PARTY_ID — party and account identifiers for the ship-to destination.
• CUSTOMER_NAME, CUSTOMER_TYPE, CUSTOMER_ACCOUNT_NUMBER — resolved from I_CUST_PARTIES and I_CUST, the columns most often sought when querying via i_cust_parties.
• SHIP_TO_ADDRESS1..4, SHIP_TO_CITY, SHIP_TO_STATE, SHIP_TO_POSTAL_CODE, SHIP_TO_COUNTRY, SHIP_TO_COUNTRY_CODE — formatted ship-to address fields from HZ_LOCATIONS and FND_TERRITORIES_VL.
• SHIP_METHOD_CODE, FREIGHT_TERMS_CODE, FREIGHT_CARRIER_CODE, FOB_CODE, SHIPPING_INSTRUCTIONS, PACKING_INSTRUCTIONS — logistics and fulfillment terms.
• QUANTITY, RESERVED_QUANTITY, SHIP_QUOTE_PRICE, SHIP_PARTIAL_FLAG — quantities, pricing, and partial-shipment indicator.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield columns for customer-specific data.

Common Use Cases and Queries

Typical uses include quote-to-order shipment extracts, customer-facing delivery reporting, freight and logistics analysis, and data migration validation. A sample query resolving customer details through the i_cust_parties join is shown below.

SELECT s.shipment_id,
       s.quote_header_id,
       s.schedule_ship_date,
       s.customer_name,
       s.customer_type,
       s.customer_account_number,
       s.ship_to_city,
       s.ship_to_country,
       s.quantity,
       s.reserved_quantity
FROM   apps.aso_pvt_shipments_v s
WHERE  s.ship_to_cust_party_id IS NOT NULL
  AND  s.schedule_ship_date >= TRUNC(SYSDATE)
ORDER BY s.schedule_ship_date;

To aggregate shipment volume by customer type and territory, the view can be grouped directly on customer_type and ship_to_country. Because the view exposes no organization or operating unit filter, results should be constrained by quote or order identifiers where multi-org isolation is required. As with all "PVT" objects, Oracle does not guarantee the view definition across patches or upgrades, so it should be used advisedly for read-only reporting and validated against release-specific documentation.