Search Results allowed_units_lookup_code




Overview
Explore in AI Chat

Overview

PO_LINES_RFQQT_V is a Purchasing (PO) module view owned by the APPS schema, with a status of VALID in both Oracle EBS 12.1.1 and 12.2.2. The ETRM listing describes it only as "Retrofitted," which indicates it exists primarily to preserve backward compatibility for earlier reference implementations rather than to serve as a current, fully supported interface. The view exposes purchase order line attributes drawn from PO_LINES, augmented with descriptive and classification columns joined from PO_LINE_TYPES, MTL_UNITS_OF_MEASURE, PO_UN_NUMBERS_TL, PO_HAZARD_CLASSES_TL, and MTL_SYSTEM_ITEMS. Because it surfaces descriptive fields such as unit of measure class, line type, hazard class, UN number, purchase basis, and matching basis, it is suited to read-only reporting and integration extracts rather than transactional processing.

Underlying Base Objects

The view is defined over seven referenced synonym objects plus one package. The driving table is PO_LINES (aliased POL), which supplies the core transactional columns. Descriptive data is joined in as follows:

All joins except the MTL_SYSTEM_ITEMS and FINANCIALS_SYSTEM_PARAMS_ALL references are written as outer joins using the (+) operator, ensuring that a PO line is returned even when its line type, UOM, UN number, or hazard class is not populated. The package PJM_PROJECT is invoked in the select list through the functions ALL_PROJ_IDTONUM and ALL_TASK_IDTONUM to convert PROJECT_ID and TASK_ID into their external numeric representations.

Key Columns

The view exposes the standard PO_LINES primary and foreign keys, including PO_HEADER_ID, PO_LINE_ID, LINE_NUM, LINE_TYPE_ID, ITEM_ID, ITEM_REVISION, CATEGORY_ID, ORG_ID, FROM_HEADER_ID, and FROM_LINE_ID. Quantity and pricing columns include QUANTITY, UNIT_PRICE, MIN_ORDER_QUANTITY, MAX_ORDER_QUANTITY, BASE_UOM, BASE_QTY, SECONDARY_UOM, and SECONDARY_QTY. Contract linkage is provided through OKE_CONTRACT_HEADER_ID and OKE_CONTRACT_VERSION_ID. The column most relevant to the user's search, ALLOWED_UNITS_LOOKUP_CODE, is sourced from MTL_SYSTEM_ITEMS and identifies the item-level UOM restriction that governs which units of measure may be entered against the line. Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, PROGRAM_ID, REQUEST_ID, and the fifteen ATTRIBUTE columns) are carried through unchanged from PO_LINES, together with ATTRIBUTE_CATEGORY for descriptive flexfield context.

Common Use Cases and Queries

Typical use is diagnostic or reporting: determining the unit of measure policy applied to ordered items, extracting hazardous material and UN number detail for shipping documentation, or reconciling purchase basis and matching basis against receiving activity. A representative query retrieving the allowed units lookup code alongside line context is:

  • SELECT line_num, item_description, unit_meas_lookup_code, allowed_units_lookup_code, quantity, unit_price FROM po_lines_rfqqt_v WHERE po_header_id = :header_id ORDER BY line_num;

Because the view is marked "Retrofitted," implementations should confirm that its column list remains aligned with the current PO_LINES structure before embedding it in long-term custom code, and should prefer a direct PO_LINES or PO_HEADERS query where the descriptive joins are not required.