Search Results cust_po_line_num




Overview
Explore in AI Chat

Overview

APPS.WSH_OPSM_ASN_ITEMS_SPECIFIC_V is a reporting view owned by the APPS schema and registered under the FND Design Data namespace WSH.WSH_OPSM_ASN_ITEMS_SPECIFIC_V. It exposes line-level order and scheduling attributes used by Oracle E-Business Suite's Order Processing and Shipping Management (OPSM) flows, and in particular by Advanced Shipment Notice (ASN) processing and integration with supplier scheduling / release management. The view consolidates order header, order line, customer cumulative key, and schedule header/line data into a single denormalized projection, making it suitable for outbound interfaces, ASN generation, and concurrent reporting programs that require order and shipment context in one query. Status is documented as VALID in the ETRM repository for both Oracle EBS 12.1.1 and 12.2.2.

The user search term packaging_code_ext corresponds directly to the PACKAGING_CODE_EXT column (VARCHAR2(10)) exposed by this view. This is an externally-supplied packaging classification attribute, typically populated through customer or supplier item cross-reference data and consumed downstream in ASN and logistics messaging.

Underlying Base Objects

The ETRM dependency metadata documents the following referenced base objects, all exposed through synonyms in the APPS schema:

The view therefore serves as a join layer: OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL provide the commercial order structure, while the RLM_* objects add scheduling and demand/cumulative context. Column names ending in _EXT identify externally-sourced extension attributes carried on the schedule lines and cross-reference records.

Key Columns

Common Use Cases and Queries

Typical uses include ASN and shipment notification data extraction, supplier scheduling reports, customer PO release reconciliation, and external integration feeds that require packaging and supplier item attributes. A basic query filtered on packaging code:

  • SELECT ORDER_LINE_ID, ORDER_LINE_NUMBER, PACKAGING_CODE_EXT, SUPPLIER_ITEM_EXT, CUST_PO_RELEASE_NUM, PROMISE_DATE FROM APPS.WSH_OPSM_ASN_ITEMS_SPECIFIC_V WHERE PACKAGING_CODE_EXT = :p_packaging_code;
  • SELECT ORDER_HEADER_ID, ORDER_LINE_ID, SOURCE_CODE, SCHEDULE_REFERENCE_NUM, CUM_START_DATE FROM APPS.WSH_OPSM_ASN_ITEMS_SPECIFIC_V WHERE ORDER_HEADER_ID = :p_header_id;

Because the view performs multiple joins across order and scheduling tables, production queries should always be constrained by identifiers such as ORDER_HEADER_ID, ORDER_LINE_ID, or PACKAGING_CODE_EXT, and combined with appropriate indexes on the underlying base tables to avoid full-scan performance degradation.