Results for “departure_net_weight”

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

Overview

WSH_TRIP_STOPS is a core table in the Oracle E-Business Suite Shipping Execution module (WSH), holding the individual stop records that make up a trip. A trip in Oracle Transportation and Shipping Execution represents a planned movement of goods along a route, and each stop on that route — a pickup, a drop-off, or an intermediate waypoint — is persisted as a single row in WSH_TRIP_STOPS. The table is owned by the WSH schema and registered as VALID in ETRM for both 12.1.1 and 12.2.2, with a documented physical schema of 84 columns in 12.2.2.

From a Data Vault modeling perspective, the metadata's heuristic classification places WSH_TRIP_STOPS as hub-leaning. This reflects that STOP_ID is a stable, unique business identifier reused across many dependent tables, rather than a pure transactional or attribute-only structure. In such a model, STOP_ID would naturally serve as the hub key, with trip and location attributes distributed to links and satellites.

Key Information Stored

The table's identity is anchored by the surrogate primary key STOP_ID, enforced through WSH_TRIP_STOPS_PK and mirrored by the unique index WSH_TRIP_STOPS_U1 on STOP_ID. Beyond this key, the most significant columns fall into several functional groups:

• Trip linkage: TRIP_ID (FK to WSH_TRIPS), WSH_LOCATION_ID (FK to WSH_LOCATIONS), and STOP_LOCATION_ID define which trip and physical location the stop belongs to.
• Sequencing and status: STOP_SEQUENCE_NUMBER and STATUS_CODE establish the stop's order on the route and its lifecycle state.
• Timing: PLANNED_ARRIVAL_DATE, PLANNED_DEPARTURE_DATE, ACTUAL_ARRIVAL_DATE, and ACTUAL_DEPARTURE_DATE capture planned versus executed timing; CARRIER_EST_DEPARTURE_DATE and CARRIER_EST_ARRIVAL_DATE hold carrier estimates.
• Loading metrics: DEPARTURE_GROSS_WEIGHT, DEPARTURE_NET_WEIGHT, DEPARTURE_VOLUME, DEPARTURE_FILL_PERCENT, and their UOM codes record the load state at departure.
• Operational flags: PENDING_INTERFACE_FLAG, TMS_INTERFACE_FLAG, WV_FROZEN_FLAG, and TRACKING_DRILLDOWN_FLAG signal interface and workflow states.
• Descriptive attributes: two flexible attribute blocks (ATTRIBUTE1–15 and the transportation-specific TP_ATTRIBUTE1–15) plus TRACKING_REMARKS, DISTANCE_TO_NEXT_STOP, and DISTANCE_UOM.

Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) and concurrent program columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID) are also present.

Common Use Cases and Queries

Typical reporting centers on trip itinerary reconstruction, on-time performance analysis, and interface monitoring. A basic itinerary query joins stops back to their parent trip:

• Route reconstruction: listing stops in sequence for a given trip, ordered by STOP_SEQUENCE_NUMBER, with PLANNED_ARRIVAL_DATE to display the schedule.
• On-time variance: comparing ACTUAL_ARRIVAL_DATE against PLANNED_ARRIVAL_DATE to measure carrier performance by stop or by TRIP_ID.
• Interface backlog: filtering on PENDING_INTERFACE_FLAG or TMS_INTERFACE_FLAG to identify stops awaiting downstream processing.
• Load monitoring: aggregating DEPARTURE_GROSS_WEIGHT and DEPARTURE_FILL_PERCENT to assess vehicle utilization.
• Dock scheduling: tracing WMS_DOCK_APPOINTMENTS_B.TRIP_STOP back to the stop for warehouse appointment reporting.

Related Objects

WSH_TRIP_STOPS sits at the intersection of several dependent WSH and logistics tables. The most significant relationships are:

• WSH_TRIPS — parent entity; joined via WSH_TRIP_STOPS.TRIP_ID.
• WSH_LOCATIONS — location master; joined via WSH_LOCATION_ID.
• WSH_DELIVERY_LEGS — references stops twice, through PICK_UP_STOP_ID and DROP_OFF_STOP_ID, linking legs to their endpoints.
• WSH_EXCEPTIONS — joins on TRIP_STOP_ID to record stop-level exceptions.
• WSH_FREIGHT_COSTS — joins on STOP_ID to allocate transportation costs.
• WSH_PICKING_BATCHES — joins on TRIP_STOP_ID for warehouse picking coordination.
• WMS_DOCK_APPOINTMENTS_B — references TRIP_STOP for dock scheduling.
• WSH_TRIP_STOPS_INTERFACE — inbound staging table keyed on STOP_ID for stop uploads.

Together these relationships confirm the table's hub-leaning role as the central reference point for trip-level stop data across Shipping Execution and Warehouse Management.