Search Results ship_from_edi_location_code1

Overview

APPS.CLN_WSH_SS_SHIPMENT_V is a view owned by the APPS schema and validated in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the CLN product family, the Supply Chain Trading Connector for RosettaNet, and its documented purpose is to expose delivery header details. The view flattens and names shipment-level attributes drawn from the shipping execution tables so that outbound RosettaNet messages, such as shipment notification and ship-from-location driven documents, can be generated from a single, denormalized row per delivery.

Its primary integration role is to supply the trading-partner-facing identifiers and address information required by RosettaNet PIP messages. The presence of columns such as SHIP_FROM_EDI_LOCATION_CODE1, SHIP_FROM_EDI_LOCATION_CODE2, SHIP_TO_EDI_LOCATION_CODE1, and SHIP_TO_EDI_LOCATION_CODE2 confirms the view is intended for EDI-enabled location exchange rather than purely internal reporting. A SELECT DISTINCT clause is applied in the view text, so duplicate rows arising from the multi-table joins are collapsed before results are returned to the calling connector logic.

Underlying Base Objects

The documented object metadata lists the referenced base objects for the 12.2.2 definition: the packages HR_GENERAL, HR_SECURITY, and WSH_UTIL_CORE; the synonyms HR_LOCATIONS_ALL, HR_LOCATIONS_ALL_TL, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTY_SITES, WSH_LOCATIONS, WSH_NEW_DELIVERIES, and WSH_TRANSACTIONS_HISTORY; and the views ORG_ORGANIZATION_DEFINITIONS and WSH_CARRIERS_V.

The view text joins WSH_NEW_DELIVERIES (aliased WND) as the delivery header driver, WSH_TRANSACTIONS_HISTORY (aliased WTH) for document context, and HR location tables (aliased HRLA, HRCS) for ship-from and ship-to addresses. Carrier, organization, and customer site data are resolved through WSH_CARRIERS_V, ORG_ORGANIZATION_DEFINITIONS, and the HZ party site tables. The inclusion of HR_SECURITY indicates the view participates in HR location security filtering.

Key Columns

• DELIVERY_ID — the delivery header identifier from WSH_NEW_DELIVERIES.
• ACTION_CODE (ACTION_TYPE) and DOCUMENT_NUMBER / DOCUMENT_CREATION_DATE / DOCUMENT_TYPE — transaction history context for the shipment document.
• SHIP_FROM_LOCATION — the LOCATION_CODE of the ship-from HR location; this is the column most directly relevant to searches for ship_from_location.
• SHIP_TO_LOCATION, SHIP_TO_EDI_LOCATION_CODE1, SHIP_TO_EDI_LOCATION_CODE2 — the corresponding destination identifiers.
• Ship-from address attributes: SHIP_FROM_ADDRESS1, SHIP_FROM_ADDRESS2, SHIP_FROM_ADDRESS3, SHIP_FROM_CITY, SHIP_FROM_POSTAL_CODE, SHIP_FROM_REGION, SHIP_FROM_COUNTRY_CODE, SHIP_FROM_EDI_LOCATION_CODE1, SHIP_FROM_EDI_LOCATION_CODE2.
• Logistics attributes: SHIP_METHOD, CARRIER, SERVICE_LEVEL, TRANSPORTATION_METHOD, FREIGHT_TERMS, FOB_CODE.
• Measurement attributes: GROSS_WEIGHT, NET_WEIGHT, WEIGHT_UOM_CODE, VOLUME, VOLUME_UOM_CODE, NUMBER_OF_LPN.
• Scheduling attributes: INITIAL_PICKUP_DATE, ULTIMATE_DROPOFF_DATE, LOADING_SEQUENCE.
• ORGANIZATION_CODE / ORGANIZATION_NAME — the shipping organization from ORG_ORGANIZATION_DEFINITIONS.
• WAYBILL — conditionally returned as the delivery waybill when DOCUMENT_TYPE equals 'SA'.

Common Use Cases and Queries

Typical usage is to retrieve a complete delivery header for a given delivery or document, or to drive RosettaNet shipment notifications between trading partners.

• Retrieve ship-from and ship-to details for one delivery:
  SELECT delivery_id, ship_from_location, ship_to_location, carrier, waybill FROM apps.cln_wsh_ss_shipment_v WHERE delivery_id = :p_delivery_id;
• Locate deliveries originating from a specific ship-from location:
  SELECT delivery_id, document_number, ship_from_location, ship_from_edi_location_code1 FROM apps.cln_wsh_ss_shipment_v WHERE ship_from_location = :p_location_code;
• Extract EDI-ready addresses for outbound messaging:
  SELECT delivery_id, ship_from_edi_location_code1, ship_to_edi_location_code1, ship_from_city, ship_to_city FROM apps.cln_wsh_ss_shipment_v WHERE action_code = 'SHIP';
• Report on shipment weight and volume by organization:
  SELECT organization_code, delivery_id, gross_weight, volume, weight_uom_code, volume_uom_code FROM apps.cln_wsh_ss_shipment_v ORDER BY organization_code, delivery_id;

Because the view joins HR-secured location data and applies DISTINCT, queries should be filtered and indexed on DELIVERY_ID wherever possible to maintain acceptable performance.