Search Results remittance_exists




Overview
Explore in AI Chat

Overview

AR_BR_REMIT_IMPORT_API_PUB is a public PL/SQL API package in the APPS schema that supports the import of Brazilian remittance data into Oracle Receivables. In Oracle EBS 12.1.1 and 12.2.2, it serves as the programmatic entry point for creating and validating remittance batch records associated with automatic receipt processing. The package carries the public (PUB) API classification, indicating that its procedures are intended for external invocation by concurrent programs, forms, or custom extensions rather than being restricted to internal use.

The business purpose centers on the inbound remittance workflow: a bank file containing customer payment advice is processed, the corresponding receipts are applied to open transactions, and the resulting remittance record must be registered consistently against the correct batch, receipt method, and bank account. This package performs the necessary existence checks and status validations before a new remittance record is created, ensuring data integrity across the receipt, batch, and bank account structures.

Key Procedures and Functions

The ETRM metadata documents seven procedures and functions within the package:

  • IMPORT_REMITTANCE_MAIN — The primary driver procedure. It orchestrates the remittance import logic, invoking the supporting validation and creation routines in sequence to process a remittance record end to end.
  • DUMMY_REMITTANCE — A helper routine associated with placeholder or test remittance handling, used in the remittance identification logic.
  • CHECK_BR_AND_BATCH_STATUS — Validates the status of the bank branch (BR) and the associated receipt batch before allowing further processing.
  • COMPARE_OLD_VERSUS_NEW_VALUES — Compares previously stored attribute values against incoming values to determine whether an update or a new record is warranted.
  • EXISTING_REMITTANCE — Identifies whether a remittance record already exists for the given context, supporting duplicate prevention.
  • NEW_REMITTANCE — Creates a new remittance record when no existing record is found.
  • REMITTANCE_EXISTS — A boolean-style existence check function used by the main driver to branch between creation and update paths.

Tables Accessed

The package references the following tables and views through APPS synonyms, as documented in ETRM:

  • AR_BATCHES — Supplies batch definition and status information; validated by CHECK_BR_AND_BATCH_STATUS.
  • AR_PAYMENT_SCHEDULES — Provides the open receivable installments against which remittance receipts are applied.
  • AR_RECEIPT_METHODS — Determines the receipt method configuration used for the imported remittance.
  • RA_CUSTOMER_TRX — Identifies the customer transactions associated with the remittance.
  • CE_BANK_ACCOUNTS and CE_BANK_ACCT_USES_ALL — Resolve the internal bank account and its usage context.
  • CE_BANK_BRANCHES_V — Provides bank branch details required for the Brazilian remittance structure.
  • AR_TRANSACTION_HISTORY — Records and verifies transaction-level history during remittance creation.

Usage Notes

AR_BR_REMIT_IMPORT_API_PUB is typically invoked by the Brazilian remittance import concurrent program or by custom PL/SQL routines that process bank return files. The recommended entry point is IMPORT_REMITTANCE_MAIN, which encapsulates the validation and creation sequence. Because the package is classified PUB and is referenced by zero other packages, it is not embedded in a broader dependency chain; callers should therefore invoke it directly rather than expecting it to be triggered implicitly.

Standard Oracle API conventions apply: callers should initialize the FND_API global context, validate inputs before invocation, and inspect the returned status rather than committing inside the package. This ensures the remittance record, batch status, and bank account validations remain transactionally consistent with the surrounding receipt application logic in Oracle Receivables.