Results for “xla_merge_seg_maps”

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

Overview

XLA_MERGE_SEG_MAPS is a Subledger Accounting (XLA) table in the Oracle E-Business Suite database. According to the ETRM repository, its documented purpose is to store the segment mapping for third party merge operations. Third party merge is the mechanism by which Oracle Subledger Accounting and its related applications (Payables, Receivables, Assets, and others) re-point historical accounting entries from one source entity to another — for example, when a supplier, customer, or asset is merged into a surviving entity. Because accounting flexfield segment values frequently carry entity-specific identification, a mapping from the old segment value to the new segment value is required so that historical journal lines remain meaningful and consistent after the merge completes. XLA_MERGE_SEG_MAPS preserves exactly that from-value to to-value relationship, scoped by application, ledger, event, and segment.

The object is documented as VALID in the XLA schema and is owned by XLA. Its physical structure in 12.2.2 comprises 16 columns. The ETRM heuristic Data Vault classification is standalone, meaning the mined foreign-key topology does not suggest a hub, link, or satellite role for this table; it is best modeled as an independent mapping or reference table rather than as part of a normalized Data Vault hub-and-spoke structure.

Key Information Stored

The primary key is defined by the constraint XLA_MERGE_SEG_MAPS_PK, which comprises five columns: EVENT_ID, APPLICATION_ID, LEDGER_ID, SEGMENT_CODE, and FROM_VALUE. These five columns together form the business-key candidate — the combination that uniquely identifies a mapping row. EVENT_ID ties the row to the subledger merge event being processed; APPLICATION_ID identifies the owning subledger application; LEDGER_ID scopes the mapping to a specific accounting ledger; SEGMENT_CODE identifies which accounting flexfield segment is being remapped; and FROM_VALUE is the pre-merge segment value.

The most significant remaining columns include:

• TO_VALUE — the post-merge segment value that replaces FROM_VALUE.
• CHART_OF_ACCOUNTS_ID — the chart of accounts context for the segment mapping. This column is the only documented foreign key reference, pointing to GL_MGT_SEG_UPGRADE_H.
• CREATION_DATE, CREATED_BY — standard audit columns recording when and by whom the mapping row was created.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit trail for the most recent modification.
• PROGRAM_UPDATE_DATE, PROGRAM_APPLICATION_ID, PROGRAM_ID, REQUEST_ID — the concurrent program and request context under which the row was inserted or updated, enabling traceability back to the merge request.

Note that while the PK is a composite surrogate over the five key columns, the natural business key is effectively the same set, since no separate single-column surrogate identifier is documented.

Common Use Cases and Queries

The principal use case is reconciliation of third party merge activity. Subledger and GL teams query this table to verify that historical accounting entries have been correctly re-pointed after a supplier, customer, or asset merge. A typical query retrieves all mappings for a given event and ledger:

• SELECT segment_code, from_value, to_value FROM xla.xla_merge_seg_maps WHERE event_id = :event_id AND ledger_id = :ledger_id ORDER BY segment_code;
• SELECT a.application_name, m.segment_code, m.from_value, m.to_value FROM xla.xla_merge_seg_maps m, fnd_application_vl a WHERE m.application_id = a.application_id AND m.chart_of_accounts_id = :coa;

Reporting use cases include auditing which source values were remapped during a merge run and validating that TO_VALUE entries exist for every affected FROM_VALUE. During implementation or support, consultants inspect this table to diagnose mismatches between expected and actual segment remapping, or to confirm that a failed merge did not leave orphaned mappings.

Related Objects

The following objects are most relevant to XLA_MERGE_SEG_MAPS:

• GL_MGT_SEG_UPGRADE_H — referenced via CHART_OF_ACCOUNTS_ID; the header table for segment upgrade/merge processing in General Ledger.
• XLA_MERGE_EVENTS (and related XLA merge event structures) — supplies EVENT_ID context for each mapping row.
• GL_LEDGERS / GL_LEDGER_LE_BSV_SPECIFIC — provides ledger context for LEDGER_ID.
• FND_APPLICATION_VL — resolves APPLICATION_ID to a subledger application name.
• FND_FLEX_VALUES_VL — resolves FROM_VALUE and TO_VALUE segment values to their descriptions.
• XLA_MERGE_SEG_MAPS_PK — the primary key constraint enforcing uniqueness of the five-column key.

Because the recorded foreign-key topology identifies only the GL_MGT_SEG_UPGRADE_H relationship, joins to event, ledger, and application tables should be treated as logical rather than enforced relationships.