Search Results xla_xlaabacr_xmlp_pkg




Overview
Explore in AI Chat

Overview

The APPS.XLA_XLAABACR_XMLP_PKG package is a generated Oracle Reports PL/SQL library package that backs the Subledger Accounting account analysis reporting infrastructure in Oracle E-Business Suite releases 12.1.1 and 12.2.2. The naming convention — the XMLP_PKG suffix combined with the XLA module prefix — identifies it as the server-side PL/SQL unit produced automatically by Oracle Reports when an XML Publisher (XMLP) report definition is compiled and deployed against the APPS schema.

The package encapsulates the report-level logic required to execute the underlying account analysis report: initializing runtime state, resolving the concurrent program context, assembling the query predicates that filter accounting data, and returning control and status information to the Reports engine. It is a pure reporting artifact rather than a business API; the API classification is documented as OTHER, and no other packages in the instance reference it. Its role is therefore confined to the execution path of the report with which it is associated.

Key Procedures and Functions

The ETRM metadata documents fifteen procedures and functions within the package. They fall into three functional groups.

Tables Accessed

The package reads from two Subledger Accounting repository tables, accessed through APPS synonyms:

  • XLA_ACCTG_METHOD_RULES — the accounting method rules that determine how subledger transactions are converted into journal entries; the report draws on these rules to present the accounting derivation underlying the analysis.
  • XLA_PRODUCT_RULES_B — the product rules that govern application-specific accounting behaviour, providing the metadata needed to interpret the selected accounting methods.

Both are reference and setup tables; the report reads them to drive selection and display rather than to modify them.

Usage Notes

This package is not intended for direct invocation. It is called by the Oracle Reports runtime when the associated XML Publisher report is executed from the Submit Request form, the concurrent manager, or an XML Publisher delivery. Custom code should never call its procedures directly, because the parameter values it returns are meaningful only inside an active report execution context. Because the object is auto-generated, any modification is lost on redeployment of the report definition, and the supported approach to extension is to customize the report itself or to build a separate custom package that reads the underlying XLA tables.