Search Results scac_code

Overview

WSH_CARRIERS_V is a Shipping Execution (WSH) view owned by the APPS schema. It presents a reporting-oriented projection of carrier (freight carrier) master data by joining the WSH_CARRIERS base table to HZ_PARTIES, the Trading Community Architecture (TCA) party registry. Its principal role is to expose carrier configuration—covering manifesting flags, fuel and freight codes, currency, transportation limits, and rating attributes—alongside the party name and party status, so that shipping users and integrations can retrieve both the operational and the descriptive identity of a carrier through a single object.

Because the view is documented as VALID and resides in the APPS schema, it is generally consumed read-only. It is commonly referenced during carrier setup validation, freight rating analysis, manifesting and compliance reporting, and by outbound interfaces that must supply carrier party details to external transportation management systems.

Underlying Base Objects

Per the ETRM metadata for 12.2.2, the view is defined over WSH_CARRIERS (WSH schema, referenced as a synonym) and HZ_PARTIES (AR/HZ, referenced as a synonym), with HZ_PARTY_USG_ASSIGNMENTS listed among referenced objects. The view text confirms the core join: WHERE WC.CARRIER_ID = HP.PARTY_ID, linking each carrier row in WSH_CARRIERS to its corresponding party in HZ_PARTIES. Carrier identity, therefore, is the party record; the carrier-specific operational columns are stored on WSH_CARRIERS and keyed to that party.

HZ_PARTY_USG_ASSIGNMENTS supports party usage classification, generally used to determine whether a party is enabled for a given business purpose such as carrier or supplier usage.

Key Columns

The view exposes a broad set of carrier attributes. Significant columns include:

• ROW_ID / CARRIER_ID: ROW_ID derives from WSH_CARRIERS.ROWID, and CARRIER_ID corresponds to the party identifier (PARTY_ID) — the primary join key between the carrier and its party record.
• CARRIER_NAME / CARRIER_ID: Descriptive identity sourced from HZ_PARTIES (PARTY_NAME aliased as CARRIER_NAME).
• SCAC_CODE and FREIGHT_CODE: Standard Carrier Alpha Code and carrier freight classification identifiers.
• MANIFESTING_ENABLED_FLAG, FREIGHT_BILL_AUTO_APPROVAL, FREIGHT_AUDIT_LINE_LEVEL: Flags and settings governing manifesting and freight bill audit behavior.
• CURRENCY_CODE, WEIGHT_UOM, VOLUME_UOM, TIME_UOM, DIMENSION_UOM, DISTANCE_UOM: Units of measure and currency driving rating and routing calculations.
• Capacity and transportation limits: MAX_NUM_STOPS_PERMITTED, MAX_TOTAL_DISTANCE, MAX_TOTAL_TIME, MAX_LAYOVER_TIME, MIN_LAYOVER_TIME, MAX_TOTAL_DISTANCE_IN_24HR, MAX_DRIVING_TIME_IN_24HR, and MAX_DUTY_TIME_IN_24HR.
• Continuous move and out-of-route parameters: ALLOW_CONTINUOUS_MOVE, MAX_CM_DISTANCE, MAX_CM_TIME, MAX_CM_DH_DISTANCE, MAX_CM_DH_TIME, MIN_CM_DISTANCE, MIN_CM_TIME, CM_FREE_DH_MILEAGE, CM_FIRST_LOAD_DISCOUNT, CM_RATE_VARIANT, and MAX_OUT_OF_ROUTE.
• Size constraints: MAX_SIZE_WIDTH, MAX_SIZE_HEIGHT, MAX_SIZE_LENGTH, MIN_SIZE_WIDTH, MIN_SIZE_HEIGHT, MIN_SIZE_LENGTH.
• Supplier linkage: SUPPLIER_ID, SUPPLIER_SITE_ID.
• Attributes and audit columns: ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE15, plus CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Note that the columns list also exposes the party STATUS (aliased as ACTIVE), DIMENSION_UOM, UNIT_RATE_BASIS, and DISTANCE_CALCULATION_METHOD, which are relevant when distinguishing active carriers and selecting the correct distance methodology.

Common Use Cases and Queries

Typical scenarios include listing active carriers prior to shipment planning, validating carrier capacity limits, reviewing which carriers have manifesting enabled, and exporting carrier master data to rating engines. A straightforward query retrieves carriers by SCAC code with status and currency:

• SELECT CARRIER_ID, CARRIER_NAME, SCAC_CODE, CURRENCY_CODE, MANIFESTING_ENABLED_FLAG FROM WSH_CARRIERS_V WHERE SCAC_CODE = :scac AND ACTIVE = 'A';
• SELECT CARRIER_ID, CARRIER_NAME, MAX_TOTAL_DISTANCE, MAX_TOTAL_TIME, TIME_UOM FROM WSH_CARRIERS_V WHERE MANIFESTING_ENABLED_FLAG = 'Y';
• SELECT CARRIER_ID, CARRIER_NAME, SUPPLIER_ID, SUPPLIER_SITE_ID, FREIGHT_BILL_AUTO_APPROVAL FROM WSH_CARRIERS_V;

Because the view is read-only and joins TCA party data, queries should filter on the party STATUS (ACTIVE) to exclude inactive carriers and consider joins to HZ_PARTY_USG_ASSIGNMENTS in customized SQL when party usage must be verified. All queries should run against the APPS schema with the standard Shipping Execution responsibility or a suitable read grant.