Search Results tp_location_code_ext




Overview
Explore in AI Chat

Overview

ECE_DSNO_DELIVERIES_V is a view shipped within the Oracle E-Business Suite e-Commerce Gateway (EC) module. Its name follows the e-Commerce Gateway outbound interface naming convention, where the prefix "ECE" denotes e-Commerce Gateway Extraction, "DSNO" denotes the outbound Delivery Ship Notice (DESADV / ASN) document, and the "_V" suffix identifies the object as a view rather than a base table. In the context of ETRM documentation for releases 12.1.1 and 12.2.2, the object carries the explicit description "No longer used," and the excerpt notes it is "Not implemented in this database."

Functionally, the view was designed to present a flattened, integration-ready projection of delivery and departure (shipment) information suitable for conversion into an outbound EDI delivery ship notice message. It consolidates transaction-profile attributes, delivery header data, departure (trip) data, equipment and carrier details, and weight/volume measurements into a single denormalized row set. Because it is documented as obsolete and unimplemented, it should be treated as a legacy artifact; the supported delivery ship notice extraction is delivered through the current e-Commerce Gateway concurrent programs and their associated interface tables rather than through this view.

Underlying Base Objects

The ETRM metadata documents no referenced base objects for this view, and states that it is not implemented in the database. The view text itself, however, reveals the tables joined to produce the projection. These include the transaction profile header and detail tables (aliased ETH and ETD on TP_HEADER_ID and TP_DETAIL_ID), which supply the e-Commerce Gateway transaction profile configuration. Delivery and departure information is drawn from the delivery table (aliased DLV, providing DELIVERY_ID, NAME, ACTUAL_DEPARTURE_ID and ACTUAL_DEPARTURE_DATE) and the departure table (aliased DPT, providing departure name, bill of lading, vehicle number, seal code, freight carrier code, weights, volumes and routing instructions). A document code lookup (aliased DLV.NAME DOCUMENT_CODE) supplies the outbound document identifier, a location/responsibility reference (aliased ERC3) supplies TP_LOCATION_CODE_EXT, and an item master reference (aliased MSI) supplies ITEM_TYPE for equipment code derivation.

Because no base objects are formally documented and the view is marked as no longer used, the joins above should be regarded as descriptive of the legacy definition only and must be validated against the specific installation before any reliance is placed on them.

Key Columns

Common Use Cases and Queries

Historically, this view was queried to extract delivery ship notice data, to reconcile ship notice content against delivery and departure records, and to investigate the date on which a shipment actually departed — frequently searched for as "actual_ship_date." Given its documented status, any query should first confirm implementation.

  • Verify existence and definition: query ALL_VIEWS / DBA_VIEWS for ECE_DSNO_DELIVERIES_V and inspect the text.
  • Retrieve departure dates for outbound ship notices: SELECT DELIVERY_ID, DELIVERY_NAME, DEPARTURE_ID, DEPARTURE_NAME, DEPARTURE_DATE FROM ECE_DSNO_DELIVERIES_V ORDER BY DEPARTURE_DATE DESC;
  • Inspect carrier and equipment detail for a shipment: SELECT DELIVERY_NAME, CARRIER_NAME_INT, EQUIPMENT_PREFIX, EQUIPMENT_NUMBER, EQUIPMENT_SEAL FROM ECE_DSNO_DELIVERIES_V;
  • Review weight and volume measures: SELECT DELIVERY_ID, DEPARTURE_GROSS_WEIGHT, DEPARTURE_NET_WEIGHT, DEPARTURE_TARE_WEIGHT, DEPARTURE_VOLUME FROM ECE_DSNO_DELIVERIES_V;

Where the view is absent or returns no rows, the corresponding delivery and departure data should be obtained from the standard e-Commerce Gateway interface tables and the shipping execution tables directly, using the source objects identified above.