Search Results iswi_pk

Overview

IEX_STRATEGY_WORK_ITEMS is a transactional table within the Oracle EBS Collections (IEX) module of release 12.1.1 and 12.2.2. It stores the individual work items that belong to a collections strategy defined in IEX_STRATEGIES. A strategy in Advanced Collections is a reusable sequence of collection activities — dunning letters, phone calls, correspondence, or custom workflow actions — and this table instantiates each of those steps as a discrete, trackable work item.

Each row represents one execution unit of a strategy, keyed by the surrogate primary key WORK_ITEM_ID, enforced through the unique index IEX_STRATEGY_WORK_ITEMS_U1 and the constraint ISWI_PK. The table carries 39 documented columns covering scheduling, execution status, escalation, and optional behavior. Because the table primarily records attributes and lifecycle state of a strategy-driven activity while pointing to parent and lookup entities through foreign keys, it can be modeled, as a heuristic suggestion, as satellite-leaning in a Data Vault context.

Key Information Stored

The most significant columns include:

• WORK_ITEM_ID — the surrogate primary key uniquely identifying each work item.
• STRATEGY_ID — the parent strategy from IEX_STRATEGIES that owns the work item.
• WORK_ITEM_TEMPLATE_ID — the template from which the work item was created.
• RESOURCE_ID — the collections agent or resource assigned to execute the item; foreign key to JTF_RS_RESOURCE_EXTNS.
• STATUS_CODE — current state of the work item (for example, pending, active, or complete).
• SCHEDULE_START / SCHEDULE_END — the planned window for the item.
• EXECUTE_START / EXECUTE_END — the actual execution timestamps.
• WORK_ITEM_ORDER — sequence position of the item within the strategy.
• UWQ_STATUS, UWQ_ACTIVE_DATE, UWQ_COMPLETE_DATE — Universal Work Queue integration fields describing the agent's task queue state.
• ESCALATED_YN, ESCALATE_YN, ESCALATE_WAIT_TIME, ESCALATE_WAIT_TIME_UOM — escalation flag and timing controls.
• OPTIONAL_YN, OPTIONAL_WAIT_TIME, OPTIONAL_WAIT_TIME_UOM — optional step handling and delays.
• NOTIFY_YN — whether notification is triggered on completion.
• CUSTOM_WORKFLOW_TYPE — identifier for a custom workflow action attached to the item.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS supporting multi-org/security partitioning.
• OBJECT_VERSION_NUMBER — optimistic locking column.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

A second unique candidate, IEX_STRATEGY_WORK_ITEMS_U1, is defined on WORK_ITEM_ID, confirming the primary business key. Additional identifiers such as STRATEGY_TEMP_ID and XDO_TEMP_ID support template and XML Publisher instantiations respectively.

Common Use Cases and Queries

Primary use cases include monitoring strategy execution, analyzing agent workload, and tracking escalations. A typical query joins work items to their strategy parents:

• List active work items per strategy by filtering STATUS_CODE.
• Report agents with overdue items using SCHEDULE_END and EXECUTE_END.
• Audit escalation behavior using ESCALATED_YN and ESCALATE_WAIT_TIME.
• Feed Universal Work Queue dashboards using UWQ_STATUS.

Sample pattern: SELECT w.WORK_ITEM_ID, w.STRATEGY_ID, w.STATUS_CODE, w.SCHEDULE_START FROM IEX.IEX_STRATEGY_WORK_ITEMS w WHERE w.UWQ_STATUS = :status. Joining to JTF_RS_RESOURCE_EXTNS via RESOURCE_ID resolves the assigned agent name.

Related Objects

• IEX_STRATEGIES — parent strategy referenced through STRATEGY_ID.
• JTF_RS_RESOURCE_EXTNS — resolved agent/resource via RESOURCE_ID foreign key.
• FND_SECURITY_GROUPS — security partitioning via SECURITY_GROUP_ID.
• IEX_STRATEGY_WORK_ITEMS templates and status code lookups (FND_LOOKUPS) drive STATUS_CODE and UOM values.
• Universal Work Queue (IEX_UWQ_*) objects consume UWQ_STATUS fields for agent task routing.

These relationships make IEX_STRATEGY_WORK_ITEMS a central operational table linking strategy definitions, agents, and the collections work queue.