Search Results pofv_plan_po_lines




Overview

POFV_PLAN_PO_LINES is an APPS-owned database view within the Oracle Purchasing (PO) module, valid in both EBS 12.1.1 and 12.2.2. It presents a denormalized, reporting-friendly projection of purchase order line data, combining the base transaction table PO_LINES_ALL with descriptive attributes drawn from headers, items, units of measure, hazard classifications, buyers, and contract references. The view is intended for planning, sourcing, and procurement reporting where consumers require line-level purchasing detail alongside human-readable header, item, and supplier context rather than normalized keys. In 12.2.2 the view is documented as referencing a broad set of base objects including PO_LINES_ALL, PO_HEADERS_ALL, MTL_SYSTEM_ITEMS, MTL_CATEGORIES, HR_ALL_ORGANIZATION_UNITS, PER_PEOPLE_F, and the OKC contracts tables, reflecting its role as a consolidated line-level planning interface.

Underlying Base Objects

The view is defined over PO_LINES_ALL (aliased PL) and PO_HEADERS_ALL (PH), joined to HR_ALL_ORGANIZATION_UNITS (OP) for operating unit name, MTL_CATEGORIES (CT) for category detail, MTL_ITEM_REVISIONS (SI), MTL_UNITS_OF_MEASURE (UM), and MTL_PARAMETERS (MP) for item master and UOM context. Hazard information is sourced from PO_HAZARD_CLASSES (HC) and PO_UN_NUMBERS (UN). Employee attribution (cancelled-by and closed-by) is resolved through PER_PEOPLE_F (CA, CL), which itself depends on HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages. Source document linkage draws on PO_HEADERS_ALL aliased as FH and PO_LINES_ALL aliased as FL through the FROM_HEADER_ID and FROM_LINE_ID columns. Contract information is joined to OKC_K_HEADERS_B (OKH), OKC_K_VERS_NUMBERS_V (OKV), and OKC_K_LINES_B (OKL) via OKE_CONTRACT_HEADER_ID and OKE_CONTRACT_VERSION_ID. Additional dependencies include FINANCIALS_SYSTEM_PARAMS_ALL, MTL_SYSTEM_ITEMS, and PO_LINE_TYPES (LT).

Key Columns

The view exposes core line identifiers (PO_LINE_ID, LINE_NUM, PO_HEADER_ID), header segment (SEGMENT1), and organization context (ORG_ID, OP.NAME). Because the user searched "source_document_number", the relevant columns are FH.SEGMENT1, which carries the segment1 value of the source document header (the source document number), together with FROM_HEADER_ID, FROM_LINE_ID, and FL.LINE_NUM. The view also includes a lookup display column, '_LA:PH.TYPE_LOOKUP_CODE:PO_LOOKUP_CODES:SOURCE DOCUMENT TYPE:DISPLAYED_FIELD', which labels the header type as the source document type. Descriptive fields include ITEM_DESCRIPTION, VENDOR_PRODUCT_NUM, and quantity/pricing columns such as QUANTITY, UNIT_PRICE, LIST_PRICE_PER_UNIT, MARKET_PRICE, and NOT_TO_EXCEED_PRICE. Status and control attributes include CANCEL_FLAG, CLOSED_CODE, CLOSED_DATE, CLOSED_REASON, and NEGOTIATED_BY_PREPARER_FLAG. Contract columns (OKE_CONTRACT_HEADER_ID, OKH.CONTRACT_NUMBER, OKV.MAJOR_VERSION, OKL.LINE_NUMBER) and employee fields (CA.FULL_NAME, CL.FULL_NAME) support sourcing and audit reporting.

Common Use Cases and Queries

Typical usage includes sourcing analysis against contract lines, closed or cancelled line audits, and preparing plan-versus-order reconciliations. A query retrieving the source document number alongside the destination PO line would resemble:

  • SELECT SEGMENT1, LINE_NUM, FROM_HEADER_ID, FROM_LINE_ID, ITEM_DESCRIPTION FROM POFV_PLAN_PO_LINES WHERE SEGMENT1 IS NOT NULL;
  • Correlating contract lines: SELECT CONTRACT_NUMBER, MAJOR_VERSION, LINE_NUMBER, SEGMENT1, LINE_NUM FROM POFV_PLAN_PO_LINES WHERE OKE_CONTRACT_HEADER_ID IS NOT NULL;
  • Auditing closed or cancelled lines: SELECT SEGMENT1, LINE_NUM, CLOSED_CODE, CANCEL_FLAG FROM POFV_PLAN_PO_LINES WHERE CANCEL_FLAG = 'Y';
  • Pricing review: SELECT SEGMENT1, LINE_NUM, QUANTITY, UNIT_PRICE, NOT_TO_EXCEED_PRICE FROM POFV_PLAN_PO_LINES;

Because the view is a standard APPS construct, no responsibility-specific grants are required beyond standard Purchasing access; filters on ORG_ID should be applied to respect operating unit security in multi-org environments.