Search Results create_transaction

Overview

APPS.HR_TRANSACTION_SNAPSHOT_SWI is a Supplemental Web Interface (SWI) style PL/SQL package body within the Oracle E-Business Suite HR (Human Resources) product family. Its primary responsibility is to manage the persistence of transaction snapshots — serialized XML/CLOB representations of HR transactional data — against the HR_TRANSACTION_SNAPSHOT table. In the Oracle HRMS architecture, transaction snapshots capture the state of a business object (such as an employee record or assignment) at a defined point in time, enabling auditing, reconciliation, running-total comparisons, and rollback of transactional changes.

As the "SWI" suffix implies, this layer sits between the public HR API surface and the underlying insertion logic. Note that the package does not implement the physical DML itself; instead, it orchestrates calls to the lower-level private package HR_SNP_INS, which performs the actual insert. This separation allows the SWI wrapper to control transaction scope (commit or rollback), base-key handling, and validation semantics independently of the core insert routine.

The package is classified as OTHER in the ETRM metadata, indicating it is an internal, non-published API rather than a formally supported public interface.

Key Procedures and Functions

• CREATE_TRANSACTION_SNAPSHOT — Accepts a document payload (CLOB) together with snapshot and object version identifiers, object name, and object identifier, and a validation flag. It assigns the base key value, delegates the physical insert to HR_SNP_INS.INS, and then either commits (when validation is disabled) or rolls back (when validation is enabled). It is declared with PRAGMA AUTONOMOUS_TRANSACTION, so it executes independently of the caller's transaction.
• UPDATE_TRANSACTION_SNAPSHOT — Accepts a document payload, an existing snapshot identifier, and an object version number, and is responsible for persisting an updated snapshot document for an already-created transaction snapshot.
• DELETE_TRANSACTION_SNAPSHOT — Removes a previously created transaction snapshot, identified by its snapshot identifier, from the transaction snapshot store.

All three procedures together provide complete lifecycle management — create, update, and delete — of transaction snapshot records. No public functions are documented; the package exposes only these three procedures.

Tables Accessed

The only documented table referenced is HR_TRANSACTION_SNAPSHOT, accessed through its APPS synonym. This table stores the snapshot rows themselves, including the CLOB document, the snapshot identifier, the object version number, the object name, and the object identifier. CREATE_TRANSACTION_SNAPSHOT writes to this table indirectly via HR_SNP_INS; UPDATE_TRANSACTION_SNAPSHOT and DELETE_TRANSACTION_SNAPSHOT operate against existing rows. No other application tables are documented as direct dependencies of this package.

Usage Notes

Because the package is classified as OTHER and is referenced by zero other packages in the documented metadata, it is not part of a public, supported API chain. It is typically invoked internally by HR transaction processing logic — for example, from within HR business object APIs or from concurrent programs that capture and persist transaction state — rather than directly from a Forms block or report.

The autonomous transaction pragma on CREATE_TRANSACTION_SNAPSHOT is significant: callers should anticipate that the procedure commits or rolls back independently of their own transaction, meaning snapshot creation cannot be rolled back by the caller's subsequent rollback. Developers extending or calling this package should account for that isolation boundary. The validation parameter, when set to the true numeric value, suppresses the commit and forces a rollback, which is useful for dry-run or validation-only scenarios.

Given the absence of documented external consumers, customizations should treat this package as an internal implementation detail and avoid building direct dependencies on it.