Results for “flex_value_set_name”

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

Overview

XLA_MAPPING_SETS_FVL is a reporting and validation view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Subledger Accounting (XLA) product. Its primary purpose is to present the definition of subledger accounting mapping sets—the user-defined rules that instruct Subledger Accounting how to derive accounts, segments, and values during journal entry generation—in a fully denormalized, user-readable form. Where the underlying transaction tables store internal numeric identifiers, language-independent codes, and lookup references, this view resolves those identifiers into meaningful names.

The _FVL suffix follows the standard Oracle naming convention for a "Flexfield Value / Validation" view: it is designed for use behind value set queries, descriptive flexfield lookups, and reporting layers where a display name is required rather than an ID. Because it joins against translation tables on USERENV('LANG'), the view returns descriptions in the session language of the querying user.

Underlying Base Objects

The view is defined over seven base objects, all accessed through APPS-owned synonyms:

• XLA_MAPPING_SETS_B — the base (language-independent) table holding mapping set definitions, context, chart of accounts, value set, and segment assignments.
• XLA_MAPPING_SETS_TL — the translation table supplying the Name and Description of each mapping set in the current language.
• FND_ID_FLEX_STRUCTURES_TL — the key flexfield structure translation table, providing the Accounting Chart of Accounts name.
• FND_ID_FLEX_SEGMENTS — the key flexfield segment definition, resolving the segment code to a segment name.
• FND_FLEX_VALUE_SETS — joined twice (aliases VAL and VAL1) to resolve the value set ID and the flex value set ID to their value set names.
• FND_APPLICATION_TL — the application translation table, resolving VIEW_APPLICATION_ID to VIEW_APPLICATION_NAME.
• FND_LOOKUP_TYPES_TL — the lookup type translation table, providing the meaning of the lookup type.

Most joins are outer joins ((+)), so rows are preserved even when translation rows or flexfield definitions are missing—an important characteristic when diagnosing incomplete or orphaned mapping set definitions.

Key Columns

• MAPPING_SET_CODE / AMB_CONTEXT_CODE — the concatenated key identifying a mapping set within an accounting methods builder context.
• NAME / DESCRIPTION — the user-facing label and description in the session language.
• ACCOUNTING_COA_ID / ACCOUNTING_COA_NAME — the chart of accounts assigned to the mapping set.
• VALUE_SET_ID / VALUE_SET_NAME and FLEX_VALUE_SET_ID / VALUE_SET_NAME — the input and output value sets used by the rule, mapped to the second occurrence of FLEX_VALUE_SET_NAME.
• FLEXFIELD_ASSIGN_MODE_CODE — indicates how the mapping is applied (for example, by segment or by value).
• FLEXFIELD_SEGMENT_CODE / FLEXFIELD_SEGMENT_NAME — the target accounting flexfield segment.
• VIEW_APPLICATION_ID / VIEW_APPLICATION_NAME — the application that owns the mapping set view, resolved via FND_APPLICATION_TL; this is the column most commonly targeted by users searching on "view_application_name".
• LOOKUP_TYPE / LOOKUP_TYPE_MEANING — the lookup governing the mapping set's permitted values.
• ENABLED_FLAG — whether the mapping set is active.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical uses include validating mapping set configuration, building custom reports of active rules, and troubleshooting journals where account derivation failed. The following query lists enabled mapping sets with their owning application and chart of accounts:

SELECT mapping_set_code, name, accounting_coa_name,
      view_application_name, lookup_type_meaning
FROM  xla_mapping_sets_fvl
WHERE  enabled_flag = 'Y'
ORDER BY view_application_name, mapping_set_code;

A second common pattern filters by owning application or by value set to inspect which rules consume a given value set. Joining this view to XLA_AMB_HEADERS or the journal line tables allows reconciliation of runtime accounting output against the configured mapping. For Subledger Accounting implementations and upgrades, XLA_MAPPING_SETS_FVL serves as the authoritative reporting layer for auditing mapping set definitions across Oracle EBS 12.1.1 and 12.2.2.