Search Results validate_adr_compatibility




Overview
Explore in AI Chat

Overview

The APPS.XLA_AAD_LOADER_UTIL_PVT package is a private (PVT) utility package within the Oracle E-Business Suite Subledger Accounting (XLA) architecture. Its principal responsibility is to support the Application Accounting Definition (AAD) loader, the mechanism by which subledger accounting setup metadata — specifically application accounting definitions and their constituent components — is staged, validated, compiled, and committed into the XLA metadata repository. The package provides the low-level infrastructure that the public AAD loader APIs depend upon: staging-area resolution for an Accounting Methods Builder (AMB) context, record locking within the AMB staging tables, error capture and reset, request coordination, definition purging, and the rebuilding of accounting views. In EBS 12.1.1 and 12.2.2 the package is compiled with AUTHID CURRENT_USER, and the header revision indicates ongoing maintenance through the 12.1.x release line. Because it is classified as PVT, it is not part of Oracle's supported public API surface, though it is referenced by ten other packages in the XLA schema.

Key Procedures and Functions

The documented program units address the lifecycle of an AAD load operation:

  • GET_STAGING_CONTEXT_CODE — Returns the AMB context code associated with the staging area for a given application and AMB context.
  • LOCK_AREA — Locks all records in the AMB tables belonging to a specified AMB context, serialising concurrent loader activity.
  • PURGE — Removes all application accounting definitions and their components for a specified AMB context code, preserving mapping sets and analytical criteria.
  • PURGE_AAD and PURGE_SUBLEDGER_SEED — Targeted removal of AAD data and of subledger seed definitions respectively.
  • PURGE_HISTORY and MERGE_HISTORY — Manage historical (audit) definition records held in the history tables.
  • INSERT_ERRORS, INSERT_AADLOADERLOG, RESET_ERRORS, and STACK_ERROR — Error and log management. STACK_ERROR accumulates diagnostic messages; RESET_ERRORS clears prior error state; INSERT_ERRORS and INSERT_AADLOADERLOG persist them to the loader error and log tables.
  • COMPILE — Compiles the staged accounting definition components into executable form.
  • COMPATIBLE_API_CALL and VALIDATE_ADR_COMPATIBILITY — Check API and Accounting Definition Repository compatibility before processing.
  • GET_SEGMENT — Resolves a segment value used during definition assembly.
  • WAIT_FOR_REQUEST — Synchronises with a concurrent request, typically the loader or view-rebuild job.
  • REBUILD_AC_VIEWS — Reconstructs the accounting views that materialise the compiled definitions.

Tables Accessed

The package reads and writes across the XLA metadata and loader schema. FND_APPLICATION supplies application identity for context resolution. Definition and component data reside in XLA_AADS_H, XLA_AAD_HDR_ACCT_ATTRS, XLA_AAD_HEADER_AC_ASSGNS, XLA_AAD_LINE_DEFN_ASSGNS, and XLA_AMB_COMPONENTS_H. Staging and runtime state are held in XLA_AAD_LOADER_DEFNS_T, XLA_AAD_LOADER_LOGS, and XLA_AAD_LOADER_LOGS_S. Error capture uses XLA_AMB_SETUP_ERRORS. Supporting reference tables include XLA_ACCTG_METHOD_RULES, XLA_ACCT_LINE_TYPES_B, XLA_ACCT_LINE_TYPES_TL, XLA_ANALYTICAL_DTLS_B, and XLA_ANALYTICAL_DTLS_TL.

Usage Notes

This package is invoked indirectly through the AAD loader and AMB setup flows, typically from concurrent programs that upload, compile, or purge subledger accounting definitions, and from the Application Accounting Definitions setup pages in the Subledger Accounting responsibility. It is not intended for direct invocation by custom code. The presence of STACK_ERROR and INSERT_AADLOADERLOG in the documented interface explains why searches concerning loader failures frequently reference this package: diagnostic output from failed definition loads is funnelled through these routines into XLA_AAD_LOADER_LOGS and XLA_AMB_SETUP_ERRORS.