Results for “gl_auto_alloc_bat_hist_det”

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

Overview

The GL_AUTO_ALLOC_BAT_HIST_DET table in the General Ledger (GL) schema of Oracle E-Business Suite stores the execution status of each concurrent program submitted for the individual steps that comprise an allocation set. When a user runs an allocation batch, Oracle General Ledger decomposes the allocation set into its constituent steps and submits a separate concurrent request for each step. This table records the outcome of those submissions, allowing the application to track which steps succeeded, failed, or remain pending within a given allocation run.

Under the heuristic Data Vault classification derived from its foreign-key structure, GL_AUTO_ALLOC_BAT_HIST_DET is modeled as a link table. This classification reflects its role as an associative entity that connects concurrent request records to allocation step execution context, rather than acting as a standalone hub of business entities or a satellite carrying descriptive history. The link semantics are reinforced by the presence of two foreign keys, both pointing to FND_CONCURRENT_REQUESTS, which capture the relationship between a step's own request and its parent request in the concurrent manager hierarchy.

Key Information Stored

The documented physical schema for 12.2.2 contains 11 columns. The most significant are summarized below.

• REQUEST_ID — The primary key of the table (GL_AUTO_ALLOC_BAT_HIST_DET_PK) and a foreign key to FND_CONCURRENT_REQUESTS. It uniquely identifies the concurrent request submitted for a particular allocation step and serves as the surrogate primary key.
• PARENT_REQUEST_ID — A foreign key to FND_CONCURRENT_REQUESTS identifying the parent concurrent request that spawned this step. This column establishes the hierarchical relationship between the batch-level request and the individual step requests, and is central to the link classification.
• STEP_NUMBER — The ordinal position of the allocation step within the allocation set, enabling ordered reconstruction of the batch execution sequence.
• PROGRAM_NAME_CODE — The code identifying the concurrent program executed for the step, distinguishing allocation, validation, and other program types.
• RUN_MODE — Indicates the mode in which the step was run, such as validation-only versus actual posting.
• STATUS_CODE — The outcome status of the step's concurrent request, used to determine success, failure, or pending state.

The remaining documented columns are the standard audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, and CREATED_BY. These follow the conventional WHO-column pattern and support change tracking and auditing. No unique business-key index is documented beyond the primary key; REQUEST_ID therefore functions as the sole documented key.

Common Use Cases and Queries

This table is primarily used for diagnosing allocation batch failures and for reconstructing the execution history of allocation sets. A typical diagnostic query joins the detail rows to the concurrent requests to surface the phase and status of each step:

• Listing all steps for a given parent request, ordered by step number, to trace the sequence of execution.
• Identifying steps whose STATUS_CODE indicates failure or error, so that remediation can be targeted.
• Correlating each step to its concurrent program and request output for log and output file retrieval.
• Reporting on allocation throughput and recurring failure patterns across accounting periods.

A representative pattern is a self-join or join against FND_CONCURRENT_REQUESTS on both REQUEST_ID and PARENT_REQUEST_ID, filtered by the parent request to return the ordered step list. Such queries are frequently embedded in custom reconciliation reports and in support diagnostics for allocation postings.

Related Objects

The following objects are most significant in relation to GL_AUTO_ALLOC_BAT_HIST_DET, based on the documented foreign-key relationships:

• FND_CONCURRENT_REQUESTS — Referenced twice, via REQUEST_ID and PARENT_REQUEST_ID. This is the primary related table, supplying request phase, status, and program information.
• FND_CONCURRENT_PROGRAMS — Provides program definitions referenced indirectly through the concurrent request records and PROGRAM_NAME_CODE.
• FND_CONCURRENT_PROGRAM_RUNS — Supplies additional run-level detail for the requests recorded in this table.
• GL_AUTO_ALLOC_BATCHES and related allocation definition tables — Define the allocation sets whose steps are tracked here.
• GL_AUTO_ALLOC_BAT_HIST — The batch-level history counterpart that this detail table complements.

Because both foreign keys resolve to FND_CONCURRENT_REQUESTS, any analysis of allocation step execution should begin by joining this table to that concurrent manager table on REQUEST_ID.