Search Results xla_event_pkg

Overview

XLA_EVENTS_PUB_PKG is the public API package of the Oracle Subledger Accounting (SLA) engine, exposed under the APPS schema and documented as an "OTHER" classification API in ETRM 12.2.2. Its stated purpose in the package header is to provide product teams with all APIs required for processing accounting events. The package is a thin wrapper over the public routines of the internal XLA_EVENT_PKG, and it deliberately does not issue COMMIT or ROLLBACK, leaving transaction control to the calling application. It is a foundational integration point in E-Business Suite: the metadata records that it is referenced by 69 other packages, making it one of the most widely consumed SLA public interfaces in both 12.1.1 and 12.2.2.

Key Procedures and Functions

The package exposes 23 documented procedures and functions. The core creation and maintenance routines are CREATE_EVENT, CREATE_BULK_EVENTS, UPDATE_EVENT, UPDATE_EVENT_STATUS, UPDATE_BULK_EVENT_STATUSES, DELETE_EVENT, DELETE_EVENTS and DELETE_BULK_EVENTS, which perform single-row and array (bulk) lifecycle operations against accounting events. Query routines include GET_EVENT_INFO, GET_EVENT_STATUS, GET_ARRAY_EVENT_INFO and EVENT_EXISTS, which return event attributes, status values, or a boolean existence check without modifying data. Structural routines DELETE_ENTITY and PERIOD_CLOSE support removal of an entity and period-close processing respectively.

Of particular relevance to a search for "update_transaction_number", the package includes a dedicated UPDATE_TRANSACTION_NUMBER procedure. The package history confirms this was introduced deliberately: a change dated 17-Apr-02 records that separate APIs were added to update transaction number, event number and reference information, replacing earlier combined routines. Prior entries in the history also note that APIs were changed to handle the then-new Transaction Number column in XLA_ENTITIES and to handle Event Number. UPDATE_TRANSACTION_NUMBER therefore allows a calling product to keep the transaction number stored on the accounting event aligned with the source transaction identifier. ALLOW_THIRD_PARTY_UPDATE is also documented, governing whether non-owning applications may modify event data.

Tables Accessed

Documented table references via APPS synonyms are WF_EVENT_T, GL_PERIOD_STATUSES and WF_PARAMETER_LIST_T. GL_PERIOD_STATUSES is consulted for period-close validation and to determine open or closed accounting periods, which governs whether event status transitions and PERIOD_CLOSE are permitted. WF_EVENT_T and WF_PARAMETER_LIST_T belong to the Oracle Workflow event infrastructure and support event raising and parameter propagation when accounting events are created or updated. The procedures primarily maintain XLA_EVENTS and related SLA entity tables, including the Transaction Number column on XLA_ENTITIES noted in the package history.

Usage Notes

XLA_EVENTS_PUB_PKG is invoked by subledger product teams and by custom code whenever accounting events must be created, queried, updated or deleted independently of the standard subledger posting flow. Typical callers are subledger application modules, concurrent programs that reprocess or purge events, and extension code that corrects transaction numbers or reference information. Because the APIs neither commit nor roll back, callers must manage transaction boundaries and error handling explicitly. Direct DML against the underlying XLA tables should be avoided in favour of these public routines to preserve SLA integrity and upgrade safety.