Search Results gl_movemerge_requests_s

Overview

The APPS.GL_MOVEMERGE_REQUESTS_PKG package body is a server-side PL/SQL component in the Oracle E-Business Suite General Ledger module. Its business purpose is to support the account move and merge functionality, which allows a ledger's account balances and transactional history to be restructured when chart of accounts segments are reorganized, combined, or eliminated. Rather than performing the transfers directly, the package manages the request-level records that drive the move/merge process. It creates, validates, and maintains rows in the GL_MOVEMERGE_REQUESTS and GL_MOVEMERGE_ACCOUNTS tables, which together define a move/merge request and the individual source-to-target account mappings associated with it. In EBS 12.1.1 and 12.2.2 the package is classified by ETRM as an "OTHER" API, indicating that it is an internal support package rather than a public programmatic interface intended for customer direct invocation. It is validated and present in the APPS schema, and ETRM records that it is not referenced by any other database object, confirming its role as a top-level implementation unit consumed by the standard move/merge forms and processes.

Key Procedures and Functions

ETRM documents eight procedures and functions within this package body:

• GET_UNIQUE_ID — Returns a unique identifier used to key new move/merge request or account records prior to insertion.
• MUST_HAVE_ACCOUNTS — Enforces the business rule that a move/merge request cannot exist without at least one associated account mapping.
• DELETE_ALL_ACCOUNTS — Removes all account-level rows belonging to a request, supporting request modification and cleanup.
• CHECK_UNIQUE_NAME — Verifies that the request name supplied by the user does not duplicate an existing move/merge request name.
• PRE_INSERT — Performs pre-insertion processing and defaulting on a request or account record before it is written to the database.
• VALIDATE_SEGMENTS — Validates the accounting flexfield segment values that make up the source and target accounts, using the flexfield key validation infrastructure.
• CHECK_LAST_OPENED_PERIOD — Determines the last opened accounting period, which constrains the point in time at which balances may validly be moved or merged.
• GET_MM_LEDGER_ID — Resolves the ledger identifier relevant to the move/merge operation, accounting for ledger and ledger set relationships.

Tables Accessed

The package reads and writes the primary move/merge tables GL_MOVEMERGE_REQUESTS (request headers) and GL_MOVEMERGE_ACCOUNTS (request account lines), and obtains surrogate keys from the sequence GL_MOVEMERGE_REQUESTS_S. Ledger context is derived from GL_LEDGERS, GL_LEDGER_RELATIONSHIPS, and GL_LEDGER_SET_ASSIGNMENTS, which are used to determine which ledger or ledger set the request applies to. FND_FLEX_KEYVAL and FND_FLEX_KEYVAL-related flexfield validation are used by VALIDATE_SEGMENTS to confirm account combinations. FND_MESSAGE supplies translated error and warning text, APP_EXCEPTION/APP_EXCEPTIONS drive the standard EBS error-raising mechanism, and DUAL is used for single-row lookups.

Usage Notes

Because ETRM shows no other database object referencing this package, it is invoked directly by the General Ledger move/merge user interface and its underlying processing rather than by a broader application API layer. Typical invocation occurs when a user defines or modifies a move/merge request in the GL responsibility, at which point the request name, ledger, period, and account mappings are validated and persisted through these procedures. It may also be called from the move/merge concurrent programs that execute the actual balance and journal transfer. Customizations should avoid calling the package directly; the supported approach is to use the standard forms or, where necessary, seed and validate request rows through the documented move/merge interfaces. Any extension should preserve the package's validation rules, particularly the requirement that every request carry at least one account, the uniqueness of request names, and the last-opened-period constraint on balance movement.