Search Results gl_auto_alloc_rev_batches_u1

Overview

GL.GL_AUTO_ALLOC_REV_BATCHES is a transactional table in the General Ledger schema of Oracle E-Business Suite, documented as VALID under both 12.1.1 and 12.2.2. It stores the reverse journal batches that the AutoAllocation rollback process generates when an allocation run must be undone. Each row records the linkage between an original journal batch or journal header included in an allocation set and the reversal batch or reversal header created to offset it. The table is registered under FND Design Data SQLGL.GL_AUTO_ALLOC_REV_BATCHES and resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10.

From a dimensional modeling perspective, the mined relationship metadata classifies this object heuristically as a link. This is a modeling suggestion rather than a physical designation: the table carries multiple foreign key references (to GL_JE_BATCHES, GL_JE_HEADERS, and FND_CONCURRENT_REQUESTS) and functions as an associative record connecting an original allocation artifact to its generated reversal. It is not a standalone hub of business entities, nor does it behave as a slowly changing satellite of descriptive attributes.

Key Information Stored

The table contains twelve documented columns, of which the following are the most significant:

• REVERSAL_JE_HEADER_ID (NUMBER 15, mandatory) — Defining column of the reversal journal header. It is the sole primary key column, enforced by GL_AUTO_ALLOC_REV_BATCHES_PK, and is also the business-key candidate surfaced by unique index GL_AUTO_ALLOC_REV_BATCHES_U1.
• REVERSAL_JE_BATCH_ID (NUMBER 15) — Defining column of the reversal batch, referencing GL_JE_BATCHES. Together with REVERSAL_JE_HEADER_ID it identifies the reversal output of the rollback.
• JE_BATCH_ID (NUMBER 15) — Defining column for the original journal batch for which the reversal was generated.
• JE_HEADER_ID (NUMBER 15) — Defining column for the original journal header for which the reversal was generated.
• REQUEST_ID (NUMBER 15) — Concurrent request identifier of the Reverse Journal program, referencing FND_CONCURRENT_REQUESTS.
• PARENT_REQUEST_ID (NUMBER 15) — Concurrent request identifier of the AutoAllocation program that originated the batch; the driving column of nonunique indexes N1 and N2.
• BATCH_TYPE_CODE (VARCHAR2) — Classifies the batch as MassAllocation, MassBudgets, MassEncumbrances, Recurring Journals, or Project Allocations, corresponding to codes 'A', 'B', 'E', 'R', and 'P'.
• Standard Who columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN provide audit lineage for each reversal record.

The primary key is a surrogate identifier (REVERSAL_JE_HEADER_ID); the unique index confirms it as the only documented business-key candidate. The parent/child pairing of PARENT_REQUEST_ID with JE_BATCH_ID and JE_HEADER_ID is served by nonunique indexes N1 and N2 respectively.

Common Use Cases and Queries

Typical scenarios include reconciling an AutoAllocation rollback run, tracing which original journals were offset, and auditing concurrent program activity. A representative query joins the table back to GL_JE_BATCHES on REVERSAL_JE_BATCH_ID:

• Identify all reversals produced by a given allocation request: SELECT reversal_je_header_id, je_batch_id, batch_type_code FROM gl_auto_alloc_rev_batches WHERE parent_request_id = :request_id;
• Trace the reversal for a specific original batch: SELECT reversal_je_batch_id FROM gl_auto_alloc_rev_batches WHERE je_batch_id = :batch_id;
• Restrict reporting to non-project batches, since batches are reversed during rollback only when the allocation set contains no project batches.
• Audit reversals by type using BATCH_TYPE_CODE, for example isolating 'R' (Recurring) or 'E' (Encumbrances) generations.
• Correlate the reverse request to its parent AutoAllocation request using REQUEST_ID, PARENT_REQUEST_ID, and FND_CONCURRENT_REQUESTS.

Related Objects

• GL.GL_JE_BATCHES — joined via REVERSAL_JE_BATCH_ID to resolve the reversal batch definition.
• GL.GL_JE_HEADERS — joined via REVERSAL_JE_HEADER_ID, the primary key relationship.
• FND_CONCURRENT_REQUESTS — referenced twice: REQUEST_ID for the Reverse Journal program and PARENT_REQUEST_ID for the AutoAllocation program.
• GL_JE_LINES — the underlying lines of the reversal journals identified through the reversal header and batch.
• GL_AUTO_ALLOC_SETS / GL_AUTO_ALLOC_BATCHES — the allocation set and batch definitions whose rollback drives row creation.