Results for “note_to_vendor”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PO_ECX_LINE_V is an APPS-owned database view in the Oracle E-Business Suite Purchasing (PO) module. It presents a denormalized, reporting-oriented projection of purchasing document lines — combining purchase order, blanket, and planned order line data with inventory item attributes and hazardous material classification. The view is a core component of the ETRM (E-Business Suite Technology Reference Model) data extraction layer, designed to flatten the complex master-detail relationships of the Purchasing schema into a single, query-friendly row set suitable for XML Publisher reports, Oracle Discoverer workbooks, and interface extractions.

The naming prefix "ECX" denotes its association with the E-Business Suite Extensible Common eXtract / XML Publisher bridge framework, indicating the view was built for extraction and reporting rather than transactional processing. The view is documented as VALID in the ETRM 12.2.2 repository and is also present in 12.1.1 environments.

Underlying Base Objects

The ETRM metadata lists the following referenced base objects:

• PO_LINES_ARCHIVE_ALL (SYNONYM) — the primary source of line-level purchasing data, including quantity, unit price, item references, and hazard class identifiers.
• PO_HEADERS_ALL (SYNONYM) — supplies header context and drives the document-type filter, restricting output to BLANKET and PLANNED documents in the first UNION branch.
• PO_DISTINCT_RELID_LINEID_V (VIEW) — a helper view resolving the distinct relationship between release identifiers and line identifiers, used to populate RELEASE_ID.
• PO_HAZARD_CLASSES (SYNONYM) — provides the HAZARD_CLASS descriptive value joined (outer-joined) on HAZARD_CLASS_ID.
• MTL_SYSTEM_ITEMS_B_KFV (VIEW) — the key flexfield view over inventory items, supplying the concatenated SEGMENT1 item number.
• FINANCIALS_SYSTEM_PARAMS_ALL (SYNONYM) — supplies the operating-unit inventory organization parameter used to reconcile item organization context.

The view body is a UNION ALL of two similar queries: one for blanket/planned agreement lines with releases, and one for standalone lines. Both enforce revision number 0, exclude cancelled lines, and restrict to open (or null) closed codes.

Key Columns

• PO_HEADER_ID, LINE_NUM, RELEASE_ID — the document/line/release composite key.
• QUANTITY, QUANT_UOM, PRICE, UNIT — pricing and quantity metrics, with UNIT hard-coded to 'UNIT'.
• ITEM, ITEMX, DESCRIPTION, ITEMRVX — item flexfield segment, vendor product number, description, and item revision.
• HAZRDMTL — the HAZARD_CLASS value from PO_HAZARD_CLASSES, the column most directly relevant to searches for po_hazard_classes.
• CATEGORYID, CONTRACT, TASKID, PROJECTID — purchasing category and project-related references.
• NOTE_TO_VENDOR — the line-level vendor note.

Common Use Cases and Queries

The view is typically queried to extract purchasing agreement and planned order line details for reporting, or to audit hazardous material classification on ordered items.

SELECT po_header_id, line_num, item, description, hazardmtl
FROM   apps.po_ecx_line_v
WHERE  hazardmtl IS NOT NULL
ORDER  BY po_header_id, line_num;

A second common pattern joins the view to organizational or category dimensions to build spend and sourcing extracts:

SELECT categoryid, SUM (quantity * price) total_value
FROM   apps.po_ecx_line_v
GROUP  BY categoryid;

Because the view already resolves item flexfields, hazardous class descriptions, and release/line relationships, it eliminates the need for consumers to replicate these joins against PO_LINES_ARCHIVE_ALL, MTL_SYSTEM_ITEMS_B_KFV, and PO_HAZARD_CLASSES directly, making it well suited to ETRM-based extraction and integration programs.