Search Results pl_detail_attribute1

Overview

ECE_DSNO_ITEM_DETAILS_V is a database view historically associated with the Oracle e-Commerce Gateway (EC) product in Oracle E-Business Suite 12.1.1 and 12.2.2. The documented ETRM metadata explicitly states the description as "No longer used" and records that the view is "Not implemented in this database." This designation indicates that the object is a legacy artifact retained for backward compatibility or historical reference rather than an actively supported integration component. In earlier EBS releases, the e-Commerce Gateway relied on a family of "DSNO" views to expose outbound shipping and delivery data to external trading partners and third-party logistics systems. ECE_DSNO_ITEM_DETAILS_V was one such interface view, intended to surface item-level picking and shipment detail. In current 12.1.1 and 12.2.2 environments, the view exists only as a stub: its view text selects thirty NULL literals from the SO_PICKING_LINE_DETAILS table, meaning that even where the object is present, it returns no meaningful column data. Users searching for the column CUSTOMER_REQUESTED_LOT_FLAG—typically in the context of lot-controlled shipping or customer-specified lot reporting—should be aware that this view cannot supply that value in a supported release.

Underlying Base Objects

The documented view text defines ECE_DSNO_ITEM_DETAILS_V over a single base table, SO_PICKING_LINE_DETAILS (aliased SPLD). The WHERE clause restricts rows to picking line details where SPLD.DELIVERY_ID IS NOT NULL and NVL(SPLD.SHIPPED_QUANTITY, 0) > 0, so the driver logic is confined to genuinely shipped picking lines associated with a delivery. Notably, the documented metadata records no referenced base objects under "Owner" or "Referenced base objects," which is consistent with the view having been neutralised: although the FROM clause names SO_PICKING_LINE_DETAILS, the SELECT list projects only NULL values and therefore exposes none of that table's columns. The practical relationship between the view and its nominal base table is consequently severed; SPLD acts only as a row-count filter, not as a source of projected data. No additional joins to inventory, lot, serial, or order tables are documented.

Key Columns

The ETRM column listing enumerates thirty columns, including DELIVERY_ID, DEPARTURE_ID, PICKING_LINE_ID, PICKING_LINE_DETAIL_ID, CONTAINER_ID, MASTER_CONTAINER_ITEM_ID, DETAIL_CONTAINER_ITEM_ID, LOAD_SEQUENCE_NUMBER, CUSTOMER_REQUESTED_LOT_FLAG, REVISION, LOT_NUMBER, SERIAL_NUMBER, SHIPPED_QUANTITY, PICK_SLIP_NUMBER, PL_DETAIL_CONTEXT, and PL_DETAIL_ATTRIBUTE1 through PL_DETAIL_ATTRIBUTE15. The columns mirror the descriptive flexfield structure and descriptive attributes of the picking line detail entity. The column of primary interest to the present search, CUSTOMER_REQUESTED_LOT_FLAG, denotes whether the customer explicitly requested a specific lot for the shipment. Because the view text assigns NULL to every position in the SELECT list, all thirty columns—including CUSTOMER_REQUESTED_LOT_FLAG—evaluate to NULL in installations where the object is present. The column names are therefore structurally documented but functionally inert.

Common Use Cases and Queries

The intended historical use case was outbound e-Commerce Gateway extraction of shipment detail, including customer-requested lot information, for transmission to trading partners. In supported 12.1.1 and 12.2.2 environments this use case is no longer served by ECE_DSNO_ITEM_DETAILS_V. A representative query demonstrates the limitation:

• SELECT delivery_id, picking_line_detail_id, customer_requested_lot_flag FROM ece_dsno_item_details_v; — returns rows (subject to the SPLD filter) with NULL in every selected column.
• SELECT COUNT(*) FROM ece_dsno_item_details_v; — may return a row count derived from shipped picking line details, but no usable attribute data.

For current requirements involving customer-requested lots, developers should query SO_PICKING_LINE_DETAILS directly or use the supported outbound interface views and concurrent programs delivered with the e-Commerce Gateway in the target release. Relying on ECE_DSNO_ITEM_DETAILS_V for CUSTOMER_REQUESTED_LOT_FLAG will produce null results and should be avoided in any customisation, report, or interface built on Oracle EBS 12.1.1 or 12.2.2.