Search Results batch_record_count




Overview
Explore in AI Chat

Overview

AR_TA_PAYMENTS_INTERFACE_BAT_V is a reporting view in the Oracle E-Business Suite Receivables (AR) module. Its name indicates its purpose: it exposes batch-level records drawn from the Automatic Receipts interface. The internal "TA" and "BAT" naming convention aligns the view with the Treasury/Automatic Receipts batch transmission process, where payment records are staged before being imported into Receivables as receipts. The view is designed to present one summarized row per batch rather than per individual payment line, making it suitable for transmission monitoring and reconciliation reporting.

The view filters its results to RECORD_TYPE = 4, which is the record-type code reserved for batch header records within the AR_PAYMENTS_INTERFACE_ALL staging table. It also applies a Multi-Org security predicate based on the ORG_ID column, restricting rows to the operating unit identified in the session's client information. This makes the view inherently organization-aware and safe for use in multi-org environments under Oracle EBS 12.1.1 and 12.2.2.

Because the ETRM metadata records the object as "Not implemented in this database," the view is documented for reference but may not be deployed in every environment. Its definition remains valuable for understanding how batch headers are surfaced from the payments interface.

Underlying Base Objects

The view is defined over a single documented base object: AR_PAYMENTS_INTERFACE_ALL. Although the metadata lists no explicitly referenced base objects, the embedded view text confirms this dependency. AR_PAYMENTS_INTERFACE_ALL is the central staging table for the Automatic Receipts and payment interface, capturing inbound payment data before validation and import into the Receivables receipts tables.

The view applies two filters against that table: a constant restriction on RECORD_TYPE = 4 to isolate batch header rows, and an ORG_ID predicate that derives the current operating unit from USERENV('CLIENT_INFO'). The NVL/DECODE logic normalizes null or missing client information to a sentinel value of -99, ensuring deterministic filtering. No joins to other tables are present in the view text, so the view is a projection and filter over a single interface table.

Key Columns

The view exposes batch header attributes plus standard audit and descriptive-flexfield columns. Notable columns include:

Common Use Cases and Queries

Typical uses include monitoring batch transmissions, reconciling deposit timing, and verifying batch amounts before import. A frequent scenario is locating batches by deposit date, matching the user's search term.

  • List batches with their deposit and GL dates:
    SELECT BATCH_NAME, DEPOSIT_DATE, GL_DATE, CURRENCY_CODE, BATCH_AMOUNT, BATCH_RECORD_COUNT, STATUS FROM AR_TA_PAYMENTS_INTERFACE_BAT_V ORDER BY DEPOSIT_DATE;
  • Find batches deposited within a date range:
    SELECT BATCH_NAME, DEPOSIT_DATE, BATCH_AMOUNT FROM AR_TA_PAYMENTS_INTERFACE_BAT_V WHERE DEPOSIT_DATE BETWEEN :from_date AND :to_date;
  • Summarize batch totals by status:
    SELECT STATUS, COUNT(*) batch_count, SUM(BATCH_AMOUNT) total_amount FROM AR_TA_PAYMENTS_INTERFACE_BAT_V GROUP BY STATUS;

Because the view enforces Org ID filtering automatically, queries return only batches belonging to the current operating unit, simplifying security-conscious reporting in 12.1.1 and 12.2.2.