Results for “processed_flag”

10 results




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

Overview

WSH_DEPARTURES is the shipping departures table in Oracle E-Business Suite, owned by the OE (Order Entry) schema and validated across EBS 12.1.1 and 12.2.2. A departure record represents a planned or executed outbound movement of goods — a truck, container, or carrier load — that consolidates one or more deliveries into a single physical shipment. It is the parent grouping object for picking batches, picking line details, and deliveries, and it carries the logistics attributes (carrier, vehicle, weights, volumes, seal, bill of lading) associated with moving that load out of the warehouse.

The primary key is WSH_DEPARTURES_PK, defined on DEPARTURE_ID. A secondary unique index, WSH_DEPARTURES_U1, also covers DEPARTURE_ID, while WSH_DEPARTURES_U2 enforces uniqueness on NAME, confirming NAME as the principal business-key candidate. Under a heuristic Data Vault classification mined from the foreign key structure, the table behaves as a hub: it holds a durable, uniquely identified business entity that is referenced by many surrounding objects. Treat this classification as a modeling suggestion rather than a documented architectural statement.

Key Information Stored

The table carries 48 documented columns. The most operationally significant are:

Common Use Cases and Queries

Typical uses include carrier load reporting, on-time departure analysis, and drill-down from a delivery or picking batch to its parent departure.

  • Departures by organization and status:
    SELECT departure_id, name, status_code, planned_departure_date
    FROM   oe.wsh_departures
    WHERE  organization_id = :org_id
    AND    status_code = :status;
  • Planned versus actual variance:
    SELECT name,
           (actual_departure_date - planned_departure_date) AS variance
    FROM   oe.wsh_departures
    WHERE  actual_departure_date IS NOT NULL;
  • Chained departures via the self-reference:
    SELECT d.name, p.name AS prior_departure
    FROM   oe.wsh_departures d, oe.wsh_departures p
    WHERE  d.arrive_after_departure_id = p.departure_id;
  • Load utilization: aggregate GROSS_WEIGHT, VOLUME, and FILL_PERCENT by FREIGHT_CARRIER_CODE over a date range.
  • Interface monitoring: rows where PROCESSED_FLAG is not yet set, joined to WSH_DELIVERIES_INTERFACE on DEPARTURE_ID.

Related Objects

The following objects reference WSH_DEPARTURES.DEPARTURE_ID and are the most significant for navigation and joining: