Search Results freight_term




Overview
Explore in AI Chat

Overview

APPS.OE_AK_SOLD_TO_SITE_USES_V is a reporting view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that exposes the "SOLD_TO" usage context of customer site records held in the Trading Community Architecture (TCA) model. Physically, the view is a filtered projection of the HZ_CUST_SITE_USES table, restricted to rows where the SITE_USE_CODE column equals 'SOLD_TO'. This restriction aligns the view with the Order Management / Advanced Pricing "AK" (Attribute / Knowledge) layer, which supplies key flexfield and descriptive attributes used to drive pricing, order entry defaults, and freight and shipping determinations.

In practical terms, the view provides a single, curated row per SOLD_TO site use, combining commercial attributes such as price list, freight term, ship via, payment terms, salesperson, order type and shipment tolerances. Because these values are commonly referenced by name in reporting contexts — for example when a user searches on "freight_term" — this view is a frequent entry point for queries that need sold-to-level commercial defaults without exposing the full, multi-purpose HZ_CUST_SITE_USES table. It is documented under ETRM metadata for 12.2.2 with owner APPS and a single referenced base object, the synonym HZ_CUST_SITE_USES.

Underlying Base Objects

The only documented base object referenced by this view is HZ_CUST_SITE_USES (accessed via a synonym). HZ_CUST_SITE_USES is the child of HZ_CUST_ACCT_SITES_ALL and stores the various use types that a customer site may serve — for example SOLD_TO, SHIP_TO, BILL_TO, and others — distinguished by SITE_USE_CODE. The view does not join to additional tables; it simply selects a fixed list of columns from that base table and applies the SITE_USE_CODE = 'SOLD_TO' predicate.

Because the underlying storage is TCA-based, any query against the view inherits TCA semantics: a SOLD_TO site use is associated with an account site (via SITE_USE_ID and the parent custody chain) and may be designated as primary. Changes made through customer maintenance or through the Order Management customer screens are reflected immediately in the view, as no materialization or aggregation occurs.

Key Columns

  • SITE_USE_ID — The unique identifier of the sold-to site use record; the primary join key to TCA site use data.
  • PRICE_LIST_ID — The default price list applied to orders for this sold-to customer site.
  • FOB_POINT — The free-on-board point governing transfer of title and risk for shipments, directly relevant to freight and delivery terms.
  • FREIGHT_TERM — The freight/carrier term code (e.g., prepaid, collect) used to derive shipping charges and responsibilities on the order.
  • SHIP_VIA — The default shipping method or carrier for the sold-to customer.
  • CONTACT_ID — The primary contact associated with the sold-to site use.
  • PAYMENT_TERM_ID — The default payment terms for the customer site.
  • PRIMARY_SALESREP_ID — The salesperson normally credited for orders placed against this site.
  • ORDER_TYPE_ID — The default order type for transactions originating from this sold-to site.
  • OVER_SHIPMENT_TOLERANCE / UNDER_SHIPMENT_TOLERANCE — The percentages by which shipments may exceed or fall short of the ordered quantity.

Common Use Cases and Queries

The view is typically used to retrieve and validate the commercial defaults — freight terms, FOB point, ship via, price list, and payment terms — that Order Management and Advanced Pricing apply when a sold-to customer is selected. A frequent reporting scenario is verifying that a specific customer site carries the expected freight term before order entry or during data-cleansing exercises.

  • Identify sold-to sites with a particular freight term for audit or setup review.
  • Report the price list, payment terms, and salesperson assignments across sold-to sites.
  • Join to HZ_CUST_SITE_USES and HZ_CUST_ACCT_SITES_ALL to resolve the customer name and account for a given SITE_USE_ID.

Sample query:

SELECT site_use_id,
       price_list_id,
       fob_point,
       freight_term,
       ship_via,
       payment_term_id,
       primary_salesrep_id,
       order_type_id
FROM   apps.oe_ak_sold_to_site_uses_v
WHERE  freight_term = :p_freight_term;

Because the view contains no joins and no aggregation, it performs efficiently as a lookup source and can be safely embedded in larger queries that join SITE_USE_ID back to the TCA customer model.