Search Results quant_uom




Overview
Explore in AI Chat

Overview

APPS.PO_ECX_LINE_V is a purchasing-line extraction view that presents a flattened, reporting-friendly projection of blanket and planned purchase agreement lines together with their associated releases. Its name reflects its heritage as part of the ECX ("Exchange") family of objects used to feed Oracle iSupplier Portal and related XML/EDI integrations, but in practice the view is widely queried as a general-purpose source for agreement line detail. The view is owned by APPS and is available in Oracle E-Business Suite 12.1.1 and 12.2.2.

The view applies a significant amount of business filtering. Only lines whose REVISION_NUM = 0 are returned, cancelled lines (CANCEL_FLAG = 'Y') are excluded, and only lines in an open state (CLOSED_CODE = 'OPEN' or null) are retained. In addition, the header must be of type BLANKET or PLANNED. As a result, the view surfaces currently effective agreement lines rather than a full historical record, which makes it suitable for active sourcing and punchout-style reporting but unsuitable as an audit or archive source.

Underlying Base Objects

Per the ETRM metadata, PO_ECX_LINE_V is defined over the following documented objects: PO_LINES_ARCHIVE_ALL (synonym), PO_HEADERS_ALL (synonym), PO_DISTINCT_RELID_LINEID_V (view), MTL_SYSTEM_ITEMS_B_KFV (view), FINANCIALS_SYSTEM_PARAMS_ALL (synonym), and PO_HAZARD_CLASSES (synonym).

  • PO_LINES_ARCHIVE_ALL supplies the core line attributes — quantity, unit of measure, price, item reference, revision, category, contract, project and task.
  • PO_HEADERS_ALL is joined on PO_HEADER_ID to validate header type and to drive the second UNION ALL branch that returns header-only (non-release) lines.
  • PO_DISTINCT_RELID_LINEID_V links release lines back to their agreement line and supplies the RELEASE_ID; the second branch hard-codes RELEASE_ID as 0.
  • MTL_SYSTEM_ITEMS_B_KFV provides the concatenated item segment (SEGMENT1) via an outer join on INVENTORY_ITEM_ID; the key flexfield view resolves the item number for display.
  • FINANCIALS_SYSTEM_PARAMS_ALL anchors the operating unit and the default inventory organization.
  • PO_HAZARD_CLASSES supplies the hazard class description through an outer join on HAZARD_CLASS_ID.

Key Columns

  • QUANT_UOM — the unit of measure lookup code for the line quantity, sourced from PO_LINES_ARCHIVE_ALL.UNIT_MEAS_LOOKUP_CODE. This is one of the most frequently referenced columns, particularly for quantity/UOM reconciliation.
  • QUANTITY — the ordered or agreed quantity on the line.
  • PO_HEADER_ID, LINE_NUM, RELEASE_ID — the composite identifier for the agreement line and, where applicable, its release.
  • ITEM, ITEMX, DESCRIPTION, ITEMRVX — concatenated item segment, vendor product number, item description and item revision.
  • PRICE, UNIT — unit price and the literal 'UNIT' price basis flag.
  • HAZRDMTL — hazard class indicator.
  • CATEGORYID, CONTRACT, TASKID, PROJECTID — purchasing category and project accounting references.

Common Use Cases and Queries

Typical uses include listing active blanket agreement lines for a supplier, validating UOM consistency, and feeding iSupplier or punchout integrations. Because the view is not organization-secured in the same manner as transactional tables, callers usually add an operating-unit predicate.

SELECT po_header_id, line_num, release_id,
       item, quant_uom, quantity, price
  FROM apps.po_ecx_line_v
 WHERE po_header_id = :p_header_id
 ORDER BY line_num, release_id;

For UOM auditing, grouping by quant_uom across a header quickly exposes lines carrying inconsistent units. Note that the view already restricts to revision 0, open, non-cancelled agreement lines, so no additional status filtering is normally required.