Search Results ar_interest_batches_all




Overview
Explore in AI Chat

Overview

AR_INTEREST_BATCHES_ALL is the header-level table in Oracle Receivables that stores Late Charge batches. In Oracle E-Business Suite 12.1.1 and 12.2.2, a late charge batch represents a single execution of the interest and late charge calculation program across a defined set of customers, transactions, and interest rate schedules. Each row in AR_INTEREST_BATCHES_ALL identifies one such run, capturing the parameters, status, and accounting context under which the late charges were computed and subsequently transferred to the general ledger.

The table is owned by the AR schema and is documented as VALID in ETRM 12.2.2, with fourteen documented columns. Its primary key is AR_INTEREST_BATCHES_PK on INTEREST_BATCH_ID, reinforced by the unique index AR_INTEREST_BATCHES_U1 on the same column. From a Data Vault modeling perspective, the metadata indicates a heuristic classification of standalone, which suggests treating this table as a hub candidate: its stable, unique business identifier (INTEREST_BATCH_ID) is not derived from another parent entity and can serve as a durable key around which satellite attributes such as batch status, GL date, and creation audit columns are attached. Because no foreign keys are documented pointing outward from this table, the modeling suggestion is a hub with one or more satellite tables, rather than a link.

Key Information Stored

The most significant columns documented in the ETRM schema are:

  • INTEREST_BATCH_ID — Surrogate primary key and the unique business-key candidate (AR_INTEREST_BATCHES_U1). All downstream late charge detail and transfer records join back to the batch through this identifier.
  • BATCH_NAME — User-facing descriptive name applied to the late charge batch, used for identification in concurrent program output, reports, and the Receivables late charge workbench.
  • CALCULATE_INTEREST_TO_DATE — The cutoff date through which interest and late charges are calculated for the batch; a core calculation parameter.
  • BATCH_STATUS — Current lifecycle state of the batch (for example, created, calculated, or transferred), governing which actions remain available.
  • GL_DATE — Accounting date carried into Oracle General Ledger when late charge activity is posted.
  • TRANSFERRED_STATUS — Indicator of whether the batch's late charge transactions have been transferred to GL, and whether that transfer completed successfully.
  • ORG_ID — Operating unit identifier, enforcing multi-org partition security so users see only their organization's batches.
  • REQUEST_ID — Concurrent request identifier linking the batch to the submission of the late charge calculation program, which supports traceability and diagnostics.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Applications Framework (OAF) to detect concurrent updates.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording creation and modification metadata.

Common Use Cases and Queries

Typical scenarios include reconciling late charge runs to GL, diagnosing batches that never reached a transferred state, and reporting on interest calculated by operating unit. A representative query lists batches by status and cutoff date:

  • SELECT INTEREST_BATCH_ID, BATCH_NAME, CALCULATE_INTEREST_TO_DATE, BATCH_STATUS, TRANSFERRED_STATUS FROM AR.AR_INTEREST_BATCHES_ALL WHERE ORG_ID = :org_id AND BATCH_STATUS = 'CREATED' ORDER BY CREATION_DATE DESC;
  • SELECT b.BATCH_NAME, b.GL_DATE, h.* FROM AR.AR_INTEREST_BATCHES_ALL b, AR.AR_INTEREST_HEADERS_ALL h WHERE b.INTEREST_BATCH_ID = h.INTEREST_BATCH_ID;
  • SELECT INTEREST_BATCH_ID, REQUEST_ID FROM AR.AR_INTEREST_BATCHES_ALL WHERE REQUEST_ID = :request_id;

These patterns support operational monitoring of the late charge calculation concurrent program, audit of accounting dates before transfer to GL, and troubleshooting of batches tied to a specific concurrent request.

Related Objects

The following significant objects reference or depend on AR_INTEREST_BATCHES_ALL through the INTEREST_BATCH_ID column:

  • AR_INTEREST_HEADERS_ALL — Header-level interest records linked by INTEREST_BATCH_ID; the primary detail extension of the batch.
  • AR_LATE_CHARGE_DOC_GT — Global temporary table populated during late charge processing, referencing INTEREST_BATCH_ID.
  • IPA_INTEREST_BATCHES — Interest batch table in the IPA schema referencing the Receivables batch.
  • IPA_INTEREST_BATCH_DETAILS — Detail-level records joined by INTEREST_BATCH_ID for the corresponding batch.

Together these objects form the late charge processing chain: AR_INTEREST_BATCHES_ALL supplies the controlling batch header, while the referenced tables hold calculated interest lines and processing workspace data.