Search Results po_lines_release_items_v




Overview
Explore in AI Chat

Overview

PO_LINES_RELEASE_ITEMS_V is an APPS-owned database view in the Oracle E-Business Suite Purchasing (PO) module. The ETRM metadata designates it specifically for "10SC ONLY," indicating that its use is restricted to a particular implementation or localization scenario rather than being a general-purpose, cross-module reporting object. In EBS 12.1.1 and 12.2.2 the view maintains VALID status in the APPS schema and exposes a denormalized projection of purchase order lines joined to item and category key flexfield information.

Functionally, the view presents one row per open purchase order line that is tied to an inventory item, combining attributes from PO_LINES with descriptive flexfield concatenated segments for both items and categories. Where an item has been de-supported, the second branch of a UNION ALL returns the same line with null item and revision values while preserving category data. This construction makes the view useful for release-level and blanket agreement line reporting where a human-readable item and category description is required alongside transactional pricing and commitment amounts.

Underlying Base Objects

The view is defined over four documented base objects, all resolved through APPS synonyms: PO_LINES, MTL_SYSTEM_ITEMS_KFV, MTL_CATEGORIES_KFV, and FINANCIALS_SYSTEM_PARAMS_ALL. PO_LINES supplies the transactional line attributes — pricing, quantity, status, and header/line identifiers. MTL_SYSTEM_ITEMS_KFV provides the concatenated key flexfield description of the inventory item through MIS.CONCATENATED_SEGMENTS. MTL_CATEGORIES_KFV supplies the category flexfield concatenation via MCA.CONCATENATED_SEGMENTS, joined on CATEGORY_ID. FINANCIALS_SYSTEM_PARAMS_ALL anchors the item join by supplying the inventory organization, ensuring that the item description reflects the correct organization context.

The join logic enforces several filters: cancelled lines (CANCEL_FLAG = 'N' or null) are excluded, expired lines are filtered out via the expiration date comparison against SYSDATE, and lines with a CLOSED_CODE of 'FINALLY CLOSED' are removed. The item must be non-null and the organization context must match POL.ORG_ID.

Key Columns

Common Use Cases and Queries

Typical applications include item-level line reporting for blanket releases, commitment analysis, and category flexfield-driven analytics. A representative query:

SELECT LINE_NUM, CONCATENATED_SEGMENTS, ITEM_DESCRIPTION, UNIT_PRICE, QUANTITY_COMMITTED
FROM   APPS.PO_LINES_RELEASE_ITEMS_V
WHERE  PO_HEADER_ID = :p_header_id
ORDER BY LINE_NUM;

Because the view already resolves the MTL_CATEGORIES_KFV segments, it is commonly used where report authors searched for that object directly, avoiding a manual join to the category flexfield. Consumers should nevertheless be aware of the "10SC ONLY" designation and verify suitability before adopting it in a general production report or integration.