Search Results po_releases_all




Overview
Explore in AI Chat

Overview

The PO_RELEASES_ALL table is the central repository for all purchase order release records within Oracle E-Business Suite Purchasing (PO) modules, including versions 12.1.1 and 12.2.2. It represents the contractual agreements for the delivery of goods or services against a master blanket purchase agreement (PO_HEADERS_ALL). Each record in this table defines a specific, scheduled delivery or a defined quantity of items from the overarching contract. The table's multi-org structure, indicated by the "_ALL" suffix, stores data for all operating units, with access controlled by the MOAC (Multi-Org Access Control) security profile. Its role is critical for managing procurement schedules, tracking deliveries, and integrating with receiving, inventory, and financial accounting processes.

Key Information Stored

The table's primary key is PO_RELEASE_ID, a unique system-generated identifier. A significant composite unique key (PO_RELEASES_UK1) enforces business logic by combining PO_HEADER_ID (linking to the parent blanket agreement) and RELEASE_NUM (the sequential release number). Other essential columns include AGENT_ID, which identifies the purchasing agent responsible for the release, and HOLD_BY, which can place the release on a purchasing hold. The table also stores critical transactional data such as release dates, shipment and job details, currency, terms, and approval status. This structure ensures each release is uniquely tied to its contract and maintains a clear audit trail for procurement fulfillment.

Common Use Cases and Queries

This table is fundamental for operational reporting and process integration. Common use cases include generating delivery schedules, tracking release statuses (e.g., approved, on hold), and reconciling received quantities against planned releases. A typical query retrieves release details for a specific blanket agreement:

  • SELECT pr.release_num, pr.release_date, pr.quantity, pr.promised_date FROM po_releases_all pr WHERE pr.po_header_id = <header_id> ORDER BY pr.release_num;

For integration with receiving, a join to RCV_SHIPMENT_LINES is standard to match physical receipts to their scheduled releases. Reporting on releases pending receipt or those exceeding promised dates also relies heavily on this table. Analysts frequently query it to monitor procurement cycle compliance and supplier performance against contractual schedules.

Related Objects

As indicated by its extensive foreign key relationships, PO_RELEASES_ALL is a cornerstone table with broad integration across EBS. Its primary relationship is with PO_HEADERS_ALL, the parent blanket agreement. Key transactional child tables include PO_LINE_LOCATIONS_ALL (defining shipment schedules), PO_DISTRIBUTIONS_ALL (accounting distributions), and RCV_SHIPMENT_LINES (receipt transactions). It is also referenced by critical interfaces and history tables such as RCV_TRANSACTIONS_INTERFACE, PO_ACTION_HISTORY, and archive tables (e.g., PO_LINE_LOCATIONS_ARCHIVE_ALL). Furthermore, it feeds into financial and business intelligence objects like FII_AP_INV_B and supply planning entities like MTL_SUPPLY and RCV_SUPPLY, highlighting its central role in the procure-to-pay and supply chain execution flows.