Search Results gl_alloc_targets




Overview
Explore in AI Chat

Overview

The GL_ALLOC_TARGETS table is a temporary data store within Oracle E-Business Suite General Ledger (GL). As indicated by the ETRM description, its primary role is to support the processing of MassAllocations and MassBudgets. These are key GL functions used to systematically distribute amounts (actuals or budget data) from a set of source accounts to a set of target accounts based on predefined allocation formulas. The table is not a permanent repository for transactional data; instead, it acts as a working table that holds intermediate results and target definitions during the execution of an allocation or budget generation request. Its "temporary" nature is underscored by its foreign key relationship to the FND_CONCURRENT_REQUESTS table, linking its data to a specific concurrent process instance.

Key Information Stored

While the specific column list is not detailed in the provided metadata, the documented foreign key relationships reveal the core data elements stored. The table centrally links an allocation target to its governing formula and specific accounting flexfield combination. Key columns inferred from these relationships include ALLOCATION_FORMULA_ID, which references the master definition in GL_ALLOC_FORMULAS; CODE_COMBINATION_ID, which identifies the target general ledger account; and REQUEST_ID, which ties the temporary records to a specific concurrent manager job for process tracking and data isolation. Other typical columns in such a working table might include amounts to be posted (e.g., allocated amounts, calculated amounts), batch information, and status flags to manage the processing workflow.

Common Use Cases and Queries

The primary use case is the execution and analysis of MassAllocation and MassBudget runs. During a concurrent request, the allocation engine populates this table with target account details and calculated figures before final journal or budget entry creation. From a reporting and troubleshooting perspective, administrators may query this table to review the results of a specific allocation run or to diagnose issues. A common query pattern would join to related master tables to provide context.

SELECT gat.request_id,
       gaf.name allocation_formula,
       gcc.concatenated_segments target_account,
       gat.allocated_amount
FROM gl_alloc_targets gat,
     gl_alloc_formulas gaf,
     gl_code_combinations gcc
WHERE gat.allocation_formula_id = gaf.allocation_formula_id
  AND gat.code_combination_id = gcc.code_combination_id
  AND gat.request_id = :request_id;

Related Objects

The ETRM metadata explicitly documents three foreign key relationships for GL_ALLOC_TARGETS, defining its integration within the GL subsystem:

  • GL_ALLOC_FORMULAS: Joined via ALLOCATION_FORMULA_ID. This is the master table containing the definition of the allocation or budget formula, including its rules and source.
  • GL_CODE_COMBINATIONS: Joined via CODE_COMBINATION_ID. This table stores the valid accounting flexfield combinations, providing the complete account information for the target of the allocation.
  • FND_CONCURRENT_REQUESTS: Joined via REQUEST_ID. This core Application Object Library table manages and tracks all concurrent processes, linking the temporary data in GL_ALLOC_TARGETS to a specific job execution.