Search Results wsh_carriers_u1

Overview

WSH.WSH_CARRIERS is the master reference table for shipping carriers within the Oracle E-Business Suite Order-to-Cash and Logistics foundation. It stores the definition, identity, manifesting behavior, financial linkage, and transportation constraint attributes for every carrier record that WSH shipping execution, freight rating, freight auditing, and pick-up/drop-off planning processes can reference. The table resides in the APPS_TS_TX_DATA tablespace with a 10% PCTFREE, and is marked VALID in the ETRM 12.2.2 documented schema, carrying 70 columns.

Like all standard Oracle Applications tables, direct DML is unsupported; the documented metadata carries the oracle internal use warning, and rows are maintained through the standard WSH Carrier windows and public APIs. From a Data Vault modeling perspective, the heuristic classification of this object is satellite-leaning, meaning the identity and structural relationships (the carrier key itself) conceptually belong to a hub, while the descriptive attributes — flags, limits, UOM defaults, and dimensional factors — behave like satellite attributes. This is a suggestion only; the physical table is a conventional denormalized master record.

Key Information Stored

The surrogate primary key is CARRIER_ID, which is also enforced by the unique index WSH_CARRIERS_U1 and is documented as a foreign key into HZ_PARTIES. The principal business-key candidate is FREIGHT_CODE, enforced by the unique index WSH_CARRIERS_U2 — this is the index referenced by the search term wsh_carriers_u2. The most significant documented columns include:

• CARRIER_ID — surrogate primary key, joining to HZ_PARTIES for carrier party identity.
• FREIGHT_CODE — unique business key identifying the carrier for freight and rating purposes.
• SCAC_CODE — Standard Carrier Alpha Code used in transportation and EDI contexts.
• SUPPLIER_ID / SUPPLIER_SITE_ID — foreign keys to PO_VENDORS and PO_VENDOR_SITES, linking the carrier to its payee supplier and site; the pair is indexed by WSH_CARRIERS_N1.
• GENERIC_FLAG — denotes a generic carrier record.
• MANIFESTING_ENABLED_FLAG — controls whether manifesting is permitted for the carrier.
• FREIGHT_BILL_AUTO_APPROVAL and FREIGHT_AUDIT_LINE_LEVEL — govern freight bill auto-approval and audit granularity.
• CURRENCY_CODE — default currency for carrier financial transactions.
• Constraint columns such as MAX_NUM_STOPS_PERMITTED, MAX_TOTAL_DISTANCE, MAX_TOTAL_TIME, MIN_LAYOVER_TIME, and the continuous-move limits (MAX_CM_DISTANCE, MAX_CM_TIME).
• UOM and dimensional defaults: TIME_UOM, DISTANCE_UOM, WEIGHT_UOM, VOLUME_UOM, DIM_DIMENSIONAL_FACTOR, and related DIM attributes.

Common Use Cases and Queries

Shipping execution relies on this table to resolve the carrier for a delivery, drive manifesting eligibility, and enforce transportation limits during load planning. Freight rating and auditing reference the supplier linkage and auto-approval flags. Reporting commonly resolves the carrier business key and its party description.

• Look up a carrier by its unique freight code: SELECT * FROM wsh_carriers WHERE freight_code = :p_code;
• Resolve the carrier party identity: SELECT c.carrier_id, c.freight_code, p.party_name FROM wsh_carriers c, hz_parties p WHERE c.carrier_id = p.party_id;
• Find carriers payable to a supplier: SELECT carrier_id, freight_code FROM wsh_carriers WHERE supplier_id = :vendor_id;
• Identify carriers eligible for manifesting or with auto-approval enabled.
• Validate transportation constraints (stops, distance, time) before building truck loads.

Related Objects

The following objects are the most significant dependents or references for WSH_CARRIERS:

• HZ_PARTIES — joined on WSH_CARRIERS.CARRIER_ID = HZ_PARTIES.PARTY_ID (documented FK).
• PO_VENDORS — joined on WSH_CARRIERS.SUPPLIER_ID = PO_VENDORS.VENDOR_ID.
• PO_VENDOR_SITES — joined on WSH_CARRIERS.SUPPLIER_SITE_ID = PO_VENDOR_SITES.VENDOR_SITE_ID.
• Shipping execution tables such as WSH_DELIVERIES and WSH_TRIPS that resolve carrier identity for a shipment or trip.
• Freight and manifesting tables that reference the carrier’s freight code and manifesting flag.
• Carrier-related public APIs and windows in the WSH module used to create and maintain carrier records.