Search Results optional_check




Overview

APPS.IEX_STRATEGY_WF is the workflow integration package for the Oracle E-Business Suite Collections (Advanced Collections / IEX) strategy engine. A "strategy" in Advanced Collections is an ordered, resource-aware plan of collection actions (calls, dunning letters, tasks, escalations) executed against a delinquent customer. This package supplies the server-side PL/SQL callback logic that a Workflow (WF) process definition invokes at each activity node, advancing a strategy from one work item to the next, suspending until an agent completes or a signal arrives, and closing the strategy when all pending work is resolved. It is declared AUTHID CURRENT_USER and resides in the APPS schema as part of the IEX product. Its header carries a 120.6 revision lineage from 12.1.1, and the object remains documented in ETRM at 12.2.2 as an OTHER-classified API, confirming continuity across the 12.1.1 to 12.2.2 migration.

Key Procedures and Functions

The documented entry points (31 procedures/functions in total; representative members below) follow the standard Workflow function signature — itemtype, itemkey, actid, funcmode and an OUT result — and are registered as Workflow function activities.

Tables Accessed

The package reads and writes the core Collections strategy tables through APPS synonyms: IEX_STRATEGIES (strategy header), IEX_STRATEGY_WORK_ITEMS and IEX_STRY_TEMP_WORK_ITEMS_B (work item instances derived from templates), IEX_STRATEGY_USER_ITEMS, IEX_STRATEGY_WORK_SKILLS, IEX_STRATEGY_WORK_TEMP_XREF, IEX_DUNNINGS, PER_COMPETENCE_ELEMENTS (competence matching for work item assignment), JTF_RS_RESOURCE_EXTNS and HZ_PARTIES (resource and customer context), MTL_UOM_CONVERSIONS, FND_NEW_MESSAGES (notification text), IEX_XML_REQUEST_HISTORIES, and WF_ITEMS for workflow engine state. It also selects from DUAL for control logic.

Usage Notes

IEX_STRATEGY_WF is invoked indirectly: the Advanced Collections strategy workflow item type references its procedures as function activities, and operational forms or concurrent processes that create and update work items call it to synchronize workflow state. It is referenced by twelve other application packages, so direct customer modification is discouraged; extensions should wrap or subscribe to the documented entry points. Because the initial search term (a product query unrelated to EBS) does not map to this object, no buying or inventory procedure exists here — the package is strictly the Collections strategy workflow driver.