Search Results ar_interest_batches_v




Overview
Explore in AI Chat

Overview

AR_INTEREST_BATCHES_V is a reporting and inquiry view owned by the APPS schema within the Oracle Receivables (AR) module. Its documented purpose is to serve as the Late Charge batch preview work bench, providing consumers with a denormalized, presentation-ready projection of interest (late charge) batch records. In Oracle EBS 12.1.1 and 12.2.2, late charges are calculated against overdue transactions and grouped into interest batches before transfer to the general ledger. The base transactional data resides in the AR_INTEREST_BATCHES table, but the identifiers, statuses, and amounts required by a user-facing work bench are not conveniently exposed there. AR_INTEREST_BATCHES_V bridges that gap by combining stored batch attributes with two derived values: a translated lookup meaning for the transfer status and a computed batch amount. This makes the view a natural data source for concurrent report queries, custom OAF or Forms-based inquiry pages, and outbound integrations needing a concise late charge batch snapshot. Because the object is a view and not a table, it carries no independent storage, no triggers, and no direct DML; all access is read-only and inherits security from the calling responsibility and the ORG_ID on the underlying rows. The view is documented as VALID in the ETRM repository, confirming that its definition compiles cleanly against Oracle's shipped schema.

Underlying Base Objects

The view text is defined over a single physical source, AR_INTEREST_BATCHES (referenced in the metadata as a SYNONYM resolving to the AR base table), aliased as IB. Two PL/SQL packages are invoked from within the SELECT list rather than joined as row sources:

Consequently the view is functionally a one-row-per-batch projection of AR_INTEREST_BATCHES, enriched by two scalar function calls. No joins to customer, transaction, or GL tables are performed at the view level, so additional context must be supplied by the caller when transaction-level detail is required.

Key Columns

Common Use Cases and Queries

The principal scenario is a late charge preview work bench: a user reviews batches not yet transferred to GL before releasing them. Because BATCH_AMOUNT and TRANSFERRED_STATUS_M are computed, queries should be filtered to limit the performance cost of the function calls per row.

  • List untransferred batches for a specific operating unit.
  • Aggregate late charge exposure by batch status.
  • Feed an integration or reconciliation extract with translated statuses.

Illustrative SQL:

  • SELECT interest_batch_id, batch_name, gl_date, batch_amount, transferred_status_m FROM ar_interest_batches_v WHERE org_id = :p_org_id AND transferred_status = 'UNTRANSFERRED';
  • SELECT batch_status, COUNT(*) batch_count, SUM(batch_amount) total_amount FROM ar_interest_batches_v GROUP BY batch_status;
  • SELECT interest_batch_id, batch_name, calculate_interest_to_date, batch_amount FROM ar_interest_batches_v WHERE gl_date BETWEEN :start_date AND :end_date ORDER BY gl_date, batch_name;

Callers should avoid applying functions directly to TRANSFERRED_STATUS_M or BATCH_AMOUNT in WHERE clauses, since doing so prevents index usage on the underlying base table and forces evaluation of the packaged function for every candidate row.