Search Results unordered_flag

Overview

ICX_PO_LINES_INQ_V is a database view historically associated with Oracle iProcurement (product code ICX) in the Oracle E-Business Suite. According to the ETRM metadata for release 12.2.2, the view is documented as Obsolete and is recorded as Not implemented in this database. This means that in a standard 12.1.1 or 12.2.2 installation the view may not exist at all, or may exist only as a legacy artifact carried forward from earlier releases. The metadata further states that no base objects are documented for the view at 12.2.2.

Functionally, the view was designed to expose purchase order line information for inquiry and reporting purposes, most likely to support the iProcurement storefront and requisition-to-order display logic. The view text shows that it selected from the PO_LINES table (aliased POL) joined to supporting lookup and reference sources such as PO_LINE_TYPES (PLT) and a unit-of-measure source (MUOM). Its naming convention — an _INQ_V suffix — is consistent with iProcurement inquiry views intended for read-only presentation of purchasing data rather than transactional processing. Because the object is obsolete and absent from the database, it should not be relied upon for new development or customizations, and any existing references should be considered for migration to supported alternatives.

Underlying Base Objects

The documented ETRM metadata for 12.2.2 lists no referenced base objects. The view text embedded in the metadata references the following sources by their table aliases:

• POL — the primary PO_LINES table, supplying the majority of the projected columns.
• PLT — a purchase order line type source, contributing LINE_TYPE and ORDER_TYPE_LOOKUP_CODE.
• MUOM — a unit-of-measure source contributing UOM_CLASS.
• ATC — a name source joined by the view, likely an address, contact, or supplier name table.
• POUN — an additional source referenced in the truncated view text.

The presence of inline developer comments in the view definition (for example, "KM REMOVE ABOVE, NOT NEEDED") indicates that the view was modified during patching or development in a manner that left redundant columns in the projection. This is characteristic of legacy or deprecated code and further supports the "Obsolete" classification.

Key Columns

The view projects a broad set of purchase order line attributes from PO_LINES. Notable columns include:

• PO_HEADER_ID, PO_LINE_ID, LINE_NUM, FROM_HEADER_ID, FROM_LINE_ID — identifiers linking the line to its header, parent document, and source document.
• ITEM_ID, ITEM_DESCRIPTION, ITEM_REVISION, VENDOR_PRODUCT_NUM — item and vendor identification details.
• QUANTITY, UNIT_PRICE, LIST_PRICE_PER_UNIT, COMMITTED_AMOUNT, NOT_TO_EXCEED_PRICE — pricing and quantity fields used in amount display and inquiry.
• PRICE_TYPE_LOOKUP_CODE, PRICE_BREAK_LOOKUP_CODE, ALLOW_PRICE_OVERRIDE_FLAG — pricing behavior controls.
• CANCEL_FLAG, CANCEL_DATE, CANCEL_REASON, CLOSED_FLAG, CLOSED_CODE, CLOSED_DATE, CLOSED_REASON — line status and closure tracking.
• REFERENCE_NUM, CONTRACT_NUM, NOTE_TO_VENDOR — free-text and contract references.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF (descriptive flexfield) columns.

The metadata does not document a column named QUOTE_VENDOR_QUOTE_NUMBER; references to vendor quote numbers are generally held in sourcing or quotation tables rather than in this obsolete iProcurement inquiry view. Users searching on that term should examine Oracle Sourcing and quotation-related views instead.

Common Use Cases and Queries

Because the view is documented as obsolete and not implemented, there is no supported use case in 12.1.1 or 12.2.2. Queries against it will fail where the object is absent. A representative legacy query, preserved for reference only, follows:

• SELECT po_header_id, line_num, item_description, quantity, unit_price FROM ICX_PO_LINES_INQ_V WHERE po_header_id = :p_header_id;
• SELECT line_num, cancel_flag, closed_flag, closed_date FROM ICX_PO_LINES_INQ_V WHERE po_line_id = :p_line_id;

For equivalent functionality, use supported PO_LINES and PO_HEADERS-based views or the standard purchasing inquiry forms and reports. Any custom code referencing ICX_PO_LINES_INQ_V should be re-pointed to these supported objects to avoid runtime errors and to remain within Oracle's supported configuration.