Search Results po_history_requisitions_all




Overview
Explore in AI Chat

Overview

The PO_HISTORY_REQUISITIONS_ALL table is a critical data retention object within Oracle E-Business Suite Purchasing (PO) module, specifically for versions 12.1.1 and 12.2.2. As indicated by its description, it serves as the repository for purged requisitions. In operational practice, requisition data is actively managed in primary transactional tables like PO_REQUISITION_HEADERS_ALL. To maintain system performance and manage data volume, organizations periodically archive and purge older requisition records. This table is the designated historical archive for those purged requisition headers, ensuring data is retained for compliance, auditing, and historical reporting purposes long after it has been removed from the active transactional tables.

Key Information Stored

The table's structure is designed to mirror key identifying and descriptive information from the original requisition header. The primary key column, SEGMENT1, holds the unique requisition number, which is the critical identifier for all historical tracing. While the provided metadata does not list all columns, a table of this nature typically stores a subset of the original requisition header attributes necessary for identification and basic reporting. This often includes data such as the original preparation date, requester, authorization status, and associated purchasing information. The presence of a primary key constraint (PO_HISTORY_REQUISITIONS_PK) on SEGMENT1 ensures the uniqueness of archived requisition records within this history table.

Common Use Cases and Queries

The primary use case for this table is historical and audit reporting on requisition activity that is no longer present in the live system. Common scenarios include generating long-term spend analysis reports, fulfilling audit requests for procurement activity beyond the online retention period, and reconciling historical data. A typical query would join this history table to other historical or transactional tables using the requisition number.

  • Sample Query Pattern: To retrieve basic information for a specific purged requisition: SELECT segment1, [other_columns] FROM po_history_requisitions_all WHERE segment1 = '<Req_Number>';
  • Reporting Use Case: Creating a unified report that queries both active requisitions (from PO_REQUISITION_HEADERS_ALL) and historical requisitions (from PO_HISTORY_REQUISITIONS_ALL) using a UNION ALL operation, providing a complete organizational view.

Related Objects

The table maintains a direct foreign key relationship with the primary transactional table for requisitions, as documented in the provided metadata. This relationship is fundamental for ensuring referential integrity between the live and historical data sets.

  • PO_REQUISITION_HEADERS_ALL: This is the active requisition headers table. The foreign key constraint defines that values in PO_HISTORY_REQUISITIONS_ALL.SEGMENT1 (the requisition number) must reference a valid record in PO_REQUISITION_HEADERS_ALL.SEGMENT1. This relationship confirms that only formally purged requisitions from the active table reside in the history table.

Other related objects would typically include history tables for requisition lines (e.g., PO_HISTORY_REQUISITION_LINES_ALL) and associated purchasing documents, which would be joined via the SEGMENT1 key for comprehensive historical reporting.