Search Results jl_br_ar_occurrence_docs_all




Overview
Explore in AI Chat

Overview

The JL_BR_AR_OCCURRENCE_DOCS_ALL table is a core data repository within the Oracle E-Business Suite Latin America Localizations module, specifically designed for the Brazilian market. It functions as the master table for storing occurrences related to collection documents, a critical component of the accounts receivable process under Brazil's complex financial and regulatory requirements. Its primary role is to track and manage the various transactional events, such as bank charges, factoring, endorsements, and settlements, that can happen to a receivable document after its initial creation. The table's multi-organization architecture, denoted by the "_ALL" suffix, allows it to store data across multiple operating units, making it integral to centralized implementations of Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is defined by its primary and foreign keys, which reveal its central role in the transactional data model. The primary key, OCCURRENCE_ID, uniquely identifies each record. The most significant foreign key relationship is with JL_BR_AR_COLLECTION_DOCS_ALL via the DOCUMENT_ID column, linking each occurrence to its parent collection document. Other critical foreign keys define the financial and party dimensions of an occurrence. These include links to GL_CODE_COMBINATIONS for various accounting flexfields (e.g., DISCOUNT_CRED_ACCT_CCID, FACTORING_DEBIT_CCID), to HZ_PARTIES and HZ_CUST_ACCOUNTS for bank and customer information, and to JL_BR_AR_BORDEROS_ALL for bordero management. Key descriptive columns include BANK_OCCURRENCE_CODE, BANK_NUMBER, and BANK_OCCURRENCE_TYPE, which classify the specific bank event being recorded.

Common Use Cases and Queries

This table is central to reporting and reconciliation for Brazilian collection processes. Common operational and analytical use cases include generating detailed audit trails of all events applied to a specific collection document, reconciling bank statements with booked occurrences, and calculating bank charges and factoring fees for period-end closing. A typical query would join this table to its parent document and customer tables to analyze occurrence patterns. For example:

  • Document Occurrence History: SELECT occ.* FROM jl_br_ar_occurrence_docs_all occ, jl_br_ar_collection_docs_all doc WHERE occ.document_id = doc.document_id AND doc.customer_trx_id = :p_trx_id ORDER BY occ.creation_date;
  • Bank Charge Reconciliation: Queries filtering on BANK_OCCURRENCE_TYPE and joining to GL_CODE_COMBINATIONS to summarize charges posted to specific general ledger accounts for a given period.
  • Bordero Settlement Reporting: Joining to JL_BR_AR_BORDEROS_ALL to report on all occurrences settled under a specific bordero (bank remittance).

Related Objects

JL_BR_AR_OCCURRENCE_DOCS_ALL is a nexus within the Brazilian AR localization schema. Its primary relationship is with the parent table JL_BR_AR_COLLECTION_DOCS_ALL. It is also intrinsically linked to the bordero process via JL_BR_AR_BORDEROS_ALL. For accounting integrity, it maintains multiple dependencies on GL_CODE_COMBINATIONS for various debit and credit accounts. For customer and bank data, it references the Trading Community Architecture tables HZ_CUST_ACCOUNTS, HZ_CUST_SITE_USES_ALL, and HZ_PARTIES. The code definitions for bank events are stored in the lookup table JL_BR_AR_BANK_OCCURRENCES. Custom reports, interfaces, and extensions will typically read from or write to this table to process collection document life cycle events.