Search Results get_acct_line_type_name




Overview
Explore in AI Chat

Overview

The APPS.JL_BR_AR_REMIT_COLL_OCCUR package is a Brazilian localization component within the Oracle E-Business Suite Receivables module, focused on the remittance and collection occurrence processing of bordero (bank collection document) transactions. Its primary business role is to support the creation and lifecycle management of collection occurrences associated with borderos, and to expose descriptive name resolution functions that translate stored lookup codes into human-readable meanings for display in SLA (Subledger Accounting) forms. The package is declared AUTHID CURRENT_USER and is classified as an OTHER API in the ETRM metadata for release 12.2.2. It carries no referenced-by dependencies, indicating it is a terminal utility invoked directly by views, forms, or concurrent processes rather than being consumed by other packages.

Key Procedures and Functions

The package exposes four documented program units:

  • REMIT_COLLECTION — Drives the remittance processing for a bordero, coordinating the collection flow for a given bordero identifier and tracking a processing status that is returned to the caller as an IN OUT parameter.
  • REMIT_OCCURRENCE — Handles the generation or updating of collection occurrences tied to a bordero, again using a bordero identifier and a status IN OUT parameter to communicate processing outcome.
  • GET_ACCT_LINE_TYPE_NAME — A function that accepts an account line type code and returns its lookup meaning. The header documentation states it is required to be called from an occurrence view, supplying the value for the ACCT_LINE_TYPE_NAME column used to name account lines in SLA forms. It carries the PRAGMA RESTRICT_REFERENCES(..., WNDS) assertion, confirming it performs no database writes.
  • GET_TRX_CLASS_NAME — A companion function that converts a transaction class code into its descriptive meaning, intended to populate the TRX_CLASS_NAME view column shown in SLA forms for bank transfer views.

Parameter lists are documented only where shown; no additional arguments should be assumed beyond those present in the source for the two remittance procedures, and the two name-resolution functions accept a single lookup code value.

Tables Accessed

The package operates across Brazilian localization and standard Receivables tables. Core localization tables include JL_BR_AR_BORDEROS, JL_BR_AR_BORDEROS_ALL, JL_BR_AR_BANK_OCCURRENCES, 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, which together hold bordero headers, occurrence definitions, and collection documents. Standard Receivables tables referenced via APPS synonyms include AR_PAYMENT_SCHEDULES and AR_PAYMENT_SCHEDULES_ALL for installment data, AR_RECEIPT_METHOD_ACCOUNTS_ALL and AR_SYSTEM_PARAMETERS for receipt configuration, and CE_BANK_ACCOUNTS and CE_BANK_ACCT_USES_ALL for bank account definitions. HZ_PARTIES supplies trading partner identity information.

Usage Notes

The package is typically invoked in three contexts. First, from SLA and occurrence views, where GET_ACCT_LINE_TYPE_NAME and GET_TRX_CLASS_NAME are called inline to render descriptive account line and transaction class names on forms such as the Create Accounting and Review Journal Entries windows. Second, from concurrent programs or PL/SQL routines that process bordero remittances, calling REMIT_COLLECTION and REMIT_OCCURRENCE with a bordero identifier and status variable. Third, from custom localization extensions built on the Brazilian Receivables data model. Because the functions are declared with WNDS purity, they are safe to reference from SQL and view definitions, whereas the two procedures require a PL/SQL execution context.