Search Results xla_upg_batches




Overview
Explore in AI Chat

Overview

XLA_UPG_BATCHES is a Subledger Accounting (XLA) table that stores upgrade batch information. It resides in the XLA schema and is documented as VALID in Oracle E-Business Suite 12.1.1 and 12.2.2. Subledger Accounting is the centralized accounting engine that transforms subledger transactions into accounting entries, and during an upgrade — most commonly the 11i to 12.x upgrade or a later release migration — the data conversion of subledger transactions, events, and accounting entries is executed in controlled, manageable units. XLA_UPG_BATCHES is the parent entity that identifies and tracks each of those units.

The table was mined as having a standalone Data Vault classification. In dimensional modeling terms, this is a heuristic suggestion rather than a documented fact: a standalone classification typically indicates a reference or processing-control entity that is not part of a hub-and-spoke structure but is instead referenced by many transactional tables as a grouping attribute. Consistent with that, the table's primary key, XLA_UPG_BATCHES_PK on UPG_BATCH_ID, is referenced by numerous XLA tables through a UPG_BATCH_ID foreign key column, positioning the batch record as a shared control parent rather than an enriched satellite.

Key Information Stored

The table contains 16 documented columns. The surrogate primary key is UPG_BATCH_ID, which also appears as the single unique index XLA_UPG_BATCHES_U1; because UPG_BATCH_ID is system-generated, it serves as the structural identifier rather than a business key derived from natural attributes.

Common Use Cases and Queries

The table is primarily used to monitor and troubleshoot subledger upgrade activity. Typical queries identify incomplete batches, measure elapsed processing time, or trace which concurrent request produced a batch.

  • Find batches whose validation has not completed: select UPG_BATCH_ID, START_DATE, END_DATE from XLA_UPG_BATCHES where VALIDATE_COMPLETE_FLAG = 'N';
  • Measure batch duration by comparing START_DATE and END_DATE, and correlate long-running batches with REQUEST_ID in FND_CONCURRENT_REQUESTS.
  • Report batch volumes by joining dependent tables such as XLA_AE_HEADERS on UPG_BATCH_ID to count accounting entries generated per batch.
  • Identify batches by source application using UPG_SOURCE_APPLICATION_ID joined to FND_APPLICATION.

Related Objects

XLA_UPG_BATCHES is referenced through the UPG_BATCH_ID foreign key by multiple XLA tables, and XLA_UPG_ERRORS provides error detail by the same key.

  • XLA_EVENTS (UPG_BATCH_ID) — subledger events processed within the batch.
  • XLA_AE_HEADERS and XLA_AE_LINES (UPG_BATCH_ID) — accounting entries and lines associated with the batch.
  • XLA_DISTRIBUTION_LINKS (UPG_BATCH_ID) — distribution linkage records for upgraded entries.
  • XLA_AE_SEGMENT_VALUES (UPG_BATCH_ID) — segment value assignments captured during upgrade.
  • XLA_TRANSACTION_ENTITIES (UPG_BATCH_ID) — transaction entity records scoped to the batch.
  • XLA_TB_WORK_UNITS (UPG_BATCH_ID) — trial balance work units tied to the batch.
  • XLA_UPG_ERRORS (UPG_BATCH_ID) — error rows raised during batch processing.