Search Results insert_transaction

Overview

APPS.IES_TRANSACTION_UTIL_PKG is a utility package within the Oracle E-Business Suite Internet Expensing (IES) module, the framework that supports web-based expense entry and transaction processing. The package encapsulates the low-level operations required to create and maintain rows in the IES transaction staging schema, which acts as the interface between self-service expense entry and the downstream Payables and Projects accounting flows. Rather than exposing direct DML against the transaction tables, the IES application layer calls the procedures and functions in this package so that status transitions, restart state, and user context are applied consistently.

The package is declared with AUTHID CURRENT_USER, meaning that all SQL statements execute under the privileges of the invoking session rather than the package owner. This design choice is significant in an APPS environment: it ensures that row-level security, custom access controls, and any session-based policies apply to the caller, and that the package can be safely invoked from concurrent programs, forms, and OAF-based self-service pages without unintended privilege escalation through the APPS schema.

The header comment records an early revision (115.3, dated 2003), indicating the package has remained stable across the EBS 12.1.1 and 12.2.2 releases and the underlying transaction model has not required structural change.

Key Procedures and Functions

• INSERT_TRANSACTION (function) — Creates a new IES transaction record and returns the generated transaction identifier. It accepts the acting user identifier and a descriptive flexfield or document script identifier, allowing the caller to stamp the new transaction with ownership and contextual metadata. This is the entry point referenced by the search term "insert_transaction" and is the routine most commonly called directly by custom integrations that need to seed an expense transaction before further processing.
• UPDATE_TRANSACTION (procedure, two overloads) — The first overload updates a transaction's processing status, optionally persisting a restart CLOB and recording the user who performed the change. The second, single-parameter overload performs a status-only or context-only refresh of the transaction record. Together the overloads support both simple status transitions and the richer restart scenario used when a partially completed transaction must be resumed.
• GETRESTARTXMLDATA (function) — Returns the serialized restart payload for a given transaction as a CLOB. This supports the save-and-resume behavior of the self-service expense flow, where in-progress data is captured as XML and rehydrated when the user returns to the transaction.
• GETTEMPORARYCLOB (procedure) — Provides an OUT NOCOPY CLOB handle for temporary large-object work. NOCOPY avoids the overhead of copying the locator, which matters when assembling large restart XML documents.

Tables Accessed

The package operates against IES_TRANSACTIONS_S, the base table and sequence-backed entity for IES transaction records, accessed through an APPS synonym. INSERT_TRANSACTION writes new rows to this table and returns the surrogate key; UPDATE_TRANSACTION modifies status, restart data, and audit columns on existing rows; GETRESTARTXMLDATA reads the stored restart payload from the same table. The DBMS_LOB built-in package is used to manipulate CLOB columns during read and write of restart data, and DUAL is referenced for singleton evaluations such as sequence retrieval and default values.

Usage Notes

IES_TRANSACTION_UTIL_PKG is an internal utility layer rather than a public concurrent program. It is invoked from the IES self-service expense pages, from the OAF controller and application module logic that manages transaction creation and status, and from any custom code that must programmatically insert or advance an IES transaction. Because the package runs AUTHID CURRENT_USER, custom callers must hold appropriate privileges on IES_TRANSACTIONS_S and its synonyms, and any invoker-rights policies on that table will be enforced. The package is referenced by one other package in the IES schema, confirming its role as a shared low-level service. When extending the expense flow, direct DML against IES_TRANSACTIONS_S should be avoided in favor of INSERT_TRANSACTION and UPDATE_TRANSACTION so that restart state and status semantics remain consistent with the standard product behavior.