Search Results x_our_number




Overview

APPS.JL_BR_AR_BANK_RETURNS_PKG is a Brazil-localization (JL_BR) PL/SQL package that supports Oracle Receivables bank return processing. It manages the data lifecycle for bank return records, which represent the responses received from collecting banks regarding trade notes (boletos) and related Receivables transactions. The package is defined with AUTHID CURRENT_USER, meaning that its SQL statements execute under the privileges of the invoking session rather than the package owner, a standard pattern for Oracle EBS tables-maintenance APIs. The header comment ($Header: jlbrrems.pls 120.5 2003/09/15) indicates the file has been in the EBS codebase since the pre-11i era and remains compatible with the 12.1.1 and 12.2.2 releases. In the ETRM 12.2.2 repository the object is classified as API classification OTHER, with four documented procedures, and it is not cited as a dependency by any other packaged object.

Key Procedures and Functions

The package exposes four documented procedures that implement the standard Oracle Forms DML integration pattern for a single base table:

Each procedure also accepts an X_calling_sequence parameter that records the call path for diagnostic and debugging purposes.

Tables Accessed

The package operates on the single table JL_BR_AR_BANK_RETURNS, accessed through its APPS synonym. This table stores the detailed return data transmitted by Brazilian banks, including occurrence codes, monetary amounts (charges, abatements, discounts, credits and interest), party references and the OUR_NUMBER field, which identifies the company's own reference for the collection document. All four procedures perform their DML directly against this table; no other documented tables are referenced.

Usage Notes

Because the procedures follow the generated Forms-server API pattern (ROWID-based lock, insert, update and delete), the package is most commonly invoked from the Oracle Receivables Brazil localization forms when users enter or maintain bank return information, and from the concurrent programs that import bank return files. The OUR_NUMBER attribute is significant in this context, as it is the field that ties a returned collection item back to its originating trade note. Custom code should call the package only through the documented procedures and should supply a meaningful X_calling_sequence, since ETRM lists no dependent packages and therefore no supported alternative entry point. Direct DML against JL_BR_AR_BANK_RETURNS is discouraged because it bypasses the locking and WHO column maintenance performed by this package.