Search Results dd_attribute_category

Overview

APPS.WSH_DSNO_ITEM_DETAILS_V is a seeded, internal Oracle E-Business Suite view owned by the APPS schema and shipped under the FND design data object WSH.WSH_DSNO_ITEM_DETAILS_V. In Oracle EBS 12.1.1 and 12.2.2 it is defined with a view type of "Internal" and holds a status of VALID in a standard installation. The view exposes item-level delivery detail information as used by the Warehouse Management and shipping modules, particularly the Delivery Sourcing / DSNO (Deliver Sourced Notifications/Orders) processing used in outbound logistics and shipping integration flows. It consolidates delivery identifiers, container and container-instance references, serial and lot information, shipped quantities, and the descriptive flexfield (DFF) attribute segments attached to both delivery details and their associated transfer pricing attributes.

The object carries an explicit Oracle warning that it is intended for internal use only and that Oracle Corporation does not support direct access to applications data through it except from standard Oracle Applications programs. It is therefore not documented as an end-user reporting interface, though it is frequently encountered by technical consultants performing data investigation.

Underlying Base Objects

The documented view metadata lists four referenced base objects: WMS_EPC (SYNONYM), WSH_DELIVERY_ASSIGNMENTS_V (VIEW), WSH_DELIVERY_DETAILS (SYNONYM), and WSH_SERIAL_NUMBERS (SYNONYM). The view joins delivery-assignment information from the delivery assignments view, delivery detail rows from WSH_DELIVERY_DETAILS, serial number information from WSH_SERIAL_NUMBERS, and EPC (Electronic Product Code) data from the WMS_EPC synonym. This combination supports the need to correlate a delivery assignment, its container hierarchy, its shipped items, and the serial/EPC identifiers attached to those items within a single queryable structure.

Key Columns

• DELIVERY_ID, DELIVERY_ASSIGNMENT_ID, DELIVERY_DETAIL_ID — Core delivery and line-level identifiers that link the row back to the delivery and its assignment.
• CONTAINER_INSTANCE_ID, MASTER_CONTAINER_ITEM_ID, DETAIL_CONTAINER_ITEM_ID, LOAD_SEQUENCE_NUMBER — Container and load-positioning data describing how items are packed and loaded.
• LOT_NUMBER, REVISION, FROM_SERIAL_NUMBER, TO_SERIAL_NUMBER, EPC — Item identification, lot/revision control, and the serial or EPC range covered.
• SHIPPED_QUANTITY, SHIPPING_QUANTITY_UOM, CUSTOMER_REQUESTED_LOT_FLAG — Quantity, unit of measure, and customer lot request indicator.
• DD_ATTRIBUTE_CATEGORY and DD_ATTRIBUTE1 … DD_ATTRIBUTE15 — Descriptive flexfield segments (VARCHAR2(150)) carried from the delivery detail. DD_ATTRIBUTE1, the column referenced by the user's search term "dd_attribute1", is the first of these fifteen context-sensitive DFF segments.
• DD_TP_ATTRIBUTE_CATEGORY and DD_TP_ATTRIBUTE1 … DD_TP_ATTRIBUTE15 — A parallel set of flexfield segments (VARCHAR2(240)) representing the transfer pricing attribute group.

Common Use Cases and Queries

Typical technical scenarios include verifying which DFF values were captured against a shipped delivery detail, reconciling serial and EPC data for a container, and tracing item-level content for a delivery assignment. Because the view is internal and unsupported for direct access, queries should be confined to diagnostics and migration validation.

SELECT delivery_id,
       delivery_detail_id,
       lot_number,
       from_serial_number,
       shipped_quantity,
       dd_attribute_category,
       dd_attribute1
  FROM apps.wsh_dsno_item_details_v
 WHERE delivery_id = :p_delivery_id;

Filtering on a specific flexfield segment, for example the searched column dd_attribute1, allows consultants to identify the population of delivery detail rows carrying a given attribute value:

SELECT delivery_id, delivery_detail_id, dd_attribute_category, dd_attribute1
  FROM apps.wsh_dsno_item_details_v
 WHERE dd_attribute1 IS NOT NULL;

Substituting the numbering (dd_attribute1 through dd_attribute15) or the transfer pricing set (dd_tp_attribute1 through dd_tp_attribute15) adapts the same pattern to other segments. All such queries should be treated as read-only and secondary to standard Oracle shipping reports.