Search Results jl_br_ap_collection_docs_all

Overview

The table JL_BR_AP_COLLECTION_DOCS_ALL is a core data object within the Oracle E-Business Suite Latin America Localizations module, specifically designed for Brazilian legal and fiscal requirements. It serves as the detailed transactional repository for bank collection documents within the Accounts Payable (AP) process. This table is critical for managing the lifecycle of supplier payment documents that are processed through Brazilian banking systems, ensuring compliance with local regulations governing electronic funds transfers and collections. Its role is to store granular line-level data associated with a broader bank collection header, linking supplier invoices, payment terms, banking details, and currency information into a unified record for processing and reporting.

Key Information Stored

The table stores essential attributes that define a Brazilian AP collection document. While the full column list is not provided in the metadata, the foreign key relationships indicate the presence of critical fields. These include a unique BANK_COLLECTION_ID (part of the primary key) to associate documents with a parent collection batch. It holds identifiers for the underlying invoice and payment schedule (INVOICE_ID, PAYMENT_NUM), linking to standard AP tables. Financial and legal context is provided through SET_OF_BOOKS_ID, CURRENCY_CODE, and VENDOR_ID with its VENDOR_SITE_ID. Banking details are captured via BANK_BRANCH_ID. The table likely also contains fields for document numbers, amounts, due dates, statuses, and timestamps to fully track the collection's progress and fiscal accountability.

Common Use Cases and Queries

This table is central to Brazilian AP operations and reporting. A primary use case is the generation and reconciliation of bank collection files (CNAB) for supplier payments. It enables queries to list all pending collections for a specific vendor or bank branch. Auditors and functional consultants query this table to verify the correct application of local tax and banking rules to payment documents. Common SQL patterns involve joining to its related master tables to produce detailed reports.

• Sample Query for Collection Details:
  SELECT doc.*, vs.vendor_site_code, v.vendor_name
FROM jl_br_ap_collection_docs_all doc,
po_vendors v,
po_vendor_sites_all vs
WHERE doc.vendor_id = v.vendor_id
AND doc.vendor_site_id = vs.vendor_site_id
AND doc.bank_branch_id = :p_bank_branch_id;

Related Objects

JL_BR_AP_COLLECTION_DOCS_ALL is intricately linked to several standard and localization tables, as documented by its foreign keys. Its primary key (JL_BR_AP_COLLEC_DOC_PK) ensures uniqueness, typically on BANK_COLLECTION_ID and another sequence. Key documented relationships include:

• AP_PAYMENT_SCHEDULES_ALL: Joined via INVOICE_ID and PAYMENT_NUM to retrieve the invoice payment schedule details.
• PO_VENDORS & PO_VENDOR_SITES_ALL: Joined via VENDOR_ID and VENDOR_SITE_ID for supplier and remit-to address information.
• AP_BANK_BRANCHES: Joined via BANK_BRANCH_ID to obtain the specific bank and branch details for the collection.
• FND_CURRENCIES: Joined via CURRENCY_CODE for currency definitions.
• GL_SETS_OF_BOOKS_11I: Joined via SET_OF_BOOKS_ID to determine the ledger context (Note: In EBS 12.2+, this is typically joined to GL_LEDGERS).

This table is likely referenced by Brazilian localization reports, interfaces, and the parent collection header table (e.g., JL_BR_AP_COLLECTIONS_ALL).