Search Results po_action_history




Overview
Explore in AI Chat

Overview

The PO_ACTION_HISTORY table is a core data object within the Oracle E-Business Suite Purchasing (PO) module, specifically for versions 12.1.1 and 12.2.2. As its documented description states, it serves as the central repository for the approval and control action history of purchasing documents. This table is fundamental to the audit trail and workflow engine, systematically recording every significant action—such as submission, approval, rejection, hold, and final closure—performed on a purchasing document throughout its lifecycle. Its role is critical for compliance, troubleshooting approval chains, and providing visibility into the document's historical status transitions.

Key Information Stored

The table's structure is designed to generically track actions for multiple document types. The primary key, PO_ACTION_HISTORY_PK, is a composite key consisting of OBJECT_ID, OBJECT_TYPE_CODE, OBJECT_SUB_TYPE_CODE, and SEQUENCE_NUM. This design allows the table to uniquely identify each step in the history of a specific document. Key columns include OBJECT_ID (the unique identifier of the document, like a PO Header ID), OBJECT_TYPE_CODE (e.g., 'PO' for Purchase Order, 'REQUISITION'), and OBJECT_SUB_TYPE_CODE (providing further document classification). The SEQUENCE_NUM orders the actions chronologically. Other critical columns typically found in such history tables, though not explicitly listed in the provided metadata, include ACTION_CODE (e.g., 'APPROVE', 'REJECT'), ACTION_DATE, PERFORMER_ID (who took the action), and NOTE.

Common Use Cases and Queries

A primary use case is generating an approval audit report for a specific purchase order. Analysts and auditors frequently query this table to understand who approved a document, when, and in what sequence. Another common scenario is diagnosing workflow issues by examining the sequence of actions to identify where a process may have stalled or deviated. A sample query to retrieve the full history for a purchase order would be:

  • SELECT object_id, sequence_num, action_code, performer_id, action_date FROM po.po_action_history WHERE object_id = <PO_HEADER_ID> AND object_type_code = 'PO' ORDER BY sequence_num;

For reporting, this table is often joined to HR tables (via PERFORMER_ID) to get employee names and to PO_HEADERS_ALL to link history with document details like PO number and supplier.

Related Objects

As indicated by the foreign key constraints in the metadata, the PO_ACTION_HISTORY.OBJECT_ID column has direct relationships with the key header tables for the major purchasing document types. The documented foreign keys are:

  • PO_HEADERS_ALL: Links action history to standard purchase orders and planned purchase orders.
  • PO_REQUISITION_HEADERS_ALL: Links action history to requisition headers.
  • PO_RELEASES_ALL: Links action history to blanket and contract agreement release documents.

This table is also integral to several standard Oracle Purchasing workflow processes and is commonly referenced in custom reports and integrations that require a complete document lifecycle audit trail.