Results for “po_release_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PO_DISTINCT_RELID_LINEID_V is a dictionary view owned by the APPS schema in Oracle E-Business Suite (validated against 12.1.1 and 12.2.2). It is a lightweight, de-duplicated projection defined over the purchasing line locations table and exposes only two columns: PO_RELEASE_ID and PO_LINE_ID. Its purpose is to provide a fast, distinct mapping of blanket purchase agreement release identifiers to the purchase order lines they reference, filtered so that only rows with a populated PO_RELEASE_ID are returned. Because purchasing release information is normally stored at the shipment/line-location level in PO_LINE_LOCATIONS_ALL, consumers of release data must otherwise scan that much wider table and resolve duplicates themselves. This view centralizes that logic, making it useful for reporting, data extraction, integration, and discovery of which releases exist against which lines without the overhead of the full line-locations record set.

Underlying Base Objects

The view is defined over a single base object, PO_LINE_LOCATIONS_ALL, which is referenced through a synonym in the APPS schema. PO_LINE_LOCATIONS_ALL stores purchase order shipment and distribution scheduling information, including the PO_RELEASE_ID column that links a line location back to its blanket agreement release. The view definition applies DISTINCT to the (PO_RELEASE_ID, PO_LINE_ID) pair, collapsing the multiple shipment rows that can exist per line and release into one row per combination. The WHERE clause, PO_RELEASE_ID IS NOT NULL, restricts output to release-bearing rows, effectively excluding standard purchase orders and unreleased blanket lines. No joins, aggregation functions, or external tables are involved, so the view remains a direct pass-through projection with very low structural complexity.

Key Columns

• PO_RELEASE_ID — The identifier of the blanket purchase agreement release created against a global or local agreement. Non-null by view definition. This is the column users most frequently search on when the term "po_release_id" is used, and it is the primary reason the view exists.
• PO_LINE_ID — The identifier of the purchase order line to which the release applies. Combined with PO_RELEASE_ID, it forms the distinct key returned by the view.

Neither column carries a descriptive attribute; the view deliberately omits headers, quantities, and status fields, so callers needing detail must join back to PO_HEADERS_ALL, PO_LINES_ALL, or PO_LINE_LOCATIONS_ALL.

Common Use Cases and Queries

Typical uses include identifying the lines associated with a given release, enumerating all releases present on a document, and feeding integration or reconciliation processes that require a compact release-to-line mapping. A simple query retrieving all distinct pairs:

SELECT po_release_id, po_line_id FROM apps.po_distinct_relid_lineid_v;

To resolve lines for a specific release:

SELECT po_line_id FROM apps.po_distinct_relid_lineid_v WHERE po_release_id = :release_id;

To enrich the mapping with line detail, join to the lines table:

SELECT v.po_release_id, v.po_line_id, l.item_description
FROM apps.po_distinct_relid_lineid_v v, apps.po_lines_all l
WHERE v.po_line_id = l.po_line_id;

Because the view is a simple DISTINCT projection, it performs predictably and is safe for read-only reporting. Its only limitation is the absence of descriptive columns; users requiring release dates, status, or quantities must obtain them from the base purchasing tables.