Results for “process_payments”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.IEX_PAYMENTS_BATCH_PUB package body is a public PL/SQL API within the Oracle E-Business Suite Collections (Advanced Collections) module, owned by the APPS schema and classified as a PUBLIC API. Its primary business function is to drive the batch processing of payment records — typically payments received against delinquent customer accounts — through a concurrent request. The package encapsulates the logic required to invoke the core payment-processing engine, coordinate date-range determination, and provide debugging and logging support for administrators diagnosing collections runs. Because it is a _PUB package, it is intended to be called from outside the owning product boundary, including concurrent programs, workflow, and custom extensions.

The package declares a substantial set of global constants and variables that establish its runtime context, including the application identifier G_APP_ID := 695, the package name, the login, program, and request identifiers sourced from FND_GLOBAL, and the global date variables G_START_DATE and G_END_DATE with a G_DATES_LOADED boolean flag. A private debug procedure gates messaging through FND_LOG at the event level and routes output to iex_debug_pub.LogMessage.

Key Procedures and Functions

• IEX_PAYMENTS_CONCUR — The concurrent-program entry point. It accepts the standard concurrent program OUT parameters (error buffer and return code), sets a message counter, and delegates to PROCESS_PAYMENTS with version 1.0, message-list initialization enabled, commit enabled, and full validation level. It emits debug markers at start and end, making it the wrapper through which the concurrent manager executes the batch.
• PROCESS_PAYMENTS — The documented worker procedure that performs the actual payment batch processing. It is the procedure invoked by IEX_PAYMENTS_CONCUR and carries the standard API contract used across the IEX public packages.

In addition, though not listed among the two publicly documented procedures, the body contains a private LOAD_DATES procedure. This procedure is significant because it is the origin of the user's search term g_start_date. LOAD_DATES declares cursors get_start_date_crs and get_end_date_crs, which query FND_CONC_REQ_SUMMARY_V for the maximum ACTUAL_START_DATE and the matching ACTUAL_START_DATE of the IEX_PROCESS_PAYMENTS program (application 695 or 222). These values are assigned to the package globals G_START_DATE and G_END_DATE, establishing the processing window for a given run.

Tables Accessed

The metadata documents that the package references tables via APPS synonyms. The clearest documented dependency is FND_CONC_REQ_SUMMARY_V, the concurrent request summary view, which is read to derive the start and end dates for a prior IEX_PROCESS_PAYMENTS execution. The date pivots on ACTUAL_START_DATE and is filtered by PROGRAM_SHORT_NAME and PROGRAM_APPLICATION_ID, with an explicit comment noting a performance fix (bug 4930381) for the dual application ID condition. Downstream, PROCESS_PAYMENTS is expected to read and write the IEX payment and collections transaction tables through their APPS synonyms, though the excerpt does not enumerate them.

Usage Notes

This package is invoked primarily as a concurrent program, most likely registered as IEX_PROCESS_PAYMENTS, and can also be called from forms, workflow, or custom PL/SQL. The header version 120.3 (2006/05/30) indicates a mature, stable interface. Two other packages are documented as referencing it, reinforcing its role as a shared public entry point. Developers should note that the global date variables are populated by LOAD_DATES from concurrent request history rather than being passed as parameters, so any custom invocation should respect that initialization pattern to avoid unexpected date ranges.