Results for “step_number”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GL_AUTO_ALLOC_BATCH_HISTORY is a General Ledger (GL) table in Oracle E-Business Suite that stores the history of all journal batches included in an allocation set run. Allocation sets distribute balances from source accounts to target accounts based on defined allocation rules. This table records the relationship between a concurrent request (the allocation run), each contributing source batch, and any generated output journal entry batches produced during execution.

The object resides in the GL schema and contains 16 documented columns in ETRM 12.2.2. Based on the documented foreign key structure, the metadata classifies this table heuristically as a Data Vault link. This classification is a modeling suggestion: the table primarily serves as an associative record connecting a concurrent request, the batches it processes, and the batches it generates, rather than functioning as an independent hub entity or a pure descriptive satellite.

Key Information Stored

The physical table defines a composite primary key, GL_AUTO_ALLOC_BATCH_HISTORY_PK, composed of REQUEST_ID, BATCH_ID, and BATCH_TYPE_CODE. This surrogate-key composition is complemented by two documented unique indexes that represent business-key candidates:

Among the 16 documented columns, the most functionally significant are:

  • REQUEST_ID: Identifies the concurrent request that executed the allocation run; foreign key to FND_CONCURRENT_REQUESTS.
  • BATCH_ID: The batch included in the allocation set run.
  • BATCH_TYPE_CODE: Distinguishes the nature or role of the batch within the run.
  • GENERATED_JE_BATCH_ID: The generated journal entry batch resulting from the allocation; foreign key to GL_JE_BATCHES.
  • PA_ALLOCATION_RUN_ID: Links to the originating Projects allocation run; foreign key to PA_ALLOC_RUNS_ALL.
  • STEP_NUMBER: Sequence of the allocation step, used by the U2 business-key candidate.
  • OWNER: Identifies the owning context or process for the allocation record.
  • ALLOCATION_METHOD_CODE: The allocation method applied for the entry.
  • STATUS_CODE: Processing state of the history record.
  • COMPLETE_FLAG: Indicates whether the allocation for the batch completed.
  • ALL_HEADERS_REVERSED: Flags whether all journal headers associated with the record were reversed.

Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are also present.

Common Use Cases and Queries

This table is typically queried to reconcile which batches were consumed by a specific allocation run and what output journal batches were produced. A common pattern joins the request to its outputs:

  • Run reconciliation: SELECT h.BATCH_ID, h.GENERATED_JE_BATCH_ID, h.STATUS_CODE FROM GL_AUTO_ALLOC_BATCH_HISTORY h WHERE h.REQUEST_ID = :request_id ORDER BY h.STEP_NUMBER.
  • Link generated batches to GL: join GENERATED_JE_BATCH_ID to GL_JE_BATCHES to confirm posting status of allocated journals.
  • Projects integration: filter by PA_ALLOCATION_RUN_ID to trace allocations originating from PA_ALLOC_RUNS_ALL.
  • Completion and reversal audit: query COMPLETE_FLAG and ALL_HEADERS_REVERSED to identify incomplete or reversed allocations.

Related Objects

  • FND_CONCURRENT_REQUESTS: joined via GL_AUTO_ALLOC_BATCH_HISTORY.REQUEST_ID; identifies the allocation concurrent program run.
  • GL_JE_BATCHES: joined via GENERATED_JE_BATCH_ID; the resulting journal entry batches.
  • PA_ALLOC_RUNS_ALL: joined via PA_ALLOCATION_RUN_ID; the source Projects allocation run.

These three foreign-key relationships represent the primary documented dependencies. Reporting queries most commonly join all three to produce a complete trace from concurrent request through source allocation to generated GL journals.