Search Results skip_wait

Overview

IEX_STRY_API_PUB is a public PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that exposes the runtime services of the Advanced Collections (IEX) Strategy engine. Strategy records define the collection actions that are applied to a delinquent customer account based on delinquency scoring, and the work items generated from a strategy drive the Collector's Work Queue and the workflow that escalates or closes tasks. IEX_STRY_API_PUB provides the supported entry points through which forms, JSP pages, and other modules assign, reassign, update, and advance those strategy work items without manipulating the underlying IEX tables directly.

The package is declared AUTHID CURRENT_USER, so it executes with the privileges of the invoking schema, and the header carries the $Header $ revision iexpsaps.pls 120.3.12010000.1 dated 29-Jul-2008, which is the code line shipped in both 12.1.1 and 12.2.2. It is classified as a PUB API and is not referenced by any other package, placing it near the top of the call stack for the Collections strategy domain.

Key Procedures and Functions

Nine procedures are documented in the ETRM metadata:

• ASSIGN_STRATEGY — creates a new strategy instance from a strategy template and, on success, launches the associated workflow. Introduced under Bug 6794510.
• REASSIGN_STRATEGY — sends a signal to the current strategy, then creates a replacement strategy from the template so that the new instance launches its own workflow.
• UPDATE_AND_SENDSIGNAL — updates a strategy work item and then calls the workflow signal API; if the signal fails, the work-item update is rolled back. Two variants exist: one accepting a strategy_work_item_Rec_Type record, and one accepting individual columns for callers such as JSP pages.
• UPDATE_WORKITEM — persists changes to a strategy work item, including status transitions.
• CHECK_STRATEGY_WORKFLOW — validates the workflow state associated with a strategy.
• SHOW_IN_UWQ — controls whether a work item is presented in the Universal Work Queue.
• COPY_WORK_ITEM_TEMPLATE — duplicates a work item template, typically when instantiating a strategy.
• SKIP_WAIT — bypasses the wait period on a work item so that it becomes actionable immediately, allowing users to advance past a configured delay rather than waiting for the scheduled release time.

All procedures follow the FND_API convention, returning x_return_status, x_msg_count, and x_msg_data, and accepting a p_commit flag that defaults to FND_API.G_FALSE.

Tables Accessed

The package reads and writes the core Collections strategy tables through APPS synonyms:

• IEX_STRATEGIES — strategy header definitions and instances.
• IEX_STRATEGY_WORK_ITEMS — the individual work items that make up a strategy.
• IEX_STRATEGY_WORK_SKILLS and IEX_STRATEGY_WORK_SKILLS_S — skill requirements assigned to work items and their sequence.
• IEX_STRY_TEMP_WORK_ITEMS_B and IEX_STRY_TEMP_WORK_ITEMS_TL — template work-item definitions, including the translated (TL) descriptions.
• DBMS_SQL and PLITBLM — dynamic SQL and PL/SQL table utilities.
• FND_LANGUAGES — language validation for translated content.

Usage Notes

IEX_STRY_API_PUB is invoked primarily from the Advanced Collections HTML/JSP user interface and the Collector's Work Queue, where assigning a strategy, updating a work item, or skipping a wait triggers these procedures. Because the package is a PUB API, customizations and extensions should call it rather than performing DML against the IEX strategy tables. When calling from custom code, set p_commit to G_FALSE so the calling transaction retains control, and inspect x_return_status against FND_API.G_RET_STS_SUCCESS before proceeding.