Search Results xla_mapping_sets_b_pk

Overview

The XLA_MAPPING_SETS_B table is a core configuration object within Oracle Subledger Accounting (XLA), the module responsible for generating accounting entries from subledger transactions across Oracle E-Business Suite 12.1.1 and 12.2.2. The table stores mapping sets that are created by end users and subsequently consumed by Account Derivation Rules to determine how subledger journal lines are derived during accounting event processing. In effect, a mapping set functions as a reusable lookup definition that translates an input value (such as a transaction attribute or source) into a corresponding output value, most commonly a chart of accounts segment or a flexfield assignment.

Because mapping sets are defined per application and per accounting context, the table acts as a definition repository rather than a transactional store. Rows are relatively static configuration data, updated infrequently, and they drive the derivation logic used consistently across periods and transactions. The heuristic Data Vault classification mined from the foreign key structure is satellite-leaning. This suggests that, in a dimensional or Data Vault model, XLA_MAPPING_SETS_B is best treated as an attribute-bearing structure that describes and holds the descriptive properties (such as the value set, segment assignment mode, and enabled flag) of a mapping set business key, rather than as an independent transactional hub or an associative link table.

Key Information Stored

The table’s primary key is XLA_MAPPING_SETS_B_PK, defined on the composite columns AMB_CONTEXT_CODE and MAPPING_SET_CODE. The AMB_CONTEXT_CODE identifies the accounting method or context in which the mapping set is valid, while MAPPING_SET_CODE is the user-facing code that uniquely names the mapping set. A separate unique index, XLA_MAPPING_SETS_B_U1, spanning AMB_CONTEXT_CODE, MAPPING_SET_CODE, and ZD_EDITION_NAME, serves as the business-key candidate supporting the multi-edition (ZD) architecture introduced for online patching in EBS 12.2.

Among the eighteen documented columns, the most significant for configuration and reporting include:

• MAPPING_SET_CODE — the user-defined identifier for the mapping set.
• AMB_CONTEXT_CODE — the accounting method builder context scope.
• ACCOUNTING_COA_ID — the chart of accounts the mapping set derives values for.
• VALUE_SET_ID and FLEX_VALUE_SET_ID — identify the value sets that constrain the input and output values.
• FLEXFIELD_ASSIGN_MODE_CODE — controls how flexfield segment values are assigned.
• FLEXFIELD_SEGMENT_CODE — the segment the mapping set ultimately targets.
• ENABLED_FLAG — active/inactive status of the mapping set.
• VIEW_APPLICATION_ID — the owning application, foreign-keyed to FND_APPLICATION.
• LOOKUP_TYPE — the lookup type associated with the mapping values.
• VERSION_NUM and UPDATED_FLAG — concurrency and change-tracking columns.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical use cases include auditing account derivation configuration, migrating mapping sets between environments, and troubleshooting journal derivation failures. A common query is to identify enabled mapping sets for a given application and context:

SELECT m.mapping_set_code,
       m.flexfield_segment_code,
       m.enabled_flag
FROM   xla_mapping_sets_b m
WHERE  m.amb_context_code = :context_code
AND    m.view_application_id = :app_id
AND    m.enabled_flag = 'Y';

To locate the owning application name, join to FND_APPLICATION on VIEW_APPLICATION_ID. Because the table feeds account derivation rules, DBAs and functional analysts also query it when validating that a newly defined mapping set will be available to the subledger accounting program before running Create Accounting. Edition-aware queries in 12.2 should account for the ZD_EDITION_NAME column.

Related Objects

The following objects are the most significant relationships based on the documented foreign keys:

• FND_APPLICATION — joined via XLA_MAPPING_SETS_B.VIEW_APPLICATION_ID = FND_APPLICATION.APPLICATION_ID; identifies the owning application.
• FRM_PART_VALUE_SETS — joined via XLA_MAPPING_SETS_B.VALUE_SET_ID = FRM_PART_VALUE_SETS.VALUE_SET_ID; defines the value set used to validate mapping values.
• XLA_MAPPING_SETS_TL — the translation table holding language-specific descriptions for each mapping set.
• XLA_MAPPING_SET_VALUES — stores the individual input-to-output value pairs belonging to a mapping set; it references this header through the composite key AMB_CONTEXT_CODE and MAPPING_SET_CODE.
• XLA_ACCT_DERIVATION_RULES — the account derivation rules that consume mapping sets during journal line derivation.
• FND_FLEX_VALUES / FND_FLEX_VALUE_SETS — provide the underlying flexfield value definitions referenced by the segment and value set columns.

Additional dependencies include the account derivation rule components and the subledger accounting program logic that resolves mapping sets at runtime. Understanding these relationships is essential when tracing how a specific transaction value is ultimately mapped to an accounting flexfield segment.