Search Results source_type_dsp




Overview

The view APPS.XLA_AAD_HDR_ACCT_ATTRS_FVL is a reporting and integration artifact within the Subledger Accounting (XLA) product of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It exposes the header-level accounting attribute assignments defined for Application Accounting Definitions (AADs), enriching the raw configuration data with translated names and lookup meanings. Its primary purpose is to present a denormalized, human-readable projection of the relationship between accounting attributes, subledger sources, and the header rules that bind them, so that functional users, implementers, and downstream integrations can inspect how a given AAD derives its journal entry attributes without joining multiple base tables manually.

The suffix _FVL indicates that this is a "Flexfield Value Language" style view designed for language-sensitive display. It resolves the source type code to its user-facing meaning via the lookup XLA_SOURCE_TYPE, which is precisely the basis for the SOURCE_TYPE_DSP column — the column the user searched for. That column provides the translated display value of the source type (for example, whether the source is a system-generated or user-entered value) used to classify where a particular accounting attribute value originates.

Underlying Base Objects

The view is defined over the following documented base objects:

All joins to the translation and lookup objects are outer joins ((+)), with XLA_SOURCES_TL additionally constrained by USERENV('LANG') so that only the session-language row is returned. This ensures rows are not lost when a translation or lookup meaning is unavailable.

Key Columns

Common Use Cases and Queries

This view is typically queried to audit or troubleshoot how a specific AAD sources each accounting attribute. A common pattern filters by account definition and displays the source type meaning:

  • Listing all attribute assignments for an event class, showing SOURCE_TYPE_DSP to confirm whether values are system or user derived.
  • Verifying that required accounting attributes have an assignment within a given product rule.
  • Reporting on the sources and assignment groups configured for a subledger application during implementation review.

Representative query:

SELECT event_class_code, accounting_attribute_name, source_type_dsp, source_name, assignment_required_code FROM xla_aad_hdr_acct_attrs_fvl WHERE application_id = :app_id AND product_rule_type_code = :rule_type ORDER BY event_class_code, accounting_attribute_name;

Because the view already resolves lookup meanings and translated names, it removes the need to join XLA_LOOKUPS and the translation tables directly, making it suitable for concurrent-program extracts, OAF pages, and integration queries where a display-ready result set is required.