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:
- DEPARTURE_ID — surrogate primary key (WSH_DEPARTURES_PK) and the join column used by every dependent table.
- NAME — user-facing departure name; enforced unique by WSH_DEPARTURES_U2, making it the business-key candidate.
- ORGANIZATION_ID — owning inventory organization, the standard multi-org partition key.
- STATUS_CODE — lifecycle state of the departure (for example open, closed, or cancelled).
- PLANNED_DEPARTURE_DATE and ACTUAL_DEPARTURE_DATE — the scheduled versus real departure timestamps, used for on-time performance reporting.
- ARRIVE_AFTER_DEPARTURE_ID — self-referencing foreign key to WSH_DEPARTURES, supporting sequenced or chained departures.
- REPORT_SET_ID — foreign key to SO_REPORT_SETS, tying the departure to its document/report grouping.
- FREIGHT_CARRIER_CODE, VEHICLE_ITEM_ID, VEHICLE_NUMBER — carrier and equipment identification.
- GROSS_WEIGHT, NET_WEIGHT, WEIGHT_UOM_CODE, VOLUME, VOLUME_UOM_CODE, FILL_PERCENT — load capacity and utilization measures.
- BILL_OF_LADING, SEAL_CODE, ROUTING_INSTRUCTIONS — transport documentation and compliance detail.
- DATE_CLOSED — the date the departure was closed for shipping transactions.
- SOURCE_CODE — origin indicator for the record.
- ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY — the standard DFF-flexfield block.
- WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the concurrent-program block (PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID, PROCESSED_FLAG) for auditing and interface processing.
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:
- WSH_DELIVERIES — references the departure twice, via PLANNED_DEPARTURE_ID and ACTUAL_DEPARTURE_ID; the primary parent-child relationship.
- SO_PICKING_BATCHES_ALL — batch assignment via DEPARTURE_ID.
- SO_PICKING_LINE_DETAILS — line-level picking linkage via DEPARTURE_ID.
- SO_LINE_DETAILS — order line detail linkage via SO_LINE_DETAILS_DEPARTURE_ID and DEPARTURE_ID.
- SO_REPORT_SETS — referenced by WSH_DEPARTURES.REPORT_SET_ID.
- WSH_DEPARTURES (self) — via ARRIVE_AFTER_DEPARTURE_ID.
- WSH_DELIVERIES_INTERFACE, WSH_REPORT_TEMP, and OE_UPGRADE_WSH_IFACE — interface, reporting, and upgrade staging tables keyed by DEPARTURE_ID.
-
Shipping departures
-
Cancelled picking lines
-
APPS.SO_ORDER_CANCELLATIONS_V·↳ FND_GLOBAL·↳ FND_PROFILE·↳ MTL_SYSTEM_ITEMS_KFV·Explore OE module →
-
APPS.SO_ORDER_CANCELLATIONS_V·↳ FND_GLOBAL·↳ FND_PROFILE·↳ MTL_SYSTEM_ITEMS_KFV·Explore OE module →
-
Cancelled picking lines
-
Order and order line cancellations
-
Order and order line cancellations
-
Picking line details
-
Picking line details
-
Shipping departures