Search Results invoice_edi_loc_code




Overview
Explore in AI Chat

Overview

APPS.WSH_DSNO_ORDERS_SPECIFIC_V is a shipped Oracle E-Business Suite view owned by the APPS schema and registered in FND Design Data as WSH.WSH_DSNO_ORDERS_SPECIFIC_V. It belongs to the WSH (Shipping Execution) product family and is part of the DSNO (Data Source for Network Objects) layer that supplies order-level descriptive data to Oracle's outbound logistics and document-generation integrations. The object is documented as an Internal view type with a status of VALID. Oracle's documentation carries an explicit warning: the object is for Oracle Internal Use Only, and Oracle Corporation does not support access to applications data through it except from standard Oracle Applications programs.

The view presents a single, denormalized row per sales or purchase order source line, combining order header attributes (order dates, order numbers, agreement references, order type and category), invoicing and shipping address details, tax attributes, currency conversion attributes, payment terms and payment amount, plus a set of order header DFF context/attribute columns. Its practical role is to feed downstream interface tables and XML/document generation processes with invoice-to and ship-to information resolved from Trading Partner, Customer (HZ), Order Management (OE), and Order Capture/Contracts (OKE/OKC) data.

Underlying Base Objects

The view is defined over a broad set of EBS base objects. Customer and party data is sourced from HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS, HZ_ORG_CONTACTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, and HZ_RELATIONSHIPS. Order data comes from OE_ORDER_HEADERS_ALL, OE_TRANSACTION_TYPES_TL, and OE_AGREEMENTS_B. Contract and terms data is drawn from OKC_K_HEADERS_B, OKE_K_HEADERS, OKE_K_TERMS, and OKE_K_FUNDING_SOURCES, with payment terms resolved from RA_TERMS. Trading partner attributes come from ECE_TP_HEADERS. Shipping-side data is supplied through WSH_DELIVERY_DETAILS and the WSH_DELIVERY_ASSIGNMENTS_V view. Two PL/SQL program units — the WSH_DSNO_OKE package and the WSH_ECE_VIEWS_DEF package — participate in the definition, indicating that portions of the view are generated or dynamically constructed by the DSNO infrastructure rather than expressed as a purely static SQL statement.

Key Columns

The column list is anchored by identifiers and descriptive fields commonly used by EDI and logistics interfaces:

Common Use Cases and Queries

Because the view is internal and unsupported for direct access, it is normally consumed by Oracle's own DSNO-based programs that populate outbound interface tables. Where DBAs or integration developers inspect it, typical uses include validating trading partner references on invoice locations and confirming address resolution for a given delivery.

To locate rows by the invoice trading partner reference:

SELECT sales_order_number, order_type_int, invoice_code_int, invoice_tp_ref_1, invoice_tp_ref_2
FROM apps.wsh_dsno_orders_specific_v
WHERE invoice_tp_ref_1 = :p_tp_ref;

To review invoicing addresses for a specific order:

SELECT sales_order_number, invoice_address1, invoice_address2, invoice_city,
       invoice_state_int, invoice_postal_code, invoice_country_int
FROM apps.wsh_dsno_orders_specific_v
WHERE sales_order_number = :p_order_number;

Given the Internal Use Only designation, any direct query should be treated as diagnostic rather than as a supported integration interface, and organizations should rely on Oracle's delivered concurrent programs and public APIs for production data extraction.