Results for “gl_movemerge_accounts”

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

Overview

GL_MOVEMERGE_ACCOUNTS is a General Ledger table in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments that stores the account mapping lines associated with mass maintenance (Move/Merge) requests. When a user submits a Mass Maintenance request through the GL Mass Maintenance form, the request can either move balances and balances-related activity from one account to another, or merge multiple source accounts into a single target account. GL_MOVEMERGE_ACCOUNTS captures the individual source-to-target account pairings that constitute the body of each such request. One row in this table represents one mapping line — one source account to be moved or merged into one target account — within a parent Move/Merge request.

The table resides in the GL schema and is classified as VALID. It is a child (detail) table of GL_MOVEMERGE_REQUESTS, as reflected by the foreign key on MOVEMERGE_REQUEST_ID. Under a heuristic Data Vault classification mined from the foreign key structure, the table is satellite-leaning, meaning it is best modeled as descriptive detail attached to the request-level parent rather than as an independent hub or a relationship linking two separate business entities.

Key Information Stored

GL_MOVEMERGE_ACCOUNTS contains 83 documented columns. The most important columns are:

• MOVEMERGE_REQUEST_ID — Foreign key to GL_MOVEMERGE_REQUESTS; identifies the parent mass maintenance request. Part of the primary key and the unique business key.
• LINE_NUMBER — Sequence number that distinguishes each mapping line within a request. Part of the primary key and unique key.
• SOURCE_SEGMENT1 … SOURCE_SEGMENT30 — The 30 accounting flexfield segments that make up the source account being moved or merged.
• TARGET_SEGMENT1 … TARGET_SEGMENT30 — The 30 accounting flexfield segments that make up the target account receiving the balances.
• CONTEXT — Descriptive flexfield context for the mapping line.
• ATTRIBUTE1 … ATTRIBUTE15 — Descriptive flexfield attribute columns for capturing additional, client-defined mapping information.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking when and by whom the row was created and last modified.

The surrogate primary key is GL_MOVEMERGE_ACCOUNTS_PK, defined on (MOVEMERGE_REQUEST_ID, LINE_NUMBER). The unique index GL_MOVEMERGE_ACCOUNTS_U1, also on (MOVEMERGE_REQUEST_ID, LINE_NUMBER), is the documented business-key candidate and enforces that no duplicate line number exists within a given request.

Common Use Cases and Queries

Typical uses focus on auditing, reconciliation, and pre/post-migration verification of mass maintenance activity. Because SOURCE and TARGET segments are stored as discrete columns rather than a single concatenated value, reporting queries frequently reconstruct the account string using the GL flexfield concatenation rules specified in FND_ID_FLEX_STRUCTURES and FND_ID_FLEX_SEGMENTS.

• Listing all mapping lines for a request:

  SELECT line_number,
         source_segment1 || '.' || source_segment2 || '.' || source_segment3 AS source_acct,
         target_segment1 || '.' || target_segment2 || '.' || target_segment3 AS target_acct
  FROM   gl_movemerge_accounts
  WHERE  movemerge_request_id = :request_id
  ORDER BY line_number;

• Auditing which accounts a specific user targeted in a recent request by joining to GL_MOVEMERGE_REQUESTS and filtering on created_by and creation_date.
• Reconstructing source-to-target mapping for reconciliation before and after the mass maintenance program updates GL_BALANCES and GL_JE_LINES.
• Validating that every source account maps to exactly one target and that no target duplicates unintended sources.

Related Objects

• GL_MOVEMERGE_REQUESTS — Parent table. Join on GL_MOVEMERGE_ACCOUNTS.MOVEMERGE_REQUEST_ID = GL_MOVEMERGE_REQUESTS.MOVEMERGE_REQUEST_ID to obtain request name, status, and parameters.
• GL_BALANCES — Destination for balances updated by the mass maintenance process; used to verify moved amounts.
• GL_JE_LINES / GL_JE_HEADERS — Journal activity repointed or reclassified during mass maintenance; used for reconciliation.
• GL_CODE_COMBINATIONS — Provides validation and descriptions for the reconstructed source and target account combinations.
• GL_MOVEMERGE_ACCOUNTS (interface or concurrent program) — The Mass Maintenance concurrent program and the GL Mass Maintenance form read and write this table directly; no separate public API is exposed.
• FND_FLEX_VALUES / FND_ID_FLEX_SEGMENTS — Supply segment-level descriptions and flexfield structure needed to render or validate the segment columns.

Because GL_MOVEMERGE_ACCOUNTS is a satellite-level detail table populated primarily by the Mass Maintenance workflow, direct DML should be avoided; all updates are expected to flow through the standard EBS mass maintenance request processing path.