Search Results xla_mapping_set_values




Overview
Explore in AI Chat

Overview

The XLA_MAPPING_SET_VALUES table is a core configuration object within the XLA (Subledger Accounting) schema of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It stores the mapping of account or segment values to a source value for a mapping set. Mapping sets allow Subledger Accounting to translate a value originating from a subledger transaction source into a target accounting flexfield value — either a complete account or an individual segment — based on effective-dated rules. Each row represents a single mapping rule entry within a defined mapping set, defining how an input value is transformed into the corresponding output value used during journal line creation.

From a Data Vault modeling perspective, the heuristic classification for this object is standalone. A standalone classification suggests the table functions primarily as an independent hub or reference entity rather than as a link between two business entities. In practice, XLA_MAPPING_SET_VALUES behaves as a reference-data satellite: it carries descriptive detail — the mapping rule definition and its effective-dating attributes — attached to the mapping set business key, with the ZD_EDITION_NAME column supporting the editioning model used in 12.2.x.

Key Information Stored

The table is documented with sixteen physical columns. The surrogate primary key is MAPPING_SET_VALUE_ID, enforced by the constraint XLA_MAPPING_SET_VALUES_PK. A second unique index, XLA_MAPPING_SET_VALUES_U1, spans MAPPING_SET_VALUE_ID and ZD_EDITION_NAME, which is a business-key candidate rather than a true natural key given the presence of the surrogate identifier.

The most important columns for querying and interpreting the data include:

  • MAPPING_SET_VALUE_ID — the surrogate primary key uniquely identifying each mapping rule row.
  • MAPPING_SET_CODE — identifies the mapping set to which this value rule belongs; the principal join key back to the mapping set definition.
  • AMB_CONTEXT_CODE — the Application Message Board context under which the mapping set operates, tying the rule to a specific subledger application context.
  • INPUT_VALUE_TYPE_CODE and INPUT_VALUE_CONSTANT — define the source side of the mapping, specifying the type of input value and, where applicable, a constant input.
  • VALUE_CONSTANT and VALUE_CODE_COMBINATION_ID — define the output side, holding either a constant output value or a reference to a code combination (account) identifier.
  • EFFECTIVE_DATE_FROM and EFFECTIVE_DATE_TO — control the date range during which the mapping rule is valid, enabling effective-dated rule maintenance.
  • ENABLED_FLAG — indicates whether the mapping rule is currently active.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
  • ZD_EDITION_NAME — the editioning column supporting the 12.2.x online patching architecture.

Common Use Cases and Queries

Typical use cases include auditing the mapping rules configured for a subledger, troubleshooting why a transaction produced an unexpected account derivation, and reporting on active effective-dated mappings for a given period. A representative query retrieves enabled rules for a mapping set:

  • SELECT mapping_set_value_id, input_value_type_code, input_value_constant, value_constant, value_code_combination_id, effective_date_from, effective_date_to FROM xla_mapping_set_values WHERE mapping_set_code = :p_mapping_set_code AND enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN effective_date_from AND NVL(effective_date_to, TRUNC(SYSDATE));
  • Joining VALUE_CODE_COMBINATION_ID to the accounting flexfield tables resolves the target account segments for reporting.
  • Effective-dating analysis highlights overlapping or gaps in rule coverage across accounting periods.

Related Objects

The following objects are most significant in relation to XLA_MAPPING_SET_VALUES: