Search Results refresh_all

Overview

IEX_METRIC_CONCUR_PVT is a private PL/SQL package owned by the APPS schema within the Oracle E-Business Suite Collections (Advanced Collections / IEX) module. The package name follows the Oracle naming convention in which the _PVT suffix signifies a private, internal package that is not part of the published API surface exposed to external integrations. Its designation as AUTHID CURRENT_USER indicates that it executes with the privileges of the invoking user rather than the definer, which is typical for internal collection-layer utilities that operate against APPS synonyms under the session's authority.

The business function of this package is to consolidate and refresh the metric summaries used by Advanced Collections to measure collection performance and delinquency exposure. Collections organizations rely on summary metrics—such as delinquency aging, promise-to-pay outcomes, and scorecard-style aggregates—to assess collector effectiveness and portfolio health. The package header reflects a version path of $Header: iexvmtcs.pls 120.3 2006/03/28, indicating it originated in the 11.5.x/12.0 lineage and remains present and documented in ETRM for both 12.1.1 and 12.2.2. Because it aggregates data across large transactional tables, the package is designed to run in a batch, concurrent-safe manner.

Key Procedures and Functions

The ETRM metadata documents a single public procedure in this package:

• Refresh_All — The sole entry point, responsible for the full recalculation of Collections metric summary data. The header declares it with standard concurrent program out-parameters for error buffer and return code, plus an inbound organization identifier. Its signature therefore follows the canonical concurrent manager submission contract: the request framework captures the error buffer for the log file and the return code to determine request success or warning status, while the organization identifier restricts the refresh scope to the single operating unit (or, where the parameter indicates a global run, to all applicable organizations). The procedure name "Refresh_All" conveys that it performs a complete rebuild of the summary tables rather than an incremental or delta refresh.

No additional procedures or functions are documented. This narrow interface confirms that the package is intended to be driven externally—typically by a scheduled concurrent request—rather than called interactively by application forms logic.

Tables Accessed

The documented table references, resolved through APPS synonyms, fall into three functional groups.

• Collections transactional data: IEX_DELINQUENCIES and IEX_DELINQUENCIES_ALL hold the delinquency records that drive aging and exposure metrics. The _ALL variant carries the organization (org_id) dimension, which aligns with the organization identifier parameter on Refresh_All.
• Collections summary data: IEX_METRIC_SUMMARIES and IEX_METRIC_SUMMARIES_ALL are the metric result tables that the procedure populates. The naming symmetry with the delinquency tables confirms that the refresh reads raw delinquencies and writes aggregated summaries, one set global and one set organization-specific.
• Customer and party master data: HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES, and HZ_PARTIES provide the customer, site, and party hierarchy attributes used to group and label metric results. These are the standard Trading Community Architecture (TCA) entities for customer accounts and locations.
• Infrastructure and utility objects: AD_DDL is the Applications DDL utility used for dynamic SQL operations, and PLITBLM is the PL/SQL table buffer package native to Oracle Forms/PL/SQL table handling. Their presence suggests the routine performs dynamic DDL or bulk array processing during the refresh.

Usage Notes

Because IEX_METRIC_CONCUR_PVT is a private package (API classification PVT) and is not referenced by any other documented package, it should be treated as an internal implementation detail of the Advanced Collections concurrent program suite. It is most likely invoked from a concurrent program definition registered by Oracle, scheduled to run on a nightly or periodic basis so that metric summaries reflect current delinquency and customer state before collectors begin their workday. Users selecting the request in the Submit Requests window, or administrators monitoring the Collections concurrent manager, are the normal consumers of its output.

Custom code should not call this package directly. Oracle does not guarantee backward compatibility for _PVT packages, and its signature or existence may change without a public interface commitment. The absence of the string "refresh_all" in any published API listing confirms it is not a supported integration point. Organizations requiring programmatic metric refreshes should instead resubmit the associated Oracle concurrent program through the standard concurrent manager APIs (FND_REQUEST.SUBMIT_REQUEST), preserving supportability across 12.1.1 and 12.2.2 upgrades.