Search Results xla_cmp_source_pkg




Overview
Explore in AI Chat

Overview

The APPS.XLA_CMP_SOURCE_PKG package body is a component of the Oracle E-Business Suite Subledger Accounting (XLA) engine, specifically within the XLA comparison and source-definition infrastructure. In EBS 12.1.1 and 12.2.2, Subledger Accounting provides a centralized accounting model where every subledger (Payables, Receivables, Assets, and others) maps its transactions into a common accounting schema. That mapping is driven by metadata definitions known as sources, which identify the columns, flexfield values, and derived attributes from which accounting amounts and identifiers are drawn. XLA_CMP_SOURCE_PKG supports the framework that compares, generates, and caches these source definitions so the accounting engine can resolve them efficiently at runtime.

The package is classified as an internal utility (API classification OTHER). It is not a public extension API; it is invoked internally by the XLA program-generation and accounting-definition machinery. Oracle documents it as VALID in the APPS schema and notes that it is referenced by eleven other database objects, confirming its role as a foundational dependency rather than a top-level entry point.

Key Procedures and Functions

ETRM 12.2.2 documents ten procedures and functions within this package body. Their names reflect the generate-cache-resolve pattern typical of XLA metadata processing:

  • GENERATESOURCE — Builds or materializes a source definition for use by the accounting engine.
  • GENERATEPARAMETERS — Produces the parameter definitions associated with generated sources.
  • GET_OBJ_PARM_FOR_TAB — Retrieves the object parameters relevant to a given table, supporting table-to-parameter mapping.
  • CACHESOURCE — Stores source metadata in session or package-level cache to avoid repeated resolution.
  • STACKSOURCE — Maintains a stack of active source definitions during nested generation or comparison processing.
  • CACHEAADOBJECT — Caches an Application Accounting Definition (AAD) object referenced during source resolution.
  • GETAADOBJECTPOSITION — Returns the position or ordering of an AAD object within its parent structure.
  • GETSOURCESINAADOBJECT — Enumerates the sources defined within a specific AAD object.
  • FLEX_VALUES_EXIST — Validates whether flexfield values exist for a referenced key flexfield or value set.
  • GENERATEGETMEANINGAPI — Generates the API used to retrieve the meaning text associated with a source lookup value.

These routines work collectively to translate declarative source and AAD metadata into executable resolution logic.

Tables Accessed

The package reads and writes the following objects, accessed through APPS synonyms:

  • XLA_SOURCES_B — the base table holding source definitions; read to obtain and cache source metadata.
  • XLA_SOURCES_TL — the translation table supplying language-specific source names and descriptions.
  • XLA_SOURCE_PARAMS — parameters belonging to each source; resolved via GENERATEPARAMETERS and GET_OBJ_PARM_FOR_TAB.
  • FND_APPLICATION — application registration data used to qualify sources by application.
  • FND_FLEX_VALUE_SETS and FND_FLEX_VALIDATION_TABLES — key flexfield value set and validation metadata used by FLEX_VALUES_EXIST.
  • FND_LOG — the standard EBS logging facility for diagnostic output.
  • DBMS_SQL and PLITBLM — Oracle-supplied packages used for dynamic SQL and PL/SQL table manipulation.

Usage Notes

XLA_CMP_SOURCE_PKG is an internal dependency and is not intended for direct invocation by custom code. It is called by the eleven dependent XLA packages, including XLA_CMP_PAD_PKG, XLA_CMP_STRING_PKG, XLA_ENVIRONMENT_PKG, and XLA_EXCEPTIONS_PKG, during Subledger Accounting configuration validation, application accounting definition generation, and runtime source resolution. Practically, it executes whenever an accounting method, definition, or source is created, validated, or applied — for example, when running the Create Accounting concurrent program or when generating subledger accounting program code. Customization should target documented public XLA APIs rather than this package; altering it risks invalidating the accounting definition framework. DBAs reviewing XLA performance may encounter it in dependency chains and trace files, where its caching routines (CACHESOURCE, CACHEAADOBJECT) are frequently the source of recursive SQL.