Search Results wsh_location_id

Overview

QA_ERES_WSH_NEW_DELIVERIES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, registered and valid in both release 12.1.1 and 12.2.2. It resides within the Quality (QA) product family and is documented as the "shipping delivery electronic record" view. Its function is to consolidate delivery header information from Oracle Shipping Execution into a single, denormalized structure tailored for electronic records management, including electronic signatures and compliance-driven record retention. The view joins the core shipping deliveries view to organization, customer, carrier, ship method, service level, and location references, producing a flattened result set that downstream e-records processes, audits, and warehouse reporting can consume without reproducing the same join logic. Because it exposes only delivery header attributes — not delivery detail lines — it is intended for tracking and identification purposes rather than line-level inventory reconciliation.

Underlying Base Objects

The view is defined over eight documented base objects, all resolved through APPS synonyms or nested views:

• WSH_NEW_DELIVERIES_V (view) — the primary source, supplying delivery identifiers, organization, customer, status, dates, waybill, carrier, mode of transport, and DFF attributes.
• MTL_PARAMETERS (synonym) — joined on ORGANIZATION_ID to retrieve ORGANIZATION_CODE.
• HR_ALL_ORGANIZATION_UNITS_TL (synonym) — joined on ORGANIZATION_ID and the current session language to retrieve the organization display name.
• WSH_LOCATIONS (synonym) — outer-joined four times as WL1 through WL4 for initial pickup, ultimate dropoff, intermediate ship-to, and pooled ship-to locations.
• QA_CUSTOMERS_LOV_V (view) — outer-joined on CUSTOMER_ID for customer name.
• WSH_CARRIER_SHIP_METHODS_V (view) — outer-joined on ORGANIZATION_ID and SHIP_METHOD_CODE for the method meaning.
• WSH_CARRIERS_V (view) — outer-joined on CARRIER_ID for the carrier name.
• WSH_LOOKUPS (view) — outer-joined on SERVICE_LEVEL and the service-level lookup type for the service level meaning.

All secondary joins use the Oracle outer-join operator (+), so the view returns delivery rows even when lookups, customers, carriers, or locations are unmatched. Language-sensitive joins rely on USERENV('LANG').

Key Columns

• DELIVERY_ID, NAME, STATUS_CODE, STATUS_NAME — delivery identity and lifecycle status.
• ORGANIZATION_ID, ORGANIZATION_CODE, NAME (HR org) — the shipping warehouse context.
• CUSTOMER_ID, CUSTOMER_NAME — ship-to customer identification, relevant where a contact or delivery contact lookup is required.
• CARRIER_ID, CARRIER_NAME, SHIP_METHOD_CODE, SHIP_METHOD_CODE_MEANING, SERVICE_LEVEL, MEANING, MODE_OF_TRANSPORT — carrier and transport information.
• WL1–WL4 UI_LOCATION_CODE — pickup, dropoff, intermediate, and pooled ship-to location codes.
• INITIAL_PICKUP_DATE, ULTIMATE_DROPOFF_DATE — planned movement dates.
• NUMBER_OF_LPN, WAYBILL, ADDITIONAL_SHIPMENT_INFO — logistics identifiers, including the waybill used for tracking.
• ATTRIBUTE1–ATTRIBUTE15, ATTRIBUTE_CATEGORY — descriptive flexfield content often used to store extended tracking or contact data.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns supporting e-record integrity.

Common Use Cases and Queries

Typical usage includes electronic record generation for shipped deliveries, carrier and waybill tracking reports, delivery status monitoring by warehouse, and audit extracts. Because delivery contact telephone numbers are not exposed as native columns, users seeking contact numbers generally read the flexfield attributes or join to customer contact tables. A representative query:

• SELECT delivery_id, name, status_name, organization_code, customer_name, carrier_name, waybill, attribute1, creation_date FROM apps.qa_eres_wsh_new_deliveries_v WHERE organization_id = :org_id AND creation_date >= :from_date; — supports e-record extracts for a warehouse over a date range, with ATTRIBUTE1 frequently repurposed for contact or tracking reference data.
• SELECT waybill, carrier_name, ship_method_code_meaning, ultimate_dropoff_date FROM apps.qa_eres_wsh_new_deliveries_v WHERE waybill = :waybill; — retrieves tracking context for a specific shipment.
• SELECT status_name, COUNT(*) FROM apps.qa_eres_wsh_new_deliveries_v GROUP BY status_name; — summarizes delivery volumes by status for operational dashboards.