Search Results xla_ae_sources_pkg




Overview
Explore in AI Chat

Overview

XLA_AE_SOURCES_PKG is a PL/SQL package body owned by the APPS schema that forms part of the Oracle E-Business Suite Subledger Accounting (SLA) engine. Its role is to resolve, describe, and format the "sources" and related descriptive metadata that the SLA engine attaches to accounting events, journal entries, and accounting lines. Sources in SLA represent the business values carried from a subledger transaction (for example an invoice number, a supplier name, or a distribution amount) into the accounting model, where they are used by journal line definitions, mapping sets, and segment rules.

The package is therefore a metadata and description utility: rather than performing accounting itself, it supplies the human-readable labels, application identifiers, and system source values that the Create Accounting process and related inquiry pages require. It is classified as an OTHER API, indicating it is an internal helper package rather than a documented public API, and it is referenced by approximately fifty other database objects within the SLA schema, confirming its position as a shared low-level service.

Key Procedures and Functions

  • GETSYSTEMSOURCENUM — Returns a system-generated numeric source value used when a source is not derived from user data but supplied by the application.
  • GETSYSTEMSOURCEDATE — Returns a system-generated date source value, typically the accounting date or event date defaulted by the engine.
  • GETSYSTEMSOURCECHAR — Returns a system-generated character source value, used for string-typed system sources.
  • GETLOOKUPMEANING — Retrieves the meaning (displayed description) for a lookup code, translating a stored value into a user-facing label.
  • GET_MAPPING_FLEXFIELD_NUMBER — Resolves the numeric value of a mapping flexfield member, used when mapping sets define numeric output segments.
  • GET_MAPPING_FLEXFIELD_CHAR — Resolves the character value of a mapping flexfield member for string-typed segment output.
  • DATE_TO_CHAR — Converts a date value into its character representation so that date sources can be presented consistently in journal entry descriptions and inquiry screens.
  • GETAPPLICATIONNAME — Returns the translated application name for a given application identifier, sourced from the application translations table.
  • GETSOURCENAME — Returns the translated name of a source, used in journal line and description templates.
  • GETACCOUNTINGSOURCENAME — Returns the translated name of an accounting source, distinguishing sources created specifically within the accounting model.
  • GETCOMPONENTNAME — Returns the descriptive name of a component referenced by accounting definitions, supporting consistent labelling across SLA setup and inquiry.

Tables Accessed

The package reads translation and setup tables exclusively; no transactional accounting tables are written. FND_APPLICATION_TL supplies translated application names for GETAPPLICATIONNAME. FND_LOOKUP_VALUES provides lookup code meanings via GETLOOKUPMEANING. XLA_SOURCES_TL and XLA_ACCT_ATTRIBUTES_TL supply translated source and accounting attribute names for GETSOURCENAME and GETACCOUNTINGSOURCENAME. XLA_ACCT_LINE_TYPES_TL and XLA_MAPPING_SETS_TL provide line type and mapping set descriptions, while XLA_MAPPING_SET_VALUES holds the flexfield member values resolved by GET_MAPPING_FLEXFIELD_NUMBER and GET_MAPPING_FLEXFIELD_CHAR. XLA_SEG_RULES_TL and XLA_DESCRIPTIONS_TL supply segment rule and description template text. PLITBLM is the standard Oracle PL/SQL table-handling package used for array operations.

Usage Notes

XLA_AE_SOURCES_PKG is invoked internally by the Subledger Accounting engine during Create Accounting and by SLA inquiry forms, rather than being called directly from custom code. The companion packages XLA_AE_JOURNAL_ENTRY_PKG, XLA_JE_VALIDATION_PKG, XLA_ACCOUNTING_CACHE_PKG, XLA_ACCOUNTING_ERR_PKG, and XLA_EXCEPTIONS_PKG all depend on it, as does the Create Accounting concurrent program chain. Because the package is not a documented public API, its signatures should be treated as internal and subject to change between 12.1.1 and 12.2.2; developers extending SLA reporting or journal line descriptions should reference the seeded source and accounting attribute definitions instead of calling these routines directly.