Search Results iex_stry_temp_work_items_b_u1

Overview

IEX_STRY_TEMP_WORK_ITEMS_B is a seed-data table in the Oracle EBS Collections (Advanced Collections / IEX) schema that stores reusable templates for collection work items. Each row defines the attributes of a work item template—such as an interaction or task—that can be applied when generating, scheduling, or assigning collector work items. The table resides in the APPS_TS_SEED tablespace, consistent with its role as a configuration/seed source rather than a high-volume transactional table. The presence of the ZD_EDITION_NAME column indicates the object participates in the EBS 12.2 Online Patching (adop) editioning model, where _B base tables are surfaced to runtime through editioning views.

From a Data Vault modeling perspective, the FK metadata describes this object as standalone, but its structure—a unique business key (WORK_ITEM_TEMP_ID) combined with descriptive, potentially time-variant attributes—suggests a satellite-style classification. The template definition can be modeled as a satellite keyed to the work item temp identity, with the standard WHO columns acting as load metadata.

Key Information Stored

• WORK_ITEM_TEMP_ID — Number(25); the surrogate/template identifier and the leading column of the unique index IEX_STRY_TEMP_WORK_ITEMS_B_U1.
• COMPETENCE_ID — FK to PER_COMPETENCES; ties the template to the competence/skill required to perform the work item.
• WORK_TYPE — Distinguishes automatic versus manual work item generation.
• CATEGORY_TYPE — Category of the work item, documented values include SEND LETTER, CALL, VISIT.
• PRIORITY_TYPE — Priority assigned to work items generated from this template.
• OPTIONAL_YN / ENABLED_FLAG — Control flags governing whether the template is optional and whether it is active.
• OPTION_WAIT_TIME / OPTION_WAIT_TIME_UOM — Deferral interval and unit of measure before the item becomes actionable.
• PRE_EXECUTION_WAIT / POST_EXECUTION_WAIT / EXECUTION_TIME_UOM — Timing parameters around item execution.
• SAME_RESOURCE_YN / TEMP_RESOURCE_ID — Whether the same resource must handle sequential items, and the default/assigned resource.
• CLOSURE_TIME_LIMIT / CLOSURE_TIME_UOM — Deadline window for closing the work item.
• SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS; enforces data security partitioning.
• Standard WHO and concurrent columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, PROGRAM_ID, REQUEST_ID, OBJECT_VERSION_NUMBER, plus ATTRIBUTE1–15 for extension.
• ZD_EDITION_NAME — Online Patching edition marker; part of the unique index IEX_STRY_TEMP_WORK_ITEMS_B_U1.

Common Use Cases and Queries

Typical usage centers on reporting and validation of collection strategy templates, and on diagnosing why generated work items carry particular timing or priority attributes.

• List active templates by category:
  SELECT work_item_temp_id, category_type, priority_type, enabled_flag
FROM iex.iex_stry_temp_work_items_b
WHERE enabled_flag = 'Y' ORDER BY category_type;
• Identify templates linked to a competence:
  SELECT t.work_item_temp_id, c.competence
FROM iex.iex_stry_temp_work_items_b t, per_competences c
WHERE t.competence_id = c.competence_id;
• Audit recent configuration changes through the WHO columns:
  SELECT work_item_temp_id, last_updated_by, last_update_date
FROM iex.iex_stry_temp_work_items_b
WHERE last_update_date > SYSDATE - 30;

Users searching for iex_stry_temp_work_items_b_u1 are typically validating the unique constraint on WORK_ITEM_TEMP_ID (with ZD_EDITION_NAME under 12.2), an important check before template loads or data fixes. Note the Oracle Internal Use Only warning: this table should be accessed only through standard Oracle Applications programs, and direct DML is discouraged.

Related Objects

• PER_COMPETENCES — referenced via COMPETENCE_ID; supplies the skill definition for the template.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; enforces security group partitioning.
• FND_USER — implicit FK for CREATED_BY and LAST_UPDATED_BY WHO columns.
• FND_CONCURRENT_PROGRAM / FND_CONCURRENT_REQUESTS — implicit FKs for PROGRAM_ID and REQUEST_ID.
• FND_LOGINS — implicit FK for LAST_UPDATE_LOGIN.
• IEX_STRY_WORK_ITEMS — the runtime work items generated from these templates, referencing the temp identity.
• XDO_TEMPLATES_B — implicit FK via XDO_TEMPLATE_ID for letter/document templating.

These relationships confirm the table's position as a configuration anchor within the IEX Collections strategy framework, feeding downstream work item generation and escalation logic.