Search Results jl_br_ar_occurrence_docs_s
Overview
JL_BR_AR_REMIT_COLL_OCCUR is an Oracle EBS Applications (APPS) PL/SQL package body that supports Brazilian localizations for Accounts Receivable collections and bank remittance processing. Its primary business function is to remit collection occurrences — that is, to transmit accounts receivable transactions to a bank for collection (cobrança) — and to manage the accounting and document records associated with those remittance events. The package is integral to the Brazilian borderô (bank collection batch) workflow, which groups receivable transactions, generates collection documents, and interfaces with banking institutions for settlement.
The object resides in the APPS schema with a status of VALID and is classified as an "OTHER" API type. It does not reference or get referenced by other database objects at the package level, though it depends on numerous tables and subprograms at the code level.
Key Procedures and Functions
The package exposes four documented subprograms:
- REMIT_COLLECTION — Drives the remittance of a collection, coordinating the submission of collection documents and related occurrences to the bank. This is the primary entry point for initiating a collection remittance process.
- REMIT_OCCURRENCE — Handles the remittance of an individual occurrence (a single receivable item within a collection), likely used when occurrences are processed one at a time rather than as a full batch.
- GET_ACCT_LINE_TYPE_NAME — A utility function that returns the descriptive name of an accounting line type, used in generating accounting entries and reports.
- GET_TRX_CLASS_NAME — A utility function that returns the transaction class name for a given receivable transaction, supporting classification and reporting logic.
Parameter lists are not documented in the ETRM metadata and are intentionally omitted.
Tables Accessed
The package reads and writes a substantial set of tables, organized into functional groups:
- Accounts Receivable core: AR_PAYMENT_SCHEDULES and AR_PAYMENT_SCHEDULES_ALL for installment and payment schedule data; AR_SYSTEM_PARAMETERS for system configuration; AR_RECEIPT_METHOD_ACCOUNTS_ALL for receipt method accounting.
- Brazilian localization tables: JL_BR_AR_BANK_OCCURRENCES, JL_BR_AR_BORDEROS, JL_BR_AR_BORDEROS_ALL, JL_BR_AR_COLLECTION_DOCS, JL_BR_AR_COLLECTION_DOCS_ALL, JL_BR_AR_OCCURRENCE_DOCS_ALL, JL_BR_AR_OCCURRENCE_DOCS_S, and JL_BR_AR_REC_MET_ACCTS_EXT_ALL maintain the borderô, collection document, and occurrence document records central to the remittance process.
- Banking and reference data: CE_BANK_ACCOUNTS, CE_BANK_ACCT_USES_ALL, and HZ_PARTIES provide bank account and party information.
Usage Notes
This package is typically invoked during the Brazilian AR collection remittance cycle, often from concurrent programs or forms that manage borderô generation and bank file transmission. It may also be called from custom code extending the standard localization. The presence of JL_BR_AR_OCCURRENCE_DOCS_S in the referenced table list — matching the user's search term — indicates the package queries this sequence or table when creating occurrence document records. Because the package is not referenced by other database objects, it should be treated as a top-level driver invoked by application logic rather than as a shared utility.
-
SEQUENCE: JL.JL_BR_AR_OCCURRENCE_DOCS_S
12.2.2
owner:JL, object_type:SEQUENCE, object_name:JL_BR_AR_OCCURRENCE_DOCS_S, status:VALID,
-
SEQUENCE: JL.JL_BR_AR_OCCURRENCE_DOCS_S
12.1.1
owner:JL, object_type:SEQUENCE, object_name:JL_BR_AR_OCCURRENCE_DOCS_S, status:VALID,
-
SYNONYM: APPS.JL_BR_AR_OCCURRENCE_DOCS_S
12.2.2
owner:APPS, object_type:SYNONYM, object_name:JL_BR_AR_OCCURRENCE_DOCS_S, status:VALID,
-
SYNONYM: APPS.JL_BR_AR_OCCURRENCE_DOCS_S
12.1.1
owner:APPS, object_type:SYNONYM, object_name:JL_BR_AR_OCCURRENCE_DOCS_S, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
TRIGGER: APPS.JL_BR_AR_OCC_DOCS_WRT_N_ABTMT2
12.1.1
owner:APPS, object_type:TRIGGER, object_name:JL_BR_AR_OCC_DOCS_WRT_N_ABTMT2, status:VALID,
-
TRIGGER: APPS.JL_BR_AR_OCC_DOCS_DUE_DATE_CHG
12.2.2
owner:APPS, object_type:TRIGGER, object_name:JL_BR_AR_OCC_DOCS_DUE_DATE_CHG, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
TRIGGER: APPS.JL_BR_AR_OCC_DOCS_WRT_N_ABTMT2
12.2.2
owner:APPS, object_type:TRIGGER, object_name:JL_BR_AR_OCC_DOCS_WRT_N_ABTMT2, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
TRIGGER: APPS.JL_BR_AR_OCC_DOCS_DUE_DATE_CHG
12.1.1
owner:APPS, object_type:TRIGGER, object_name:JL_BR_AR_OCC_DOCS_DUE_DATE_CHG, status:VALID,
-
TRIGGER: APPS.JL_BR_AR_OCC_DOCS_WRT_N_ABTMT1
12.1.1
owner:APPS, object_type:TRIGGER, object_name:JL_BR_AR_OCC_DOCS_WRT_N_ABTMT1, status:VALID,
-
TRIGGER: APPS.JL_BR_AR_OCC_DOCS_DIS_N_OTHER
12.2.2
owner:APPS, object_type:TRIGGER, object_name:JL_BR_AR_OCC_DOCS_DIS_N_OTHER, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
TRIGGER: APPS.JL_BR_AR_OCC_DOCS_WRT_N_ABTMT1
12.2.2
owner:APPS, object_type:TRIGGER, object_name:JL_BR_AR_OCC_DOCS_WRT_N_ABTMT1, status:VALID,
-
TRIGGER: APPS.JL_BR_AR_OCC_DOCS_DIS_N_OTHER
12.1.1
owner:APPS, object_type:TRIGGER, object_name:JL_BR_AR_OCC_DOCS_DIS_N_OTHER, status:VALID,
-
PACKAGE BODY: APPS.JL_BR_AR_REMIT_COLL_OCCUR
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:JL_BR_AR_REMIT_COLL_OCCUR, status:VALID,
-
PACKAGE BODY: APPS.JL_BR_AR_REMIT_COLL_OCCUR
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:JL_BR_AR_REMIT_COLL_OCCUR, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
APPS.JL_BR_AR_REMIT_COLL_OCCUR dependencies on JL_BR_AR_OCCURRENCE_DOCS_S
12.2.2
-
APPS.JL_BR_AR_REMIT_COLL_OCCUR dependencies on JL_BR_AR_OCCURRENCE_DOCS_S
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1