Search Results hazardous_material_code_int




Overview
Explore in AI Chat

Overview

The APPS.CLN_XML_ITEMS_V view is a component of the Oracle Supply Chain Trading Connector for RosettaNet (CLN) module. It supplies the item-level detail required for the SHIPITEM section of the OAG SHOW_SHIPMENT_005 XML payload, the RosettaNet business message used to communicate shipment contents between trading partners. Rather than storing data, the view reshapes delivery, order, and item master information into a flat, message-oriented result set whose column aliases map directly to the XML tags emitted by the connector.

For users searching on CUSTOMER_PART_NUMBER, this view is the authoritative source. That column is aliased from MTL_CUSTOMER_ITEMS.CUSTOMER_ITEM_NUMBER and carries the buyer's own item identifier as agreed in the customer item cross-reference. It sits alongside SUPPLIER_PART_NUMBER, derived from MTL_ITEM_FLEXFIELDS.ITEM_NUMBER, so both sides of the trading-partner item mapping appear on the same row. The view is defined in the APPS schema and is reported as VALID in both Oracle EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over the following documented objects:

  • MTL_CUSTOMER_ITEMS (synonym) — customer item cross-reference; source of CUSTOMER_PART_NUMBER.
  • MTL_ITEM_FLEXFIELDS (view) — item flexfield description; source of SUPPLIER_PART_NUMBER.
  • WSH_NEW_DELIVERIES, WSH_DELIVERY_ASSIGNMENTS, WSH_DELIVERY_DETAILS (synonyms) — delivery headers, delivery-to-detail assignments, and delivery detail lines that drive shipped quantities, UOMs, lots, serial numbers, and shipping instructions.
  • WSH_DSNO_PACKED_QUANTITY_V (view) — packed quantity per delivery detail.
  • RLM_SCHEDULE_LINES_ALL (synonym) — country of origin, customer item revision, and packaging code.
  • OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL (synonyms) — sales order header and line context, including order number, line number, customer line number, shipment number, and original system document reference.

These nine objects are joined in a single SELECT DISTINCT, producing one row per shipment item line. Delivery detail identifiers link to the sales order line, which in turn links to the customer item and item flexfield records.

Key Columns

Common Use Cases and Queries

The primary use case is troubleshooting or validating the SHIPITEM output of an outbound SHOW_SHIPMENT_005 message. A user asking why a customer part number is missing or incorrect can query the view directly for a given delivery:

  • Locate a customer part number for a shipment: SELECT delivery_id, customer_part_number, supplier_part_number, shipped_quantity FROM cln_xml_items_v WHERE delivery_id = :delivery_id;
  • Search by customer part number to find affected deliveries: SELECT delivery_id, sales_order_num, customer_part_number FROM cln_xml_items_v WHERE customer_part_number = :cpn;
  • Reconcile ordered versus shipped quantities: SELECT sales_order_num, order_line_number, ordered_quantity, shipped_quantity FROM cln_xml_items_v WHERE sales_order_num = :order_number;
  • Audit lot and serial traceability by order: SELECT sales_order_num, customer_part_number, lot_number, customer_model_serial_number FROM cln_xml_items_v WHERE sales_order_num = :order_number;

Because a missing CUSTOMER_PART_NUMBER almost always indicates an absent row in MTL_CUSTOMER_ITEMS for the item and customer combination, these queries should be paired with a check of the customer item cross-reference. All queries should be run against the APPS schema, or a synonym granted to the reporting user.