Search Results ar_br_main_remit_batch_v




Overview

AR_BR_MAIN_REMIT_BATCH_V is a seed data view owned by the APPS schema in Oracle E-Business Suite Receivables (AR). It is a component of the Brazilian localization remittance (Boleto / borderô) printing framework, providing the main remittance batch data set consumed by the concurrent program and report logic that generates bank remittance documents. The view flattens the relationship between a remittance batch (AR_BATCHES), the customer transactions and payment schedules assigned to that batch, the drawee (customer) and drawee site information, and the associated banks and branches, so that a single row represents one transaction within a remittance batch, ready for formatted output.

Because the view is a denormalized reporting object, it abstracts more than twenty base tables and several packaged APIs, exposing only the attributes required for remittance layout. It is registered as VALID in ETRM for both 12.1.1 and 12.2.2, meaning its structure is consistent across these releases.

Underlying Base Objects

The view is defined as a join across the following documented base objects:

The transaction history alias (RAH) and payment schedules anchor each row to a specific installment, while HZ joins resolve party name, account number, fiscal code, category, and address. Bank and branch details are derived from IBY extension views and CE bank account objects, with the organization unit context supplied through CE_BANK_ACCT_USES_OU_V.

Key Columns

Common Use Cases and Queries

The view is typically queried by the Brazilian remittance report to list transactions belonging to a batch, or by support teams to diagnose why a transaction is missing or misprinted on a borderô. A representative query is:

  • SELECT batch_id, trx_number, trx_date, due_date, amount_due_remaining, party_name, drawee_bank_name FROM ar_br_main_remit_batch_v WHERE batch_id = :p_batch_id ORDER BY trx_number;
  • Reporting outstanding remitted amounts by bank: SELECT drawee_bank_name, SUM(amount_due_remaining) FROM ar_br_main_remit_batch_v GROUP BY drawee_bank_name;
  • Audit of flexfield usage: SELECT trx_number, attribute_category, attribute1 FROM ar_br_main_remit_batch_v WHERE attribute_category IS NOT NULL;

Because the view joins through the organization unit context (CE_BANK_ACCT_USES_OU_V) and utilizes FND_GLOBAL to resolve the operating unit, queries should be executed with the correct MO:/org context set, otherwise bank account rows may not resolve and remittance data will be incomplete.