Search Results delete_param_value

Overview

The APPS.IEX_UTILITIES package is a shared utility library within the Oracle E-Business Suite Advanced Collections (IEX) module. It does not implement a single business process; instead it provides reusable PL/SQL constructs that other collections-related packages, forms, and concurrent programs invoke to perform common operations. These operations include account balance calculation, identifier and lookup validation, resource resolution for collectors and dunning activities, delinquency and dunning profile evaluation, and a lightweight caching mechanism for application preference values. Because it is a utility package, IEX_UTILITIES is referenced by 57 other packages, making it a foundational dependency across the Collections application codebase.

The package declares numerous collection-oriented types at the specification level, including resource_rec_type for resource and user identity data, Condition_REC and Condition_Tbl for building dynamic WHERE clauses, and several numeric index-by tables such as t_del_id, t_asset_id, t_del_children, and t_numbers. These types are exposed to callers and are central to how the package passes sets of delinquency and asset identifiers between its routines.

Key Procedures and Functions

The 36 documented routines fall into several functional groups:

• Validation: VALIDATE_ANY_ID, VALIDATE_ANY_VARCHAR, and VALIDATE_LOOKUP_CODE verify that a given identifier, character value, or lookup code exists in a specified column and table before downstream processing proceeds.
• Balance and account: ACCT_BALANCE returns the account balance for a supplied customer account identifier.
• Resource resolution: GET_ACCESS_RESOURCES, GET_ASSIGN_RESOURCES, GET_ASSIGN_ACCOUNT_RESOURCES, GET_CASE_RESOURCES, GET_ASSIGNED_COLLECTOR, and GET_DUNNING_RESOURCE retrieve the collectors, resources, or user identities associated with accounts, cases, or dunning activities.
• Lookups and configuration: GET_LOOKUP_MEANING resolves a lookup code to its meaning, while GET_GRACE_DAYS returns the configured grace period.
• Caching and parameters: GET_CACHE_VALUE, PUT_PARAM_VALUE, GET_PARAM_VALUE, and DELETE_PARAM_VALUE implement a session-level caching and parameter persistence mechanism, allowing callers to store and retrieve values without repeated queries.
• Dunning and delinquency: DUNNINGPROFILECHECK, DUNNINGMINAMOUNTCHECK, STAGEDDUNNINGMINAMOUNTCHECK, and MAXSTAGEFORANDELINQUENCY evaluate whether accounts qualify for dunning based on profile and minimum amount thresholds, and determine the maximum stage for a delinquency.

Parameter lists are deliberately not enumerated here; callers should reference the package specification for exact signatures.

Tables Accessed

The package reads and writes against several core Receivables and Collections tables via APPS synonyms. Customer and account data is drawn from HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES, HZ_CUST_SITE_USES and its _ALL counterpart, HZ_CUSTOMER_PROFILES, HZ_CUST_PROFILE_AMTS, and HZ_PARTY_PREFERENCES. Payment and system configuration data comes from AR_PAYMENT_SCHEDULES, AR_PAYMENT_SCHEDULES_ALL, and AR_SYSTEM_PARAMETERS_ALL. Collections-specific data is sourced from IEX_DELINQUENCIES_ALL, IEX_DUNNINGS, IEX_AG_DN_XREF, and application preferences held in IEX_APP_PREFERENCES_B. DBMS_SQL is referenced to support the dynamic SQL used by the validation routines that accept arbitrary column and table names.

Usage Notes

IEX_UTILITIES is normally invoked indirectly. Collections forms call its validation, resource, and dunning routines during user interactions, while concurrent programs rely on the delinquency and amount-check procedures during batch dunning runs. Custom code that needs to determine collector assignment, validate lookups, or read application preference values should call these documented programs rather than querying the underlying tables directly. Because 57 other packages depend on this specification, changes to its types or interfaces carry broad impact and should be regression-tested accordingly.