Search Results header_fob_lookup_code




Overview
Explore in AI Chat

Overview

PO_LINES_INQ_V is a Purchasing (PO) inquiry view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. As its name and the documented description ("Retrofitted") indicate, it is a denormalized, read-only projection over the purchasing line model, engineered to support inquiry and reporting screens rather than transactional Data Manipulation Language operations. The view flattens data from PO_LINES_ALL, PO_LINE_TYPES, PO_HEADERS_ALL, unit-of-measure and hazard-class reference tables, and vendor/contact/site objects into a single row shape that can be queried without repeated joins by Oracle Forms inquiry blocks, concurrent report programs, and external integrations.

The "Retrofitted" designation reflects that the view originates from an earlier release lineage and was carried forward for backward compatibility. Consequently, columns retain legacy naming, and several positional expressions in the view text remain intentionally blank or NULL placeholders (documented as the terminal ", NULL , NULL , NULL ," sequence), preserving column ordinals relied upon by historical consumer code.

Underlying Base Objects

ETRM metadata for 12.2.2 lists the following referenced objects: AP_TERMS, FND_GLOBAL (package), GL_DAILY_CONVERSION_TYPES, HR_ALL_ORGANIZATION_UNITS_TL, HR_LOCATIONS_ALL_TL, MTL_UNITS_OF_MEASURE, PO_DOCUMENT_TYPES_ALL_B, PO_DOCUMENT_TYPES_ALL_TL, PO_GA_ORG_ASSIGNMENTS, PO_HAZARD_CLASSES_TL, PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_LINE_TYPES, PO_REQUISITION_LINES_ALL, PO_SYSTEM_PARAMETERS, PO_UN_NUMBERS_TL, PO_VENDORS, PO_VENDOR_CONTACTS, and PO_VENDOR_SITES_ALL.

PO_LINES_ALL is the primary driving table; the view exposes columns such as PO_LINE_ID, PO_HEADER_ID, LINE_NUM, ITEM_ID, UNIT_PRICE, QUANTITY, and all fifteen ATTRIBUTE columns. PO_LINE_TYPES supplies LINE_TYPE and ORDER_TYPE_LOOKUP_CODE. MTL_UNITS_OF_MEASURE contributes the UOM_CLASS. PO_HAZARD_CLASSES_TL supplies HAZARD_CLASS through header-context joins, and PO_UN_NUMBERS_TL provides UN_NUMBER. Vendor and site attribution derives from PO_VENDORS, PO_VENDOR_CONTACTS, and PO_VENDOR_SITES_ALL, while AP_TERMS supports payment-term resolution. PO_SYSTEM_PARAMETERS is referenced essentially to supply organizational purchasing defaults — notably the operating unit context used to validate the base-organization security on each line — rather than to expose its columns directly. FND_GLOBAL supplies session context values (org_id, user_id, responsibility_id). Because most base objects are synonyms, all access is resolved within APPS.

Key Columns

The view exposes nearly the entire PO_LINES_ALL attribute set. Identity and structural keys include PO_LINE_ID, PO_HEADER_ID, LINE_NUM, FROM_HEADER_ID, FROM_LINE_ID, LINE_TYPE_ID, and REFERENCE_NUM. Commercial columns include UNIT_PRICE, LIST_PRICE_PER_UNIT, MARKET_PRICE, NOT_TO_EXCEED_PRICE, COMMITTED_AMOUNT, MIN_RELEASE_AMOUNT, MIN_ORDER_QUANTITY, and MAX_ORDER_QUANTITY.

Quantity and status semantics are notable: QUANTITY carries the ordered amount, while QUANTITY_COMMITTED tracks committed releases. CANCEL_FLAG is wrapped with DECODE so that 'I' (inactive) surfaces as NULL; CLOSED_CODE defaults to 'OPEN'; FIRM_STATUS_LOOKUP_CODE defaults to 'N'; and USER_HOLD_FLAG defaults to 'N' through NVL. OUTSIDE_OPERATION_FLAG is likewise NVL-defaulted to 'N'. Dates include CREATION_DATE, CANCEL_DATE, FIRM_DATE, CLOSED_DATE, and LAST_UPDATE_DATE. Descriptive columns include ITEM_DESCRIPTION, VENDOR_PRODUCT_NUM, NOTE_TO_VENDOR, and ATTRIBUTE_CATEGORY plus ATTRIBUTE1 through ATTRIBUTE15.

Common Use Cases and Queries

Typical scenarios include line-level purchasing inquiry screens, open-commitment and backlog reporting, price-variance analysis, and integration extracts where a flattened line row avoids joining PO_LINES_ALL to line types, UOM classes, and vendor lookup tables.

Sample query for open, uncancelled lines against a header:

  • SELECT po_line_id, line_num, item_description, quantity, unit_price, unit_meas_lookup_code, closed_code, user_hold_flag FROM apps.po_lines_inq_v WHERE po_header_id = :p_header_id AND cancel_flag IS NULL AND closed_code = 'OPEN';
  • SELECT line_type, order_type_lookup_code, COUNT(*) FROM apps.po_lines_inq_v WHERE creation_date >= TRUNC(SYSDATE) - 30 GROUP BY line_type, order_type_lookup_code;
  • SELECT po_header_id, line_num, item_id, quantity, quantity_committed, committed_amount FROM apps.po_lines_inq_v WHERE quantity_committed < quantity ORDER BY po_header_id, line_num;

Because the view references PO_SYSTEM_PARAMETERS and FND_GLOBAL, queries executed under a responsibility with operating-unit context enforce multi-org security on the underlying lines; results are therefore restricted to the active organization. No documented modification privileges exist, and all access should be treated as read-only.