Results for “ship_method_code_from”

50+ results




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

Overview

ASO_SHIPMENTS is a core Order Capture (ASO) table within Oracle E-Business Suite 12.1.1 and 12.2.2 that stores shipping information for a quote, functioning at either the header level or the line level. Because many quotes contain multiple lines shipped to different destinations, Oracle models shipping data as a flexible, multi-row structure tied to ASO_QUOTE_HEADERS_ALL and ASO_QUOTE_LINES_ALL. A row may exist for an entire quote header, for a single quote line, or for both, with context driven by the presence or absence of QUOTE_HEADER_ID and QUOTE_LINE_ID.

From a Data Vault modeling perspective, the mined foreign-key structure is hub-leaning: ASO_SHIPMENTS acts primarily as a business hub on its own natural key (SHIPMENT_ID) rather than a pure transactional link. The table holds both descriptive shipping attributes and derived or computed references, and it is heavily referenced by downstream tax, freight, pricing, billing, and demand-planning objects.

Key Information Stored

The table contains 61 documented columns. The most operationally significant are listed below.

Common Use Cases and Queries

ASO_SHIPMENTS is queried when resolving shipping detail for a quote, driving freight and tax calculation, and validating the shipment referenced by downstream tax lines. Because the user search term jai_crm_quote_taxes maps to JAI_CRM_QUOTE_TAXES.SHIPMENT_ID referencing ASO_SHIPMENTS, the most relevant pattern joins the two:

  • Tax reporting by shipment: SELECT t.* FROM jai_crm_quote_taxes t, aso_shipments s WHERE t.shipment_id = s.shipment_id AND s.quote_header_id = :header_id;
  • Header-level vs. line-level identification: filter QUOTE_LINE_ID IS NULL for header shipments, or QUOTE_LINE_ID IS NOT NULL for line shipments.
  • Freight and pricing reconciliation: join ASO_FREIGHT_CHARGES, ASO_PRICE_ADJUSTMENTS, and ASO_PAYMENTS on QUOTE_SHIPMENT_ID = SHIPMENT_ID.
  • Ship-to analysis: join HZ_PARTIES and HZ_PARTY_SITES on SHIP_TO_PARTY_ID and SHIP_TO_PARTY_SITE_ID.
  • Inventory reservation tracing: join MTL_RESERVATIONS on RESERVATION_ID.

Typical reporting uses include shipment schedule variance (PROMISE_DATE versus SCHEDULE_SHIP_DATE), freight cost summaries by carrier and terms, and audit of shipping attributes on converted or amended quotes.

Related Objects

The following objects are the most significant dependencies based on the documented FK relationships.

  • ASO_QUOTE_HEADERS_ALL and ASO_QUOTE_LINES_ALL — parent quote objects, joined on QUOTE_HEADER_ID and QUOTE_LINE_ID.
  • JAI_CRM_QUOTE_TAXES — the tax detail object referenced by the search term, joined via SHIPMENT_ID = QUOTE_SHIPMENT_ID.
  • ASO_TAX_DETAILS — tax lines tied to a shipment via QUOTE_SHIPMENT_ID.
  • ASO_FREIGHT_CHARGES, ASO_PAYMENTS, and ASO_PRICE_ADJUSTMENTS — pricing and payment children on QUOTE_SHIPMENT_ID.
  • ASO_QUOTE_PARTIES and ASO_QUOTE_LINE_ATTRIBS_EXT — additional quote context keyed by QUOTE_SHIPMENT_ID.
  • RA_CUSTOMER_TRX_ALL and ASO_BI_QUOTE_LINES_ALL — receivables and BI staging consumers of SHIPMENT_ID.
  • HZ_PARTIES, HZ_PARTY_SITES, MTL_RESERVATIONS, and FND_SECURITY_GROUPS — reference parents for parties, sites, reservations, and security.

Of these, JAI_CRM_QUOTE_TAXES, ASO_TAX_DETAILS, and ASO_FREIGHT_CHARGES are the objects most frequently co-queried with ASO_SHIPMENTS in tax and freight analysis.