Search Results flexfield_segment_code




Overview
Explore in AI Chat

Overview

XLA_MAPPING_SETS_VL is a validation view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the XLA (Subledger Accounting) product and exposes translated mapping set definitions used by the Subledger Accounting engine to derive accounting attribute values during journal creation. Mapping sets associate a subledger event, an accounting method, and a specific accounting attribute with the source of its value, such as an application column, a value set, or a lookup type. The view combines the base descriptive columns stored in XLA_MAPPING_SETS_B with the language-specific name and description held in XLA_MAPPING_SETS_TL, filtered to the session language via USERENV('LANG'). Its validation status is VALID at the documented release level. Because it presents denormalized, translation-aware metadata, the view is the preferred dictionary source for reporting on, auditing, or integrating with mapping set configuration rather than querying the underlying tables directly.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms in the APPS schema: XLA_MAPPING_SETS_B, which stores the language-independent attributes, and XLA_MAPPING_SETS_TL, which stores translated name and description text keyed by language. The join is performed on the composite key of MAPPING_SET_CODE and AMB_CONTEXT_CODE, and the TL row is restricted by T.LANGUAGE = USERENV('LANG'). The view also projects a ROW_ID pseudo-column derived from B.ROWID and surfaces the standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) from the base table. This structure follows the standard Oracle EBS _B/_TL pattern, where the _B table is the single source of truth and the _TL table provides multilanguage display attributes. The view does not introduce any independent storage; it is a pure projection and join.

Key Columns

  • MAPPING_SET_CODE / AMB_CONTEXT_CODE: The composite identifier of the mapping set and its accounting method (AMB) context; these form the join key to the TL table and are the primary lookup values.
  • NAME / DESCRIPTION: The translated display text from the _TL table in the session language.
  • ACCOUNTING_COA_ID: References the chart of accounts associated with the mapping set.
  • VALUE_SET_ID / FLEX_VALUE_SET_ID: Identifies the value set used when mapping to a flexfield segment or value set source.
  • FLEXFIELD_ASSIGN_MODE_CODE / FLEXFIELD_SEGMENT_CODE: Indicates how the flexfield value is assigned and which segment is targeted.
  • VIEW_APPLICATION_ID: Identifies the application owning the view that supplies the mapped value.
  • LOOKUP_TYPE: Specifies the lookup type when the mapping source is a lookup code.
  • ENABLED_FLAG: Indicates whether the mapping set is currently active (Y/N).
  • UPDATED_FLAG: Flags whether the mapping set definition has been changed and may require regeneration of the associated account derivation logic.
  • VERSION_NUM: Tracks the version of the mapping set definition for concurrency and upgrade purposes.

Common Use Cases and Queries

Typical uses include auditing active mapping sets for an accounting method, reconciling upgrade status after patches, and joining mapping set metadata to account derivation rules. The UPDATED_FLAG column is frequently queried to detect mapping sets modified since the last generation run. A representative query returns enabled mapping sets for a given context:

  • SELECT mapping_set_code, amb_context_code, name, enabled_flag, updated_flag, version_num FROM xla_mapping_sets_vl WHERE amb_context_code = :p_amb_context AND enabled_flag = 'Y' ORDER BY mapping_set_code;
  • SELECT mapping_set_code, name, flexfield_segment_code FROM xla_mapping_sets_vl WHERE updated_flag = 'Y';

Developers routinely filter by AMB_CONTEXT_CODE to isolate the accounting method, and by ENABLED_FLAG to exclude inactive configurations. Because the view already resolves the session language, reports built on it require no additional translation logic.