Results for “soldto_contact_id”

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

Overview

WSH_OPSM_ASN_ITEMS_V is a Shipping Execution (WSH) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. The view consolidates Advance Shipment Notice (ASN) line-level detail for outbound shipping transactions managed by Warehouse Management and Shipping Execution. It is designed to support integration flows and operational reporting where the OPSM (Order Promising and Shipping Management / Supply Chain integration) interface requires ASN item details tied to deliveries, containers, sales orders, and item attributes.

The view aggregates columns from two related component views, combining "common" ASN data with order-specific attributes. This structure allows downstream processes — including outbound EDI 856 transactions, customs documentation, and shipment manifest reporting — to retrieve a unified, line-numbered picture of what is being shipped to each customer.

Underlying Base Objects

The view is defined over two documented base objects:

• WSH_OPSM_ASN_ITEMS_COMM_V (VIEW) — supplies common ASN attributes such as delivery ID, container instance ID, item ID, customer identifiers, quantities, weights, and dimensions.
• WSH_OPSM_ASN_ITEMS_SPECIFIC_V (VIEW) — supplies order-specific attributes including order line number, promise date, and invoice-to organization/contact identifiers.

The two are joined on ORDER_HEADER_ID, SOURCE_CODE, and ORDER_LINE_ID, and the result set is ordered by ORDER_LINE_NUMBER. Because both components are themselves views, the object ultimately resolves to base WSH, OE (Order Management), and inventory tables, but the documented dependency is limited to these two intermediate views.

Key Columns

• DELIVERY_ID / DELIVERY_DETAIL_ID — Identify the shipment and its line detail.
• CONTAINER_INSTANCE_ID — The packing container (LPN) associated with the item.
• ITEM_ID / CUSTOMER_ITEM_ID — Internal and customer-facing item identifiers.
• SOLDTO_CUSTOMER_ID / SOLDTO_CONTACT_ID / DESTINATION_CONT_ID / INVOICE_TO_ORG_ID — Party and contact references for routing and billing.
• ORDER_HEADER_ID / ORDER_LINE_ID / SALES_ORDER_NUMBER / ORDERTYPE / ORDER_LINE_NUMBER — Order context linking the ASN to the originating sales order.
• ORDERED_QUANTITY / CANCELLED_QUANTITY / SHIPPED_QUANTITY / ORDER_QUANTITY_UOM_INT — Quantity measures and unit of measure.
• REQUESTED_DATE / PROMISE_DATE — Scheduled and promised shipment/order dates.
• NET_WEIGHT / WEIGHT_UOM_CODE / VOLUME / VOLUME_UOM_CODE — Physical shipping characteristics.
• LOT_CONTROL_CODE / SERIAL_NUMBER_CONTROL_CODE / SERIAL_TYPE — Lot and serial tracking indicators.
• HAZARD_CLASS_INT / ITEM_DESCRIPTION / DESCRIPTION / PACKING_INSTRUCTIONS — Descriptive and compliance content.
• OPSM_INTEGRATED_FLAG — Indicates OPSM integration status.
• CONCATENATED_SEGMENTS — Flexfield-concatenated account/organization segment value.

Common Use Cases and Queries

Typical scenarios include building EDI ASN extracts, generating packing lists and manifests, and reconciling shipped quantities per order line. A representative query filtering ASN lines for a specific delivery is:

SELECT delivery_id, delivery_detail_id, sales_order_number, order_line_number, item_description, shipped_quantity, order_quantity_uom_int FROM apps.wsh_opsm_asn_items_v WHERE delivery_id = :p_delivery_id ORDER BY order_line_number;

To isolate items still pending OPSM integration:

SELECT sales_order_number, order_line_number, opsm_integrated_flag FROM apps.wsh_opsm_asn_items_v WHERE opsm_integrated_flag = 'N';

Because the view joins two component views on order keys and orders output by line, it is best used with delivery- or order-scoped predicates to avoid unnecessary full scans during high-volume shipping windows.