Search Results xla_descriptions_b




Overview
Explore in AI Chat

Overview

The XLA_DESCRIPTIONS_B table is a core reference table within the Subledger Accounting (XLA) product of Oracle E-Business Suite, owned by the XLA schema. It stores all description definitions created for an application, providing the descriptive metadata that is subsequently attached to accounting header and line types. In practice, this table acts as the registry of allowable descriptions that Subledger Accounting uses when constructing and presenting accounting entries, ensuring consistent labeling and classification across subledger transactions.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone, suggesting it functions primarily as a reference or lookup hub rather than a link or satellite. The absence of discovered foreign key relationships reinforces that the table serves as an independent definition source, with its keys consumed by downstream configuration and transaction objects rather than depending on parent entities itself.

Key Information Stored

The table is defined with 12 documented columns. The most significant include:

  • APPLICATION_ID — Identifies the Oracle application that owns the description definition; part of the composite primary key.
  • AMB_CONTEXT_CODE — The Accounting Methods Builder context code, scoping the description to a specific subledger accounting context; part of the primary key.
  • DESCRIPTION_TYPE_CODE — Categorizes the kind of description being defined; part of the primary key.
  • DESCRIPTION_CODE — The unique code for the description entry; part of the primary key.
  • TRANSACTION_COA_ID — References the chart of accounts applicable to the transaction description.
  • ENABLED_FLAG — Indicates whether the description definition is active and available for use.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle audit columns tracking who created and last modified the record.
  • ZD_EDITION_NAME — The editioning column used for online patching and edition-based redefinition in EBS 12.2.x.

The surrogate primary key is defined by XLA_DESCRIPTIONS_B_PK, comprising APPLICATION_ID, AMB_CONTEXT_CODE, DESCRIPTION_TYPE_CODE, and DESCRIPTION_CODE. A unique index, XLA_DESCRIPTIONS_B_U1, adds ZD_EDITION_NAME to this composite, representing the business-key candidate inclusive of the editioning context.

Common Use Cases and Queries

Typical scenarios involve validating description configurations, reporting on enabled descriptions per application, and troubleshooting Subledger Accounting setups where descriptions fail to appear against accounting header or line types.

  • Listing all enabled descriptions for a given application and context:
SELECT description_code, description_type_code,
       transaction_coa_id, enabled_flag
  FROM xla.xla_descriptions_b
 WHERE application_id = :app_id
   AND amb_context_code = :context
   AND enabled_flag = 'Y';
  • Joining to application definitions to resolve application names for reporting.
  • Auditing configuration drift by comparing creation and update metadata across environments.
  • Feeding data dictionary extractions and integration mappings where description codes drive downstream labeling.

Related Objects

Because the mined relationship data classifies this table as standalone, no foreign keys are documented; nevertheless, the following objects are significant partners based on the description and key structure:

These objects are joined on APPLICATION_ID, AMB_CONTEXT_CODE, DESCRIPTION_TYPE_CODE, and DESCRIPTION_CODE to complete description resolution and reporting.