Search Results shipment_confirmed_date

Overview

ECE_DSNO_ITEMS_V is a view within the Oracle E-Business Suite e-Commerce Gateway (EC) module. In the ETRM reference metadata for release 12.2.2, this object carries the explicit description "No longer used" and is recorded as "Not implemented in this database." These two facts are the most important characteristics of the view: it is a legacy artifact retained in the data dictionary for backward compatibility and historical reference, but it is not created in a standard, currently supported 12.1.1 or 12.2.2 installation.

The name and structure indicate that the view was once part of the outbound or inbound item/customer item interface serviced by the e-Commerce Gateway. The "_V" suffix follows the Oracle convention for a view, and the prefix "ECE_DSNO_ITEMS" suggests an ECE (e-Commerce Gateway) object associated with a shipment, delivery, or dispatch-oriented transaction set (the "DSNO" token). The view joined shipping/delivery, picking, sales order line, customer item, and inventory item information to produce a flat, denormalized projection suitable for an interface file or report. Because the object is no longer used, any reference to it in custom code, concurrent programs, or integration definitions should be treated as obsolete and migrated to supported alternatives such as the order management and shipping tables directly, or the documented public views in the Order Management and Inventory modules.

Underlying Base Objects

The ETRM metadata for this object documents no referenced base objects in release 12.2.2, consistent with the "Not implemented" status. The documented view text, however, reveals the tables that formed the original definition. The primary sources are the shipping and delivery tables (aliases SPLD, DLV, SPL, EDPQ, RDL), the sales order line table (SOL), the inventory item master (MSI), the customer item master (MCI), and the item master alias MIF. These represent the dispatch, packing, and order-line entities that fed the e-Commerce Gateway item interface. Typical column sources include SPL.INVENTORY_ITEM_ID, SOL.HEADER_ID, SOL.ORDER_LINE_ID, SOL.CUSTOMER_ITEM_ID, MCI.CUSTOMER_ITEM_NUMBER, MIF.ITEM_NUMBER, and MSI container attributes. Because the view is not implemented in supported releases, DBAs should not expect a valid dependency in DBA_DEPENDENCIES; the view text is retained only as documentation of a removed object.

Key Columns

• DELIVERY_ID / DEPARTURE_ID / CONTAINER_ID — Identifiers for the shipment delivery, actual departure, and container, sourced from the shipping and packing tables.
• ITEM_ID — The inventory item identifier (SPL.INVENTORY_ITEM_ID) for the shipped item.
• ORDER_HEADER_ID / ORDER_LINE_ID / ORDER_LINE_NUMBER — Sales order header and line identifiers and the human-readable line number.
• CUSTOMER_ITEM_ID / CUSTOMER_PART_NUMBER — The customer's item reference (SOL.CUSTOMER_ITEM_ID) and its display number (MCI.CUSTOMER_ITEM_NUMBER). This pairing is directly relevant to searches for "customer_item_description," since the customer item number is the customer-facing identifier commonly sought in item-level reporting.
• SUPPLIER_PART_NUMBER — The internal item number (MIF.ITEM_NUMBER), presented as the supplier-facing part number.
• REQUESTED_DATE / PROMISE_DATE / SHIPMENT_CONFIRMED_DATE — Date fields supporting scheduling and shipment tracking.
• SHIPPED_QUANTITY / ORDERED_QUANTITY / CANCELLED_QUANTITY / PACKED_QUANTITY — Quantity metrics for the shipped, ordered, cancelled, and packed amounts.
• LIST_PRICE / SELLING_PRICE — Pricing columns from the order line.
• COMMODITY_CODE, CONTAINER_ITEM_FLAG, CONTAINER_TYPE_CODE, CUSTOMER_ORDER_FLAG — Item and container classification attributes from MCI and MSI.
• Configuration columns — CONFIGURATION_ITEM_FLAG, OPTION_FLAG, SHIP_MODEL_COMPLETE_FLAG, INCLUDED_ITEM_FLAG, ATO_LINE_ID, PARENT_LINE_ID, LINK_TO_LINE_ID, supporting configured/ATO item handling.
• Customer-defined flexfields — CUSTOMER_DOCK_CODE, CUSTOMER_PRODUCTION_LINE, CUSTOMER_JOB, PLANNING_PRODUCTION_SEQ_NUMBER, and TRANSACTION_REFERENCE_KEY.

Common Use Cases and Queries

Because ECE_DSNO_ITEMS_V is documented as no longer used and not implemented in the database, it should not appear in new development. The realistic use case is historical investigation of legacy e-Commerce Gateway interfaces that referenced this view, or reconstruction of customer item mapping logic during retrofitting of old interfaces. In those scenarios, the equivalent modern query is written against the base tables the view once joined:

SELECT sol.header_id, sol.line_id, sol.line_number,
       sol.customer_item_id, mci.customer_item_number,
       msi.segment1 AS internal_item_number
FROM oe_order_lines_all sol,
       mtl_customer_items mci,
       mtl_system_items_b msi
WHERE sol.customer_item_id = mci.customer_item_id
  AND sol.inventory_item_id = msi.inventory_item_id
  AND sol.org_id = msi.organization_id;

A DBA confirming the object's status can query the data dictionary:

SELECT owner, view_name FROM dba_views WHERE view_name = 'ECE_DSNO_ITEMS_V';

An empty result confirms the documented "Not implemented in this database" status for 12.1.1 and 12.2.2. If the view is encountered in an upgraded environment, it should be treated as obsolete and replacement logic directed to the Order Management and Inventory public APIs and tables.