Search Results po_system_parameters




Overview
Explore in AI Chat

Overview

APPS.PO_LINES_INQ_V is a purchasing inquiry view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes purchase order line information in a denormalized, reporting-ready form. Rather than requiring the caller to join PO_LINES_ALL, PO_LINE_TYPES, PO_HEADERS_ALL, PO_VENDORS, and a dozen ancillary lookup tables, the view pre-joins these objects and applies Oracle's own DECODE and NVL normalization rules. This makes it the preferred access point for inquiry screens (notably the Purchasing "Lines" and "Purchase Order Summary" windows), for Oracle Purchasing's own inquiry logic, and for custom reports and integrations that need line-level PO data without reimplementing Oracle's business-rule transformations.

The view is defined in the APPS schema and is delivered as a read-only construct; it carries no DML semantics of its own. Because it references FND_GLOBAL for organizational and user context, query results can vary by the session's active organization, so it must be executed in an environment where FND_GLOBAL has been initialized (for example, through a concurrent program or an OAF/Forms session).

Underlying Base Objects

The view is defined over a set of synonyms and views owned primarily by APPS. The documented referenced objects include PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_LINE_TYPES, PO_HEADERS_ALL, PO_DOCUMENT_TYPES_ALL_B, PO_DOCUMENT_TYPES_ALL_TL, PO_HAZARD_CLASSES_TL, PO_UN_NUMBERS_TL, PO_REQUISITION_LINES_ALL, PO_GA_ORG_ASSIGNMENTS, MTL_UNITS_OF_MEASURE, PO_VENDORS, PO_VENDOR_SITES_ALL, PO_VENDOR_CONTACTS, AP_TERMS, GL_DAILY_CONVERSION_TYPES, HR_ALL_ORGANIZATION_UNITS_TL, HR_LOCATIONS_ALL_TL, and FND_GLOBAL. Notably, PO_SYSTEM_PARAMETERS is a referenced base object, which is significant: several line attributes surfaced by the view are governed by purchasing system parameters (for example, price override and receipt tolerance behavior) established once per operating unit. The joins to PO_LINE_LOCATIONS_ALL and PO_LINE_TYPES supply scheduling and line-type semantics, while the joins to the vendor and terms objects allow the view to present supplier and payment context alongside each line.

Key Columns

The view exposes a broad column set including PO_HEADER_ID, PO_LINE_ID, LINE_NUM, LINE_TYPE, ORDER_TYPE_LOOKUP_CODE, ITEM_ID, ITEM_DESCRIPTION, ITEM_REVISION, QUANTITY, UNIT_PRICE, LIST_PRICE_PER_UNIT, COMMITTED_AMOUNT, NOT_TO_EXCEED_PRICE, MIN_RELEASE_AMOUNT, UOM_CLASS, UNIT_MEAS_LOOKUP_CODE, VENDOR_ID, SEGMENT1 (the PO number), QUOTE_VENDOR_QUOTE_NUMBER, and REFERENCE_NUM. Status-oriented columns include CLOSED_CODE (defaulted to 'OPEN'), CLOSED_FLAG, CLOSED_DATE, CLOSED_REASON, CANCEL_FLAG (with 'I' converted to NULL), CANCEL_DATE, CANCEL_REASON, USER_HOLD_FLAG (defaulted to 'N'), and FIRM_STATUS_LOOKUP_CODE (defaulted to 'N'). Tolerance and control columns include QTY_RCV_TOLERANCE, OVER_TOLERANCE_ERROR_FLAG, ALLOW_PRICE_OVERRIDE_FLAG, UNORDERED_FLAG, CAPITAL_EXPENSE_FLAG, TAXABLE_FLAG, and FIRM_DATE. The fifteen ATTRIBUTE columns are surfaced for descriptive flexibility.

Common Use Cases and Queries

Typical uses include open-order reporting, buyer/line aging, price-override auditing, and integration extracts. The following sample returns open lines for a given operating unit's requisitioning context:

  • List open PO lines with pricing and status:

    SELECT poh_segment1, line_num, item_description, quantity, unit_price, closed_code, user_hold_flag FROM apps.po_lines_inq_v WHERE closed_code = 'OPEN' AND NVL(user_hold_flag,'N') = 'N';

  • Identify lines assigned to a buyer/organization via PO_GA_ORG_ASSIGNMENTS and FND_GLOBAL context.
  • Extract line data for interface programs keyed on PO_LINE_ID, PO_HEADER_ID, and LAST_UPDATE_DATE.
  • Report quantity and price tolerances that are governed by PO_SYSTEM_PARAMETERS values.

Because the view resolves organization context through FND_GLOBAL and joins many synonym-based tables, it should be queried with an explicit operating unit or driven from a concurrent program, and it should not be used for high-volume DML or as a substitute for the base tables when row-level locking is required.