Search Results reset_global
Overview
XLA_DATAFIXES_PUB is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It is part of the Subledger Accounting (XLA) architecture that underpins the accounting engine shared by Payables, Receivables, Assets, Cost Management, and other subledgers. The package exists to provide controlled data-fix and diagnostic capabilities against the XLA journal entry model. Rather than serving as a normal runtime accounting API, XLA_DATAFIXES_PUB is intended for corrective and investigative operations: removing or reversing posted accounting entries, re-running accounting for events, blocking transfer of journal entries to the General Ledger, validating the integrity of accounting entries, and auditing data-fix activity. It is classified as a PUB package, meaning its procedures are exposed as a supported public interface for callers such as other XLA packages, concurrent programs, and diagnostics utilities. The object is documented as VALID in the ETRM repository for release 12.2.2 and applies equally to the 12.1.1 code line, where the same subledger accounting data model is in force.
Key Procedures and Functions
The package exposes nine documented procedures and functions:
- RESET_GLOBAL — Resets package-level global state so that a subsequent data-fix operation starts from a clean context.
- DELETE_JOURNAL_ENTRIES — Physically removes journal entry headers and lines associated with specified transactions or events.
- REVERSE_JOURNAL_ENTRIES — Reverses existing subledger journal entries, generating offsetting accounting rather than deleting the original records.
- REDO_ACCOUNTING — Re-drives the accounting process for events, typically after source data or accounting setup has been corrected.
- DO_NOT_TRANSFER_JE — Marks journal entries so they are excluded from transfer to the General Ledger.
- VALIDATE_JOURNAL_ENTRY — Checks a journal entry for structural and referential integrity before or after a fix.
- AUDIT_DATAFIX — Records audit information describing the data-fix action performed, supporting traceability and governance.
- LOG_ERROR — Captures and stores error information encountered during a data-fix run.
- GET_TRANSACTION_DETAILS — Retrieves transaction-level detail used to identify and describe the records targeted by a fix.
Tables Accessed
The package operates across the core XLA tables through APPS synonyms. Journal entry headers and lines are held in XLA_AE_HEADERS and XLA_AE_LINES, which are the primary targets of delete, reverse, and validate operations. XLA_EVENTS and XLA_EVENT_TYPES_B define the accounting events being reprocessed, while XLA_TRANSACTION_ENTITIES and XLA_ENTITY_ID_MAPPINGS link those events back to their source transactions. XLA_DISTRIBUTION_LINKS and XLA_SUBLEDGERS record the distribution and subledger context. XLA_LEDGER_OPTIONS and XLA_TB_DEFN_JE_SOURCES supply ledger and trial-balance journal source configuration, with XLA_TRIAL_BALANCES holding related balances. GL_IMPORT_REFERENCES ties subledger entries to their General Ledger import. XLA_ACCT_PROG_EVENTS_GT is a global temporary table used during accounting program event processing, XLA_UPG_ERRORS stores error records, and PLITBLM is the standard PL/SQL index-by table used for bulk collections.
Usage Notes
XLA_DATAFIXES_PUB is not invoked during ordinary accounting runs. It is called from diagnostic scripts, data-fix concurrent programs, and support-driven remediation executed under an APPS session, and it is also referenced by other XLA packages including XLA_JOURNAL_ENTRIES_PKG and XLA_JOURNAL_ENTRIES_PUB_PKG. Because its operations delete or reverse posted accounting, usage requires careful validation of the affected events, ledger, and period status, and the audit and error-logging procedures should be exercised so that every fix is traceable. Calling code should reset global state before each operation. The package should be treated strictly as a controlled maintenance interface, with testing performed in a non-production environment before any corrective action is applied.