Results for “key_flexfield_flag”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

XLA_SOURCES_VL is a multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite, defined for the XLA - Subledger Accounting product. It presents subledger accounting source definitions together with their language-translated names and descriptions. A "source" in Subledger Accounting (SLA) is an input value — such as an amount, date, or code — captured from a subledger transaction and made available to the accounting program that creates journal entries. Sources are the building blocks referenced by journal line definitions, account derivation rules, and mapping sets.

The VL suffix indicates that the view joins a base table to its translation table and filters the translated rows to the session's runtime language using USERENV('LANG'). The view is therefore exposed for reporting, integration, and inquiry purposes: users see the source name and description in their own language while the underlying non-translated attributes remain language-independent. Because it is not a table, the view cannot be updated directly; source definitions are maintained through the SLA setup pages or the underlying base tables.

Underlying Base Objects

The ETRM metadata documents two referenced base objects, both exposed to APPS as synonyms:

  • XLA_SOURCES_B — the base (non-translated) table holding the source definition, including its application, source type, data type, and validation attributes.
  • XLA_SOURCES_TL — the translation table holding the language-specific NAME and DESCRIPTION, keyed by LANGUAGE.

The join is performed on three columns — APPLICATION_ID, SOURCE_CODE, and SOURCE_TYPE_CODE — which together form the logical key of a source. The VL view selects the ROWID of the base table as ROW_ID and appends the translated NAME and DESCRIPTION. Only rows whose translation language equals the session language are returned; effectively every source is presented exactly once per language. The remaining columns are drawn entirely from XLA_SOURCES_B and are identical across languages.

Key Columns

Common Use Cases and Queries

The view is typically queried to list available sources for a given subledger application, to resolve the translated display name for a SOURCE_CODE, or to feed integration and reporting logic. A common scoped query filters by application and source type, joining the view to journal line definition tables where required.

SELECT application_id,
       source_type_code,
       source_code,
       name,
       datatype_code,
       enabled_flag
FROM   apps.xla_sources_vl
WHERE  application_id = 200
AND    enabled_flag  = 'Y'
ORDER  BY name;

To locate the physical column behind a source, query SOURCE_TABLE_NAME and SOURCE_COLUMN_NAME for the relevant key:

SELECT source_code, name, source_table_name, source_column_name
FROM   apps.xla_sources_vl
WHERE  application_id   = 200
AND    source_type_code = 'ADJUSTED';

Because the view joins the translation table, results automatically reflect the language of the querying session. Analysts should note that the reported ROW_ID refers to XLA_SOURCES_B, and that sources created without an active translation for a given language may appear only after the corresponding XLA_SOURCES_TL row is present.