Search Results gl_movemerge_requests_pk

Overview

GL_MOVEMERGE_REQUESTS is a General Ledger table in Oracle E-Business Suite that stores the definitions of mass maintenance requests used by the Mass Maintenance (Move/Merge) program. The mass maintenance process allows accountants to move or merge account balances, budgets, and encumbrances between accounts across a chart of accounts. Each row in this table represents a named, reusable request definition that captures the selection criteria, account mappings, ledger context, and execution status for a given mass maintenance operation.

The table resides in the GL schema and is documented as VALID in both ETRM 12.1.1 and 12.2.2. Its documented description is "Mass maintenance request definitions." It consists of 31 physical columns and is the parent header record in a two-level structure, with the detail account mappings held in GL_MOVEMERGE_ACCOUNTS. The heuristic Data Vault classification mined from the foreign-key structure is satellite-leaning, which suggests a modeling approach that treats this table as a descriptor-bearing satellite attached to the ledger and concurrent-request hubs, rather than as a pure hub or link entity.

Key Information Stored

The surrogate primary key is MOVEMERGE_REQUEST_ID, enforced by the GL_MOVEMERGE_REQUESTS_PK constraint. Two unique indexes define business-key candidates: GL_MOVEMERGE_REQUESTS_U1 on MOVEMERGE_REQUEST_ID, and GL_MOVEMERGE_REQUESTS_U2 on the combination of NAME, CHART_OF_ACCOUNTS_ID, and LEDGER_ID, meaning a request name must be unique within a given chart of accounts and ledger.

• NAME — the user-assigned identifier for the mass maintenance request definition.
• LEDGER_ID — foreign key to GL_SETS_OF_BOOKS_11I, identifying the ledger against which the request executes.
• CHART_OF_ACCOUNTS_ID — foreign key linking to GL_MGT_SEG_UPGRADE_H, scoping the request to a chart of accounts.
• STATUS_CODE — the current processing state of the request definition.
• REQUEST_TYPE_CODE — indicates whether the operation is a move or a merge.
• DESCRIPTION — free-text description of the request.
• CONCURRENT_REQUEST_ID — foreign key to FND_CONCURRENT_REQUESTS, tying the definition to its concurrent program run.
• LAST_MOVEMERGE_PERIOD — the most recent period for which mass maintenance was applied.
• ORIGINAL_MOVEMERGE_REQUEST_ID — reference to a source request when a definition is copied or derived.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — the standard descriptive flexfield columns.

Common Use Cases and Queries

Typical reporting identifies which mass maintenance requests exist for a ledger, their status, and their execution history. A common query joins the request definition to the concurrent request log to audit when a request last ran.

SELECT r.movemerge_request_id, r.name, r.status_code, r.request_type_code, c.phase_code, c.status_code dcp_status FROM gl_movemerge_requests r, fnd_concurrent_requests c WHERE r.concurrent_request_id = c.concurrent_request_id AND r.ledger_id = :ledger_id;

Accountants and support analysts also enumerate the detail mappings for a given request by joining GL_MOVEMERGE_ACCOUNTS on MOVEMERGE_REQUEST_ID. Reporting on LAST_MOVEMERGE_PERIOD supports reconciliation of which periods have been processed, and querying ORIGINAL_MOVEMERGE_REQUEST_ID helps trace derived or copied definitions back to their source. Because the flexfield columns are present, reports may filter by CONTEXT and ATTRIBUTE values when the implementation has configured a descriptive flexfield.

Related Objects

• GL_MOVEMERGE_ACCOUNTS — the detail table referencing GL_MOVEMERGE_REQUESTS via MOVEMERGE_REQUEST_ID; holds the individual account move/merge mappings.
• GL_SETS_OF_BOOKS_11I — referenced through GL_MOVEMERGE_REQUESTS.LEDGER_ID; supplies ledger context.
• FND_CONCURRENT_REQUESTS — referenced through CONCURRENT_REQUEST_ID; provides execution and completion status.
• GL_MGT_SEG_UPGRADE_H — referenced through CHART_OF_ACCOUNTS_ID; scopes the request to a chart of accounts.

These relationships establish GL_MOVEMERGE_REQUESTS as the header entity in the mass maintenance data model, with all account-level detail and processing history reachable through the documented foreign keys.