Search Results unordered_flag




Overview
Explore in AI Chat

Overview

PO_LINES_TRX_V is a public Oracle E-Business Suite view owned by the APPS schema and classified under the PO (Purchasing) product family. In the ETRM 12.2.2 documentation it carries a VALID status across the 12.1.1 and 12.2.2 release lines. As its description states, it is a view on the PO_LINES table. Its purpose is to expose purchasing document line information in a transaction-oriented form, meaning the columns are oriented toward transactional attributes of a purchase order or blanket agreement line rather than toward a pure master-data listing.

The view is intended for reporting and integration scenarios where line-level purchasing data must be read directly, without navigating the full base table. Because it is a view rather than a table, it carries no independent storage, no triggers, and no writable semantics; it is a read-only projection used by concurrent programs, Oracle Reports, BI Publisher data templates, and custom SQL executed against the APPS schema. It is particularly relevant for extracting quantity, pricing, commitment, receiving tolerance, and lifecycle flag information for purchase order lines.

Underlying Base Objects

According to the documented view metadata, PO_LINES_TRX_V is defined over two referenced base objects:

  • PO_LINES (SYNONYM) — the primary driving object. PO_LINES holds one row per purchase order line, including the line number, item, category, unit of measure, quantity, unit price, and the various status and control flags.
  • PO_DISTRIBUTIONS_ALL (SYNONYM) — the purchasing distribution object, which stores the accounting and charge distribution detail for each line.

The synonym layer means the view resolves to the underlying PO schema tables through APPS-owned synonyms, so application code should always reference the view as APPS.PO_LINES_TRX_V rather than qualifying the physical tables directly. Because the view's SELECT list closely mirrors the column set of PO_LINES, the join to distributions is used to shape the result toward transactional reporting completeness rather than to duplicate line rows.

Key Columns

The projection exposes a broad set of purchasing attributes. The most frequently used columns include:

Common Use Cases and Queries

The view is commonly used to report open committed quantities, to reconcile ordered versus received quantities, and to feed downstream integrations such as supplier portals or data warehouses. A representative query for open, non-cancelled lines within an operating unit is:

  • SELECT PO_LINE_ID, PO_HEADER_ID, LINE_NUM, ITEM_ID, QUANTITY, UNIT_PRICE, COMMITTED_AMOUNT, CLOSED_FLAG, ORG_ID FROM APPS.PO_LINES_TRX_V WHERE ORG_ID = :p_org_id AND NVL(CANCEL_FLAG,'N') = 'N' AND NVL(CLOSED_FLAG,'N') = 'N';
  • SELECT l.PO_HEADER_ID, l.LINE_NUM, l.ITEM_DESCRIPTION, l.QUANTITY, l.UNIT_PRICE FROM APPS.PO_LINES_TRX_V l WHERE l.LAST_UPDATE_DATE >= TRUNC(SYSDATE) - 30 ORDER BY l.PO_HEADER_ID, l.LINE_NUM;

Because the view is read-only, tuning efforts should focus on the underlying PO_LINES and PO_DISTRIBUTIONS_ALL indexes, and queries should always filter by ORG_ID and by a valid date or identifier range to avoid full scans.