Search Results period_start




Overview
Explore in AI Chat

Overview

XTR_BATCHES is a core Treasury (XTR) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the fundamental information for each batch process executed within the ETRM (Enterprise Treasury and Risk Management) application. Every revaluation, accrual, amortization, rollover, intercompany transfer, and accounting generation run performed by the Treasury engine creates a corresponding row in this table, making XTR_BATCHES the central control record that ties together the downstream financial results produced by that run.

From a Data Vault modeling perspective, the mined foreign-key structure classifies XTR_BATCHES heuristically as a hub. It holds a stable, unique business key (BATCH_ID) that is referenced by numerous surrounding tables, which is characteristic of a hub entity. Analysts building a dimensional or Data Vault style model of ETRM should treat XTR_BATCHES as the batch hub from which satellite (descriptive attributes such as period and type) and link (associations to deals, journals, and balances) structures radiate.

Key Information Stored

The table is documented with 13 columns in the ETRM 12.2.2 physical schema. The most significant are:

  • BATCH_ID — Surrogate primary key, enforced by the XTR_BATCHES_PK constraint. It uniquely identifies each batch run and is the value propagated to child tables.
  • COMPANY_CODE — Identifies the legal entity or party for which the batch was run; part of the foreign-key relationship to XTR_PARTY_INFO and part of the composite unique index.
  • PERIOD_START / PERIOD_END — The accounting period window covered by the batch, defining which transactions the run processed.
  • GL_GROUP_ID — Identifier linking the batch to the General Ledger group under which resulting accounting entries are consolidated.
  • BATCH_TYPE — Classifies the nature of the run (for example revaluation, accrual, amortization, or rollover), driving how downstream results are interpreted.
  • UPGRADE_BATCH — Flag indicating whether the batch was created as part of an upgrade or migration process rather than normal operation.
  • REQUEST_ID — The concurrent request identifier that submitted the batch, enabling traceability back to the submitting program in the concurrent manager.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO columns recording audit and user context.

The documented business-key candidate is the unique index XTR_BATCHES_U1 (COMPANY_CODE, BATCH_ID), which distinguishes the surrogate primary key from the composite business identifier scoped by company. The single foreign key outbound from this table is COMPANY_CODE referencing XTR_PARTY_INFO.

Common Use Cases and Queries

XTR_BATCHES is most often queried to audit and reconcile Treasury batch processing. Typical scenarios include locating the batch that produced a revaluation or accrual entry, reviewing period coverage for a given entity, and tracing a batch back to its concurrent request. A representative query joining the batch to its party information is:

  • SELECT b.batch_id, b.company_code, b.batch_type, b.period_start, b.period_end, b.request_id FROM xtr_batches b WHERE b.company_code = :company AND b.batch_type = :type;
  • Filtering by REQUEST_ID to reconcile a concurrent program run: WHERE b.request_id = :request_id
  • Joining to XTR_JOURNALS to retrieve accounting output: SELECT j.* FROM xtr_batches b, xtr_journals j WHERE b.batch_id = j.batch_id AND b.batch_id = :batch_id;
  • Aggregating batch activity by type and period for operational reporting: SELECT batch_type, COUNT(*) FROM xtr_batches GROUP BY batch_type;

Related Objects

XTR_BATCHES is referenced by a wide set of Treasury tables through BATCH_ID and related batch columns. The most significant dependencies are:

Together these relationships establish XTR_BATCHES as the hub through which Treasury batch activity is consolidated and audited across ETRM.