Search Results interest_batch_id




Overview

IPA_INTEREST_BATCHES is a table owned by the IPA schema within Oracle E-Business Suite, associated with the Capital Resource Logistics – Projects product family. Its documented purpose is to store interest batch information, meaning it records the results of interest calculations applied to project expenditures within a defined accounting period. In the Oracle Projects architecture, this table serves as the integration point between Oracle Receivables' interest calculation engine and the project cost/expenditure model, capturing which expenditures had interest applied, at what rate, and during which GL period. From a Data Vault modeling perspective, the heuristic classification for this table is standalone, with no downstream dependents in the mined FK graph. This suggests it behaves as a link-like association object bridging AR_INTEREST_BATCHES_ALL and PA_EXPENDITURE_ITEMS_ALL, though it functions operationally as a single fact record per interest line.

Key Information Stored

The table contains 13 documented columns. The surrogate primary key is INTEREST_BATCH_ID, which is also the sole unique index (IPA_INTEREST_BATCHES_U1) and therefore the primary business-key candidate for row identification. This column simultaneously serves as a foreign key to AR_INTEREST_BATCHES_ALL, making it the critical linkage to Receivables interest logic.

  • INTEREST_BATCH_ID — Primary key and the join key to AR interest batches.
  • EXPENDITURE_ITEM_ID — Foreign key to PA_EXPENDITURE_ITEMS_ALL, identifying the specific expenditure line to which interest is applied.
  • INTEREST_APPLIED — The computed interest amount attributed to the expenditure item.
  • RATE_TYPE — The classification of the interest rate applied (e.g., standard, penalty, or organization-specific).
  • GL_PERIOD, PERIOD_BEGIN_DATE, PERIOD_END_DATE — The accounting period context and its date boundaries.
  • EXPENDITURE_ITEM_DATE — The date of the source expenditure item, used to derive elapsed interest time.
  • EXPENDITURE_TASK_ID, PROJECT_ID — Project and task attribution for reporting and cost aggregation.
  • STATUS — Lifecycle state of the interest record (e.g., pending, applied, reversed).
  • REVERSAL_DATE — The date on which the interest was (or is scheduled to be) reversed.
  • BATCH_ID — A grouping identifier to consolidate related interest lines for concurrent processing and reconciliation.

Common Use Cases and Queries

Typical reporting scenarios include reconciling interest applied to project expenditures per GL period, auditing reversal activity, and tracing interest back to the originating AR batch. A representative join pattern is:

  • Join to PA_EXPENDITURE_ITEMS_ALL on EXPENDITURE_ITEM_ID to retrieve expenditure details, organization, and cost.
  • Join to AR_INTEREST_BATCHES_ALL on INTEREST_BATCH_ID to obtain the AR-side batch header, currency, and customer context.
  • Aggregate INTEREST_APPLIED by GL_PERIOD and PROJECT_ID for period-close interest accrual reporting.
  • Filter on STATUS or REVERSAL_DATE to isolate reversed or pending interest records for audit.
  • Group by BATCH_ID to reconcile total interest processed in a single batch run against the AR batch total.

Because the table carries both project dimensions and period attributes, it is well suited to cross-module reporting between Oracle Projects and Oracle Receivables, particularly in month-end reconciliation of unbilled or billed interest on project-related receivables.

Related Objects

The most significant related objects derive directly from the documented foreign keys and the surrounding AR/PA data model:

  • AR_INTEREST_BATCHES_ALL — referenced via INTEREST_BATCH_ID; the upstream AR interest batch header.
  • PA_EXPENDITURE_ITEMS_ALL — referenced via EXPENDITURE_ITEM_ID; the source project expenditure line.
  • Oracle Receivables interest calculation APIs and concurrent programs that populate the AR batch headers.
  • Oracle Projects expenditure reporting views that derive cost and billing context from PA_EXPENDITURE_ITEMS_ALL.
  • General Ledger period/interface tables used when interest amounts are transferred during period close.

These relationships establish IPA_INTEREST_BATCHES as the project-side detail recorder for interest applied against receivables-related expenditures.