Search Results dates_negative_tolerance

Overview

The APPS.WMS_SHIP_TO_SITES_V view is a Warehouse Management (WMS) reporting and integration object that exposes customer ship-to site information in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a denormalized, read-only projection of ship-to site usage records joined to their parent party site and location address details, allowing downstream processes, concurrent programs, and custom reports to retrieve ship-to characteristics without reconstructing the multi-table Oracle Receivables and Trading Community Architecture (TCA) relationship model.

The view is owned by the APPS schema and is documented as VALID in the ETRM metadata. Its principal role is to consolidate the shipping-relevant attributes of a customer site — ship-to usage, shipping method, freight terms, FOB point, partial shipment allowance, warehouse association, and address — into a single queryable interface. Because the view surfaces the SHIPPING_METHOD_CODE column (aliased from SITE.SHIP_VIA), it directly answers the common reporting question of "what shipping method is assigned to a given ship-to site."

Underlying Base Objects

The view is defined over four documented base objects, all accessed through synonyms in the APPS schema:

• HZ_CUST_SITE_USES_ALL — the primary driving table, aliased as SITE; filtered to records where SITE_USE_CODE = 'SHIP_TO'.
• HZ_CUST_ACCT_SITES_ALL — aliased as ACCT_SITE; provides the customer account identifier and account-site status.
• HZ_PARTY_SITES — aliased as PARTY_SITE; links the account site to its physical party site.
• HZ_LOCATIONS — aliased as LOC; supplies the address components (ADDRESS1–ADDRESS4, CITY, STATE, POSTAL_CODE, COUNTRY).

The join path is: HZ_CUST_SITE_USES_ALL.CUST_ACCT_SITE_ID = HZ_CUST_ACCT_SITES_ALL.CUST_ACCT_SITE_ID, then HZ_CUST_ACCT_SITES_ALL.PARTY_SITE_ID = HZ_PARTY_SITES.PARTY_SITE_ID, then HZ_PARTY_SITES.LOCATION_ID = HZ_LOCATIONS.LOCATION_ID. The join also enforces an ORG_ID compatibility condition (NVL(SITE.ORG_ID,-99) = NVL(ACCT_SITE.ORG_ID,-99)), preserving operating-unit isolation and ensuring sites without an ORG_ID are matched consistently across both tables.

Key Columns

• SITE_USE_ID — primary identifier of the ship-to site use.
• SHIPPING_METHOD_CODE — aliased from SITE.SHIP_VIA; the carrier or shipping method assigned to the site. This is the column most frequently searched by users.
• FREIGHT_TERMS_CODE and FOB_POINT_CODE — commercial shipping terms (aliased from FREIGHT_TERM and FOB_POINT).
• SHIP_PARTIAL_ALLOWED — whether partial shipments are permitted (from SHIP_PARTIAL).
• SOLD_FROM_ORG_ID / SHIP_FROM_ORG_ID — both derived from SITE.WAREHOUSE_ID; identify the warehouse associated with the site.
• CUSTOMER_ID, PRICE_LIST_ID, PAYMENT_TERM_ID — account-level commercial defaults.
• ADDRESS_LINE_1 through ADDRESS_LINE_4, TOWN_OR_CITY, STATE, POSTAL_CODE, COUNTRY — the physical ship-to address.
• ADDRESS_LINE_5 — a concatenation of city, state, and postal code for display convenience.
• STATUS, PRIMARY_FLAG, DEMAND_CLASS_CODE, and shipment tolerance columns (OVER_SHIPMENT_TOLERANCE, UNDER_SHIPMENT_TOLERANCE, etc.) — operational attributes used in order and shipping validation.

Common Use Cases and Queries

Typical scenarios include shipping setup reports, order-entry validations, and integration extracts that must resolve the shipping method for a customer destination. A sample query listing ship-to sites by shipping method:

• SELECT site_use_id, customer_id, shipping_method_code, freight_terms_code, town_or_city, state, country FROM apps.wms_ship_to_sites_v WHERE shipping_method_code = :p_method ORDER BY customer_id;

A second common pattern joins the view to order or delivery data to compare the site's configured SHIPPING_METHOD_CODE against the method actually used on the transaction, supporting audit and exception reporting. Because the view filters to SHIP_TO usage only and enforces ORG_ID alignment, it is safe to use directly in reports without additional site-use filtering.