Search Results xla_gl_transfer_batches_u1

Overview

XLA.XLA_GL_TRANSFER_BATCHES_ALL is the transferred batches history table within the Subledger Accounting (XLA) schema in Oracle EBS 12.1.1 and 12.2.2. It maintains a persistent log of every GL transfer submitted from Subledger Accounting to the General Ledger, capturing the parameters, run identifiers, and status of each transfer request. The table forms the audit trail that allows administrators and support personnel to trace how and when accounting events were moved from subledger applications such as Payables, Receivables, Assets, and Cost Management into GL_JE_BATCHES and GL_JE_HEADERS.

From a dimensional modeling perspective, the mined metadata classifies this object heuristically as a standalone structure, though its columns reference legal entities, cost types, and cost groups. A Data Vault modeling suggestion would treat GL_TRANSFER_RUN_ID as a hub-like business key, with the surrounding request, user, and date attributes behaving as satellite descriptive context. Regardless of modeling treatment, the table's operational role is transactional logging rather than master data management.

Key Information Stored

The unique index XLA_GL_TRANSFER_BATCHES_U1 enforces uniqueness on GL_TRANSFER_RUN_ID, making it the business-key candidate and the principal identifier for each transfer batch. This column is unique for each set of books, so consumers must scope queries by SET_OF_BOOKS_ID (or its 12.2.x replacement, LEDGER_ID, where applicable) to avoid cross-ledger ambiguity.

• GL_TRANSFER_RUN_ID — unique surrogate-style identifier for the transfer batch; the primary join key to downstream request tracking.
• REQUEST_ID — the concurrent request that last updated the row; a foreign key to FND_CONCURRENT_REQUESTS.REQUEST_ID.
• APPLICATION_ID — the calling application that initiated the transfer (e.g., 200 for Payables, 222 for Receivables).
• USER_ID — the user who submitted the transfer.
• SELECTION_TYPE — identifies the transfer mode: 1 for Batch Transfer, 2 for Document Invoice Specific Transfer.
• SET_OF_BOOKS_ID — the ledger from which the subledger journal entries are transferred.
• AE_CATEGORY — the journal category of the source document.
• GL_TRANSFER_MODE — the level of summarization: D (Detail), A (Summarized by accounting date), or P (Summarized by accounting period).
• TRANSFER_FROM_DATE / TRANSFER_TO_DATE — the date range governing which accounting events are eligible for transfer.
• GL_TRANSFER_DATE — the system date on which the transfer was submitted.
• GLLEZL_REQUEST_ID — the Journal Import concurrent request spawned by the transfer.
• TRANSFER_STATUS — the outcome state of the batch, essential for monitoring failed or incomplete transfers.
• LEGAL_ENTITY_ID — the legal entity associated with the transferred entries, referencing FV_LEGAL_ENTITIES.
• COST_TYPE_ID / COST_GROUP_ID — Cost Management context, referencing CST_COST_TYPES and CST_COST_GROUPS.

Common Use Cases and Queries

The most frequent operational scenario is troubleshooting a failed or missing GL transfer. A support analyst identifies the concurrent request, then resolves it against this table to recover the transfer parameters and the associated Journal Import request:

• Locate a transfer by concurrent request: SELECT gl_transfer_run_id, set_of_books_id, gl_transfer_mode, transfer_status, gllezl_request_id FROM xla_gl_transfer_batches_all WHERE request_id = :req_id;
• Audit all transfers for a period and ledger: filter on SET_OF_BOOKS_ID and GL_TRANSFER_DATE between the period start and end dates.
• Trace the Journal Import outcome by joining GLLEZL_REQUEST_ID to FND_CONCURRENT_REQUESTS to confirm the import completed normally.
• Reconciliation reporting: group by APPLICATION_ID and AE_CATEGORY to verify that each subledger has transferred the expected volume of entries.

Because the table retains historical batches indefinitely, it is also useful for capacity trending and for confirming the summarization approach (GL_TRANSFER_MODE) applied in prior periods.

Related Objects

• FV_LEGAL_ENTITIES — joined on LEGAL_ENTITY_ID = LEGAL_ENTITY_ID.
• CST_COST_TYPES — joined on COST_TYPE_ID.
• CST_COST_GROUPS — joined on COST_GROUP_ID.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID and GLLEZL_REQUEST_ID to resolve program names and completion status.
• XLA_GL_TRANSFER_BATCHES_ALL (index) — XLA_GL_TRANSFER_BATCHES_U1 supports direct lookup by GL_TRANSFER_RUN_ID.
• GL_JE_BATCHES / GL_JE_HEADERS — the downstream tables receiving the transferred journal entries resulting from each batch.
• XLA_EVENTS / XLA_AE_HEADERS — the upstream Subledger Accounting sources whose accounted events this batch transfers.