Search Results g_log_level

Overview

The package body APPS.XLA_AAD_DOWNLOAD_PVT is a private (PVT) PL/SQL package belonging to the Oracle Subledger Accounting (XLA) module in Oracle E-Business Suite releases 12.1.1 and 12.2.2. The XLA_AAD_ prefix indicates that the package supports the Subledger Accounting Account Analysis and Drilldown (AAD) feature set, while the _DOWNLOAD_PVT suffix identifies it as an internal utility responsible for exporting or downloading subledger accounting data for external consumption, offline analysis, or integration purposes. In the EBS architecture, the Account Analysis functionality provides a means for users to examine subledger journal entries, balances, and source transactions from multiple applications in a consolidated view. The download component extends this capability by serializing the retrieved data into a transportable format, allowing the results to be written to a server-side file for downstream processing, archival, or reporting.

As a private package, XLA_AAD_DOWNLOAD_PVT is not intended to be called directly by customers or third-party code. It is invoked internally by the Account Analysis Drilldown infrastructure, which may include public API wrappers, concurrent program entry points, or OAF-based user interface flows. The package depends on the FND_LOG logging framework for instrumentation, defining standard trace levels (statement, procedure, event, exception, error, and unexpected) and a default module identifier of xla.plsql.xla_aad_download_pvt. This instrumentation reflects the development standards for XLA packages, where meaningful diagnostic output can be enabled without modifying source code.

Key Procedures and Functions

The documented interface exposes a single procedure:

• DOWNLOAD — The primary procedure that performs the actual download operation. Its documented role is to retrieve account analysis data and emit it to a designated destination. The package body declares a global variable g_destination_file (VARCHAR2(240)), which strongly suggests the procedure writes output to a file whose name or path is resolved at runtime. The declaration of g_application_id and g_amb_context_code further indicates that the download is scoped by application and by an application context code, consistent with XLA’s multi-application architecture. Because the ETRM metadata does not publish the formal parameter list, no parameter signature is asserted here; callers should treat DOWNLOAD as an internally consumed entry point.

The package also contains a local private procedure named trace, which accepts a message, module name, and severity level and conditionally forwards output to FND_LOG. This routine is not part of the externally documented interface but controls the diagnostic behavior of DOWNLOAD.

Tables Accessed

The ETRM metadata for XLA_AAD_DOWNLOAD_PVT does not enumerate specific base tables, and the package is documented as referencing no APPS synonyms directly. This is consistent with its role as a formatting and export utility: data is most likely assembled by calling other XLA Account Analysis packages and the retrieval is delegated to those modules. Where table access does occur, it is expected to target XLA account analysis views and underlying Subledger Accounting repository objects such as journal entry headers and lines, accounting balances, and mapping metadata. Any writes are directed to output files rather than to transaction tables, given the presence of g_destination_file. Consumers should reconcile the actual data selection by reviewing the Account Analysis public APIs that this package complements.

Usage Notes

Typical invocation occurs through the Account Analysis and Drilldown user interface, where a user requests a download of analysis results, and through any concurrent program that wraps the same logic for batch generation of downloadable files. Custom code should not call XLA_AAD_DOWNLOAD_PVT directly, as it is a private package subject to change between releases. Integrators requiring similar output should instead use the supported public XLA APIs or the Account Analysis reporting interfaces. Because the package relies on server-side file destinations, administrators must ensure that the database directory used for g_destination_file is writable by the APPS schema and that appropriate UTL_FILE or directory object grants are in place. The package is referenced by one other package, confirming its role as a dependent helper rather than an entry point, and diagnostic tracing can be enabled through the standard FND logging profile options when troubleshooting download failures.