Search Results transaction_reason




Overview
Explore in AI Chat

Overview

The APPS.POBV_PLAN_PO_LINES view exposes planned purchase order (PO) line information for Oracle E-Business Suite 12.1.1 and 12.2.2 environments. It belongs to the PO – Purchasing product and is documented as a retrofitted view, meaning it was carried forward from an earlier code line to preserve backward compatibility for forms, reports, or integrations that referenced the original object. The view filters strictly on planned documents: the join to PO_HEADERS_ALL restricts results to headers where TYPE_LOOKUP_CODE equals 'PLANNED', thereby excluding standard, blanket, and contract purchase agreements.

Functionally, the view acts as a reporting and integration surface over planned PO lines. Note that it does not expose a SOURCE_DOCUMENT_LINE_ID column despite that being a frequent search term; such a column belongs to requisition-to-order linkage tables, and any consumer looking for document-line lineage must trace it through PO_LINES_ALL or the distribution tables instead. The view also enforces organization security through the predicate '_SEC:PL.ORG_ID' IS NOT NULL and is defined WITH READ ONLY, so it cannot be used as a DML target.

Underlying Base Objects

The view is defined over four base objects, each referenced as a synonym in the APPS schema:

  • PO_LINES_ALL — the primary table, aliased PL, supplying line-level attributes. Joined on PO_HEADER_ID and LINE_TYPE_ID.
  • PO_HEADERS_ALL — aliased PH, supplying header segment and document type. The join filters to TYPE_LOOKUP_CODE = 'PLANNED'.
  • PO_LINE_TYPES — aliased LT, supplying the descriptive line type. This is an outer join (LINE_TYPE_ID(+)), so lines with an unmapped or missing line type are still returned.
  • HR_ALL_ORGANIZATION_UNITS — aliased OP, supplying the operating unit name. Joined on PL.ORG_ID = OP.ORGANIZATION_ID.

The inner joins to PO_HEADERS_ALL and HR_ALL_ORGANIZATION_UNITS mean that a planned line will be suppressed if its header is not typed as PLANNED or if its operating unit is not resolvable.

Key Columns

The view projects a broad set of purchasing attributes, including descriptive flexfield-style lookup expressions embedded as literal strings:

Common Use Cases and Queries

Typical uses include reporting on planned PO lines by operating unit, validating pricing against list or market price, and integrating planned line data into external planning systems.

  • Listing planned lines for an operating unit: 
    SELECT po_header_id, segment1, line_num, item_description, quantity
FROM   apps.pobv_plan_po_lines
WHERE  org_id = :p_org_id
ORDER  BY segment1, line_num;
  • Identifying lines that may be cancelled: 
    SELECT po_line_id, segment1, line_num, cancel_date, closed_code
FROM   apps.pobv_plan_po_lines
WHERE  cancel_date IS NULL
AND    closed_code = 'OPEN';
  • Comparing unit price against list price: 
    SELECT po_line_id, unit_price, list_price_per_unit
FROM   apps.pobv_plan_po_lines
WHERE  unit_price > list_price_per_unit;

Because the view is READ ONLY and subject to organization security, all queries implicitly return only lines the session is authorized to see. Where document-line lineage is required, developers must supplement the view with joins to PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, or requisition linkage tables, as no source-document-line identifier is exposed here.