Results for “order_line_attribute2”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The WSH_DSNO_ITEMS_V view is a Shipping Execution (WSH) dictionary object owned by the APPS schema. It is a consolidation view that exposes line-level item detail for the Delivery Satellite Notification (DSNO) message payload used by Warehouse Management and Shipping Execution integration flows. In Oracle EBS 12.1.1 and 12.2.2, this view serves as the reporting and integration surface through which shipping, order fulfillment, and warehouse personnel retrieve a flattened, business-oriented representation of delivery contents, including order references, quantities, pricing, and customer-facing attributes.

Its role in EBS reporting is to abstract the underlying DSNO communication and specification model into a single queryable structure, allowing functional users and developers to build reports, extracts, and interface programs without joining the constituent WSH delivery detail and specification tables directly. Because it is defined in the APPS schema as a VALID view, it can be used in custom concurrent programs, BI Publisher data models, and Oracle Reports definitions.

Underlying Base Objects

The documented base objects referenced by WSH_DSNO_ITEMS_V are:

• WSH_DSNO_ITEMS_COMM_V (view) — supplies the common transaction columns, such as delivery, container, item, order, and quantity information.
• WSH_DSNO_ITEMS_SPECIFIC_V (view) — supplies specification and pricing/attribute columns, including split linkage, order date type, promise date, and the order line descriptive flexfield segments.
• WMS_DEPLOY (package) — a Warehouse Management System deployment package, referenced as part of the DSNO product integration.
• WSH_ECE_VIEWS_DEF (package) — the E-Commerce Exchange (ECE) view definition package that governs how DSNO outbound views are exposed for XML messaging.

The view text joins the COMM and SPECIFIC sub-views on the delivery detail, line, and item identifiers, producing the union of transactional and specification data required by the DSNO message.

Key Columns

• DELIVERY_ID, DELIVERY_DETAIL_ID, CONTAINER_INSTANCE_ID — identify the delivery, its detail line, and any container (LPN) the item is packed in.
• ITEM_ID, ORDER_HEADER_ID, ORDER_LINE_ID, ATO_LINE_ID — link the shipped item back to the sales order and any associated ATO configuration line.
• CUSTOMER_ITEM_ID, CUSTOMER_PART_NUMBER, SUPPLIER_PART_NUMBER — customer- and supplier-facing item identification.
• SHIPPED_QUANTITY, ORDERED_QUANTITY, CANCELLED_QUANTITY, PACKED_QUANTITY, ITEM_UOM_CODE_INT — the core quantity and unit-of-measure facts.
• REQUESTED_DATE, PROMISE_DATE, ORDER_DATE_TYPE_CODE, SHIPMENT_CONFIRMED_DATE — the shipment and order date context.
• UNIT_LIST_PRICE, UNIT_SELLING_PRICE and the ORDER_LINE_PRICING_CONTEXT/ATTRIBUTE1–10 columns — pricing and pricing flexfield details.
• OPTION_FLAG, COMPONENT_CODE, LINK_TO_LINE_ID, SPLIT_FROM_LINE_ID — configuration and line-splitting lineage.
• ORDER_LINE_CONTEXT with ORDER_LINE_ATTRIBUTE1–15 — the order line descriptive flexfield (DFF) segments.
• HAZARDOUS_MATERIAL_CODE_INT, HAZARD_CLASS_INT, HAZARD_CLASS_DESCRIPTION, COMMODITY_CODE_INT — compliance and trade classification data.

Common Use Cases and Queries

Typical uses include shipment manifest reporting, customer delivery notification extraction, and reconciliation of packed versus shipped quantities. The following sample retrieves shipped item detail for a given delivery:

• SELECT delivery_id, delivery_detail_id, item_id, customer_item_id, shipped_quantity, packed_quantity, item_uom_code_int FROM apps.wsh_dsno_items_v WHERE delivery_id = :p_delivery_id;
• SELECT order_header_id, order_line_id, customer_part_number, requested_date, promise_date, unit_selling_price FROM apps.wsh_dsno_items_v WHERE order_header_id = :p_order_id ORDER BY order_line_id;
• SELECT container_instance_id, container_item_flag, container_type_code_int, hazardous_material_code_int FROM apps.wsh_dsno_items_v WHERE delivery_id = :p_delivery_id AND container_item_flag = 'Y';

Because the view draws on the DSNO common and specific sub-views, consumers should supply selective predicates (delivery or order identifiers) to avoid full scans and should not rely on columns inherited from the flexfield contexts unless those segments are populated for the organization.