Search Results planned_day

Overview

The APPS.WSH_DEPARTURE_TEMPLATES_V view is a reporting and integration object within Oracle E-Business Suite, owned by the APPS schema. Although its documented product association is OE (Order Entry), the view exposes configuration metadata that belongs functionally to Oracle Shipping Execution (WSH). It presents a denormalized, ready-to-query representation of departure templates — the reusable definitions that describe how outbound shipments are grouped and scheduled for carrier pickup and dispatch.

Departure templates store the recurring logistics pattern for a warehouse: the freight carrier, the vehicle used, the frequency of departure, the day of the week and time of departure, and the weight and volume unit-of-measure defaults. Because the base tables are highly normalized (numeric item IDs, coded lookups), the view adds a resolved vehicle description by joining to the item master. This makes the view directly consumable by reports, concurrent programs, and external integrations that need human-readable departure schedules without embedding the lookup logic themselves.

Underlying Base Objects

The view is defined over two documented base objects, both accessed through APPS synonyms:

• WSH_DEPARTURE_TEMPLATES — the primary driving table. All template attributes, descriptive flexfield segments (ATTRIBUTE1 through ATTRIBUTE15), and the standard EBS WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID) originate here.
• MTL_SYSTEM_ITEMS — joined as a nullable outer join on MSI.INVENTORY_ITEM_ID(+) = WDT.VEHICLE_ITEM_ID. This resolves the vehicle inventory item to its DESCRIPTION, exposed as VEHICLE_DESCRIPTION.

Because the join to MTL_SYSTEM_ITEMS is outer (+), every departure template row is preserved even when the VEHICLE_ITEM_ID is null or does not resolve to a defined item, in which case VEHICLE_DESCRIPTION returns null. The view also fabricates a ROW_ID column from WDT.ROWID, providing a pseudo-row identifier suitable for certain Oracle Forms or update frameworks.

Key Columns

• DEPARTURE_TEMPLATE_ID — primary identifier for the template; the join key back to the base table.
• NAME — user-defined template name displayed in shipping setup.
• ORGANIZATION_ID — the inventory organization (warehouse) the template belongs to; essential for multi-org filtering.
• VEHICLE_ITEM_ID / VEHICLE_DESCRIPTION — the vehicle inventory item and its resolved description.
• VEHICLE_NUMBER — the license or fleet identifier of the vehicle.
• FREIGHT_CARRIER_CODE — the carrier assigned to the scheduled departure.
• PLANNED_FREQUENCY — the recurrence cadence of the departure.
• PLANNED_DAY — the day of the week (or period) on which the departure is planned. This is frequently queried to derive weekly dispatch calendars and cut-off schedules.
• PLANNED_TIME — the scheduled departure time.
• WEIGHT_UOM_CODE / VOLUME_UOM_CODE — default units of measure applied to shipment weight and volume.
• ROUTING_INSTRUCTIONS — free-text instructions for the driver or carrier.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield context and segments for customer-specific extensions.

Common Use Cases and Queries

The view supports shipping setup validation, carrier scheduling reports, and interface extracts. A typical query filtering by planned departure day and organization:

• SELECT departure_template_id, name, vehicle_number, freight_carrier_code, planned_frequency, planned_day, planned_time FROM wsh_departure_templates_v WHERE organization_id = :p_org_id AND planned_day = 'MON' ORDER BY planned_time;
• Extracting carrier calendars: SELECT freight_carrier_code, planned_day, planned_time, vehicle_description FROM wsh_departure_templates_v WHERE organization_id = :p_org_id;
• Auditing templates lacking a valid vehicle: SELECT departure_template_id, name FROM wsh_departure_templates_v WHERE vehicle_item_id IS NOT NULL AND vehicle_description IS NULL;
• Incremental integration extracts using the WHO columns: SELECT * FROM wsh_departure_templates_v WHERE last_update_date >= :p_since;

Because the view is a simple two-table definition with no aggregation, it performs efficiently and is safe for high-volume read access, though callers should always constrain on ORGANIZATION_ID in multi-org environments.