Search Results jl_br_ar_collection_docs_all




Overview
Explore in AI Chat

Overview

The JL_BR_AR_COLLECTION_DOCS_ALL table is a core transactional entity within the Oracle E-Business Suite Latin America Localizations module, specifically designed for Brazilian legal and financial requirements. It functions as the master repository for collection documents, a critical component of the accounts receivable process in the Brazilian localization. This table stores the header-level information for various financial instruments, such as borderôs (collection batches), that are processed through the banking system for collection from customers. Its role is integral to managing the lifecycle of receivables, from document creation and bank submission through to application and settlement, ensuring compliance with local accounting practices and banking regulations in Oracle EBS releases 12.1.1 and 12.2.2.

Key Information Stored

The table's primary key is DOCUMENT_ID, which uniquely identifies each collection document record. A critical foreign key is BORDERO_ID, linking the document to its parent collection batch in the JL_BR_AR_BORDEROS_ALL table. The table's structure is heavily oriented towards accounting control, as evidenced by its numerous foreign key relationships to the GL_CODE_COMBINATIONS table. These relationships store the Chart of Accounts IDs (CCIDs) for various financial activities associated with the collection process, including unapplied cash (UNAPPLIED_CCID), unearned revenue (UNEARNED_CCID), bank charges (BANK_CHARGES_CCID), interest calculations (CALCULATED_INTEREST_CCID, INTEREST_REVENUE_CCID), and factoring operations (FACTORING_DOCS_CCID). Additional key columns link to banking setup, such as BANK_ACCOUNT_ID and RECEIPT_METHOD_ID, which reference the AR_RECEIPT_METHOD_ACCOUNTS_ALL table to define the destination bank account for collected funds.

Common Use Cases and Queries

Primary use cases revolve around the generation of reports for audit trails, bank reconciliation, and accounting entries for collected documents. A common reporting requirement is to list all collection documents within a specific borderô batch for review. A typical SQL query would join to the borderôs table and relevant code combinations to provide a meaningful description.

  • Sample Query for Document Listing:
    SELECT doc.document_id, bor.bordero_number, doc.creation_date
    FROM jl_br_ar_collection_docs_all doc,
    jl_br_ar_borderos_all bor
    WHERE doc.bordero_id = bor.bordero_id
    AND bor.bordero_date BETWEEN :p_start_date AND :p_end_date
    ORDER BY bor.bordero_number, doc.document_id;
  • Accounting Analysis: Technical consultants often query this table to trace the CCIDs used for posting specific types of collection-related journal entries, such as interest revenue or bank charges, which is crucial for validating the integrity of the subledger accounting (SLA) setup.

Related Objects

The table maintains defined foreign key relationships with several key EBS objects, as documented in the ETRM metadata. These relationships are fundamental to its integration within the application.

  • JL_BR_AR_BORDEROS_ALL: Linked via BORDERO_ID. This is the primary parent table, defining the collection batch to which the document belongs.
  • GL_CODE_COMBINATIONS: Linked via multiple CCID columns (e.g., UNAPPLIED_CCID, UNEARNED_CCID, BANK_CHARGES_CCID, INTEREST_REVENUE_CCID). These relationships define the accounting flexfields for all financial aspects of the document.
  • AR_RECEIPT_METHOD_ACCOUNTS_ALL: Linked via the composite foreign key on (BANK_ACCOUNT_ID, RECEIPT_METHOD_ID). This ties the collection document to the specific bank account and receipt method defined in the Receivables module.