Search Results supplier_order_line_number




Overview
Explore in AI Chat

Overview

The APPS.CLN_PO_ECX_LINE_LOC_ARCH_V view is a denormalized, integration-oriented projection over Oracle Purchasing line and shipment (line location) data. It consolidates attributes from the purchasing document header, line, and shipment levels into a single row structure intended for supplier-facing or exchange-based (ECX) archiving and outbound messaging scenarios. Within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, the view carries an Oracle Internal Use Only designation. Oracle Corporation does not support direct access to application data through this object except from standard Oracle Applications programs. The ETRM metadata classifies the view type as Internal, and the underlying FND design data is registered under the CLN product short name, indicating the object belongs to a specialized application module rather than the core PO schema.

Because the object name contains the ARCH token, its role is best understood as an archival or integration staging structure rather than a general transaction inquiry view. It is typically consumed by concurrent programs, exchange extracts, or supplier collaboration flows that require a flattened representation of purchase order line and shipment information keyed by a supplier order line number.

Underlying Base Objects

The documented dependencies for this view are limited and well defined. It is defined over the following base objects:

  • PO_LINE_LOCATIONS_ALL — the shipment or order line location detail table, providing quantities, dates, and ship-to information.
  • PO_LINES_ALL — the purchase order line table, providing line-level identifiers and numbering.
  • MTL_UNITS_OF_MEASURE_TL — the unit of measure translation table, used to resolve the UOM display value.

These base tables are accessed through APPS synonyms. The view joins them to associate each line location with its parent line and, in turn, with header and release context captured via the PO_HEADER_ID and PO_RELEASE_ID columns. The metadata confirms that CLN_PO_ECX_LINE_LOC_ARCH_V is not referenced by any other database object, establishing it as a leaf or terminal consumption object in the dependency chain.

Key Columns

The view exposes eighteen columns. The most significant include:

Common Use Cases and Queries

This view is most often used to extract supplier-facing line and shipment details for archiving, reconciliation, or exchange messaging. A typical query filters by supplier order line number or by purchase order identifiers.

Retrieve all shipments for a specific supplier order line number:

SELECT supplier_order_line_number,
       line_num,
       shipment_num,
       ordered_quantity,
       uom,
       need_by_date,
       promised_date
FROM   apps.cln_po_ecx_line_loc_arch_v
WHERE  supplier_order_line_number = :p_supplier_order_line_number;

Correlate shipments to a purchase order for integration reconciliation:

SELECT po_header_id,
       po_line_id,
       line_location_id,
       shipment_num,
       ordered_quantity,
       last_accept_date
FROM   apps.cln_po_ecx_line_loc_arch_v
WHERE  po_header_id = :p_po_header_id
ORDER BY line_num, shipment_num;

Because the object is documented as Internal Use Only and is not supported for direct data access outside standard Oracle Applications programs, any query usage should be validated against the corresponding application flow and treated as read-only reporting rather than a supported integration interface.