Results for “po_act_hist_v”

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

Overview

PO_ACT_HIST_V is an APPS-owned database view in the Oracle E-Business Suite Purchasing (PO) module. Its documented purpose is to "accommodate dynamic SQL built for security user exit." In practice, the view exposes the action history of purchasing documents — the audit trail of approvals, cancellations, returns, and other state transitions recorded against requisitions, purchase orders, releases, and related objects — while appending ten generic security columns. These columns (SECURITY1 through SECURITY10) are populated with the constant value TO_CHAR(1) in the shipped definition and exist as placeholder slots that customer security user exits can substitute with dynamic SQL predicates to enforce row-level access rules. The view is defined with status VALID in both EBS 12.1.1 and 12.2.2, and it participates in the standard multi-org and function-security framework.

Because the view is a reporting and integration surface rather than a transactional object, it is typically consumed by inquiry forms, custom reports, and outbound interfaces that need a read-consistent picture of document action history without touching the base table directly. The inclusion of the PROGRAM_DATE column makes the view a useful source for auditing when a given action record was last touched by a concurrent request, which is frequently the reason users search for "program_date" in connection with this object.

Underlying Base Objects

The view is defined over a single documented referenced object, PO_ACTION_HISTORY, accessed through a synonym in the APPS schema. The SELECT list maps almost every column of PO_ACTION_HISTORY directly, with DBA documentation listing the exposed names as OBJECT_ID, TYPE, SUBTYPE, SEQUENCE_NUM, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, ACTION_CODE, ACTION_DATE, EMPLOYEE_ID, NOTE, OBJECT_REVISION_NUM, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_DATE, APPROVAL_PATH_ID, OFFLINE_CODE, and PROGRAM_UPDATE_DATE, followed by SECURITY1–SECURITY10.

Note the slight naming discrepancy between the view text (which selects OBJECT_TYPE_CODE and OBJECT_SUB_TYPE_CODE) and the documented column list (which shows TYPE and SUBTYPE); implementations should verify the actual catalogued column names in the target instance before writing production SQL. One row in PO_ACTION_HISTORY corresponds to one row in PO_ACT_HIST_V, so the view imposes no join fan-out or aggregation. All auditing columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are inherited unchanged from the base table, preserving the Who columns used by EBS audit conventions.

Key Columns

• OBJECT_ID — Identifier of the purchasing document whose history is recorded.
• TYPE / OBJECT_TYPE_CODE — Document type discriminator (for example, purchase order versus requisition).
• SUBTYPE / OBJECT_SUB_TYPE_CODE — Further classification within the document type.
• SEQUENCE_NUM — Ordering key for actions within a document's history; combined with OBJECT_ID it supports deterministic chronological retrieval.
• ACTION_CODE — The action performed (approve, cancel, return, close, and so on).
• ACTION_DATE — Business-effective timestamp of the action, distinct from the audit LAST_UPDATE_DATE.
• EMPLOYEE_ID — Employee who performed or is associated with the action.
• NOTE — Free-text annotation captured with the action.
• OBJECT_REVISION_NUM — Revision of the document at the time of the action.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_DATE, PROGRAM_UPDATE_DATE — Concurrent program context. PROGRAM_DATE records the date the program last updated the row, which is the element most often targeted by searches on this object.
• APPROVAL_PATH_ID — Approval routing context for approval-related actions.
• OFFLINE_CODE — Indicates offline processing state where applicable.
• SECURITY1–SECURITY10 — Constant TO_CHAR(1) placeholders replaced or filtered by security user exit logic.

Common Use Cases and Queries

Typical scenarios include reconstructing the approval audit trail for a purchase order, reporting on actions executed by a concurrent program during a date range, and building custom extracts where the ten security columns are leveraged by a user exit. A representative query listing the latest actions for a document is:

SELECT object_id, action_code, action_date, employee_id, program_date
FROM po_act_hist_v
WHERE object_id = :p_object_id
ORDER BY sequence_num;

To audit rows touched by a specific concurrent program over a period:

SELECT object_id, action_code, program_id, request_id, program_date
FROM po_act_hist_v
WHERE program_date BETWEEN :p_from AND :p_to;

Because the view returns one row per action record and preserves the base table's Who columns, it can also be joined back to PO_HEADERS_ALL on OBJECT_ID (filtered by TYPE) to enrich action history with document-level attributes in custom reports.