Search Results po_change_requests_n1

Overview

The PO.PO_CHANGE_REQUESTS table is a transactional table in the Oracle E-Business Suite Purchasing module that stores change requests submitted against purchase orders, releases, and requisitions. These change requests may originate from either suppliers or internal requesters. The table captures the full context of a proposed change, including the document being modified, the level at which the change applies (header, line, shipment, or distribution), the old and new values for the affected attributes, and the processing status of the request.

From a dimensional modelling perspective, the dependency information characterizes PO_CHANGE_REQUESTS as a standalone object with a single documented foreign key to PO_RELEASES_ALL via PO_RELEASE_ID. A heuristic Data Vault classification therefore places it as a standalone transactional entity, with no documented parent hubs or links within the ETRM scope. It functions primarily as a change-audit and workflow table rather than a master data reference.

The table resides in the APPS_TS_TX_DATA tablespace with PCT Free 10. Its indexes are held in APPS_TS_TX_IDX. Correct index usage is central to performance, particularly for the unique and nonunique indexes documented below.

Key Information Stored

The table contains 79 documented columns. The most operationally significant are:

• CHANGE_REQUEST_ID — The surrogate unique key identifying each individual change request. The unique business-key candidate is enforced by the unique index PO_CHANGE_REQUESTS_U1, which is the object referenced when users search for "po_change_requests_u1".
• CHANGE_REQUEST_GROUP_ID — Groups all change requests submitted together on a purchase order at a given time.
• INITIATOR — Source of the request; documented values are "SUPPLIER" or "REQUESTER".
• ACTION_TYPE — The requested action, documented as "MODIFICATION" or "CANCELLATION".
• REQUEST_REASON — Free-text reason for the submission, up to 2000 characters.
• REQUEST_LEVEL — Level of the change; "HEADER", "LINE", "SHIPMENT", or "DISTRIBUTION".
• REQUEST_STATUS — Processing state; documented values include "PENDING", "ACCEPTED", and "REJECTED", plus internal statuses.
• DOCUMENT_TYPE — Distinguishes purchase order, release, or requisition.
• DOCUMENT_HEADER_ID — PO Header Id or Requisition Id that owns the change.
• DOCUMENT_NUM and DOCUMENT_REVISION_NUM — Human-readable document number and revision.
• OLD_/NEW_ paired columns such as OLD_QUANTITY/NEW_QUANTITY, OLD_PRICE/NEW_PRICE, OLD_PROMISED_DATE/NEW_PROMISED_DATE — the before/after values proposed by the change.
• REQUESTER_ID, RESPONDED_BY, RESPONSE_DATE, RESPONSE_REASON — the responder and outcome of the workflow.
• WF_ITEM_TYPE and WF_ITEM_KEY — links the change request to the Oracle Workflow process that routes and approves it.

Common Use Cases and Queries

Typical reporting includes extracting pending supplier change requests by PO, exposing response turnaround times, and auditing the delta between old and new values for price or quantity changes. The four nonunique indexes support the dominant access paths: PO_CHANGE_REQUESTS_N1 on DOCUMENT_HEADER_ID, N2 on DOCUMENT_LINE_ID, N3 on CHANGE_REQUEST_GROUP_ID, and N4 on REQUEST_STATUS and REQUEST_LEVEL.

Sample query — open changes against a PO header:

SELECT cr.change_request_id, cr.initiator, cr.action_type,
       cr.request_level, cr.request_status, cr.request_reason
FROM   po.po_change_requests cr
WHERE  cr.document_header_id = :header_id
AND    cr.request_status = 'PENDING';

To retrieve all requests submitted together, filter by grouping key or by status across a document number:

SELECT cr.document_num, cr.change_request_group_id, cr.request_level,
       cr.old_quantity, cr.new_quantity, cr.old_price, cr.new_price
FROM   po.po_change_requests cr
WHERE  cr.request_status = 'ACCEPTED'
AND    cr.document_num = :po_number
ORDER  BY cr.change_request_group_id, cr.creation_date;

Workflow-driven dashboards frequently join WF_ITEM_KEY and WF_ITEM_TYPE to WF_ITEM_ACTIVITY_STATUSES to surface approvals pending on suppliers or requesters.

Related Objects

• PO.PO_RELEASES_ALL — referenced by the documented foreign key PO_CHANGE_REQUESTS.PO_RELEASE_ID on the PO_RELEASE_ID column.
• PO.PO_HEADERS_ALL / PO.PO_HEADERS — the parent document when DOCUMENT_TYPE is a purchase order; join on DOCUMENT_HEADER_ID = PO_HEADER_ID.
• PO.PO_LINES_ALL — joined via DOCUMENT_LINE_ID for line-level and shipment-level changes.
• PO.PO_LINE_LOCATIONS_ALL — joined via DOCUMENT_LINE_LOCATION_ID for shipment-level changes.
• PO.PO_DISTRIBUTIONS_ALL — joined via DOCUMENT_DISTRIBUTION_ID for distribution-level changes.
• PO_PO_CHANGE_REQUESTS public API — the PL/SQL interface that inserts and processes rows in this table.
• WF_ITEMS / WF_ITEM_ACTIVITY_STATUSES — joined via WF_ITEM_TYPE and WF_ITEM_KEY to expose approval routing.