Search Results allowed_units_lookup_code

Overview

ICX_PO_RFQ_LINES_V is an APPS-owned database view in Oracle E-Business Suite, classified under the ICX product (Oracle iProcurement). Its documented description is "Request for Quotations Details View." The view exposes line-level purchasing document information — specifically the columns and derived values required to present Request for Quotation (RFQ) line details. In EBS 12.1.1 and 12.2.2 it is a reporting and integration object: it is not maintained by the purchasing transaction APIs and carries no direct DML of its own, but it consolidates PO line, line type, unit of measure, shipment, and shipment destination attributes into a single denormalized row per purchaser line. The view is validated and available for ad hoc queries, custom concurrent programs, BI Publisher data models, and third-party integrations that need RFQ line context.

Users often reach this view when constructing queries around quantity constraints, since columns such as MIN_ORDER_QUANTITY and MAX_ORDER_QUANTITY are exposed directly.

Underlying Base Objects

The view text joins PO_LINES against a set of descriptive and dependent objects; all joins to the descriptive tables are outer joins, which preserves the line rows when reference data is missing.

• PO_LINES (POL) is the driving table and supplies the line identity, item, quantity, hazmat, and order-quantity columns.
• PO_LINE_TYPES (PLT) supplies LINE_TYPE and ORDER_TYPE_LOOKUP_CODE; joined via LINE_TYPE_ID.
• PO_LINE_LOCATIONS (PLL) supplies shipment-level columns such as QUANTITY, SHIPMENT_NUM, PRICE_OVERRIDE, and SHIP_VIA_LOOKUP_CODE.
• MTL_SYSTEM_ITEMS (MSI) and the ICX_UTIL package supply the item flexfield segments and description-update flags; joined on ITEM_ID with the organization resolved against FINANCIALS_SYSTEM_PARAMETERS (FSP).
• MTL_UNITS_OF_MEASURE (MUOM) provides UOM_CLASS; PO_UN_NUMBERS (PUN) and PO_HAZARD_CLASSES (PHC) provide UN_NUMBER and HAZARD_CLASS; HR_LOCATIONS (HRL) provides LOCATION_CODE; AP_TERMS (APT) provides payment terms description.

Key Columns

• PO_HEADER_ID, PO_LINE_ID, LINE_NUM, LINE_TYPE_ID, LINE_TYPE — the document and line identity and classification.
• ITEM_ID, item flexfield segment (via ICX_UTIL.ITEM_FLEX_SEG), ITEM_REVISION, ITEM_DESCRIPTION, CATEGORY_ID, VENDOR_PRODUCT_NUM — item and catalog context.
• MIN_ORDER_QUANTITY and MAX_ORDER_QUANTITY — the minimum and maximum orderable quantities carried on the RFQ line; MAX_ORDER_QUANTITY defines the ceiling beyond which a supplier response or order quantity is not permitted.
• UNIT_MEAS_LOOKUP_CODE, UOM_CLASS — unit of measure and its class.
• QUANTITY, PRICE_OVERRIDE, SHIPMENT_NUM, SHIP_VIA_LOOKUP_CODE, LOCATION_CODE, APT.DESCRIPTION — shipment and delivery detail including destination and terms.
• TAXABLE_FLAG, NOTE_TO_VENDOR, UN_NUMBER, HAZARD_CLASS, FROM_HEADER_ID, FROM_LINE_ID — purchasing and compliance attributes.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, and the 15 ATTRIBUTE flex columns) are exposed for auditing and extensions.

Common Use Cases and Queries

Typical usage is to report RFQ line detail alongside quantity limits, delivery destinations, and units of measure.

• Reviewing order-quantity constraints on RFQ lines.
• Reporting RFQ lines by item, category, or supplier destination.
• Feeding iProcurement-facing extracts with UOM and item description data.

Sample query locating lines by maximum order quantity:

SELECT line_num, item_description, unit_meas_lookup_code, min_order_quantity, max_order_quantity, quantity FROM apps.icx_po_rfq_lines_v WHERE max_order_quantity IS NOT NULL AND po_header_id = :p_header_id ORDER BY line_num;

Sample query listing RFQ lines with shipment information:

SELECT pol.line_num, pol.item_description, pol.quantity, pol.location_code, pol.ship_via_lookup_code, ap.description terms FROM apps.icx_po_rfq_lines_v pol WHERE pol.last_update_date >= :p_since ORDER BY pol.po_header_id, pol.line_num, pol.shipment_num;