Search Results pre_export

Overview

XLA_AAD_LOADER_INSTALL_PVT is a private (PVT) PL/SQL package body in the APPS schema that supports the installation and loader infrastructure for Oracle Subledger Accounting (XLA) Application Accounting Definitions (AAD). In Oracle E-Business Suite 12.1.1 and 12.2.2, Subledger Accounting is the central accounting engine that derives journal entries and account balances from subledger transactions. Application Accounting Definitions are the metadata objects that define, for a given application and event, the journal line types, conditions, and account derivation rules used to produce those entries.

The package forms part of the internal machinery used to move, validate, and deploy AAD metadata during installation, upgrade, and patch application. Because it is classified as PVT, its entry points are not part of the supported public API surface; they are invoked by other XLA loader and installer packages, and by internal routines that the Application Accounting Definition Loader relies upon. The embedded header (xlaalins.pkb, version 120.0) and the constant C_FILE_NAME reference the loader upload logic, confirming its role in the AAD load and install chain. The package also contains a local tracing routine that writes to the FND_LOG framework using the module identifier xla.plsql.xla_aad_loader_install_pvt, providing diagnostic output at the statement, procedure, event, exception, error, and unexpected severity levels.

Key Procedures and Functions

• PRE_EXPORT — A preparatory routine invoked before an AAD export operation. Its purpose is to set up or validate the state required so that a subsequent export of application accounting definition metadata can proceed cleanly. This is the procedure most directly associated with the user search term "pre_export", and it is typically the first step in any export-oriented loader workflow.
• GET_SEGMENT — A retrieval function that returns a segment value used by the loader and installer logic. It supports the parsing or assembly of definition identifiers and segment strings during the load and install process.

Only these two procedures are documented in the ETRM metadata. No parameter lists are published for either routine, and neither should be assumed to have a freely callable signature.

Tables Accessed

The ETRM metadata records no table references through APPS synonyms for this package body at the level of detail captured. In practice, a loader/installer private package of this type interacts with the XLA definition and loader staging tables, including the application accounting definition repository and the upload/interface tables used to stage metadata prior to validation and deployment. Because the documented metadata does not enumerate these tables, the specific read and write targets should be confirmed by inspecting the live package source in the target environment rather than assumed.

Usage Notes

XLA_AAD_LOADER_INSTALL_PVT is not intended for direct invocation by end users or by custom application code. It is called internally by the AAD loader and installer flow, most commonly as part of concurrent program processing that installs or migrates application accounting definitions during patching, upgrade, or an explicit AAD load. The PRE_EXPORT procedure is engaged at the beginning of an export sequence, while GET_SEGMENT is consumed by the surrounding loader logic as it assembles definition content.

Referenced by zero other packages according to the metadata, it occupies a leaf position in the dependency graph, which reinforces its role as a private helper rather than a shared service. Tracing behavior is governed at runtime by the FND_LOG level; when logging is enabled for the xla.plsql.xla_aad_loader_install_pvt module, diagnostic messages surface through the standard EBS logging framework. Because the package is private and unsupported for customer extension, modifications are overwritten by patching, and any diagnostic or debugging effort should rely on FND_LOG output rather than code changes.