Search Results iex_checklist_utility




Overview
Explore in AI Chat

Overview

IEX_CHECKLIST_UTILITY is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified as an OTHER API within the ETRM repository. It is a component of the Advanced Collections (IEX) application family and provides shared utility logic for the checklist and questionnaire processing framework used by Collections strategies and the Universal Work Queue. The package abstracts common operations—image resolution for user interface elements, metric rating updates, checklist item updates, and configuration changes to leasing, loan, and business-level setups—so that multiple Collections modules can reuse the same internal logic rather than duplicating it.

In EBS 12.1.1 and 12.2.2 the package carries a VALID status and depends only on the SYS STANDARD package, indicating that it does not itself invoke other APPLSYS or product APIs. This narrow dependency footprint makes it a low-level utility rather than an orchestration layer.

Key Procedures and Functions

The ETRM metadata documents twelve callable units:

Tables Accessed

The package operates across three functional areas. The Collections checklist and strategy area includes IEX_CHECKLIST_ITEMS_B, IEX_QUESTIONNAIRE_ITEMS, IEX_STRATEGY_TEMPLATES_B, IEX_STRATEGY_TEMPLATE_GROUPS, and IEX_STRATEGY_TEMPLATE_GROUPS_S; these support item definitions and template grouping. Metric-related reads and writes touch IEX_METRIC_RATINGS and IEX_METRIC_RATINGS_S. Filtering logic uses IEX_OBJECT_FILTERS. Foundation tables FND_FORM_FUNCTIONS, FND_MENUS, FND_MENU_ENTRIES, FND_RESPONSIBILITY, and FND_RESP_FUNCTIONS are accessed for menu and responsibility checks, while DUAL serves utility arithmetic or single-row queries.

Usage Notes

IEX_CHECKLIST_UTILITY is referenced by IEX_STRATEGY_CNT_PUB and IEX_UWQ_POP_SUM_TBL_PVT, confirming that it is invoked internally by Collections strategy processing and Universal Work Queue population logic rather than by end users directly. It is not documented as a public API, and no concurrent program or form is registered against it. Customizations should therefore avoid direct calls; instead, developers should route changes through the referencing public packages. When troubleshooting checklist or metric rating behavior in 12.1.1 or 12.2.2, this package is a useful focal point because most checklist write operations ultimately pass through UPDATE_CHECKLIST_ITEM or UPDATE_METRIC_RATING.