Results for “purchase_order_date”

50+ results




Overview
Explore in AI Chat

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

Overview

APPS.WSH_DSNO_ORDERS_SPECIFIC_V is a Shipping Execution (WSH) view that consolidates order-header, customer, address, contact, agreement, and payment-term attributes into a single denormalized structure for outbound order information. The name prefix "DSNO" denotes Delivery Ship Notice Outbound, indicating the view's role within the Oracle E-Business Suite outbound EDI/XML messaging and shipping-integration framework. It is a supporting object referenced by the WSH_DSNO (ship notice) extraction logic and is exposed by the WSH_ECE_VIEWS_DEF package, which supplies derived values such as contact area codes and telephone numbers.

The view is defined in the APPS schema and is documented as VALID. It presents one row per order header record sourced from Order Management (OE), joined outward to delivery and customer master data. Because the PURCHASE_ORDER_DATE column is implemented as a direct alias of OEH.ORDERED_DATE, a search on "purchase_order_date" against this view resolves to the order's original ordered date rather than a true procurement document date. This aliasing behaviour is a common source of confusion in reporting.

Underlying Base Objects

The view is defined over a wide set of documented base objects:

The joins establish the linkage from the sales order down to the ship-to/invoice customer account site, site use, location addresses, and organization contacts. Delivery-related rows are attached through WSH_DELIVERY_DETAILS and WSH_DELIVERY_ASSIGNMENTS_V, which map order lines to delivery details and assignments. The WSH_DSNO_OKE and WSH_ECE_VIEWS_DEF PL/SQL packages supply additional derived values, including contact and EDI location attributes used in outbound messages.

Key Columns

Common Use Cases and Queries

The view supports ship-notice generation, order-data extraction for outbound EDI, and customer-facing order extracts. Typical patterns include filtering by date range and joining to WSH delivery tables.

SELECT source_header_id,
       sales_order_number,
       purchase_order_date,
       sales_order_date,
       invoice_city,
       payment_terms_int
FROM   apps.wsh_dsno_orders_specific_v
WHERE  purchase_order_date >= :from_date
AND    purchase_order_date <  :to_date;

For contact and EDI attributes:

SELECT sales_order_number,
       invoice_contact_last_name,
       invoice_telephone,
       invoice_edi_loc_code,
       invoice_tp_ref_1
FROM   apps.wsh_dsno_orders_specific_v
WHERE  invoice_edi_loc_code IS NOT NULL;

Because PURCHASE_ORDER_DATE mirrors the sales order ordered date, reports must not treat it as a procurement date; a genuine PO date must be sourced from procurement tables. Queries should be schema-qualified as APPS and executed with appropriate Shipping Execution and Order Management privileges.