Search Results pofv_quotation_lines




Overview
Explore in AI Chat

Overview

POFV_QUOTATION_LINES is an APPS-owned database view in the Oracle E-Business Suite Purchasing (PO) module. It exposes the line-level detail of supplier quotations — PO headers and lines whose header TYPE_LOOKUP_CODE is 'QUOTATION' — joined to the descriptive attributes required to render a quotation line in a user-facing or reporting context. The view is marked VALID and is documented in ETRM as "Retrofitted," indicating it was introduced or regenerated to support the Oracle EBS 12.1.1 / 12.2.2 code line rather than being part of the original 11i object set.

Because a quotation in Oracle Purchasing is stored in the same PO_HEADERS_ALL and PO_LINES_ALL tables as a standard purchase order, the distinction between the two document families is carried entirely by the header type lookup. POFV_QUOTATION_LINES encapsulates that distinction and supplies the decoded, denormalized attributes — line type, organization name, unit of measure description, project and task names, hazard class, and UN number — that a raw PO_LINES_ALL query cannot provide without multiple joins. Its role is therefore primarily reporting and integration-facing: it presents quotation lines in a form suitable for OBIEE/BI Publisher extracts, custom concurrent programs, and interface queries.

Underlying Base Objects

The view is defined over fourteen documented base objects, all referenced through APPS synonyms and all residing in the PO, INV, HR, and PA schemas:

The joins are predominantly outer joins ((+) syntax), preserving quotation lines even when item, revision, category, project, task, or hazard data is absent. Descriptor markers such as '_DF:PO:PO_LINES:QL' and '_KF:INV:MSTK:SI' are embedded as literal columns, identifying the descriptive flexfield and key flexfield contexts associated with the source line.

Key Columns

Common Use Cases and Queries

Typical uses include extracting active quotation lines for supplier price comparison, feeding a quotation-to-order conversion report, and exposing quotation terms to a procurement dashboard. A representative query filters by operating unit and header number:

  • SELECT ql.line_num, ql.segment1, ql.item_description, ql.unit_price, ql.min_order_quantity, ql.max_order_quantity, ql.unit_meas_lookup_code FROM pofv_quotation_lines ql WHERE ql.org_id = :p_org_id AND ql.segment1 = :p_quotation_num ORDER BY ql.line_num;
  • SELECT ql.segment1, ql.line_num, ql.name, ql.line_type, ql.uom_class FROM pofv_quotation_lines ql WHERE ql.creation_date >= :p_since AND ql.last_update_date >= :p_since;
  • SELECT ql.project_id, ql.pj_name, ql.task_name, ql.unit_price FROM pofv_quotation_lines ql WHERE ql.project_id IS NOT NULL;

Because the view is read-only and applies no bind predicates of its own, queries should always constrain ORG_ID or the quotation header to avoid full scans across operating units. For incremental integrations, LAST_UPDATE_DATE supports high-water-mark extraction. As with any Purchasing view, security is governed by the underlying Purchasing document security and MO/operating unit profile settings, not by the view itself.