Search Results pa_alloc_runs_all

Overview

The GL_AUTO_ALLOC_BATCH_HISTORY table is a General Ledger (GL) table that serves as a central audit and tracking repository for automated allocation processing within Oracle E-Business Suite. Its primary role is to maintain a historical record of every journal batch generated during the execution of an allocation set run. This includes batches created for both GL-based allocations and cross-module allocations originating from Projects (PA). The table is fundamental for tracing the lineage of automatically generated journals back to their source allocation processes, enabling reconciliation, troubleshooting, and audit compliance.

Key Information Stored

The table's structure captures the relationship between an allocation run and its resulting journal batches. Its primary key is a composite of REQUEST_ID, BATCH_ID, and BATCH_TYPE_CODE, ensuring a unique record for each batch in each concurrent request. Key columns include REQUEST_ID, which links to the concurrent manager request (FND_CONCURRENT_REQUESTS) that executed the allocation set; BATCH_ID, which identifies the specific batch within the allocation set; and BATCH_TYPE_CODE, which classifies the batch. Crucially, the GENERATED_JE_BATCH_ID column stores the identifier of the resulting General Ledger journal batch (in GL_JE_BATCHES) created by the allocation. For allocations sourced from Oracle Projects, the PA_ALLOCATION_RUN_ID column provides the foreign key link to the PA_ALLOC_RUNS_ALL table.

Common Use Cases and Queries

This table is essential for generating audit reports on allocation execution history and diagnosing failed or unexpected allocation results. A common use case is to identify all journal batches created by a specific allocation run for reconciliation purposes. Another critical scenario involves tracing a journal batch back to its source allocation parameters. Sample queries include retrieving the allocation history for a given Projects allocation run or listing all journal batches generated by a specific concurrent request.

• Find journals from a Projects allocation: SELECT * FROM gl_auto_alloc_batch_history gabh, gl_je_batches gjb WHERE gabh.generated_je_batch_id = gjb.je_batch_id AND gabh.pa_allocation_run_id = :run_id;
• Audit allocation set run results: SELECT request_id, batch_id, batch_type_code, generated_je_batch_id FROM gl_auto_alloc_batch_history WHERE request_id = :conc_request_id ORDER BY batch_id;

Related Objects

The GL_AUTO_ALLOC_BATCH_HISTORY table is a nexus connecting allocation execution data across modules. Its documented foreign key relationships are critical for joins in reporting and data validation.

• FND_CONCURRENT_REQUESTS: Joined via REQUEST_ID to obtain details about the submission and status of the allocation run (e.g., phase, status, completion details).
• GL_JE_BATCHES: Joined via GENERATED_JE_BATCH_ID to access the actual journal batch header information, including name, status, and accounting date.
• PA_ALLOC_RUNS_ALL: Joined via PA_ALLOCATION_RUN_ID to trace GL journals back to their specific source allocation run within Oracle Projects, which is the direct relationship indicated by the user's search term.