Search Results xla_sources




Overview
Explore in AI Chat

Overview

XLA_SOURCES_F_PKG is the Forms PL/SQL wrapper for the XLA_SOURCES entity within the Oracle E-Business Suite Subledger Accounting (XLA) architecture. Its header comment confirms that it is generated from the XLAUTB table-definition utility and carries the standard "Forms PL/SQL Wrapper" designation used throughout Oracle EBS for packages that expose a single base entity to the Oracle Forms runtime.

The underlying business object, XLA_SOURCES, defines the accounting sources available to the Subledger Accounting engine. Each source row describes a discrete data element — an amount, date, or attribute drawn from a subledger transaction table or derived through a PL/SQL function — that can be mapped into journal line definitions. The package therefore serves as the programmatic gateway through which the Accounting Methods Builder (AMB) and related setup forms create, modify, and delete source definitions. Because the package is declared AUTHID CURRENT_USER, it executes with the privileges of the calling schema rather than the package owner, consistent with Oracle's standard generated-wrapper convention.

Key Procedures and Functions

The package exposes seven documented procedures, corresponding to the standard generated-wrapper pattern:

  • INSERT_ROW — Creates a new source definition row. Its signature enumerates the full column set of the entity, including application and source code, source type, PL/SQL function name, flex value set, sum, visible, translated, and enabled flags, lookup type, datatype code, key flexfield attributes (segment code, flexfield application, ID flex code, key flexfield flag), descriptive name and description, source column and source table names, and the standard WHO audit columns.
  • LOCK_ROW — Acquires a pessimistic lock on an existing source row, using the primary key components (application ID, source code, source type code) so that concurrent form sessions cannot modify the same definition simultaneously.
  • UPDATE_ROW — Persists changes to an existing source definition following a successful lock.
  • DELETE_ROW — Removes a source definition from the entity.
  • ADD_LANGUAGE — Inserts a translation row, enabling the source name and description to be maintained in an additional language.
  • LOAD_ROW — Loads a fully specified row, typically used by the multilingual or seed-data loading paths.
  • TRANSLATE_ROW — Maintains the translated (TL) attributes of an existing source.

The procedures do not encapsulate business validation; their role is to provide a stable, Forms-callable interface to the underlying tables.

Tables Accessed

The wrapper reads and writes the following objects through APPS synonyms:

  • XLA_SOURCES_B — the base (non-translated) table holding the source definition, including the PL/SQL function name, datatype, flexfield attributes, and enablement flags.
  • XLA_SOURCES_TL — the translation table holding language-specific name and description values, maintained by ADD_LANGUAGE and TRANSLATE_ROW.
  • FND_APPLICATION — validates the owning application of the source.
  • FND_FLEX_VALUE_SETS — validates the flex value set referenced where a source draws values from a value set.
  • FND_LANGUAGES — supplies the installed language list used by the translation procedures.

Usage Notes

XLA_SOURCES_F_PKG is not intended for general application development. It is invoked by the Oracle Forms-based Subledger Accounting setup screens when an administrator defines or edits accounting sources, and by seed-data or language-loading routines that populate source definitions during installation or patching. The ETRM metadata records no other packages referencing it, which reflects its narrow role as a forms-layer wrapper rather than a shared business API.

Custom code should not call these procedures directly. Subledger Accounting source definitions are tightly coupled to the AMB configuration model, and inserting rows without corresponding journal line definition metadata can leave the accounting engine in an inconsistent state. Any extension work in this area should be performed through the supported setup forms or through Oracle-provided upgrade and loading utilities that invoke the wrapper in the correct sequence. The package is identical in behavior across EBS 12.1.1 and 12.2.2, as the XLA data model was not restructured between those releases.