Search Results po_release_number




Overview
Explore in AI Chat

Overview

POR_RCV_REQS_ALL_V is an Oracle E-Business Suite (EBS) view owned by the APPS schema and used by Oracle iProcurement (ICX). It consolidates requisition demand that is eligible for receiving into a single, query-friendly structure. The view is documented as VALID in EBS 12.1.1 and 12.2.2, and it belongs to the family of purchasing and receiving views that expose requisition, purchase order, release, and vendor information side by side.

The view joins requisition headers and lines to their downstream purchase order, release, vendor, and distribution records so that receiving and iProcurement pages can display the correct sourcing document for a given requisition line. A prominent characteristic is the combined ORDER_NUM_REL_NUM column, which concatenates the PO number with the release number where a release exists (PO number, a hyphen, then the release number) and simply shows the PO number otherwise.

Underlying Base Objects

According to the ETRM documented metadata, POR_RCV_REQS_ALL_V is defined over the following base objects: PO_REQUISITION_HEADERS, PO_REQUISITION_LINES, PO_REQ_DISTRIBUTIONS, PO_RELEASES_ALL, PO_DISTRIBUTIONS_TRX_V, PO_HEADERS_ALL, PO_LINES_TRX_V, PO_LINE_LOCATIONS_TRX_V, PO_SYSTEM_PARAMETERS, RCV_SHIPMENT_LINES, HR_ALL_ORGANIZATION_UNITS_TL, and OE_ORDER_HEADERS, along with supporting packages such as POR_VIEW_REQS_PKG, PO_CLM_INTG_GRP, and OE_ORDER_IMPORT_INTEROP_PUB.

The view text documented in ETRM shows two branches combined with UNION ALL. The first branch selects from the purchasing tables and joins PO_REQUISITION_HEADERS and PO_REQUISITION_LINES to PO_DISTRIBUTIONS, PO_HEADERS, PO_LINE_LOCATIONS, PO_RELEASES (outer-joined via POLL.PO_RELEASE_ID = POR.PO_RELEASE_ID(+)), and PO_VENDORS. The second branch handles inventory-sourced requisition lines, joining OE_ORDER_HEADERS to the requisition and sourcing vendor details from HR_ALL_ORGANIZATION_UNITS_TL. Rows are filtered so that only open, approved, receivably routed demand is returned: quantity ordered less delivered and cancelled must be greater than zero, approved flag must be 'Y', cancel flag must be 'N', and the closed code must not be one of FINALLY CLOSED, CLOSED, CLOSED FOR RECEIVING, or CANCELLED. Receiving routing is restricted to value 3 and shipment type must be STANDARD, BLANKET, or SCHEDULED.

Key Columns

  • REQUISITION_HEADER_ID / SEGMENT1 / DESCRIPTION / PREPARER_ID — Requisition identity, number, description, and the preparer.
  • TO_PERSON_ID — The deliver-to person on the requisition line.
  • ORDER_NUM_REL_NUM — Formatted PO-and-release identifier built from POH.SEGMENT1 and POR.RELEASE_NUM.
  • PO_NUMBER — Purchase order number (POH.SEGMENT1).
  • ORDER_NUMBER — Order number for internal/inventory-sourced demand.
  • PO_RELEASE_NUMBER — Release number from POR.RELEASE_NUM. This is the column most directly associated with the search term "po_release_number."
  • VENDOR — Vendor name from the PO vendor source, or organization name for inventory-sourced rows.
  • CREATION_DATE — Requisition creation date.
  • GET_REQ_TOTAL — Requisition total returned by POR_VIEW_REQS_PKG.GET_REQ_TOTAL.

Common Use Cases and Queries

The view supports receiving and iProcurement reporting where users need to trace requisition demand to its PO or release. Because releases are outer-joined, PO_RELEASE_NUMBER is NULL for non-release sourcing and populated for release-based sourcing.

Find release-sourced requisition lines:

  • SELECT SEGMENT1, PO_NUMBER, PO_RELEASE_NUMBER, ORDER_NUM_REL_NUM, VENDOR FROM APPS.POR_RCV_REQS_ALL_V WHERE PO_RELEASE_NUMBER IS NOT NULL;

Trace open demand for a specific requisition:

  • SELECT SEGMENT1, PO_NUMBER, PO_RELEASE_NUMBER, VENDOR, CREATION_DATE FROM APPS.POR_RCV_REQS_ALL_V WHERE SEGMENT1 = :req_number;

List all demand prepared by a buyer or deliver-to person by joining TO_PERSON_ID or PREPARER_ID to PER_ALL_PEOPLE_F. Typical consumers include iProcurement receiving pages, buyer worklists, and release-versus-standard sourcing audits. When tuning queries, note that the UNION ALL branches and the multiple transaction views (PO_DISTRIBUTIONS_TRX_V, PO_LINES_TRX_V, PO_LINE_LOCATIONS_TRX_V) mean performance is best with predicates on SEGMENT1, PO_NUMBER, or PO_RELEASE_NUMBER.