Search Results pos_po_rfq_lines_v




Overview
Explore in AI Chat

Overview

POS_PO_RFQ_LINES_V is a dictionary-defined view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the POS product family — iSupplier Portal — and its documented purpose is to display Request for Quotation (RFQ) lines. The view consolidates purchasing line data from the Oracle Purchasing base tables and presents a denormalized, portal-ready record set that the iSupplier Portal uses to render RFQ line information to suppliers.

Because it is a view rather than a table, no data is stored in POS_PO_RFQ_LINES_V. Each query resolves joins across PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, MTL_SYSTEM_ITEMS, and supporting lookup tables at runtime. The object carries a VALID status in the ETRM registry and is exposed as APPS.POS_PO_RFQ_LINES_V. It is widely referenced in custom extensions, XML Publisher reports, and integration extracts where RFQ line detail is required without the overhead of reimplementing the underlying join logic. The column MAX_ORDER_QUANTITY, which users frequently search for, is one of the RFQ-specific quantity constraint fields projected directly from PO_LINES_ALL.

Underlying Base Objects

The view is defined over the following documented base objects and synonyms:

  • PO_LINES_ALL — the primary purchasing line table, aliased POL.
  • PO_LINE_LOCATIONS_ALL — shipment and location detail, aliased PLL.
  • PO_LINE_TYPES — line type definition, aliased PLT.
  • MTL_SYSTEM_ITEMS — master item attributes, aliased MSI.
  • MTL_UNITS_OF_MEASURE — unit of measure class, aliased MUOM.
  • PO_UN_NUMBERS and PO_HAZARD_CLASSES — hazardous material and UN number reference data.
  • FINANCIALS_SYSTEM_PARAMS_ALL — used to resolve the active inventory organization.
  • HR_LOCATIONS_ALL — ship-to location codes, aliased HRL.
  • AP_TERMS — payment terms description, aliased APT.
  • POS_GET — the iSupplier Portal PL/SQL package, supplying ITEM_FLEX_SEG and related utilities.

All joins against PUN, PHC, MUOM, PLT, MSI, and PLL are outer joins, ensuring RFQ lines are returned even when optional reference data is absent. The equality between POL.PO_LINE_ID and PLL.PO_LINE_ID is likewise outer-joined to preserve header-level lines that have no shipment split.

Key Columns

Columns fall into several functional groups. Identifiers include ROWID, PO_HEADER_ID, PO_LINE_ID, LINE_NUM, and LINE_TYPE_ID. Item detail is covered by ITEM_ID, ITEM_FLEX_SEG, ITEM_REVISION, ITEM_DESCRIPTION, CATEGORY_ID, and VENDOR_PRODUCT_NUM. Quantity and price fields include QUANTITY (from PLL), UNIT_PRICE, PRICE_OVERRIDE, MIN_ORDER_QUANTITY, and MAX_ORDER_QUANTITY — the latter two being the ordering constraints exposed for RFQ lines. Shipping data is represented by LINE_LOCATION_ID, SHIP_TO_LOCATION_ID, SHIPMENT_NUM, SHIP_VIA_LOOKUP_CODE, and LOCATION_CODE. Compliance fields include UN_NUMBER and HAZARD_CLASS. The standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) and 15 descriptive flexfield ATTRIBUTE columns support audit and extension requirements.

Common Use Cases and Queries

Typical scenarios include extracting RFQ line constraints for supplier portal displays, validating minimum and maximum order quantities during quote entry, and feeding downstream requisition or sourcing reports. A representative query returning ordering constraints for a given RFQ line follows:

  • SELECT po_header_id, po_line_id, line_num, item_description, min_order_quantity, max_order_quantity FROM apps.pos_po_rfq_lines_v WHERE po_header_id = :p_header_id;
  • SELECT line_num, item_flex_seg, quantity, unit_price, ship_to_location_id FROM apps.pos_po_rfq_lines_v WHERE po_line_id = :p_line_id;
  • SELECT h.po_header_id, l.line_num, l.min_order_quantity, l.max_order_quantity FROM apps.pos_po_rfq_lines_v l, apps.po_headers_all h WHERE l.po_header_id = h.po_header_id AND h.segment1 = :p_rfq_num;

When querying, note that the view exposes RFQ context only through the PO_HEADER_ID link; header-level attributes such as the RFQ number must be joined from PO_HEADERS_ALL. Because the joins involve outer-joined reference tables, filters on MUOM or MSI columns can implicitly convert the outer join to an inner join unless the (+) syntax is preserved in custom SQL. The MAX_ORDER_QUANTITY column is sourced directly from PO_LINES_ALL and returns NULL when no maximum has been defined for the RFQ line.