Search Results validate_and_compile_aad

Overview

XLA_AMB_AAD_PKG is an Oracle E-Business Suite (EBS) PL/SQL package owned by the APPS schema that supports the Subledger Accounting (XLA) infrastructure, specifically the Application Accounting Definition (AAD) and Accounting Methods Builder (AMB) configuration layer. The AAD is the central container that binds application accounting definitions to a ledger and controls how subledger transactions are transformed into accounting entries by the Subledger Accounting Engine. This package provides utilities used to validate and compile those definition components so that the runtime accounting engine can execute them efficiently.

In EBS releases 12.1.1 and 12.2.2, the package is documented in the EBS Technical Reference Manual (ETRM) as a VALID object with an API classification of OTHER, indicating it is an internal, supporting package rather than a published public API. Its primary role is to ensure that the setup data underpinning the AAD — header and line assignments, account derivation rules, descriptive flexfield mappings, conditions, and event class configurations — is internally consistent and compilable before accounting programs depend upon it.

Key Procedures and Functions

• VALIDATE_AND_COMPILE_AAD — the single documented routine in this package. It performs two related operations: it validates the definition of an Application Accounting Definition, and it compiles the definition into the runtime form that the Subledger Accounting Engine consumes. Validation verifies that assignment rules, conditions, and account derivation references are complete and consistent against the underlying event model. Compilation renders those rules into a form usable at transaction processing time. Because ETRM does not publish the parameter list, the precise signature should be confirmed from the actual package specification in the target instance.

Tables Accessed

The package accesses a broad set of XLA configuration tables through APPS synonyms. It reads the AAD header and line assignment tables (XLA_AAD_HEADER_AC_ASSGNS, XLA_AAD_LINE_DEFN_ASSGNS) to determine how account derivation rules are assigned. It references account attribute and derivation metadata through XLA_ACCT_ATTRIBUTES_B, XLA_ANALYTICAL_HDRS_B, XLA_ANALYTICAL_SOURCES, XLA_CONDITIONS, XLA_DESCRIPTIONS_B, XLA_DESCRIPT_DETAILS_B, and XLA_DESC_PRIORITIES to resolve sources, conditions, and descriptive detail priorities. It also draws on the event model tables XLA_EVENT_CLASSES_B, XLA_EVENT_CLASS_ATTRS, XLA_EVENT_CLASS_PREDECS, XLA_EVENT_SOURCES, and XLA_EVENT_TYPES_B to integrate the AAD with the correct event types. Errors encountered during validation and compilation are recorded in XLA_AMB_SETUP_ERRORS, providing a diagnosable log for setup administrators.

Usage Notes

XLA_AMB_AAD_PKG is typically invoked indirectly rather than by end users. The ETRM dependency data shows it is referenced by XLA_AAD_INSTALL_PVT, by itself (for internal helper calls), and by the concurrent program report package XLA_XLAABACR_XMLP_PKG. This indicates the package is driven by the AMB setup user interface and by the concurrent programs that create or regenerate Application Accounting Definitions. Administrators configuring accounting methods in the Accounting Methods Builder trigger this logic when they validate or generate an AAD, and the results are surfaced through XLA_AMB_SETUP_ERRORS.

Because the package is classified as OTHER and is part of the internal Subledger Accounting framework, custom code should not call it directly. Any integration or extension that requires AAD validation or compilation should use the supported public interfaces (such as the Accounting Methods Builder forms and their concurrent programs) so that upgrade paths and supportability are preserved.