Search Results purge_aad




Overview
Explore in AI Chat

Overview

XLA_AAD_LOADER_UTIL_PVT is a private (PVT) PL/SQL utility package in the Oracle E-Business Suite Subledger Accounting (XLA) module. It provides the shared infrastructure used by the Application Accounting Definition (AAD) loader and related setup-transport components to validate, stage, load, and maintain AAD metadata in a target environment. The package is not exposed to end users; instead it is called by the public XLA loader APIs and by concurrent programs that move AAD definitions between environments, typically during implementation, patching, or environment synchronization activities.

The package body declares global collections (t_array_int, t_array_msg, t_array_varchar30) that accumulate error numbers and messages across a loading session, and it defines a local trace facility built on FND_LOG levels (statement, procedure, event, exception, error, unexpected) with the module identifier xla.plsql.xla_aad_loader_util_pvt. This logging infrastructure supports diagnostic troubleshooting of AAD load and purge operations.

Key Procedures and Functions

The documented API comprises 21 procedures and functions, including the PURGE_AAD routine that corresponds to the user search term. Principal members include:

  • PURGE_AAD / PURGE / PURGE_HISTORY / PURGE_SUBLEDGER_SEED — Housekeeping routines that remove AAD loader data, history records, and seed data from the XLA tables. PURGE_AAD is the entry point most commonly associated with the search term.
  • GET_STAGING_CONTEXT_CODE — Retrieves the context code used to identify staging records during the load process.
  • LOCK_AREA — Obtains a locking mechanism to serialize concurrent loader activity.
  • MERGE_HISTORY — Merges loader history rows into the permanent history tables.
  • GET_SEGMENT — Extracts individual segments from composite values used by the AAD loader definitions.
  • RESET_ERRORS / STACK_ERROR / INSERT_ERRORS — Manage the in-memory error stack and persist accumulated errors to the loader log tables.
  • WAIT_FOR_REQUEST — Synchronizes processing with a concurrent request.
  • COMPATIBLE_API_CALL and VALIDATE_ADR_COMPATIBILITY — Enforce API and Accounting Definition Rule compatibility checks.
  • COMPILE / REBUILD_AC_VIEWS — Recompile database objects and rebuild accounting views after AAD changes.
  • INSERT_AADLOADERLOG — Writes entries to the AAD loader log.

Tables Accessed

The package operates against the XLA setup and loader schema through APPS synonyms. It reads application metadata from FND_APPLICATION and AAD definition data from XLA_AADS_H, XLA_AAD_HDR_ACCT_ATTRS, XLA_AAD_HEADER_AC_ASSGNS, and XLA_AAD_LINE_DEFN_ASSGNS. Staging and loader definitions reside in XLA_AAD_LOADER_DEFNS_T, with operational logs stored in XLA_AAD_LOADER_LOGS and its sequence-backed counterpart XLA_AAD_LOADER_LOGS_S. Accounting method and line-type metadata are drawn from XLA_ACCTG_METHOD_RULES, XLA_ACCT_LINE_TYPES_B, and XLA_ACCT_LINE_TYPES_TL. Supporting structures include XLA_AMB_COMPONENTS_H, XLA_AMB_SETUP_ERRORS, and the analytical detail tables XLA_ANALYTICAL_DTLS_B and XLA_ANALYTICAL_DTLS_TL.

Usage Notes

XLA_AAD_LOADER_UTIL_PVT is invoked indirectly. During AAD upload or upgrade, the public XLA loader API calls these utility routines to validate compatibility, stage records, log errors, and rebuild views. Purge operations such as PURGE_AAD are typically triggered from the AAD loader concurrent program or from administrative setup screens when stale or rejected AAD data must be cleared before a reload. Because the package is classified PVT, it should not be called directly from custom code; Oracle does not guarantee its signature across patches. The package is referenced by 10 other packages, confirming its role as shared infrastructure rather than a standalone API. On 12.1.1 and 12.2.2, behavior is essentially consistent with the 120.20 maintenance level of the source.