Search Results reassign_strategy

Overview

IEX_STRY_API_PUB is the public PL/SQL API package for the Oracle EBS Advanced Collections (IEX) strategy engine. It encapsulates the business logic that governs how collection strategies are defined, applied to delinquent customers, and progressed through their automated workflow of work items and waiting periods. In EBS 12.1.1 and 12.2.2 the package is owned by APPS and classified as a PUB interface, meaning its procedures are intended to be called from forms, concurrent programs, and custom extensions. The package is the programmatic entry point through which collection agents, the Collections Workbench, and background processes manipulate a customer's active strategy — including the reassignment of a strategy from one customer or agent to another, which is the operation surfaced by the search term "reassign_strategy." The body is implemented in the source file iexpsapb.pls and carries the header suffix 120.11.12020000.3, indicating a 12.2 maintenance level that is also compatible with 12.1.1 code lines. Central to its design is consistent error signalling through FND_MSG_PUB, so callers receive standard IEX messages for invalid, missing, and null arguments.

Key Procedures and Functions

Nine documented entry points make up the public surface of the package. They are not exhaustively listed in the excerpt, but the following are recorded in the ETRM metadata:

• REASSIGN_STRATEGY — Moves an existing strategy assignment from its current owner (customer or collector) to a new target, re-establishing the associated work items and skills so that the collection workflow continues under the new assignment.
• ASSIGN_STRATEGY — Creates the initial association between a strategy and a customer or collector, instantiating the strategy's work items and required skills.
• UPDATE_AND_SENDSIGNAL — Persists changes to a strategy's runtime state and raises the workflow signal that drives the next step in the strategy engine.
• CHECK_STRATEGY_WORKFLOW — Evaluates whether a strategy's workflow is complete or still has pending work, returning status to the caller.
• UPDATE_WORKITEM — Updates the status, dates, or ownership of an individual work item within an active strategy.
• SHOW_IN_UWQ — Determines whether a given item should appear in the Universal Work Queue, exposing collection tasks to the appropriate agent.
• COPY_WORK_ITEM_TEMPLATE — Clones a work item template into a live work item instance for a specific strategy run.
• SKIP_WAIT — Bypasses a waiting period so the next work item in the strategy can be actioned immediately.

An additional internal helper, AddInvalidArgMsg, along with AddMissingArgMsg and AddNullArgMsg, builds standardized FND messages for argument validation; these are private and not part of the PUB contract.

Tables Accessed

All tables are referenced through APPS synonyms. IEX_STRATEGIES holds the strategy definition and its assignment to a customer or collector. IEX_STRATEGY_WORK_ITEMS stores the live work items generated for each active strategy, while IEX_STRATEGY_WORK_SKILLS and IEX_STRATEGY_WORK_SKILLS_S hold the skills required by those items and their translation set. IEX_STRY_TEMP_WORK_ITEMS_B and IEX_STRY_TEMP_WORK_ITEMS_TL store template (base and translated) work items used by COPY_WORK_ITEM_TEMPLATE. FND_LANGUAGES supplies language context for translation-aware operations. DBMS_SQL and PLITBLM are used for dynamic SQL and PL/SQL table manipulation. These references confirm the package both reads strategy configuration and writes runtime state.

Usage Notes

The package is typically invoked from the Advanced Collections forms, from concurrent programs that advance strategies in batch, and from custom code that needs to drive the strategy engine directly. Because it is a PUB API, Oracle supports calling it, but callers must honour the standard EBS API conventions: initialise the FND message stack, pass a valid user id (G_USER_ID), and inspect FND_MSG_PUB after every call. REASSIGN_STRATEGY in particular is used when a collector changes, when a customer record is merged, or when collection responsibility is transferred, and it should be called only against a strategy that is currently active. No other packages reference this package, so its contract is consumed solely by external callers.