Results for “over_shipment_tolerance”

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

Overview

The OE_AK_SOLD_TO_SITE_USES_V view is an Order Management (ONT) dictionary object owned by the APPS schema. It exposes a curated set of defaultable order-entry attributes that are maintained at the customer location level, specifically for locations whose site use is classified as SOLD_TO. The view functions as a lightweight lookup layer used by Oracle Order Management's defaulting framework to retrieve values such as price list, FOB point, freight terms, shipping method, payment terms, and sales representative when a sold-to customer and site are selected on an order.

The name follows the OE_AK convention, where "AK" reflects an attribute or key style helper view. Because the underlying site-use records store foreign-key identifiers rather than human-readable codes, the view presents those identifiers directly; descriptive code columns are surfaced in the documented column list through naming such as FOB_POINT_CODE. In a reporting or integration context, the view is useful for extracting the defaulted commercial terms associated with a specific sold-to site without navigating the full HZ_CUST_SITE_USES structure.

Underlying Base Objects

The view is defined exclusively over the HZ_CUST_SITE_USES synonym, which resolves to the APPS.HZ_CUST_SITE_USES customer site-use table in the Oracle Trading Community Architecture (TCA) model. No other base tables are referenced in the documented definition. The relationship is one-to-one at the row level: each qualifying row in HZ_CUST_SITE_USES whose SITE_USE_CODE equals 'SOLD_TO' produces one row in the view.

Filtering by the SOLD_TO site-use code is the defining characteristic of the view. Although the base table contains multiple site-use codes such as SHIP_TO, BILL_TO, and others, this view restricts its result set to sold-to sites, which are the party-side locations used during order header entry. Because it is a simple single-table projection with a WHERE predicate, the view is inherently read-only and non-updatable.

Key Columns

• SOLD_TO_SITE_USE_ID — The site-use identifier; the effective primary key for a sold-to location and the join key back to customer and site data.
• PRICE_LIST_ID — Foreign key to the price list defaulted for the customer site.
• FOB_POINT_CODE — FOB point code assigned to the site; relevant to the searched term "fob_point" and to shipping/terms defaulting.
• FREIGHT_TERMS_CODE — Freight terms code defaulted for the location.
• SHIPPING_METHOD_CODE — Default shipping method for the site.
• CONTACT_ID — Default contact associated with the sold-to site.
• PAYMENT_TERM_ID — Payment terms identifier defaulted at order entry.
• SALESREP_ID / PRIMARY_SALESREP_ID — Sales representative defaulted for the site.
• ORDER_TYPE_ID — Default order type identifier.
• OVER_SHIPMENT_TOLERANCE and UNDER_SHIPMENT_TOLERANCE — Permitted over- and under-shipment percentages.

Common Use Cases and Queries

The primary use case is retrieving default commercial and shipping attributes for a sold-to site, including FOB point, to validate or reproduce Order Management defaulting logic. The following query returns all defaultable attributes for a given site-use identifier:

• SELECT sold_to_site_use_id, price_list_id, fob_point_code, freight_terms_code, shipping_method_code, payment_term_id, order_type_id FROM oe_ak_sold_to_site_uses_v WHERE sold_to_site_use_id = :p_site_use_id;

To inspect FOB point and freight terms across many sold-to locations, the view can be joined to customer and site tables on SOLD_TO_SITE_USE_ID and filtered accordingly. Tolerance columns support auditing of order-level shipment tolerance defaults. Because the view is a read-only projection over HZ_CUST_SITE_USES, it is suitable for reporting and extraction rather than data maintenance.