Results for “ship_to_country_code”

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

Overview

ASO_SHIPMENTS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the ASO (Order Capture) product family. In release 12.1.1 and 12.2.2 the object is documented as VALID and is defined over the ASO shipping and party-site data model. It presents shipment-level detail for quote and order lines — promise dates, scheduling dates, ship-to party and address attributes, shipping method and freight attributes, quantities, reservation information, and descriptive flexfield columns — in a denormalized form that is convenient for inquiry, reporting, and interface extraction.

Because the view resolves the raw foreign-key identifiers of the shipment record into human-readable party names and address elements, it is frequently used where a report or external interface must display ship-to information without performing additional joins against the party and location tables. The view is read-only by design; it does not carry DML semantics, and any maintenance of shipment data occurs against the underlying base table through the supporting PL/SQL package.

Underlying Base Objects

The documented base objects for ASO_SHIPMENTS_V are:

• ASO_SHIPMENTS (exposed through a synonym) — the principal shipment record, supplying shipment identifiers, dates, flags, shipping attributes, quantities, reservation data, and the DFF attribute columns.
• ASO_I_PARTIES_V (VIEW) — supplies the ship-to party name and contact name components.
• ASO_I_PARTY_SITES_V (VIEW) — supplies the ship-to address elements joined through the ship-to party site identifier.
• ASO_I_COUNTRIES_V (VIEW) — supplies country-related reference values used in resolving the ship-to address.
• ASO_SHIPMENT_PVT (PACKAGE) — the shipment maintenance package associated with the underlying data; it is documented as a referenced base object and is the programmatic entry point for shipment manipulation rather than the view itself.

The join structure links the shipment row to its party site, party, and customer account through the ship-to identifiers, so that each output row represents one shipment with its resolved ship-to context.

Key Columns

• SHIPMENT_ID, QUOTE_HEADER_ID, QUOTE_LINE_ID, ORDER_LINE_ID — identifiers linking the shipment to its quote and order line context.
• PROMISE_DATE, REQUEST_DATE, SCHEDULE_SHIP_DATE — the scheduling and commitment dates used in fulfillment reporting.
• SHIP_TO_PARTY_ID, SHIP_TO_PARTY_SITE_ID, SHIP_TO_CUST_ACCOUNT_ID — the ship-to party, site, and account keys.
• SHIP_TO_PARTY_NAME, SHIP_TO_CONTACT_FIRST_NAME, SHIP_TO_CONTACT_MIDDLE_NAME, SHIP_TO_CONTACT_LAST_NAME — resolved party and contact names.
• SHIP_TO_ADDRESS1..4, SHIP_TO_CITY, SHIP_TO_STATE, SHIP_TO_PROVINCE, SHIP_TO_COUNTY, SHIP_TO_POSTAL_CODE, SHIP_TO_COUNTRY, SHIP_TO_COUNTRY_CODE — resolved ship-to address elements.
• SHIP_PARTIAL_FLAG — the flag indicating whether partial shipment of the line is permitted; this is the column most commonly sought when users search for "ship_partial_flag".
• SHIP_SET_ID, SHIP_METHOD_CODE, FREIGHT_TERMS_CODE, FREIGHT_CARRIER_CODE, FOB_CODE, SHIPMENT_PRIORITY_CODE — shipping setup and preference attributes.
• SHIPPING_INSTRUCTIONS, PACKING_INSTRUCTIONS — free-text fulfillment instructions.
• QUANTITY, RESERVED_QUANTITY, RESERVATION_ID — ordered, reserved, and reservation reference data.
• SHIP_FROM_ORG_ID — the shipping organization.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1..15 — descriptive flexfield columns carried through from the shipment record.
• WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) — audit and concurrent program context.

Common Use Cases and Queries

Typical usages include quote and order shipment inquiries, fulfillment reports that must display resolved ship-to addresses, and interface extracts that need promise and schedule dates together with the partial-shipment flag. The most frequent ad hoc request is for shipments where partial shipping is allowed or disallowed.

SELECT shipment_id, quote_header_id, quote_line_id,
       ship_partial_flag, schedule_ship_date, promise_date,
       ship_to_party_name, ship_to_city, quantity
FROM   aso_shipments_v
WHERE  ship_partial_flag = 'Y';

The same view supports address-oriented reporting, for example listing shipments by ship-to city and country while retaining shipping method and carrier, and it supports extract patterns filtered on the ship-from organization or on the quote header identifier. Because the view resolves party and address attributes inline, these queries avoid the extra joins that would otherwise be required against ASO_I_PARTIES_V, ASO_I_PARTY_SITES_V, and ASO_I_COUNTRIES_V.