Search Results xla_acct_attributes_b




Overview
Explore in AI Chat

Overview

XLA_ACCT_ATTRIBUTES_B is a reference table in the XLA (Subledger Accounting) schema of Oracle E-Business Suite, available in both Release 12.1.1 and 12.2.2. It defines the set of accounting attributes that Oracle Subledger Accounting makes available to end users. Accounting attributes are pre-defined by the Subledger Accounting Architecture and represent the discrete pieces of information — such as ledger, currency, amount, accounting date, and account derivation sources — that can be referenced when constructing journal line definitions, application accounting definitions, and account derivation rules. The table therefore functions as the semantic dictionary that underpins the Subledger Accounting rule-building framework, ensuring that only architecture-approved attributes can be selected during configuration.

The table is a multilingual (_B) base table, with translated (_TL) counterparts when applicable. Its physical footprint is compact: the ETRM 12.2.2 documentation records 14 columns owned by XLA. From a Data Vault modeling perspective, the mined relationship metadata classifies this object heuristically as standalone — that is, it behaves as a reference or lookup hub of accounting attribute codes with no documented foreign-key dependencies to other tables. The primary key, XLA_ACCT_ATTRIBUTES_B_PK, is defined on the single column ACCOUNTING_ATTRIBUTE_CODE.

Key Information Stored

The most significant columns documented in the ETRM schema are:

  • ACCOUNTING_ATTRIBUTE_CODE — the primary key and business key of the table; uniquely identifies each architecture-defined accounting attribute.
  • DATATYPE_CODE — indicates the data type of the attribute (for example, character, number, or date), governing how the attribute may be used in rule definitions.
  • JOURNAL_ENTRY_LEVEL_CODE — specifies the level at which the attribute applies (for example, header, line, or distribution level) within the journal entry structure.
  • ASSIGNMENT_EXTENSIBLE_FLAG — denotes whether the attribute can be assigned through extensibility, such as via descriptive flexfields.
  • ASSIGNMENT_REQUIRED_CODE — indicates whether assignment of a value to the attribute is mandatory during rule configuration.
  • ASSIGNMENT_GROUP_CODE — groups related attributes so that they are presented or assigned together in the configuration user interface.
  • ASSIGNMENT_LEVEL_CODE — the level at which the attribute may be assigned in the accounting rules (for example, application, definition, or line level).
  • INHERITED_FLAG — identifies attributes whose values are inherited from a parent context rather than sourced directly.
  • ZD_EDITION_NAME — the editioning identifier introduced in 12.2 online patching; it participates in the unique index XLA_ACCT_ATTRIBUTES_B_U1, which is defined on (ACCOUNTING_ATTRIBUTE_CODE, ZD_EDITION_NAME).
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide standard WHO-style audit tracking for each row.

Note that the surrogate primary key on ACCOUNTING_ATTRIBUTE_CODE and the business-key unique index incorporating ZD_EDITION_NAME serve distinct roles: the former enforces entity integrity, while the latter supports edition-aware uniqueness under the 12.2 patching model.

Common Use Cases and Queries

Subledger Accounting implementers and support analysts query this table when troubleshooting rule configuration, validating which attributes are available, and documenting the mapping between accounting attributes and their intended usage. Typical scenarios include reviewing all attributes permitted at line level, or identifying attributes that are extensible and thus usable with descriptive flexfield sources.

A representative query lists attributes by journal entry level and assignment characteristics:

  • SELECT accounting_attribute_code, datatype_code, journal_entry_level_code, assignment_required_code, assignment_group_code, inherited_flag FROM xla.xla_acct_attributes_b WHERE journal_entry_level_code = 'L';
  • SELECT accounting_attribute_code, assignment_required_code FROM xla.xla_acct_attributes_b WHERE assignment_extensible_flag = 'Y';

In reporting, the table is joined to account derivation and journal line definition tables to expose friendly attribute names alongside configuration metadata, and is used in reconciliation scripts to verify that a given attribute referenced by an accounting rule exists in the approved architecture set. Because the table is a reference object, queries against it are low volume and highly cacheable.

Related Objects

The ETRM metadata classifies the object as standalone, so the documented relationship data is limited. Based on Subledger Accounting architecture, the most significant related objects include:

  • XLA_ACCT_ATTRIBUTES_TL — the translated table that supplies language-specific attribute names and descriptions, joined on ACCOUNTING_ATTRIBUTE_CODE.
  • XLA_ACCT_ATTR_ASSIGNMENTS — records assignments of accounting attributes to application accounting definitions and journal line types; joined on ACCOUNTING_ATTRIBUTE_CODE.
  • XLA_ACCOUNTING_ATTRIBUTES_VL — the view commonly used by configuration forms, exposing attribute codes alongside translated names.
  • XLA_ACCT_DERIVATION_RULES_B — account derivation rules that reference accounting attributes as sources or targets.
  • XLA_JOURNAL_LINES_B and associated journal line definition objects — the rule structures whose columns are populated from the attribute set defined here.

Implementers should treat XLA_ACCT_ATTRIBUTES_B as read-only reference data; new attributes are delivered by Oracle patches rather than inserted manually, since the attribute list is owned by the Subledger Accounting Architecture.