Search Results po_change_requests




Overview
Explore in AI Chat

Overview

PO_CHANGE_REQUESTS is a Purchasing (PO) module table in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. It stores change requests raised against purchase orders, releases, and requisitions, submitted either by suppliers through the Supplier Portal or by internal requesters. Each row captures the substance of a proposed modification — the document targeted, the action requested, the old and new values, and the workflow and approval state that governs whether the change is applied.

The table is central to the change management and supplier collaboration flows in Purchasing. It provides the staging record through which a requested change is validated, optionally routed for approval, and ultimately accepted or rejected, rather than allowing documents to be silently overwritten. The heuristic Data Vault classification mined from its foreign key structure is standalone; from a modeling suggestion perspective, this means the object can reasonably be treated as a hub-like or independent entity anchored on its own identifier rather than as a pure link between two other hubs.

Key Information Stored

The documented physical schema contains 79 columns. The most significant are:

Standard audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) are present as expected.

Common Use Cases and Queries

The primary operational use is to drive the supplier-initiated change approval flow. Buyers query pending requests and respond to them; reports track outstanding requests by age and status.

  • Open supplier change requests: filter on REQUEST_STATUS, INITIATOR, and VENDOR_ID to list requests awaiting a buyer response.
  • Document-level change history: join on DOCUMENT_HEADER_ID to see every change requested against a given purchase order, ordered by CREATION_DATE.
  • Approval monitoring: use APPROVAL_REQUIRED_FLAG and WF_ITEM_KEY to reconcile requests against their Workflow status.
  • Price and schedule variance reporting: compare OLD_PRICE against NEW_PRICE, or OLD_PROMISED_DATE against NEW_PROMISED_DATE, to quantify the commercial impact of requests.
  • Cycle-time analysis: measure elapsed time between CREATION_DATE and RESPONSE_DATE to assess buyer responsiveness.

Sample pattern:

  • SELECT CHANGE_REQUEST_ID, DOCUMENT_NUM, DOCUMENT_LINE_NUMBER, INITIATOR, REQUEST_STATUS, OLD_PRICE, NEW_PRICE FROM PO.PO_CHANGE_REQUESTS WHERE REQUEST_STATUS = 'PENDING' ORDER BY CREATION_DATE;

Related Objects

The documented foreign key links PO_RELEASE_ID to PO_RELEASES_ALL, tying a request to a specific release. Beyond that relationship, the table is best understood alongside the base Purchasing documents and the Workflow infrastructure:

Collectively these objects let developers and analysts trace a change request from its originating supplier or requester through to the affected purchasing document and its approval outcome.