Search Results gl_aloc_dtli1




Overview
Explore in AI Chat

Overview

The GL_ALOC_DTL table is a core data repository within the Oracle E-Business Suite, specifically for the Process Manufacturing Financials (GMF) module. It functions as the detailed results table for allocation processing. Its primary role is to store the calculated allocation amounts that distribute expenses across various cost objects, such as items, resources, or departments. As indicated in the ETRM documentation, the Actual Costing Process directly consumes the data in this table to determine precise expense allocations for manufactured items, making it a critical component for accurate product cost calculation in process manufacturing environments.

Key Information Stored

The table stores the granular results of each allocation run. Based on the provided metadata, its structure is defined by a composite primary key and links to a master allocation table. Key columns include:

  • ALLOCDTL_ID: A unique identifier for each detail record, supporting the GL_ALOC_DTLI1 index.
  • CALENDAR_CODE: Part of the primary key (GL_ALOC_DTL_PK), identifying the accounting calendar.
  • PERIOD: Part of the primary key, identifying the specific accounting period within the calendar.
  • ALLOC_ID: Part of the primary key and a foreign key to GL_ALOC_MST, linking the detail line to its parent allocation definition.
  • LINE_NO: Part of the primary key, defining the sequence of the detail record within the allocation.

While the excerpt does not list all data columns, typical data stored would include the allocated amount, the target cost object (e.g., item ID, department ID), and potentially the source of the expense being allocated.

Common Use Cases and Queries

The primary use case is supporting the Actual Costing Process, which queries this table to pull finalized allocation amounts for cost updates. It is also central for allocation audit reports and cost analysis. Common SQL patterns involve joining to the master table (GL_ALOC_MST) to retrieve allocation names and criteria. A typical query to review allocation results for a specific period would be:

  • SELECT d.CALENDAR_CODE, d.PERIOD, m.ALLOC_NAME, d.LINE_NO, d.ALLOCATED_AMT
  • FROM GMF.GL_ALOC_DTL d, GMF.GL_ALOC_MST m
  • WHERE d.ALLOC_ID = m.ALLOC_ID
  • AND d.CALENDAR_CODE = '&CALENDAR' AND d.PERIOD = '&PERIOD';

Data in this table is typically populated by the allocation execution engine and should not be manually manipulated.

Related Objects

GL_ALOC_DTL has a direct and essential relationship with the GL_ALOC_MST table, as enforced by the foreign key on the ALLOC_ID column. GL_ALOC_MST contains the definition, rules, and bases for the allocation. The table is a key source for the Actual Costing Process within GMF. Given its purpose, it may also be referenced by GMF-specific cost inquiry forms and reports that display how overhead and expenses have been assigned to final products.