Results for “program_date”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PO_ACTION_HISTORY is the document approval and control action history table in the Oracle Purchasing (PO) module. It resides in the PO schema and is classified as VALID in Oracle EBS 12.1.1 and 12.2.2. The table records the audit trail of workflow-driven and manually initiated actions performed against purchasing documents — purchase orders, requisitions, and releases. Each row captures a discrete action event, the individual or approval path responsible, and the temporal context in which the action occurred, providing a chronological control history for the document lifecycle.

From a dimensional modeling perspective, the heuristic Data Vault classification mined from the foreign key structure is link. This suggests PO_ACTION_HISTORY behaves as an associative structure connecting a purchasing document (by OBJECT_ID) to an employee actor and an approval path, with descriptive action attributes. Modelers should treat the document, employee, and approval path references as the participating hubs of the link.

Key Information Stored

The primary key, PO_ACTION_HISTORY_PK, is a composite surrogate spanning OBJECT_ID, OBJECT_TYPE_CODE, OBJECT_SUB_TYPE_CODE, and SEQUENCE_NUM. Because the key incorporates the document identifier, every record is scoped to a specific purchasing object and ordered within that object by the sequence number.

• OBJECT_ID — Identifier of the purchasing document acted upon; resolves polymorphically to PO_HEADERS_ALL, PO_REQUISITION_HEADERS_ALL, or PO_RELEASES_ALL.
• OBJECT_TYPE_CODE / OBJECT_SUB_TYPE_CODE — Discriminate the document class and subtype, enabling the OBJECT_ID to be interpreted correctly across header and release tables.
• SEQUENCE_NUM — Orders actions within a document, establishing the chronological history chain.
• ACTION_CODE — The business action performed, such as submit, approve, reject, withdraw, or cancel.
• ACTION_DATE — Timestamp when the action was executed.
• EMPLOYEE_ID — The employee who performed the action; foreign key to PSB_EMPLOYEES.
• APPROVAL_PATH_ID — The approval path associated with the action; foreign key to OKE_APPROVAL_PATHS.
• APPROVAL_GROUP_ID — Approval group context for the action.
• NOTE — Free-text annotation supplied by the actor.
• OBJECT_REVISION_NUM — Document revision at the time of the action.
• OFFLINE_CODE — Indicates whether the action was performed in an offline or background mode.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — Concurrent program context, supporting auditability and reconciliation of automated actions.

Standard WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) are also present on the table.

Common Use Cases and Queries

The table is the authoritative source for approval-history reporting, workflow troubleshooting, and segregation-of-duties auditing. A typical query retrieves the full action history for a purchase order in chronological order:

• SELECT a.action_code, a.action_date, a.employee_id, a.note FROM po_action_history a WHERE a.object_id = :p_po_header_id AND a.object_type_code = 'PO' ORDER BY a.sequence_num;
• Joining to PO_HEADERS_ALL on OBJECT_ID to enrich actions with document number, vendor, and status for audit extracts.
• Joining to PSB_EMPLOYEES on EMPLOYEE_ID to resolve the actor's name for approval audit reports.
• Joining to OKE_APPROVAL_PATHS on APPROVAL_PATH_ID to reconstruct the routing that produced each action.
• Aggregating by ACTION_CODE over ACTION_DATE ranges to measure cycle time between submit and approval, or to detect unusual rejection volumes.
• Filtering on REQUEST_ID or PROGRAM_ID to isolate actions generated by concurrent programs rather than users.

Related Objects

PO_ACTION_HISTORY references and is joined with the following significant objects:

• PO_HEADERS_ALL — joined via OBJECT_ID; primary source for purchase order documents.
• PO_REQUISITION_HEADERS_ALL — joined via OBJECT_ID; source for requisition documents.
• PO_RELEASES_ALL — joined via OBJECT_ID; source for release documents.
• PSB_EMPLOYEES — joined via EMPLOYEE_ID to resolve the acting user.
• OKE_APPROVAL_PATHS — joined via APPROVAL_PATH_ID to resolve approval routing.

Together these relationships make PO_ACTION_HISTORY the central link for reconstructing who did what to a purchasing document, when, and through which approval path.