Search Results gl_auto_alloc_set_history




Overview
Explore in AI Chat

Overview

The GL_AUTO_ALLOC_SET_HISTORY table is a core data object within the Oracle E-Business Suite General Ledger (GL) module, present in both releases 12.1.1 and 12.2.2. As its name and description indicate, this table serves as the central repository for the historical audit trail of allocation set runs. An allocation set is a group of allocation formulas that are processed together to automatically distribute amounts across accounts, departments, or other segments. This table logs every execution instance, providing a critical record for tracking the performance, results, and auditability of these automated financial processes. Its role is essential for compliance, troubleshooting, and performance analysis of periodic allocation activities.

Key Information Stored

The table's structure is designed to link an allocation run to its controlling parameters and execution context. Based on the provided metadata, key columns include the REQUEST_ID, which serves as the primary key and links the history record to a specific concurrent request in the FND_CONCURRENT_REQUESTS table. The ALLOCATION_SET_ID is a foreign key to GL_AUTO_ALLOC_SETS, identifying the specific set of allocation formulas that were executed. Other significant foreign keys include LEDGER_ID (identifying the target ledger), BUDGET_VERSION_ID (linking to GL_BUDGET_VERSIONS if the allocation was for budget data), and ACCESS_SET_ID (linking to GL_ACCESS_SETS, which controls data security). While the full column list is not provided, typical complementary data would include timestamps, run status, and the user who submitted the request.

Common Use Cases and Queries

This table is primarily queried for audit reports and operational monitoring. Common scenarios include generating a history report of all allocation runs for a given period or ledger, investigating failed or incomplete runs, and reconciling allocated amounts back to their source executions. A typical query pattern joins this table to related master tables to provide descriptive information.

  • Listing recent allocation set runs: SELECT hist.REQUEST_ID, sets.NAME, hist.LEDGER_ID, cr.REQUEST_DATE FROM GL_AUTO_ALLOC_SET_HISTORY hist, GL_AUTO_ALLOC_SETS sets, FND_CONCURRENT_REQUESTS cr WHERE hist.ALLOCATION_SET_ID = sets.ALLOCATION_SET_ID AND hist.REQUEST_ID = cr.REQUEST_ID ORDER BY cr.REQUEST_DATE DESC;
  • Identifying runs for a specific allocation set: SELECT REQUEST_ID, LEDGER_ID FROM GL_AUTO_ALLOC_SET_HISTORY WHERE ALLOCATION_SET_ID = &set_id;
  • Troubleshooting by finding details of a failed concurrent request associated with an allocation.

Related Objects

As defined by its foreign key relationships, GL_AUTO_ALLOC_SET_HISTORY is integrally connected to several key GL and application foundation objects. The primary foreign key to FND_CONCURRENT_REQUESTS ties every history record to the standard EBS concurrent processing framework. Its relationship to GL_AUTO_ALLOC_SETS is fundamental, linking history to the definition of the allocation rules that were processed. Links to GL_LEDGERS (via LEDGER_ID), GL_BUDGET_VERSIONS, and GL_ACCESS_SETS provide the full execution context regarding the target data, budget type, and data access security. Data from this table may also be surfaced through standard GL allocation reports and audit inquiries within the application.