Search Results refresh_case_folder

Overview

The APPS.AR_CMGT_REFRESH_CONC package body is an Oracle Receivables utility that supports the Case Management (Collections Management) feature set in Oracle E-Business Suite 12.1.1 and 12.2.2. Its primary business purpose is to refresh the contents of a case folder, ensuring that the aggregate collections case data held in the folder structure reflects the most current customer, transaction, and activity information. This refresh operation is essential because case folders consolidate data from multiple sources, and stale folder content can mislead collections agents who rely on the folder as a single view of a customer's outstanding receivables and dispute history.

The package follows a submission-oriented design pattern common in EBS. Rather than performing a potentially long-running refresh synchronously, it submits an asynchronous concurrent request to the Concurrent Manager through the FND_REQUEST API. This isolates the refresh workload from the calling session and prevents the calling form from blocking while folder data is recomputed. The program submitted is ARCMRFHB, the concurrent program associated with case folder refresh processing, with the case folder identifier passed as the first argument.

Key Procedures and Functions

• SUBMIT_REFRESH_REQUEST — The entry point that accepts a case folder identifier and a caller-origin indicator, then submits the refresh concurrent request. Before submission, it calls FND_REQUEST.SET_OPTIONS with protected mode so that request options cannot be overridden by the caller, and it submits ARCMRFHB with implicit submission disabled. It returns the concurrent request identifier to the caller for subsequent status monitoring. The p_called_from parameter allows the package to record which UI or program initiated the refresh, which is useful for diagnostics and for enforcing invocation-specific behavior.
• REFRESH_CASE_FOLDER — The procedure that performs or coordinates the actual refresh logic for a given case folder. It is the documented operation that the concurrent request ultimately executes, rebuilding the folder content so that the case reflects current receivable and collections data.

Tables Accessed

• AR_CMGT_CASE_FOLDERS — The central table accessed by this package. It stores the case folder header and definition records for Collections Management. The refresh process reads the relevant folder record to identify what data must be re-derived and writes back the refreshed folder state so that the user interface and downstream processes see current information.

Usage Notes

This package is typically invoked from the Collections Management forms or from custom extensions when a user or process requests that a case folder be rebuilt. Because refresh can be resource-intensive, the design deliberately routes work through the Concurrent Manager rather than executing inline. Developers integrating with this package generally call AR_CMGT_REFRESH_CONC.SUBMIT_REFRESH_REQUEST with a valid case folder identifier and capture the returned request ID to monitor completion via the standard FND concurrent request views.

The package is referenced by one other package in the application, indicating it participates in a larger Collections Management refresh chain rather than operating in isolation. When troubleshooting, the debug flag driven by the AFLOG_ENABLED profile option controls diagnostic output through arp_util.debug, so enabling FND logging is advisable before investigating refresh failures. Users searching for "refresh_case_folder" should note that the concrete refresh behavior is exposed through the REFRESH_CASE_FOLDER procedure, while SUBMIT_REFRESH_REQUEST is the asynchronous submission wrapper used by callers.