Results for “aso_quote”

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

Overview

The APPS.ASO_PVT_SHIPMENTS_V view is a reporting and integration object within the Oracle E-Business Suite Order Capture (ASO) module. It exposes shipment-level information associated with quotes, joining the base shipment records stored in the ASO shipment structures with customer, party, and address information held in the Oracle Trading Community Architecture (TCA) and FND reference data. As a "PVT" (private) view, it is intended primarily for internal application use and for read-only reporting and interface purposes rather than direct transactional maintenance. The view is relevant when querying shipment details tied to a quote header and quote line, and it surfaces both shipment scheduling attributes and shipping destination attributes. Because the user search term was "aso_quote", this view is most commonly encountered when tracing the shipments that belong to a quote, since it carries QUOTE_HEADER_ID and QUOTE_LINE_ID as linking columns. It is a standard APPS-owned object and is documented as VALID in the ETRM metadata for 12.1.1 and 12.2.2.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, ASO_PVT_SHIPMENTS_V is defined over the following referenced base objects:

• ASO_SHIPMENTS (SYNONYM) — the primary shipment record source, providing all SHIP.* columns.
• HZ_CUST_ACCOUNTS (SYNONYM) — customer account information for the ship-to account.
• HZ_PARTIES (SYNONYM) — party name, party type, and party identifier details.
• HZ_PARTY_SITES (SYNONYM) — the ship-to party site linkage.
• HZ_LOCATIONS (SYNONYM) — address components such as ADDRESS1–ADDRESS4, CITY, STATE, PROVINCE, COUNTY, POSTAL_CODE and COUNTRY.
• HZ_RELATIONSHIPS (SYNONYM) — used to resolve party relationships referenced as I_PARTY_REL.
• FND_TERRITORIES_VL (VIEW) — provides the territory short name (SHIP_TO_COUNTRY) from the country code.

The view therefore acts as a denormalized join between ASO shipment data and TCA/HZ master data, allowing shipment rows to be reported with resolved customer and address context without the caller having to reconstruct those joins manually.

Key Columns

The view exposes the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) plus concurrent program context columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE). Quote linkage is provided by QUOTE_HEADER_ID and QUOTE_LINE_ID. Scheduling columns include PROMISE_DATE, REQUEST_DATE and SCHEDULE_SHIP_DATE. Shipping attributes include SHIP_TO_PARTY_ID, SHIP_TO_PARTY_SITE_ID, SHIP_PARTIAL_FLAG, SHIP_SET_ID, SHIP_METHOD_CODE, FREIGHT_TERMS_CODE, FREIGHT_CARRIER_CODE, FOB_CODE, SHIPPING_INSTRUCTIONS, PACKING_INSTRUCTIONS, SHIPMENT_PRIORITY_CODE and SHIP_QUOTE_PRICE. Quantity-related columns are QUANTITY, RESERVED_QUANTITY and RESERVATION_ID, with ORDER_LINE_ID linking to the fulfillment order line. Address and customer columns include SHIP_TO_ADDRESS1–4, SHIP_TO_CITY, SHIP_TO_STATE, SHIP_TO_PROVINCE, SHIP_TO_COUNTY, SHIP_TO_POSTAL_CODE, SHIP_TO_COUNTRY_CODE, SHIP_TO_COUNTRY, CUSTOMER_NAME and CUSTOMER_TYPE. The ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 columns provide DFF extensibility.

Common Use Cases and Queries

Typical usage is reporting shipments associated with a given quote, or listing quote shipments with resolved ship-to details. A representative query is:

• SELECT quote_header_id, quote_line_id, ship_to_party_id, ship_to_city, ship_to_country, quantity, reserved_quantity, promise_date, schedule_ship_date FROM aso_pvt_shipments_v WHERE quote_header_id = :p_quote_header_id;
• SELECT s.quote_line_id, s.ship_to_party_site_id, s.customer_name, s.ship_method_code, s.quantity FROM aso_pvt_shipments_v s WHERE s.quote_header_id = :p_quote_header_id ORDER BY s.quote_line_id;

These queries support quote-to-shipment traceability, shipping destination verification, and integration extracts where downstream systems need quote shipment context. Because the object is a view, it is read-only; DML must be performed against the underlying ASO shipment tables.