Search Results jl_br_ar_bank_occurrences




Overview
Explore in AI Chat

Overview

The table JL_BR_AR_BANK_OCCURRENCES is a core data repository within the Oracle E-Business Suite Latin America Localizations module, specifically designed for the Brazilian market. It serves as the master reference table for storing bank occurrence codes, which are critical for managing and tracking the status of financial transactions within the Brazilian banking system. This table is integral to the Accounts Receivable (AR) processes, enabling the system to interpret and process standardized return codes and statuses provided by banks for payments, collections, and other financial instruments. Its role is to provide a centralized, validated list of codes that can be associated with specific banking institutions, ensuring compliance with local regulatory reporting and financial reconciliation requirements.

Key Information Stored

The table's structure is designed to uniquely identify an occurrence code for a specific bank. Its primary key is a composite of three columns, ensuring uniqueness per bank and code type. The critical columns are:

  • BANK_PARTY_ID: A foreign key to HZ_PARTIES, this column stores the unique identifier for the banking institution (party) to which the occurrence code applies.
  • BANK_OCCURRENCE_CODE: Stores the actual alphanumeric code that represents a specific bank occurrence or status (e.g., a payment return reason).
  • BANK_OCCURRENCE_TYPE: Categorizes the occurrence code, allowing for logical grouping (e.g., distinguishing between payment, collection, or protest-related occurrences).

Together, these columns define a valid bank occurrence. The table likely contains additional descriptive columns (such as meaning, start/end dates, or active status) to fully define each code, though they are not explicitly listed in the provided metadata.

Common Use Cases and Queries

This table is primarily used in transactional reporting, reconciliation, and exception handling workflows. A common use case is identifying all valid occurrence codes for a specific bank when processing a bank statement file or investigating a returned payment. For reporting, it is frequently joined to transaction tables to generate detailed reports on payment failures or collection statuses. A typical query pattern involves joining to the HZ_PARTIES table to retrieve the bank's name:

SELECT hp.party_name, jb.bank_occurrence_code, jb.bank_occurrence_type
FROM jl_br_ar_bank_occurrences jb, hz_parties hp
WHERE jb.bank_party_id = hp.party_id
AND hp.party_name = 'Bank Name';

Another critical use case is supporting the application logic that automatically applies business rules (like updating invoice status or creating adjustment transactions) when a specific bank occurrence code is received from an electronic payment file.

Related Objects

The JL_BR_AR_BANK_OCCURRENCES table maintains defined foreign key relationships with other core localization tables, as documented in the ETRM metadata:

  • HZ_PARTIES: The table references HZ_PARTIES via the BANK_PARTY_ID column. This relationship ties each occurrence code to a specific banking institution defined in the Trading Community Architecture (TCA) registry.
  • JL_BR_AR_OCCURRENCE_DOCS_ALL: This transactional table holds a foreign key reference to JL_BR_AR_BANK_OCCURRENCES. It joins on the composite key (BANK_OCCURRENCE_CODE, BANK_NUMBER, BANK_OCCURRENCE_TYPE), linking specific documents or transactions (like receipts or invoices) to the master bank occurrence codes stored in this table. This is the primary relationship for applying occurrence data to business documents.