Results for “to_postal_code”

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

Overview

WSH_BOLS_RD_V is an APPS-owned reporting view within the Oracle E-Business Suite Shipping Execution (WSH) module. The name follows the WSH convention for Bill of Lading (BOL) reporting views, with the "RD" suffix indicating its use in a reporting/document context. The view consolidates data required to produce and reproduce Bill of Lading documentation — the legal transport document issued by a shipper to a carrier. Its scope spans shipment details, trip and stop information, carrier references, port-of-loading and port-of-discharge data, weight and volume attributes, and document instance/print status. Because it joins delivery, trip, stop, location, and document-instance data, it serves as a denormalized reporting surface for both printed BOL output and downstream integration queries. Users searching on stop_location_id are typically navigating this view to resolve the origin/destination stop locations associated with a trip, which are exposed here through the WSH_TRIP_STOPS aliases WTS1 and WTS2.

Underlying Base Objects

The view is defined over the following documented base objects:

• WSH_DOCUMENT_INSTANCES (synonym) — supplies the ROWID, SEQUENCE_NUMBER, DOCUMENT_INSTANCE_ID, DOCUMENT_TYPE, STATUS, FINAL_PRINT_DATE, ENTITY_NAME, ENTITY_ID, and DOC_SEQUENCE_CATEGORY_ID columns referenced as WDI.
• WSH_DELIVERY_LEGS (synonym) — aliased WDL, contributes booking number, service contract, carrier/shipper export references, ports, signing and date fields, POD data, weight, volume, and loading order/tender status.
• WSH_NEW_DELIVERIES (synonym) — aliased WND, provides problem contact, description, waybill, additional shipment info, FOB and dock codes, delivery ID, name, reason of transport, and COD attributes.
• WSH_TRIPS (synonym), WSH_TRIP_STOPS (synonym) — aliased WT, WTS1, and WTS2, providing ship method, vehicle number, carrier, trip ID, trip name, and the two STOP_LOCATION_ID references.
• WSH_LOCATIONS (synonym) — aliased WSLOC1 and WSLOC2, contributing location code, city, address lines, province/state/county, postal code, and country.
• HR_ORGANIZATION_UNITS and HR_GENERAL, HR_SECURITY — provide organization name and enforce organization-level security filtering.
• HZ_CUST_ACCOUNTS, HZ_PARTIES, PO_VENDORS — supply party/vendor context.

Key Columns

• STOP_LOCATION_ID — appears twice (WTS1, WTS2), identifying the origin and destination trip stops.
• DOCUMENT_INSTANCE_ID / SEQUENCE_NUMBER / DOCUMENT_TYPE / STATUS — identify the BOL document instance, its print status, and final print date.
• BOOKING_NUMBER, SERVICE_CONTRACT, CARRIER_EXPORT_REF, SHIPPER_EXPORT_REF — commercial transport references.
• PORT_OF_LOADING, PORT_OF_DISCHARGE — routing information.
• SHIPPER_SIGNED_BY, CARRIER_SIGNED_BY, POD_BY, POD_FLAG — signature and proof-of-delivery evidence.
• GROSS_WEIGHT, NET_WEIGHT, WEIGHT_UOM_CODE, VOLUME, VOLUME_UOM_CODE — shipment measurement attributes.
• DELIVERY_ID, DELIVERY_LEG_ID, TRIP_ID, CARRIER_ID, SHIP_METHOD_CODE — linking keys to delivery, trip, and carrier entities.

Common Use Cases and Queries

Typical uses include reproducing printed BOL content, auditing carrier and POD data, and integrating shipment stop information into external systems. A query resolving stop locations for a trip might select the trip ID, trip name, and both stop location identifiers:

• SELECT TRIP_ID, NAME, STOP_LOCATION_ID FROM WSH_BOLS_RD_V WHERE TRIP_ID = :trip_id;
• SELECT DOCUMENT_INSTANCE_ID, STATUS, FINAL_PRINT_DATE FROM WSH_BOLS_RD_V WHERE DOCUMENT_TYPE = 'BOL';
• SELECT DELIVERY_ID, CARRIER_ID, SHIP_METHOD_CODE, GROSS_WEIGHT FROM WSH_BOLS_RD_V WHERE DELIVERY_LEG_ID = :leg_id;

Because the view integrates organization-security packages, queries execute within the caller's organization context, and results reflect only organizations the user is authorized to access.