Search Results fob_name

Overview

WSH_DELIVERIES_V is a reporting and integration view in Oracle E-Business Suite that consolidates delivery header information for use in departure planning and ship confirm processes. It belongs to the Order Entry (OE) product family and is most commonly referenced during outbound logistics operations, including carrier selection, bill of lading generation, and advance ship notice (ASN) processing. The view joins the delivery record to both the planned departure and the actual ship confirm departure, exposing denormalized departure attributes side by side so that planners and integrators do not need to resolve multiple foreign keys against WSH_DEPARTURES manually.

Although the user search term was "fob_name," the view text provided does not expose an FOB-related column directly. FOB (Free On Board) terms are typically carried on the order or shipment line rather than at the delivery header level, so a delivery-centric view such as WSH_DELIVERIES_V would not normally surface a FOB name. Practitioners searching for fob_name in this context should expect to join onward to WSH_DELIVERY_ASSIGNMENTS, WSH_NEW_DELIVERIES, or order line tables to reach FOB code and its meaning.

Underlying Base Objects

The ETRM metadata records no documented base objects for this view, and notes that it is "not implemented in this database" — meaning the view is delivered as part of the application schema (APPS) and resolved at runtime against the WSH tables. Based on the view text, it is defined over the following primary objects:

• WSH_DELIVERIES (aliased DEL) — the driving table supplying delivery identity, status, weights, volumes, and audit columns.
• WSH_DEPARTURES (aliased DEP1 and DEP2) — joined twice, once for the planned departure and once for the ship confirm departure.
• WSH_LOOKUPS or FND_LOOKUPS (aliased S1, S2, S3) — supplying the meaning for delivery status and departure status codes.
• RA_CUSTOMERS (aliased RC) — providing customer name and number.
• HR_LOCATIONS (aliased SU1, SU2, SU3) — resolving the ultimate, intermediate, and pooled ship-to locations.
• FND_USER joined to PER_ALL_PEOPLE_F (aliased FU1, FU2) — resolving picker and packer names.
• FND_CONCURRENT_PROGRAMS or a report set source (aliased SRS) — supplying the report set name.

Key Columns

The view exposes a broad set of delivery attributes. Notable columns include:

• DELIVERY_ID, DELIVERY_NAME, ORGANIZATION_ID — unique delivery identifiers and owning inventory organization.
• STATUS_CODE and STATUS — delivery status code and its decoded meaning.
• DPW_DEPARTURE_ID, DPW_DEPARTURE_NAME, DPW_PLANNED_DEPARTURE_DATE, DPW_FREIGHT_CARRIER_CODE, DPW_BOL — planned departure context used during departure planning.
• SC_DEPARTURE_ID, SC_DEPARTURE_NAME, SC_ACTUAL_DEPARTURE_DATE, SC_BOL — ship confirm departure context.
• CUSTOMER_ID, CUSTOMER_NAME, CUSTOMER_NUMBER — ship-to customer details.
• ULTIMATE_SHIP_TO, INTERMEDIATE_SHIP_TO, POOLED_SHIP_TO — location strings for the three ship-to roles.
• GROSS_WEIGHT, WEIGHT_UOM_CODE, VOLUME, VOLUME_UOM_CODE — shipment measurements.
• PICKER_NAME, PACKER_NAME, WAYBILL, ASN_DATE_SENT, DATE_CLOSED, SOURCE_CODE.

Common Use Cases and Queries

Typical scenarios include building departure manifests, tracking ASN transmission, and reporting on ship confirm status. A representative query retrieving delivery and departure status is:

• SELECT delivery_name, status, dpw_departure_name, sc_departure_name, dpw_freight_carrier_code, gross_weight FROM wsh_deliveries_v WHERE organization_id = :org_id AND status_code = 'CL';

Because FOB is not a native column here, a search on fob_name should be redirected to order or shipment line tables and joined back to this view via delivery_id when delivery-level context is also required.