Search Results xla_mapping_set_values_n1

Overview

The XLA.XLA_MAPPING_SET_VALUES table is a core configuration object within the Oracle Subledger Accounting (SLA) framework, owned by the XLA schema. It stores the individual value entries that make up an Accounting Methods Builder (AMB) mapping set. Mapping sets are used to derive a target value from a source value during subledger journal line creation, supporting both accounting rule definitions and the derivation of account code combinations. Each row in this table represents one source-to-target value pairing within a given mapping set, scoped by the AMB context code and the mapping set code.

Under the heuristic Data Vault classification supplied in the metadata, this object is modeled as standalone, meaning it does not carry a mined foreign-key relationship to a parent hub or link. This is consistent with the fact that SLA mapping configuration is typically denormalized and keyed by a local surrogate identifier rather than enforced relational dependencies.

Key Information Stored

The table contains sixteen documented columns. The most significant are:

• MAPPING_SET_VALUE_ID – The surrogate primary key (XLA_MAPPING_SET_VALUES_PK), a NUMBER(15) that uniquely identifies each mapping set value row. It also appears as the leading column of the unique business index XLA_MAPPING_SET_VALUES_U1, together with ZD_EDITION_NAME.
• AMB_CONTEXT_CODE – The Accounting Methods Builder context that scopes the mapping set to a specific subledger application and accounting configuration.
• MAPPING_SET_CODE – Identifies the mapping set to which the value belongs. Together with AMB_CONTEXT_CODE, this forms the nonuniquely indexed lookup path XLA_MAPPING_SET_VALUES_N1.
• VALUE_CONSTANT – A literal value used when the mapping resolves to a constant rather than a code combination.
• VALUE_CODE_COMBINATION_ID – The target account code combination identifier when the mapping output is an account.
• EFFECTIVE_DATE_FROM and EFFECTIVE_DATE_TO – The date range over which the mapping value is valid, enabling date-effective derivation logic.
• INPUT_VALUE_TYPE_CODE and INPUT_VALUE_CONSTANT – Describe the type and literal content of the input side of the mapping.
• ENABLED_FLAG – Internal flag controlling whether the value row is active.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard WHO audit columns (foreign keys to FND_USER and FND_LOGINS).
• ZD_EDITION_NAME – Editioning support column, used to partition configuration across application editions.

Common Use Cases and Queries

Typical use cases include auditing mapping set configuration, tracing how a particular account was derived during journal creation, and validating date-effective coverage for SLA rules. A common query retrieves all enabled values for a given mapping set:

SELECT MAPPING_SET_VALUE_ID, VALUE_CONSTANT, VALUE_CODE_COMBINATION_ID, EFFECTIVE_DATE_FROM, EFFECTIVE_DATE_TO
FROM XLA.XLA_MAPPING_SET_VALUES
WHERE AMB_CONTEXT_CODE = :p_context
AND MAPPING_SET_CODE = :p_mapping_set
AND NVL(ENABLED_FLAG,'Y') = 'Y'
ORDER BY MAPPING_SET_VALUE_ID;

Because mapping set values map codes to constants or to account combinations, they are frequently joined to GL_CODE_COMBINATIONS via VALUE_CODE_COMBINATION_ID for account-detail reporting. Reconciliation and audit reports commonly filter on the effective date range to identify gaps or overlapping validity windows.

Related Objects

• GL_CODE_COMBINATIONS – Joined on VALUE_CODE_COMBINATION_ID to resolve the target accounting flexfield combination.
• FND_USER – Referenced through CREATED_BY and LAST_UPDATED_BY for audit attribution.
• FND_LOGINS – Referenced through LAST_UPDATE_LOGIN.
• XLA_MAPPING_SETS – Parent configuration table keyed logically by AMB_CONTEXT_CODE and MAPPING_SET_CODE.
• XLA_ACCOUNTING_RULES / XLA_ACCOUNTING_RULE_DETAILS – Consume mapping sets during journal line generation.
• XLA_ACCOUNTING_EVENTS and XLA_AE_LINES – Downstream subledger tables reflecting the derived accounts produced by mapping set evaluation.
• XLA.XLA_MAPPING_SET_VALUES_U1 and XLA.XLA_MAPPING_SET_VALUES_N1 – The unique and nonunique indexes supporting primary-key and lookup access paths.

Direct DML against this table should be avoided in production; access is intended through standard Oracle Applications programs as noted in the object documentation.