Search Results pon_action_hist_pkg

Overview

APPS.PON_ACTION_HIST_PKG is a PL/SQL package body in the Oracle E-Business Suite Sourcing (PON) module that maintains the PON_ACTION_HISTORY table. This table acts as an audit and workflow trail for objects managed by Oracle Sourcing, capturing the sequence of actions performed against auctions, RFQs, spot buys, and related negotiation documents. Every time a buyer, supplier, or automated process advances a sourcing document through its lifecycle — for example, publishing an auction, opening or closing bidding, awarding a line, or applying an amendment — a corresponding history row is written or updated.

The package encapsulates the insert and update logic for that audit table so that calling modules do not manipulate PON_ACTION_HISTORY directly. In Oracle EBS 12.1.1 and 12.2.2 the package is registered in the ETRM repository under owner APPS with an API classification of OTHER, and is referenced by one dependent package. Only one procedure, RECORDHISTORY, is exposed as a documented public entry point; the remaining logic is implemented through private table handlers.

Key Procedures and Functions

• RECORDHISTORY — The single public procedure. It is the supported entry point through which callers register an action against a sourcing object. Internally, the package delegates the physical write to the private table handlers, so callers need only supply the object identity, object type, action type, acting user, and optional note or reason information.
• InsertRowHandler (private) — Performs the INSERT into PON_ACTION_HISTORY. It stamps ACTION_DATE with SYSDATE at execution time and stores the object identifiers, object type code, sequence number, action type, action user, action note, and action reason code.
• UpdateRowHandler (private) — Issues an UPDATE against PON_ACTION_HISTORY keyed on OBJECT_ID, OBJECT_ID2, OBJECT_TYPE_CODE, and SEQUENCE_NUM, restricted to rows where ACTION_TYPE IS NULL. It sets ACTION_TYPE to the supplied value and refreshes ACTION_DATE with SYSDATE. This supports the pattern of reserving a history slot and later completing it with the confirmed action.

Tables Accessed

The package reads and writes a single table, PON_ACTION_HISTORY, accessed through the APPS synonym. The table stores the audit record for each sourcing action: the primary object identifier and a secondary identifier (OBJECT_ID2), the OBJECT_TYPE_CODE distinguishing document families such as auctions, spot buys, and RFQs, a SEQUENCE_NUM ordering the events within a document, the ACTION_TYPE, ACTION_DATE, ACTION_USER_ID, ACTION_NOTE, and ACTION_REASON_CODE. InsertRowHandler populates a new row, while UpdateRowHandler finalizes a previously inserted row whose ACTION_TYPE had not yet been determined. Because the header comment identifies PON_SPOTBUY as a valid object type code, the same table and package are reused across multiple sourcing flows rather than being duplicated per document type.

Usage Notes

PON_ACTION_HIST_PKG is invoked from Sourcing business logic — including the OAF-based negotiation and auction pages, workflow-driven state transitions, and any concurrent or batch process that must record an action against a sourcing document. When users search for "pon_auctions," this package is relevant because auction publish, bid open/close, extension, and award events are recorded as history rows in PON_ACTION_HISTORY, which downstream history and audit displays read back. The dependent package referenced in the ETRM metadata calls RECORDHISTORY to log its own actions without touching the table directly.

From a customization standpoint, direct DML against PON_ACTION_HISTORY is discouraged; custom code should call RECORDHISTORY so that date stamping and the reserved-row update convention are applied consistently. The private handlers are not part of the supported interface and may change between releases. Because ACTION_DATE is always set from SYSDATE, callers cannot backdate a history entry, and because the update handler is guarded by ACTION_TYPE IS NULL, re-invoking it on an already-completed row produces no change. In 12.1.1 and 12.2.2 the package is shipped under the APPS schema with the standard PON file-system header, confirming it is a standard, patched product object rather than a customer extension.