Search Results gl_alloc_interim_1

Overview

GL_ALLOC_INTERIM_1 is a temporary (transient) working table used by the General Ledger MassAllocations and MassBudgets engines in Oracle E-Business Suite 12.1.1 and 12.2.2. During an allocation or budget run, the allocation engine needs a scratch area to stage the computed source, basis, and target amounts before they are posted to GL_JE_BATCHES, GL_JE_HEADERS, and GL_JE_LINES. GL_ALLOC_INTERIM_1 serves exactly that purpose: it holds the intermediate, pre-posting results of an allocation formula so that the journal creation step can materialise the final journal entries.

Because the table is a transient work area, the ETRM metadata explicitly states it is "Not implemented in this database." This means the physical table exists only during the runtime of the allocations program and is created or populated on demand, or that it is not present in the specific database instance profiled. Either way, DBAs should not expect persistent rows in this object and must not build permanent reporting solutions directly against it.

From a Data Vault modelling perspective, the FK relationship GL_ALLOC_INTERIM_1.FORMULA_ID → GL_ALLOC_FORMULA_LINES indicates the table behaves as a satellite-leaning structure. It records descriptive, run-scoped detail attached to the formula (business key) defined in GL_ALLOC_FORMULA_LINES, rather than acting as an independent hub or a pure link between two hubs. This is a heuristic suggestion, not a documented classification.

Key Information Stored

The documented metadata exposes only a limited column set, so the following reflects the documented keys plus the standard structural expectations for an allocation interim table.

• FORMULA_ID — foreign key to GL_ALLOC_FORMULA_LINES.FORMULA_ID. Identifies which allocation (MassAllocation or MassBudget) formula produced the interim row. This is the primary business-key candidate.
• FORMULA_LINE_NUMBER — the line within the formula. Combined with FORMULA_ID, this forms the composite foreign key to GL_ALLOC_FORMULA_LINES and is the natural parent-key pair for each interim record.
• Interim amount columns — the calculated source, basis, and target amounts staged for the run before journal generation.
• Code combination / account columns — the accounting flexfield combination to which the interim amount applies.
• Run/period identifiers — values that scope the interim rows to a specific allocation run and accounting period.

Because no surrogate primary key or unique index is documented beyond the composite foreign key, the practical key of this table is (FORMULA_ID, FORMULA_LINE_NUMBER) plus whatever run-scoped discriminator the allocation engine assigns at runtime. No separate hub surrogate key is exposed in the metadata.

Common Use Cases and Queries

Direct querying of GL_ALLOC_INTERIM_1 is uncommon because its contents are transient. Typical use cases are diagnostic rather than reporting:

• Troubleshooting a MassAllocation run that produced unexpected or missing journal entries, by inspecting the staged amounts before posting.
• Verifying that a formula's basis and target lines resolve to the expected accounting combinations.
• Confirming that the allocation engine populated the interim table successfully during a given run.

A representative diagnostic pattern:

SELECT ai.FORMULA_ID,
       ai.FORMULA_LINE_NUMBER,
       fl.LINE_DESCRIPTION
FROM   GL_ALLOC_INTERIM_1 ai,
       GL_ALLOC_FORMULA_LINES fl
WHERE  ai.FORMULA_ID = fl.FORMULA_ID
AND    ai.FORMULA_LINE_NUMBER = fl.FORMULA_LINE_NUMBER;

For durable reporting on allocation results, query the posted journal tables (GL_JE_BATCHES, GL_JE_HEADERS, GL_JE_LINES) or the allocation definition tables (GL_ALLOC_FORMULAS, GL_ALLOC_FORMULA_LINES) instead. Use GL_ALLOC_INTERIM_1 only within a live run window or during controlled debugging.

Related Objects

• GL_ALLOC_FORMULA_LINES — joined on FORMULA_ID and FORMULA_LINE_NUMBER. The direct parent of the interim rows and the documented FK target.
• GL_ALLOC_FORMULAS — the header definition of the allocation formula referenced by FORMULA_ID.
• GL_JE_BATCHES / GL_JE_HEADERS / GL_JE_LINES — the final posting destination once interim amounts are journalised.
• GL_ALLOC_RUNS / allocation run history — run-scoped context that binds interim rows to a specific execution.
• MassAllocations and MassBudgets concurrent programs — the engine processes that populate and consume this table at runtime.