Search Results ar_batch_sources_all




Overview
Explore in AI Chat

Overview

The table JL_BR_AR_BANK_RETURNS_ALL is a core data object within the Oracle E-Business Suite Latin America Localizations module, specifically designed for the Brazilian market. Its primary function is to store records of validated bank returns. In the context of Brazilian accounts receivable (AR) processes, this table is critical for managing the lifecycle of collection documents, such as bank slips (boletos), that have been returned by a financial institution. The table's ALL suffix indicates it is a multi-organization access control (MOAC) enabled table, meaning it stores data for all operating units and requires a security profile or MOAC context for proper querying. It serves as the system of record for tracking the reason, timing, and parties involved when a payment instrument is not honored, enabling subsequent corrective actions like applying charges or initiating dunning procedures.

Key Information Stored

The table's structure is centered on identifying the returned document and categorizing the return event. The primary key is the RETURN_ID, which uniquely identifies each return record. Essential foreign key columns establish relationships to other core entities. The DOCUMENT_ID links to JL_BR_AR_COLLECTION_DOCS_ALL, connecting the return to the specific collection document it affects. The CUSTOMER_ID references HZ_CUST_ACCOUNTS to identify the customer associated with the returned payment. Party identifiers (BANK_PARTY_ID, COLLECTOR_BANK_PARTY_ID, COLLECTOR_BRANCH_PARTY_ID) link to HZ_PARTIES to detail the involved financial institutions. The BATCH_SOURCE_ID links to AR_BATCH_SOURCES_ALL, potentially tying the return record to a specific receivables batch. While the provided metadata does not list all columns, typical data would also include return codes, return dates, amounts, and status flags.

Common Use Cases and Queries

This table is primarily accessed for operational reporting, reconciliation, and process automation related to returned payments. Common scenarios include generating daily reports of all returns for a specific bank or branch, calculating returned payment fees, and identifying customers with frequent return occurrences. A typical query would join to customer and document tables to create a actionable report.

SELECT jbr.return_id,
jbr.return_date,
hca.account_number,
hp.party_name customer_name,
jcd.document_number,
jcd.amount_due_original
FROM jl_br_ar_bank_returns_all jbr,
hz_cust_accounts hca,
hz_parties hp,
jl_br_ar_collection_docs_all jcd
WHERE jbr.customer_id = hca.cust_account_id
AND hca.party_id = hp.party_id
AND jbr.document_id = jcd.document_id
AND jbr.return_date BETWEEN :p_start_date AND :p_end_date
AND jbr.org_id = :p_org_id;

Integration points include custom workflows that trigger notifications to collectors or automatically apply return charges defined by Brazilian regulations.

Related Objects

As indicated by its foreign keys, JL_BR_AR_BANK_RETURNS_ALL is integrally connected to several fundamental EBS tables. Its most direct relationship is with JL_BR_AR_COLLECTION_DOCS_ALL, the table for Brazilian collection documents. It also links to the Trading Community Architecture (TCA) foundation via HZ_CUST_ACCOUNTS and HZ_PARTIES for customer and bank entity data. The link to AR_BATCH_SOURCES_ALL integrates the return into the standard receivables transaction flow. Developers and analysts should also investigate related application programming interfaces (APIs) within the JL.BR.AR collections packages and any associated views (e.g., JL_BR_AR_BANK_RETURNS) that may provide a simplified or secured access layer to this transactional data.