Results for “tracking_remarks”

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

Overview

WSH.WSH_DELIVERY_LEG_DETAILS is a Shipping Execution (WSH) transactional table that stores the association between a delivery leg and the delivery lines (delivery details) transported on that leg, together with the cumulative and leg-specific quantities and timestamps captured during the shipping lifecycle. It holds "Delivery Leg Delivery Line information" and exists to bridge the header-level routing/runtime structure of a delivery leg with the line-level fulfillment detail that must be tracked for loading, departure, arrival, and receipt events.

Within Oracle EBS 12.1.1 and 12.2.2, the table participates directly in the shipping confirmation, manifesting, and delivery-tracking flows: as deliveries are consolidated and routed, the application records per-line quantities at each stage of the trip, enabling partial shipments, multi-stop routing, and reconciliation of what was loaded against what was actually delivered or received.

The mined Data Vault classification for this object is standalone. As a modeling suggestion, this placement is consistent with a link-style object that resolves a many-to-many association between a delivery leg and a delivery detail, since the primary key is a composite of both parent identifiers and no parent hub is captured solely by a surrogate identifier. Analysts building a Data Vault layer may therefore treat it as a link (or a link with satellite attributes), with the descriptive quantity, status, and timestamp columns modeled as satellite payload attached to that link.

Key Information Stored

The documented physical schema in 12.2.2 contains 25 columns. The most significant are:

• DELIVERY_LEG_ID — identifier of the delivery leg (trip segment) on which the line was carried.
• DELIVERY_DETAIL_ID — identifier of the delivery line being tracked on that leg.
• DELIVERED_QUANTITY — quantity confirmed as delivered at the completion of the leg.
• LOADED_QUANTITY — quantity loaded onto the vehicle for the leg.
• RECEIVED_QUANTITY — quantity acknowledged as received at the destination.
• ACTUAL_DEPARTURE_DATE — actual departure timestamp from the origin.
• ACTUAL_ARRIVAL_DATE — actual arrival timestamp at the destination.
• ACTUAL_RECEIPT_DATE — actual receipt date recorded for the line.
• CARRIER_EST_DEPARTURE_DATE — carrier-provided estimated departure.
• CARRIER_EST_ARRIVAL_DATE — carrier-provided estimated arrival.
• LOADING_START_DATETIME / LOADING_END_DATETIME — loading window for the leg.
• UNLOADING_START_DATETIME / UNLOADING_END_DATETIME — unloading window for the leg.
• STATUS_CODE — current status of the leg-line association.
• TRACKING_REMARKS — free-text remarks supporting tracking and exception handling.

The documented primary key, WSH_DELIVERY_LEG_DETAILS_PK, is the composite of DELIVERY_LEG_ID and DELIVERY_DETAIL_ID. Both are therefore surrogate composite key components rather than independent business keys; the pairing itself is the unique business-key candidate, enforcing that a given delivery line appears at most once per delivery leg. The remaining columns — including CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID — are standard WHO/audit columns used for concurrency control and traceability.

Common Use Cases and Queries

Typical reporting scenarios include load-versus-delivered variance analysis, carrier performance and on-time departure/arrival measurement, and reconciliation of delivered quantities to received quantities for billing or claims.

• Retrieve all lines on a given leg: SELECT DELIVERY_DETAIL_ID, LOADED_QUANTITY, DELIVERED_QUANTITY, RECEIVED_QUANTITY FROM WSH_DELIVERY_LEG_DETAILS WHERE DELIVERY_LEG_ID = :leg_id;
• Identify short-shipped lines: compare LOADED_QUANTITY against DELIVERED_QUANTITY, filtering rows where the difference is non-zero.
• Measure carrier timeliness: join CARRIER_EST_DEPARTURE_DATE and CARRIER_EST_ARRIVAL_DATE against ACTUAL_DEPARTURE_DATE and ACTUAL_ARRIVAL_DATE.
• Audit loading/unloading durations using LOADING_START_DATETIME, LOADING_END_DATETIME, UNLOADING_START_DATETIME, and UNLOADING_END_DATETIME.
• Feed warehouse or transportation analytics by extracting STATUS_CODE and TRACKING_REMARKS as dimensional attributes.

Related Objects

Because the object is documented as standalone with no enumerated foreign keys, relationships are inferred from the composite key columns and shipping lineage:

• WSH_DELIVERY_LEGS — joined on DELIVERY_LEG_ID; the parent leg record.
• WSH_DELIVERY_DETAILS — joined on DELIVERY_DETAIL_ID; the delivery line definition.
• WSH_DELIVERIES — via the delivery header underlying the detail line.
• WSH_TRIPS / WSH_TRIP_STOPS — trip and stop context for the leg.
• WSH_NEW_DELIVERIES — deliveries view commonly used alongside leg details for consolidated reporting.
• WSH_DELIVERY_ASSIGNMENTS — grouping of details into deliveries that feeds leg-level quantities.

Shipping confirmation and tracking APIs, plus the Oracle Shipping Execution concurrent programs, transact against this table to maintain the quantity and timestamp payload over the delivery lifecycle.