Search Results po_purge_req_list_pk

Overview

The PO_PURGE_REQ_LIST table is a critical data structure within the Oracle E-Business Suite Purchasing (PO) module, specifically for the requisition purge process. It functions as a staging or candidate list, identifying specific requisition header records that have been selected for archival or deletion during a purge operation. This table is central to the purge functionality, ensuring data integrity by maintaining a controlled, referentially sound list of records before any permanent removal from the primary transaction tables. Its role is to support system performance and data management by facilitating the clean-up of obsolete requisition data in a structured and auditable manner.

Key Information Stored

The table's structure is intentionally simple, designed to store a list of identifiers. Based on the provided metadata, the primary and most significant column is REQUISITION_HEADER_ID. This column holds the unique identifier (REQUISITION_HEADER_ID) for each requisition header that has been marked as a candidate for purging. The table's sole purpose is to maintain this list, which is populated by the purge concurrent program or related logic before the actual deletion or transfer of data to archive tables occurs. The existence of a primary key constraint (PO_PURGE_REQ_LIST_PK) on this single column ensures that no duplicate requisition header IDs are entered into the candidate list.

Common Use Cases and Queries

The primary use case for this table is the execution and verification of the requisition purge process. Administrators or custom scripts may interact with it to analyze purge candidates or troubleshoot failed purge jobs. A common query would involve joining this table to PO_REQUISITION_HEADERS_ALL to see details of the requisitions slated for removal. For instance, to review the candidate list before submission, one might use:

• SELECT prh.requisition_header_id, prh.segment1, prh.creation_date FROM po_requisition_headers_all prh WHERE prh.requisition_header_id IN (SELECT requisition_header_id FROM po_purge_req_list);

Conversely, to identify requisions that were selected for purge but may still have dependent lines or unprocessed statuses, a NOT EXISTS check against related detail tables like PO_REQUISITION_LINES_ALL could be performed. The table is typically cleared after a successful purge cycle.

Related Objects

The PO_PURGE_REQ_LIST table has a direct and singular relationship with a core Purchasing transaction table, as documented in the provided metadata.

• PO_REQUISITION_HEADERS_ALL: This is the primary table referenced by PO_PURGE_REQ_LIST. A foreign key constraint enforces that every REQUISITION_HEADER_ID in the purge list must correspond to a valid, existing record in PO_REQUISITION_HEADERS_ALL. This prevents the purge process from attempting to delete non-existent requisition headers.

While not explicitly listed in the brief metadata, this table is intrinsically linked to the purge concurrent program (e.g., Purge Requisition and Purchase Documents) and potentially to archive tables (such as PO_REQUISITION_HEADERS_ARCHIVE) where the purged data is ultimately moved.