Search Results xla_source_type




Overview
Explore in AI Chat

Overview

The view APPS.XLA_AAD_HDR_ACCT_ATTRS_FVL is a reporting and integration-facing construct within the Oracle E-Business Suite Subledger Accounting (XLA) architecture. It exposes the header-level configuration that links subledger accounting attributes to their sources and application accounting definitions. In the context of Oracle EBS 12.1.1 and 12.2.2, this view presents a denormalized, language-aware picture of the Accounting Attribute Definition (AAD) header records, resolving foreign keys into descriptive names for source, source type, and assignment group. It is commonly used by functional and technical consultants to inspect how a given accounting attribute — for example, an amount, a currency, or a date — is sourced during the creation of subledger journal entries.

Underlying Base Objects

The view is defined over four referenced objects, joined through outer and inner joins. The driving table is XLA_AAD_HDR_ACCT_ATTRS (a synonym over the base AAD header accounting attribute table), aliased as AHA. It is joined to XLA_ACCT_ATTRIBUTES_VL (aliased AAL) on accounting_attribute_code to retrieve attribute metadata. Source-level descriptions are obtained from XLA_SOURCES_TL (aliased SOU) via an outer join on the composite key of application_id, source_code, and source_type_code. Two references to XLA_LOOKUPS (aliased LKP1 and LKP2) provide translated meaning values for source_type_code (lookup type XLA_SOURCE_TYPE) and assignment_group_code (lookup type XLA_ACCT_ATTR_ASSGN_GROUP). The XLA_SOURCES_TL join is filtered by USERENV('LANG') so that the source name is returned in the session language.

Key Columns

The view exposes a broad set of columns. Identity and context columns include row_id, application_id, amb_context_code, product_rule_type_code, product_rule_code, event_class_code, and event_type_code. The sourcing triad consists of source_application_id, source_type_code, and source_code. Descriptive and translated columns include source_name, source_type_dsp (the meaning of the XLA_SOURCE_TYPE lookup), assignment_group_code, and assignment_group_name. Attribute-level details are supplied through accounting_attribute_code, accounting_attribute_name, journal_entry_level_code, assignment_required_code, assignment_level_code, and datatype_code. The event_class_default_flag indicates whether the attribute is defaulted at the event class level. Standard audit columns — creation_date, created_by, last_update_date, last_updated_by, and last_update_login — round out the projection.

Common Use Cases and Queries

A frequent application is to determine which accounting attributes apply to a given event class or product rule, and how their source type is defined. Because the user searched for xla_source_type, the following query isolates the source type meaning alongside the source and attribute descriptions:

  • Filter by event class: SELECT event_class_code, accounting_attribute_name, source_name, source_type_dsp FROM xla_aad_hdr_acct_attrs_fvl WHERE event_class_code = :p_event_class;
  • Inspect source type distribution: SELECT source_type_code, source_type_dsp, COUNT(*) FROM xla_aad_hdr_acct_attrs_fvl GROUP BY source_type_code, source_type_dsp;
  • Locate attributes by rule: SELECT product_rule_code, accounting_attribute_code, assignment_group_name FROM xla_aad_hdr_acct_attrs_fvl WHERE application_id = :p_appl_id;

These queries are valuable when troubleshooting subledger journal entry generation, validating custom accounting configurations, or documenting the metadata that drives Create Accounting. Analysts should note that the view returns translated values and relies on the session language, and that outer joins on the source and lookup tables may yield null descriptions where configuration data is incomplete.