Search Results iex_strategy_work_items_pkg




Overview
Explore in AI Chat

Overview

IEX_STRATEGY_WORK_ITEMS_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM documentation as an "OTHER" API type. It supports the Collections and Advanced Collections (IEX) module, specifically the work item component of collection strategies. Within Advanced Collections, a strategy defines the ordered set of actions a collector or the system should perform against a delinquent customer, and individual work items represent the actionable units generated when a strategy is applied to a customer account or delinquency event. This package provides the low-level data manipulation layer for the IEX_STRATEGY_WORK_ITEMS table, exposing discrete row-level operations rather than a business-event driven API surface. Its status is documented as VALID in the ETRM repository for both 12.1.1 and 12.2.2, confirming it remains a supported internal object across the release family. The package declares both a specification and a body, and its dependency footprint is deliberately narrow: it references only the SYS.STANDARD package and the IEX_STRATEGY_WORK_ITEMS table through APPS synonyms.

Key Procedures and Functions

The ETRM metadata documents four procedures in this package, collectively forming a standard CRUD-style interface for a single base table:

  • INSERT_ROW — Creates a new strategy work item record, populating the columns of IEX_STRATEGY_WORK_ITEMS with the supplied attribute values. It is the entry point for adding an actionable work item to an existing collection strategy definition.
  • UPDATE_ROW — Modifies the attributes of an existing strategy work item identified by its primary key, allowing changes to work item properties without inserting a duplicate record.
  • LOCK_ROW — Acquires an exclusive row-level lock on the specified work item record. This is a concurrency-control primitive that prevents simultaneous modification of the same work item by competing sessions, and it precedes update or delete operations within a transaction.
  • DELETE_ROW — Removes a strategy work item record from the table, typically invoked when a work item is no longer required in a strategy definition.

The specification exposes these four entry points only; no additional public functions are documented in the ETRM listing. Parameter signatures are not enumerated in the available metadata and should be verified against the deployed specification in the target instance.

Tables Accessed

The single documented table is IEX_STRATEGY_WORK_ITEMS, accessed via the APPS synonym layer. This table is the persistent store for the individual work items that compose a collection strategy. It typically holds the sequence or ordering of the work item within the strategy, the work item type, timing or due-date rules, and assignment characteristics that govern how the item is presented to a collections agent or processed by the Collections engine. The INSERT_ROW and UPDATE_ROW procedures write to this table, DELETE_ROW removes rows, and LOCK_ROW reads the row with a locking clause. No other base tables, views, or sequences appear in the documented dependency list, indicating the package is intentionally a thin, table-scoped data access module rather than a cross-functional business API.

Usage Notes

This package is an internal, table-level API and is not intended as a public extension point. It is referenced by only one other documented package, IEX_STRATEGY_WORK_ITEMS_PVT, which is the private business logic counterpart in the standard EBS public/private (PKG/PVT) design pattern. In practice, callers should invoke IEX_STRATEGY_WORK_ITEMS_PVT, which in turn delegates row maintenance to this package; direct calls from custom code bypass validation logic embedded in the PVT layer and are therefore discouraged. DML on strategy work items occurs primarily through the Advanced Collections strategy setup forms and through internal strategy generation processing, where work items are instantiated as delinquencies are evaluated. Because the procedures include an explicit LOCK_ROW, any custom caller must manage transaction boundaries and commit/rollback explicitly. Implementations should treat IEX_STRATEGY_WORK_ITEMS_PKG as a stable but private object: it is valid in both 12.1.1 and 12.2.2, yet Oracle documentation for it is minimal, and signature changes across patches are possible without notice.