Search Results dummy_remittance

Overview

The APPS.AR_BR_REMIT_IMPORT_API_PUB package body supports the Oracle Receivables Brazilian remittance import process, handling the creation and validation of remittance batches derived from bank remittance files. The package encapsulates the public API layer (as denoted by the _PUB suffix) that orchestrates the loading of remittance records, matching them to existing batch structures, and applying the appropriate state transitions. Its internal name is IMPREMAPI, and its constants map directly to the FND message-level framework (FND_MSG_PUB.G_MSG_LVL_ERROR, G_MSG_LVL_SUCCESS, and the debug tiers), indicating that message accumulation and structured error reporting are integral to its design. The header version (ARBRIMRB.pls 120.4) reflects the 11i-era codebase carried forward into EBS 12.1.1 and 12.2.2, where the package remains in use for remittance-import automation.

Key Procedures and Functions

The package exposes seven documented units:

• DUMMY_REMITTANCE — Examines a remittance batch to determine whether it is empty (that is, whether it contains any transaction-history records flagged as current). If empty, it invokes the batch cancellation routine to clear the unused batch. This is the unit most directly associated with the search term "dummy_remittance."
• CHECK_BR_AND_BATCH_STATUS — Validates the consistency between the individual remittance (BR) records and the parent batch status before further processing proceeds.
• COMPARE_OLD_VERSUS_NEW_VALUES — Performs change detection, comparing previously stored remittance values against incoming values to determine whether an update or a new version is required.
• EXISTING_REMITTANCE — Handles the path where an incoming remittance already exists in the system, determining how it should be reconciled or updated.
• NEW_REMITTANCE — Handles the creation path for remittances not previously loaded.
• REMITTANCE_EXISTS — A predicate-style function that reports whether a given remittance already exists, supporting the branch logic used by the two procedures above.
• IMPORT_REMITTANCE_MAIN — The main entry point that coordinates the overall import flow, calling the validation, comparison, and creation/update routines in sequence.

Tables Accessed

The package operates across the core Receivables and Cash Management tables, referenced through APPS synonyms:

• AR_BATCHES — Source of BATCH_APPLIED_STATUS and the parent remittance batch record; read to determine whether a batch is eligible for cancellation or processing.
• AR_TRANSACTION_HISTORY — Counts current records (CURRENT_RECORD_FLAG = 'Y') tied to a batch, which is the basis for the empty-batch test in DUMMY_REMITTANCE.
• AR_PAYMENT_SCHEDULES — Supplies the RESERVED_VALUE used as the batch identifier input to DUMMY_REMITTANCE.
• AR_RECEIPT_METHODS, CE_BANK_ACCOUNTS, and CE_BANK_ACCT_USES_ALL — Provide receipt-method and bank-account context for remittance records being imported.
• RA_CUSTOMER_TRX — Links remittance records to the customer transactions they settle.

Usage Notes

The package is invoked in the context of remittance file import, typically through Oracle Receivables' Brazilian localization flows and related concurrent programs. DUMMY_REMITTANCE is called during batch finalization to prune empty batches and avoid leaving orphaned remittance headers. IMPORT_REMITTANCE_MAIN serves as the primary callable entry point for custom integrations that need to load remittances programmatically. Because the package uses NOCOPY parameters and FND message stacking, callers should pass a VARCHAR2 return status and inspect the message stack after each invocation. ETRM reports no dependent packages, so the API is intended for direct invocation from forms, concurrent programs, or custom PL/SQL rather than as an internal-only routine.