Search Results check_work_items_completed

Overview

The APPS.IEX_STRATEGY_WF package body is a core workflow orchestration component within the Oracle E-Business Suite Advanced Collections (IEX) module. Its principal business function is to drive the strategy-based collection workflow engine, binding collection strategies to Oracle Workflow item types and managing the lifecycle of the individual work items that comprise a strategy. In Oracle EBS 12.1.1 and 12.2.2, collections agents execute strategies against delinquent customers; each strategy expands into a sequence of work items (calls, dunning letters, correspondence, or custom activities) that must be processed, optionally escalated, placed on hold, completed, or aborted based on runtime conditions. The package encapsulates the PL/SQL logic that determines whether work items are complete, whether optional or escalation branches apply, whether fulfillment or XML delivery steps have finished, and whether the overall strategy should be closed.

The package is classified as OTHER in the ETRM metadata, reflecting that it is primarily an internal engine rather than a public API, though it is referenced by twelve other packages within the Collections and Receivables footprint.

Key Procedures and Functions

The documented package exposes 31 procedures and functions. The following represent the principal public entry points and control routines:

• CHECK_WORK_ITEMS_COMPLETED — Evaluates whether all work items belonging to a strategy have reached a terminal state; central to the completion determination referenced in the private abort logic.
• CLOSE_STRATEGY — Finalizes a strategy instance once its work items have completed or been terminated.
• CREATE_NEXT_WORK_ITEM — Instantiates the subsequent work item in the strategy sequence.
• PROCESS_STATUS — Interprets and acts upon the status of an in-flight work item.
• UPDATE_WORK_ITEM — Persists changes to work item attributes during processing.
• SET_NOTIFICATION_RESOURCES — Resolves and assigns the resources (collectors or contacts) responsible for a notification-driven work item.
• SEND_SIGNAL, WAIT_SIGNAL, WAIT_COMPLETE_SIGNAL — Manage inter-item signaling and blocking waits within the workflow.
• OPTIONAL_CHECK, ESCALATE_CHECK, ONHOLD_CHECK, FULFIL_CHECK, NOTIFY_CHECK, CUSTOM_CHECK — Conditional gate routines that determine whether the optional, escalation, hold, fulfillment, notification, or custom branches of a strategy apply.
• WAIT_OPTIONAL, WAIT_ESCALATION, CAL_PRE_WAIT, CAL_POST_WAIT — Timing and calendar-delay routines controlling pauses before subsequent actions.
• WI_FAILED_FIRST_TIME — Handles first-time failure of a work item, supporting retry or fallback logic.

Tables Accessed

The package reads and writes the following documented tables (through APPS synonyms):

• IEX_STRATEGIES — Strategy header definitions and JTF object mapping.
• IEX_STRATEGY_WORK_ITEMS, IEX_STRY_TEMP_WORK_ITEMS_B, IEX_STRATEGY_WORK_TEMP_XREF — Instance-level and template-level work item definitions and their cross-references.
• IEX_STRATEGY_USER_ITEMS, IEX_STRATEGY_WORK_SKILLS — Agent-assigned items and required competencies.
• IEX_DUNNINGS, IEX_XML_REQUEST_HISTORIES — Correspondence and XML delivery tracking.
• WF_ITEMS, FND_NEW_MESSAGES — Workflow runtime state and notification queue.
• HZ_PARTIES, JTF_RS_RESOURCE_EXTNS, PER_COMPETENCE_ELEMENTS — Customer, resource, and competency data.
• MTL_UOM_CONVERSIONS, DUAL — Unit-of-measure conversion and scalar evaluations.

Usage Notes

IEX_STRATEGY_WF is invoked predominantly by the Oracle Workflow engine when a Collections strategy is launched from the Advanced Collections agent interface or through the strategy scheduling concurrent programs. Work items transition through the engine calling the check, wait, and create routines described above. Custom implementations extending Collections (for example, bespoke workflow item types) can reference the package where DBA/developer privileges permit, but the procedures are not documented as a supported public API. The private abort_processes and custom_abort_process routines illustrate defensive termination logic that aborts incomplete workflows when a strategy is cancelled. Because twelve packages depend on it, changes should be regression-tested against the full Collections workflow chain in both 12.1.1 and 12.2.2 environments.