Search Results delete_processed_event

Overview

XLA_EVENTS_PKG is a core PL/SQL package owned by the APPS schema in Oracle E-Business Suite Subledger Accounting (SLA). It manages the lifecycle of accounting events — the entries posted by subledger applications into the SLA model — from creation through update, status change, and eventual purge. Each accounting event represents a business transaction (an invoice, payment, receipt, or similar) that must be evaluated by the Subledger Accounting Program to generate journal entries. This package is the internal engine behind the public API XLA_EVENTS_PUB_PKG, and it also exposes reusable logic to other SLA packages such as XLA_ACCOUNTING_PUB_PKG, XLA_JOURNAL_ENTRIES_PKG, and XLA_DATAFIXES_PUB.

Key Procedures and Functions

• INITIALIZE: Performs one-time setup within a session, typically resolving application, ledger, and language context.
• CREATE_EVENT: Creates a standard accounting event from a subledger transaction.
• CREATE_MANUAL_EVENT: Creates a user-defined event outside the normal transaction flow.
• CREATE_BULK_EVENTS: Creates events in bulk for high-volume processing scenarios.
• UPDATE_EVENT / UPDATE_MANUAL_EVENT: Modifies event attributes for standard and manual events respectively.
• UPDATE_EVENT_STATUS / UPDATE_BULK_EVENT_STATUSES: Change the processing status of single or multiple events, driving the SLA processing pipeline.
• DELETE_EVENT / DELETE_PROCESSED_EVENT / DELETE_EVENTS / DELETE_BULK_EVENTS: Remove events individually, after processing, or in bulk.
• DELETE_ENTITY / PURGE_ENTITY: Remove all events associated with an entity (transaction type and source), used in purge and cleanup routines.
• GET_EVENT_INFO / GET_ARRAY_EVENT_INFO: Return event attributes for a single event or a set, supporting downstream processing.
• GET_EVENT_STATUS: Retrieves the current status of an event.
• EVENT_EXISTS: Boolean check confirming whether an event already exists, used to prevent duplicate creation.
• UPDATE_TRANSACTION_NUMBER: Updates the transaction reference number associated with an event.
• ALLOW_THIRD_PARTY_UPDATE: Permits external applications to update event records, supporting extensibility.

Additional private procedures and functions exist beyond the documented set of 25, supporting internal validation and array handling.

Tables Accessed

The package reads and writes SLA tables via APPS synonyms, including XLA_DISTRIBUTION_LINKS, XLA_ENTITY_ID_MAPPINGS, and XLA_ENTITY_TYPES_B, which map subledger transactions to SLA entities and events. It also references accounting tables such as XLA_AE_HEADERS, XLA_AE_HEADER_ACS, XLA_AE_HEADER_DETAILS, XLA_AE_LINES, XLA_AE_LINE_ACS, XLA_AE_LINE_DETAILS, and XLA_AE_SEGMENT_VALUES, used to detect existing accounting and manage event status. XLA_ACCOUNTING_ERRORS captures errors during event processing. GL_LEDGERS and GL_JE_BATCHES provide ledger and journal batch context. FND_APPLICATION_TL and FND_LANGUAGES supply application names and language translations.

Usage Notes

This package is not typically called directly by end users or forms. It is invoked internally by the Subledger Accounting Program, by the public wrapper XLA_EVENTS_PUB_PKG, and by data-fix scripts (XLA_DATAFIXES_PUB) and journal entry processing (XLA_JOURNAL_ENTRIES_PKG). Custom code that creates or manipulates accounting events should use XLA_EVENTS_PUB_PKG rather than the internal package, as the public API validates input and enforces supported usage. The package is referenced by eight other packages and depends on XLA_EVENTS_PUB_PKG and SYS.STANDARD. Direct calls carry risk of bypassing validation and are discouraged outside supported data-fix and upgrade scenarios.