Search Results ll_qty




Overview

APPS.JAI_PO_RFQQT_V is an Oracle E-Business Suite internal database view owned by the APPS schema and registered under FND Design Data as JA.JAI_PO_RFQQT_V. The object carries the designation "Oracle Internal Use Only," meaning Oracle Corporation does not support direct access to application data through this view except from standard Oracle Applications programs. Its status is VALID, and it exists under both EBS 12.1.1 and 12.2.2. The view belongs to the JA (Oracle Financials for India / JAI) product family and is oriented toward purchasing document extraction, specifically the RFQ/quotation line data model. It presents a flattened, report-friendly projection of purchasing header, line, and shipment information, joining the three core purchasing tables so that consumers can retrieve quote line details without reconstructing multi-level parent-child relationships themselves. Because the name embeds "PO", "RFQ", and "QT" (quotation), the view is intended for RFQ and quotation reporting rather than transactional processing.

Underlying Base Objects

Per the documented dependency metadata for 12.2.2, APPS.JAI_PO_RFQQT_V references exactly three base objects, all exposed through APPS synonyms:

  • PO_HEADERS_ALL — source of purchasing document header identity (PO_HEADER_ID).
  • PO_LINES_ALL — source of line-level attributes, including line number, item, description, unit of measure, price, and quantity.
  • PO_LINE_LOCATIONS_ALL — source of shipment-level attributes, including shipment number, shipment quantity, shipment UOM, ship-to organization and location, and need-by date.

The dependency listing notes that JAI_PO_RFQQT_V is not referenced by any other database object, confirming it functions as a terminal, consumer-facing view with no downstream dependents inside the database. The join is driven by the standard purchasing foreign-key chain: PO_HEADER_ID links headers to lines, PO_LINE_ID links lines to line locations, and LINE_LOCATION_ID identifies each shipment row.

Key Columns

The view exposes seventeen columns across header, line, and shipment grain. Header and line identifiers (PO_HEADER_ID, PO_LINE_ID, LINE_NUM, ITEM_ID, ITEM_DESCRIPTION) provide document context. Two unit-of-measure columns are significant to the user's search for "ll_uom":

  • L_UOM (VARCHAR2 25) — the line-level unit of measure drawn from PO_LINES_ALL.
  • LL_UOM (VARCHAR2 25) — the line-location (shipment) level unit of measure drawn from PO_LINE_LOCATIONS_ALL. The "LL" prefix denotes line location, so this column reflects the UOM applicable to a specific shipment or schedule row of the line.

Complementing these are L_QTY and LL_QTY (line quantity and shipment quantity), UNIT_PRICE and PRICE_OVERRIDE (the negotiated and overridden price values), SHIPMENT_NUM, SHIP_TO_ORGANIZATION_ID, SHIP_TO_LOCATION_ID, NEED_BY_DATE (stored as VARCHAR2 in this view), and CLOSED_CODE (VARCHAR2 30), which conveys the closure state of the shipment. Because UOM can legitimately differ between the line and the shipment, LL_UOM is the authoritative column when shipment-level precision is required.

Common Use Cases and Queries

Typical uses include RFQ/quotation line reporting, supplier quotation comparisons, shipment-level UOM validation, and India-localization purchasing extracts that feed downstream JAI reports. A representative query retrieving shipment UOM alongside line UOM is:

  • SELECT PO_HEADER_ID, PO_LINE_ID, LINE_NUM, ITEM_DESCRIPTION, L_UOM, LL_UOM, LL_QTY, UNIT_PRICE, SHIP_TO_ORGANIZATION_ID, NEED_BY_DATE FROM APPS.JAI_PO_RFQQT_V WHERE LL_UOM IS NOT NULL;
  • SELECT PO_HEADER_ID, LINE_NUM, LL_UOM, LL_QTY, CLOSED_CODE FROM APPS.JAI_PO_RFQQT_V WHERE CLOSED_CODE = 'OPEN';

Practitioners should note the Oracle Internal Use Only warning: direct querying is discouraged in supported configurations, and custom code relying on this view may be affected by patch or upgrade changes. Where local extension is unavoidable, joining the view back to PO_HEADERS_ALL on PO_HEADER_ID is common to obtain document type and supplier context not exposed by the view itself.