Search Results isui_pk

Overview

The IEX.IEX_STRATEGY_USER_ITEMS table is a Collections (IEX) module object in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores custom work item templates that have been added to a particular strategy defined in IEX_STRATEGIES. In the Advanced Collections workflow model, a strategy is an ordered sequence of collection actions; templates define the individual work items that drive those actions. While Oracle ships seeded work item templates, the IEX_STRATEGY_USER_ITEMS table records the user-defined or custom templates that a collector or administrator associates with a strategy, together with ordering information, execution wait and escalation rules, and optional notification behavior.

The table is owned by the IEX schema, has a status of VALID, and is documented in ETRM 12.2.2 with 31 columns. The primary key constraint is ISUI_PK on STRATEGY_USER_ITEM_ID, mirrored by the unique index IEX_STRATEGY_USER_ITEMS_U1 on the same column. The metadata classifies the object as standalone under the heuristic Data Vault classification, meaning it is best modeled as its own hub-like entity rather than as a dependent satellite or link. In practice this reflects that the table is an independently keyed configuration entity keyed by a surrogate ID, with foreign key references outward rather than a strict parent/child dependency chain within IEX.

Key Information Stored

The most business-relevant columns fall into several functional groups:

• Identity: STRATEGY_USER_ITEM_ID is the surrogate primary key and unique-index column. STRATEGY_ID identifies the parent strategy, and WORK_ITEM_TEMP_ID identifies the underlying work item template being added. STRATEGY_TEMPLATE_ID associates the record with a strategy template context.
• Sequencing: WORK_ITEM_ORDER controls the position of the item within the strategy's ordered execution flow.
• Execution timing: PRE_EXECUTION_WAIT, PRE_EXECUTION_TIME_UOM, POST_EXECUTION_WAIT, and EXECUTION_TIME_UOM define delays before and after the item runs and their units of measure.
• Optional handling: OPTIONAL_YN, OPTIONAL_WAIT_TIME, and OPTIONAL_WAIT_TIME_UOM govern items that may be skipped or conditionally delayed.
• Escalation and notification: NOTIFY_YN, ESCALATE_YN, ESCALATE_WAIT_TIME, and ESCALATE_WAIT_TIME_UOM determine whether the item generates notifications and whether it escalates after a defined interval.
• Resource and workflow: RESOURCE_ID, CUSTOM_WORKFLOW_TYPE, and XDO_TEMP_ID tie the item to a resource, a custom workflow type, and an XML Publisher (XDO) template.
• Audit and concurrency: the standard CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER, and the PROGRAM_* / REQUEST_ID columns support auditing and the concurrent request that touched the row.

The business-key candidate is STRATEGY_USER_ITEM_ID, established by the unique index IEX_STRATEGY_USER_ITEMS_U1. The table also carries SECURITY_GROUP_ID, which references FND_SECURITY_GROUPS and supports multi-org or security-group partitioning.

Common Use Cases and Queries

Typical uses include reviewing which custom items are attached to a strategy, validating ordering and timing configuration before deployment, and auditing escalation and notification rules. A common reporting query lists items for a given strategy in execution order:

• SELECT strategy_user_item_id, work_item_order, work_item_temp_id, notify_yn, escalate_yn FROM iex.iex_strategy_user_items WHERE strategy_id = :p_strategy_id ORDER BY work_item_order;
• Join to FND_SECURITY_GROUPS on security_group_id to report items by security group.
• Filter on escalate_yn = 'Y' to identify items with escalation behavior, or on notify_yn = 'Y' for notification-bearing items when tuning collector workloads.
• Reconcile with OBJECT_VERSION_NUMBER when diagnosing concurrent update conflicts on strategy configuration.

Related Objects

• FND_SECURITY_GROUPS — referenced via IEX_STRATEGY_USER_ITEMS.SECURITY_GROUP_ID.
• IEX_STRATEGIES — parent strategy referenced through STRATEGY_ID.
• IEX_WORK_ITEM_TEMPLATES (and related template tables) — source for WORK_ITEM_TEMP_ID.
• XML Publisher (XDO) template objects — resolved through XDO_TEMP_ID.
• Concurrent program and request metadata (FND_CONCURRENT_REQUESTS) — linked via REQUEST_ID and the PROGRAM_* columns.