Results for “revision_no”

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

Overview

PO_PURCHASE_ORDER_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite Purchasing (PO). It exposes a flattened, denormalized representation of standard purchase orders and blanket purchase agreement releases, combining header, line, shipment, distribution, vendor, buyer, and ship-to location attributes into a single query surface. The view is defined as a UNION ALL of two branches. The first branch returns approved STANDARD purchase orders; the second branch returns approved releases created against BLANKET agreements. Because the view spans both document families, it is frequently used in purchasing reports, supplier-facing extracts, and downstream interface programs that require a consolidated purchase order and release listing without joining the underlying transactional tables directly.

In Oracle EBS 12.1.1 and 12.2.2, the view remains a read-only, non-materialized database object. It carries no maintenance or DML responsibility; all columns are derived at query time from the base purchasing tables. The object is validated as VALID in the APPS schema.

Underlying Base Objects

The view is defined over purchasing, human resources, and supplier tables, several of which are synonyms for the corresponding _ALL base tables. The documented referenced base objects are: PO_HEADERS (synonym to PO_HEADERS_ALL), PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL, PO_RELEASES and PO_RELEASES_ALL, PO_VENDORS (view), PER_PEOPLE_F (view), HR_LOCATIONS (view), and the HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages. In the view text, the standard branch joins PO_HEADERS to PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL, PO_VENDORS, HR_LOCATIONS, and PER_PEOPLE_F. The release branch performs an equivalent join across PO_HEADERS_ALL, PO_RELEASES, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL, PO_VENDORS, HR_LOCATIONS, and PER_PEOPLE_F. The two branches are combined with UNION.

Key Columns

• PO_NO — SEGMENT1 of PO_HEADERS, the purchase order or agreement number.
• RELEASE_NO — In the standard branch this is TO_NUMBER of an empty string (NULL); in the release branch it is POR.RELEASE_NUM. This column is the basis for the "release_no" search and is populated only for blanket release rows.
• PO_DATE — Creation date of the header or release, depending on branch.
• BUYER_NAME — Full name of the purchasing agent from PER_PEOPLE_F.
• VENDOR_NAME — Supplier name from PO_VENDORS.
• REVISION_NUM, TYPE_LOOKUP_CODE, CURRENCY_CODE — Document revision, document type (STANDARD or RELEASE), and ordering currency.
• LINE_NUM, ITEM_DESCRIPTION, UNIT_MEAS_LOOKUP_CODE — Line-level description and unit of measure.
• PRICE_OVERRIDE, QUANTITY, QUANTITY_CANCELLED, QUANTITY_RECEIVED, QUANTITY_BILLED — Shipment pricing and quantity tracking values.
• LOCATION_CODE — Ship-to location code from HR_LOCATIONS.
• QUANTITY_ORDERED, QUANTITY_CANCELLED — Distribution-level ordered and cancelled quantities.
• ORG_ID — Operating unit identifier for multi-org security filtering.

Common Use Cases and Queries

The view supports purchasing analysis, supplier reporting, and reconciliation of ordered, received, and billed quantities at PO or release level. A common query filters on a specific purchase order or release:

• Retrieve a PO and its releases: SELECT PO_NO, RELEASE_NO, PO_DATE, BUYER_NAME, VENDOR_NAME, LINE_NUM, QUANTITY, QUANTITY_RECEIVED FROM PO_PURCHASE_ORDER_V WHERE PO_NO = :p_po_number AND ORG_ID = :p_org_id ORDER BY RELEASE_NO NULLS FIRST, LINE_NUM;
• List all releases for a blanket agreement: SELECT PO_NO, RELEASE_NO, PO_DATE, BUYER_NAME, VENDOR_NAME FROM PO_PURCHASE_ORDER_V WHERE PO_NO = :p_blanket AND RELEASE_NO IS NOT NULL AND ORG_ID = :p_org_id;
• Order versus receipt analysis: SELECT PO_NO, LINE_NUM, SUM(QUANTITY_ORDERED), SUM(QUANTITY_RECEIVED) FROM PO_PURCHASE_ORDER_V WHERE ORG_ID = :p_org_id GROUP BY PO_NO, LINE_NUM;
• Supplier activity extract: SELECT VENDOR_NAME, COUNT(DISTINCT PO_NO) FROM PO_PURCHASE_ORDER_V WHERE ORG_ID = :p_org_id GROUP BY VENDOR_NAME;

Because ORG_ID is exposed, queries should always apply operating unit security predicates to remain consistent with EBS multi-org access rules. Since the view is defined on transactional tables without indexed helper columns, high-volume extracts may benefit from additional selective predicates such as PO_NO or PO_DATE.