Search Results order_by_area_code

Overview

ECE_DSNO_ORDERS_V is a database view historically shipped with the Oracle E-Business Suite e-Commerce Gateway (EC) module. The ETRM metadata for both Oracle EBS 12.1.1 and 12.2.2 classifies this object with the description "No longer used," and the implementation notes state that it is "Not implemented in this database." In other words, although the view was once part of the EC schema, it is a deprecated artifact in the two releases referenced and should not be relied upon for any new development, reporting, or integration work.

Despite its deprecated status, the view definition remains instructive because it documents the intended purpose: exposing a flattened, denormalized order record suitable for e-Commerce Gateway outbound/inbound processing. The naming convention (DSNO) suggests a data source for order-related document generation, while the column aliases map internal Oracle Order Management attributes to friendly, external-facing names used by EDI or XML trading-partner messages. For users who searched for "purchase_order_date," the relevant fact is that the view exposes this value through the column alias PURCHASE_ORDER_DATE, sourced from SOH.DATE_ORDERED.

Underlying Base Objects

The ETRM documentation records no referenced base objects for this view, meaning the standard repository does not enumerate the underlying tables as it typically would. However, the embedded view text reveals the base objects through its SELECT clause. These include:

• SPLD — a shipping/delivery detail source (DELIVERY_ID, CONTAINER_ID)
• DLV — a delivery source exposing ACTUAL_DEPARTURE_ID
• SPH — a picking header source (PICKING_HEADER_ID, ORDER_HEADER_ID)
• SOH — the sales order header source, providing PURCHASE_ORDER_NUM, DATE_ORDERED, ORDER_NUMBER, ORDER_CATEGORY, SHIP_PARTIAL_FLAG, and PAYMENT_TYPE_CODE
• SOA — a sales agreement source (AGREEMENT_NUM)
• SOT — an order type source (NAME)
• ERA1 — an address source for the "order by" party (ADDRESS_ID, ORIG_SYSTEM_REFERENCE, CUSTOMER_NAME, address lines, and contact details)
• ERC2 — an address source for the invoice party (ADDRESS_ID, ORIG_SYSTEM_REFERENCE, LOCATION, and address lines)

The view is therefore a join across order, delivery, picking, agreement, order type, and party address data. The exact join predicates are truncated in the provided excerpt, but the DISTINCT keyword indicates the joins can produce duplicates that the view suppresses.

Key Columns

The most pertinent column for the "purchase_order_date" search is PURCHASE_ORDER_DATE, aliased from SOH.DATE_ORDERED. It represents the date the order was placed and is distinct from CUSTOMER_REQUEST_DATE (SOH.DATE_REQUESTED_CURRENT), which captures the customer-requested ship date. Other notable columns include:

• PURCHASE_ORDER_NUMBER — the buyer's PO reference (SOH.PURCHASE_ORDER_NUM)
• SALES_ORDER_NUMBER and SALES_ORDER_DATE — the internal order number and its date
• DELIVERY_ID, DEPARTURE_ID, CONTAINER_ID, PICKING_HEADER_ID, ORDER_HEADER_ID — shipment and picking identifiers
• AGREEMENT_NUMBER_INT, ORDER_TYPE_INT, ORDER_CATEGORY — commercial classification fields
• ORDER_BY_* columns — the ordering party's address, contact, and codes
• INVOICE_* columns — the invoicing party's address and codes

Common Use Cases and Queries

Because the view is documented as "No longer used" and "Not implemented," it should not appear in current production queries or integrations. Historically it may have supported e-Commerce Gateway order mapping or reconciliation between Oracle Orders and trading-partner documents. If a legacy query references it, the correct action is to migrate to supported Order Management views such as OE_ORDER_HEADERS_V or purpose-built EC interface tables.

For reference, a query retrieving the purchase order date once looked like:

• SELECT PURCHASE_ORDER_NUMBER, PURCHASE_ORDER_DATE, SALES_ORDER_NUMBER FROM ECE_DSNO_ORDERS_V WHERE PURCHASE_ORDER_DATE >= :start_date;

In 12.1.1 and 12.2.2 this statement is expected to fail or return no data because the object is not implemented. Consultants should treat ECE_DSNO_ORDERS_V strictly as historical documentation and validate replacement data sources before building any new reporting artifact.