Search Results gl_alloc_history




Overview
Explore in AI Chat

Overview

The GL_ALLOC_HISTORY table is a core data object within the Oracle E-Business Suite General Ledger (GL) module. It serves as the system of record for tracking the execution history of two critical financial processes: MassAllocations and MassBudgets. These processes are used to systematically distribute amounts across multiple accounting flexfield combinations, such as allocating overhead costs or spreading budget figures. The table's primary role is to provide an auditable trail, linking each run of these processes to its specific parameters, the concurrent request that executed it, and the associated allocation or budget definition batch. This historical data is essential for troubleshooting, reconciliation, and compliance reporting.

Key Information Stored

The table's structure centers on identifiers that link the historical run to its source definition and execution context. The key columns, as defined by its primary and unique keys, include:

  • ALLOCATION_BATCH_ID: Foreign key to GL_ALLOC_BATCHES, identifying the specific MassAllocation or MassBudget formula that was executed.
  • REQUEST_ID: Foreign key to FND_CONCURRENT_REQUESTS, linking to the concurrent manager job details (status, completion time, submitted by). This column participates in multiple key constraints.
  • NAME: The name of the allocation or budget batch at the time of the run, providing a quick reference point.
  • SET_OF_BOOKS_ID: Foreign key to GL_SETS_OF_BOOKS, identifying the ledger for which the process was run.

This combination ensures each historical entry is uniquely tied to a single execution instance of a defined batch.

Common Use Cases and Queries

This table is primarily queried for audit trails and process analysis. A common reporting use case is to list all runs of a particular allocation batch to analyze results over time. A typical query would join to FND_CONCURRENT_REQUESTS for status and user information:

SELECT gah.NAME, fcr.request_id, fcr.request_date, fcr.completion_date, fcr.phase_code, fcr.status_code
FROM gl.gl_alloc_history gah,
applsys.fnd_concurrent_requests fcr
WHERE gah.request_id = fcr.request_id
AND gah.allocation_batch_id = :batch_id
ORDER BY fcr.request_date DESC;

Another critical use case is troubleshooting: identifying if and when a specific allocation last ran successfully by checking the concurrent request phase and status. Support personnel may also query it to find all allocations run for a specific ledger (SET_OF_BOOKS_ID) within a date range.

Related Objects

GL_ALLOC_HISTORY is centrally linked to several key EBS objects, as indicated by its foreign keys:

  • GL_ALLOC_BATCHES: The master table containing the definition of the MassAllocation or MassBudget formulas. The ALLOCATION_BATCH_ID foreign key points here.
  • FND_CONCURRENT_REQUESTS: The core Applications concurrent processing table. The REQUEST_ID link provides execution logistics (who, when, runtime).
  • GL_SETS_OF_BOOKS: The ledger definition table. The SET_OF_BOOKS_ID foreign key ties the history to the specific financial ledger.

Queries against GL_ALLOC_HISTORY are almost always joined to these tables to provide meaningful contextual information beyond the basic identifiers.