Search Results update_history

Overview

INV_TRANSACTIONS_UTIL2 is an Oracle E-Business Suite utility package owned by APPS and classified under the OTHER API category. It forms part of the Inventory transaction infrastructure, providing supporting routines that coordinate transaction history processing with Oracle Workflow. The package is closely tied to transaction error handling: when an Inventory transaction processed through the Transaction Manager fails, the resulting error condition must be recorded in transaction history and surfaced to the workflow layer so that the originating document or business flow can be corrected and resubmitted. INV_TRANSACTIONS_UTIL2 encapsulates that coordination logic, wrapping the core history update routine and translating its outcome into a Workflow result status of COMPLETE:SUCCESS or COMPLETE:FAILURE. In Oracle EBS 12.1.1 and 12.2.2, this package operates alongside INV_TRANSACTIONS_UTIL (specifically its Update_Txn_History procedure) and the RCV error package, both of which it depends upon for return status evaluation.

Key Procedures and Functions

• UPDATE_TXN_HISTORY — The central routine for writing or updating transaction history records in MTL_TXNS_HISTORY. It accepts the item type, item key, a history or transaction type indicator such as 'ER' (error), and returns a status value used by callers to determine success or failure.
• UPDATE_TXN_HIST_SUCCESS_WF — The Workflow-facing wrapper that invokes UPDATE_TXN_HISTORY during the RUN activity function mode and converts the returned status into a Workflow result string. A successful history update yields 'COMPLETE:SUCCESS'; any failure raises the package's private update_history exception and returns 'COMPLETE:FAILURE'.
• SEND_INVENTORY_ADJUSTMENT — Handles notification or document transmission associated with inventory adjustments, integrating adjustment activity with the Workflow messaging layer.
• SEND_DOCUMENT — Provides document dispatch functionality, supporting the workflow notification of inventory-related documents generated or affected by transaction processing.

All procedures include optional debug tracing governed by the INV_DEBUG_TRACE profile option, which, when set to 1, writes trace messages through INV_TRX_UTIL_PUB.TRACE.

Tables Accessed

• MTL_TXNS_HISTORY — The principal target table, receiving inserted or updated transaction history rows, including error-status entries created by the error workflow path.
• MTL_CLIENT_PARAMETERS — Read for inventory client-level configuration and parameter values that influence transaction processing behavior.
• HZ_CUST_ACCOUNTS — Referenced for customer account information required when documents or adjustments relate to customer-facing transactions.
• PO_WF_ITEMKEY_S — Supplies Workflow item key sequence values used to generate unique item keys for workflow activities.
• DUAL — Used for single-row evaluations and system function calls.

Usage Notes

INV_TRANSACTIONS_UTIL2 is not intended for direct ad hoc execution. It is invoked primarily as a Workflow activity function: the error handling workflow for Inventory transactions calls UPDATE_TXN_HIST_SUCCESS_WF during the RUN function mode, passing the item type, item key, activity identifier, and function mode, and receiving the result string back into Workflow. Customizations that extend Inventory transaction error handling, particularly those requiring history records to be written before a workflow resumes, may call UPDATE_TXN_HISTORY directly, observing the same return-status contract used internally. Because the package raises exceptions after setting resultout to 'COMPLETE:FAILURE', callers in custom code should handle both the update_history exception and unexpected Oracle errors. The package is referenced by one other package in the ETRM catalog, reflecting its role as a shared utility rather than a primary entry point. When troubleshooting, enabling INV_DEBUG_TRACE at the site or user level provides detailed trace output that identifies the exact item key, activity, and failure point.