Search Results jl_br_ar_remit_borderos_all




Overview
Explore in AI Chat

Overview

The table JL_BR_AR_REMIT_BORDEROS_ALL is a core data object within the Oracle E-Business Suite Latin America Localizations module, specifically supporting Brazilian financial processes. Its primary role is to track the linkage between formatted bank transfer batches and the underlying financial instruments known as borderôs (promissory notes). It serves as a critical junction table, managing the relationship between the request IDs generated during the electronic funds transfer (EFT) formatting process and the specific receivables documents being remitted to the bank. This functionality is essential for automating and reconciling bulk payment and collection processes in compliance with Brazilian banking standards.

Key Information Stored

The table's structure is designed to maintain referential integrity between payment programs and borderôs. Its primary key is the FORMAT_REQUEST_ID, which uniquely identifies each formatted bank transfer batch. The table holds two crucial foreign key columns that define its relationships. The BORDERO_ID column links each formatting request to one or more specific promissory note records in the JL_BR_AR_BORDEROS_ALL table. The OUTPUT_PROGRAM_ID column links the request to the specific payment program configuration in the AP_PAYMENT_PROGRAMS table that was used to generate the formatted bank file. This design ensures full auditability from the original receivable document to the final bank transmission.

Common Use Cases and Queries

A primary use case is tracing the status and details of a bank remittance batch back to its constituent transactions. For instance, to identify all borderôs included in a specific formatting request, a query would join this table to the borderos detail table. Conversely, to find the remittance history of a particular bordero, a query would filter on BORDERO_ID. This table is also central to reconciliation reports that verify which electronic payments have been successfully formatted and submitted to the bank. A typical reporting query might join JL_BR_AR_REMIT_BORDEROS_ALL to JL_BR_AR_BORDEROS_ALL and RA_CUSTOMER_TRX_ALL to pull in customer and invoice information for a complete remittance advice.

Related Objects

  • JL_BR_AR_BORDEROS_ALL: The primary foreign key relationship. This table stores the master records for the promissory notes (borderôs) themselves.
  • AP_PAYMENT_PROGRAMS: The secondary foreign key relationship. This standard Oracle Payments table defines the program used to format the payment batch for bank transmission.
  • JL_BR_AR_REMIT_BORDEROS_ALL_PK: The primary key constraint enforcing uniqueness on the FORMAT_REQUEST_ID column.
  • Related transactional data would typically be accessed via joins to core Receivables tables like RA_CUSTOMER_TRX_ALL and AR_PAYMENT_SCHEDULES, using the bordero as the linking entity.