Results for “transactional_currency_code”

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

Overview

The WSH_DSNO_ORDERS_V view is a Shipping Execution (WSH) dictionary object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It forms part of the DSNO (Delivery Shipping Notification / Order) reporting layer used by Oracle's shipping and order-release integration framework. The view consolidates order-level header information — purchase order data, sales order data, party addresses, tax and currency attributes, payment terms, and freight terms — into a single denormalized projection suitable for outbound shipping documents, EDI transactions, and delivery-level reporting.

The view is designed primarily as a supporting object for the DSNO extraction programs, providing a flattened order header context that delivery and container records can be joined against. Because it merges common order attributes with order-specific attributes, it abstracts the underlying complexity of order sources (trading partner versus internal order data) from downstream consumers such as shipping notification reports, labels, and interfaces.

Underlying Base Objects

According to the documented ETRM metadata, WSH_DSNO_ORDERS_V references the following base objects:

• WSH_DSNO_ORDERS_COMM_V (VIEW) — Provides the "common" order columns, such as delivery ID, container instance ID, order header ID, sales order number, order-by address and party information, and invoice party name fields.
• WSH_DSNO_ORDERS_SPECIFIC_V (VIEW) — Provides the order-specific columns, including purchase order number and date, sales order date, agreement number, order type, order category, request date, partial shipment flag, invoice address details, tax exemption data, currency conversion attributes, payment terms, and order header descriptive flexfield (DFF) attributes.
• WSH_DSNO_OKE (PACKAGE) — A PL/SQL package used within the DSNO framework, typically referenced in the view definition or its supporting logic for order key extraction and flexibility (OKE-style) resolution.
• WSH_ECE_VIEWS_DEF (PACKAGE) — The E-Commerce Exchange (ECE) views definition package that governs the column mapping and metadata exposed by the DSNO views for outbound EDI/document generation.

Architecturally, the view is a union-style or join-based composite: COMM columns originate from WSH_DSNO_ORDERS_COMM_V, while SPEC columns originate from WSH_DSNO_ORDERS_SPECIFIC_V. This separation allows the same delivery/container context to carry multiple order interpretations without duplicating common party data.

Key Columns

• DELIVERY_ID, CONTAINER_INSTANCE_ID, ORDER_HEADER_ID — Core keys linking the order header to its delivery and container, enabling joins back to WSH_DELIVERIES and WSH_DELIVERY_ASSIGNMENTS.
• SALES_ORDER_NUMBER, PURCHASE_ORDER_NUMBER — Human-readable order identifiers; the sales order number comes from the common view, the purchase order number and date from the specific view.
• ORDER_BY_* columns — Full "order by" party address, contact, and EDI location references, used to populate ship-to/order-by blocks on shipping documents.
• INVOICE_* columns — Invoice party address, contact, and EDI location details, sourced from the specific view.
• TRANSACTIONAL_CURRENCY_CODE, CURRENCY_CONVERSION_* — Currency and conversion rate/date/type used for monetary reporting.
• TAX_EXEMPT_FLAG, TAX_EXEMPT_NUMBER, TAX_EXEMPT_REASON_CODE_INT — Tax exemption handling for the order.
• ORDER_HEADER_CONTEXT, ORDER_HEADER_ATTRIBUTE1... — Descriptive flexfield context and segment values, enabling site-specific extensibility.

Common Use Cases and Queries

Typical scenarios include generating delivery-level shipping notifications, populating EDI 856/810 documents, and building custom order-to-delivery reports. A representative query joining the view to a delivery is:

• SELECT delivery_id, sales_order_number, purchase_order_number, order_by_name, invoice_city FROM apps.wsh_dsno_orders_v WHERE delivery_id = :p_delivery_id;
• SELECT o.sales_order_number, d.delivery_name, o.order_by_name FROM apps.wsh_dsno_orders_v o, apps.wsh_deliveries_v d WHERE o.delivery_id = d.delivery_id;
• SELECT order_header_id, transactional_currency_code, payment_terms_int, fob_payment_method_code_int FROM apps.wsh_dsno_orders_v WHERE sales_order_number = :p_order;

Because the view exposes ECE-oriented columns, it is frequently consumed by Oracle E-Commerce Gateway concurrent programs and custom extension extracts rather than directly by end users.