Search Results customer_job




Overview
Explore in AI Chat

Overview

APPS.WSH_OPSM_ASN_ITEMS_COMM_V is a shipping-execution view in the Oracle E-Business Suite Shipping (WSH) module. The suffix "OPSM" denotes Oracle Process Manufacturing (OPM) integration, "ASN" denotes Advanced Shipment Notice, "ITEMS" identifies the granularity as shipment line items, and "COMM" indicates it is intended for outbound communication or interface publishing. In release 12.1.1 and 12.2.2 the view is owned by the APPS schema, carries a valid status, and is registered in FND Design Data under the application short name WSH (FND Design Data: WSH.WSH_OPSM_ASN_ITEMS_COMM_V).

Functionally the view flattens shipping data across deliveries, containers, delivery details, sales order references, and item master attributes so that downstream consumers, typically an ASN or shipment-notification interface, can extract a single denormalized row per shipped item. Because it is a view rather than a table, it stores no data; all values are resolved at query time from the underlying WSH, MTL, and PO objects.

Underlying Base Objects

The documented reference list establishes the principal sources from which the view is constructed. Shipping execution data originates from three WSH synonyms: WSH_NEW_DELIVERIES supplies delivery-level attributes; WSH_DELIVERY_DETAILS supplies delivery detail lines; and WSH_DELIVERY_ASSIGNMENTS links deliveries to the source order or line. Item and customer-item information is drawn from MTL_SYSTEM_ITEMS and its key flexfield view MTL_SYSTEM_ITEMS_B_KFV, MTL_CUSTOMER_ITEMS, MTL_ITEM_FLEXFIELDS, and MTL_CROSS_REFERENCES_VL, which provides manufacturer and supplier part cross-references. Organization context comes from MTL_PARAMETERS, commodity classification from MTL_COMMODITY_CODES, and hazardous-material attributes from PO_HAZARD_CLASSES. The join graph therefore spans Inventory, Shipping, Purchasing, and Order Management reference data, which explains why the view exposes both inventory-native attributes (lot and serial control codes, weights, volumes) and order-native attributes (sales order number, ordered quantity, unit list price).

Key Columns

The column list is broad and can be grouped by function. Transaction identifiers include DELIVERY_ID, CONTAINER_INSTANCE_ID, DELIVERY_DETAIL_ID, ITEM_ID, ORDER_HEADER_ID, ORDER_LINE_ID, and ATO_LINE_ID. Commercial references include SALES_ORDER_NUMBER, CUST_PO_NUMBER, SOLDTO_CUSTOMER_ID, SOLDTO_CONTACT_ID, CUSTOMER_ITEM_ID, CUSTOMER_PART_NUMBER, and SUPPLIER_PART_NUMBER. Quantities and pricing include SHIPPED_QUANTITY, ORDERED_QUANTITY, CANCELLED_QUANTITY, UNIT_LIST_PRICE, and the related UOM columns ITEM_UOM_CODE_INT and ORDER_QUANTITY_UOM_INT. Physical characteristics include NET_WEIGHT, WEIGHT_UOM_CODE, VOLUME, and VOLUME_UOM_CODE.

Of particular interest to users searching for "customer_job" is the presence of CUSTOMER_JOB (VARCHAR2, 50), a customer-specific production job reference commonly populated for make-to-order and OPM-regulated shipments. It sits alongside closely related fields CUSTOMER_PRODUCTION_LINE, CUST_PRODUCTION_SEQ_NUM, and CUSTOMER_MODEL_SERIAL_NUMBER, all of which support customer-defined production tracking. Serialization and lot control are exposed through SERIAL_NUMBER_CONTROL_CODE, LOT_CONTROL_CODE, and SERIAL_TYPE, while OPSM_INTEGRATED_FLAG identifies records that originated under OPM integration. Hazard information, where applicable, is surfaced via HAZARDOUS_MATERIAL_CODE_INT, HAZARD_CLASS_INT, and HAZARD_CLASS_DESCRIPTION.

Common Use Cases and Queries

The view is most frequently queried to build or reconcile ASN extracts, to report shipment contents by customer job or production line, and to feed external logistics or regulatory systems. A typical query retrieves shipment detail filtered by customer job:

  • SELECT delivery_id, sales_order_number, customer_job, customer_part_number, shipped_quantity, item_uom_code_int, shipment_confirmed_date FROM apps.wsh_opsm_asn_items_comm_v WHERE customer_job = :p_customer_job;
  • SELECT sales_order_number, cust_po_number, ordered_quantity, shipped_quantity, ordered_quantity - shipped_quantity AS open_quantity FROM apps.wsh_opsm_asn_items_comm_v WHERE order_line_id = :p_line_id;
  • SELECT delivery_id, container_instance_id, item_id, lot_control_code, serial_number_control_code, opsm_integrated_flag FROM apps.wsh_opsm_asn_items_comm_v WHERE opsm_integrated_flag = 1;

Because the view joins numerous base objects, restrictive predicates (delivery, order, item, or customer job) are strongly advised to limit execution cost. WHERE clauses on CUSTOMER_JOB, SALES_ORDER_NUMBER, or DELIVERY_ID leverage the primary selection paths, while filters on hazard or commodity columns should be applied after the driving shipping keys are supplied.