Search Results gl_movemerge_requests_u2

Overview

GL.GL_MOVEMERGE_REQUESTS is a General Ledger table that stores Mass Maintenance request definitions in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Mass Maintenance encompasses two distinct GL utilities: Mass Creation of accounts and Move/Merge of accounts and account balances. Each row in this table represents a single saved request definition, capturing the request name, its type, and its current processing status. When a request is created, STATUS_CODE is initialized to 'NR' (Not Run); the Mass Maintenance concurrent program subsequently updates the row to reflect progress and completion.

From a Data Vault modeling perspective, the metadata heuristic classifies this object as satellite-leaning. This reflects its role as a descriptive attribute table attached to business keys rather than a pure transaction hub or an association link. Modelers designing a warehouse layer over EBS should treat GL_MOVEMERGE_REQUESTS as a descriptive satellite, with MOVEMERGE_REQUEST_ID as the durable identifier.

Key Information Stored

The primary key is the surrogate column MOVEMERGE_REQUEST_ID, which is enforced by the unique index GL_MOVEMERGE_REQUESTS_U1. Two business-key candidates are documented: MOVEMERGE_REQUEST_ID (U1) and the composite of NAME, CHART_OF_ACCOUNTS_ID, and LEDGER_ID (index GL_MOVEMERGE_REQUESTS_U2). The U2 index is significant for developers searching on this object, since it enforces that a request name must be unique within a given chart of accounts and ledger combination — and it is the natural lookup path when resolving a request by name.

The most operationally important columns include:

• MOVEMERGE_REQUEST_ID — Surrogate primary key and the column referenced by dependent children.
• NAME — The user-assigned request name, limited to 25 characters.
• LEDGER_ID — Identifies the ledger the request operates against; foreign key to GL_SETS_OF_BOOKS_11I.
• CHART_OF_ACCOUNTS_ID — The chart of accounts context for the request, used in the U2 uniqueness rule.
• STATUS_CODE — Current lifecycle state of the request (initially 'NR').
• REQUEST_TYPE_CODE — Distinguishes Mass Creation from Move/Merge requests.
• CONCURRENT_REQUEST_ID — Links the definition to its FND_CONCURRENT_REQUESTS execution record.
• LAST_MOVEMERGE_PERIOD — The last accounting period processed, supporting incremental re-runs.
• ORIGINAL_MOVEMERGE_REQUEST_ID — Supports request lineage and re-submission scenarios.
• DESCRIPTION — Free-text description up to 240 characters.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield context and segment values.
• Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include auditing which requests have not yet run, tracing a definition back to its concurrent program execution, and reporting the last period processed for each Move/Merge request. A representative query lists pending requests by ledger:

• SELECT mmr.movemerge_request_id, mmr.name, mmr.status_code, mmr.request_type_code FROM gl_movemerge_requests mmr WHERE mmr.status_code = 'NR' AND mmr.ledger_id = :p_ledger;
• Joining to FND_CONCURRENT_REQUESTS via CONCURRENT_REQUEST_ID retrieves phase and status from the concurrent manager layer.
• Joining to GL_SETS_OF_BOOKS_11I on LEDGER_ID resolves the ledger name and currency.
• The U2 index supports efficient lookup by the composite of NAME, CHART_OF_ACCOUNTS_ID, and LEDGER_ID.

Related Objects

• GL.GL_MOVEMERGE_ACCOUNTS — Child table referencing MOVEMERGE_REQUEST_ID; holds the account ranges defined for each request.
• GL.GL_SETS_OF_BOOKS_11I — Referenced via LEDGER_ID for ledger definition.
• FND_CONCURRENT_REQUESTS — Referenced via CONCURRENT_REQUEST_ID for execution tracking.
• GL_MGT_SEG_UPGRADE_H — Referenced via CHART_OF_ACCOUNTS_ID per the documented relationship.
• Mass Maintenance concurrent program (GLXMMERQ/related GL programs) — The process that reads these definitions and updates STATUS_CODE.