Results for “iex_checklist_items_u1”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IEX.IEX_CHECKLIST_ITEMS_B is an Oracle E-Business Suite table in the IEX (Advanced Collections / Trade Management) schema that stores the master definitions of checklist items used for administrative task tracking. Each row represents a reusable checklist item – a task, questionnaire, or administrative step – that can be assigned to collections agents, collectors, or operational workflows. The table resides in the APPS_TS_TX_DATA tablespace and is registered in FND Design Data as IEX.IEX_CHECKLIST_ITEMS_B with a status of VALID across both 12.1.1 and 12.2.2.

The "_B" suffix denotes the base table of a translated entity, and the presence of the ZD_EDITION_NAME column indicates this object participates in the Oracle EBS 12.2.2 online patching (Editioning) model. Under a Data Vault modelling heuristics classification, the metadata designates this object as standalone, suggesting it is best treated as a reference/hub-style entity rather than a link or satellite, because it holds descriptive master data with no documented foreign-key derivation from another parent.

Key Information Stored

The primary key is CHECKLIST_ITEM_ID, a NUMBER(15) surrogate identifier described as the "PK of checklist item." The unique index IEX_CHECKLIST_ITEMS_U1 is defined over (CHECKLIST_ITEM_ID, ZD_EDITION_NAME), making the pair the business-key candidate that also satisfies Editioning requirements.

• CHECKLIST_ITEM_NAME (VARCHAR2 30) – human-readable name of the checklist item.
• CHECKLIST_ITEM_TYPE (VARCHAR2 30) – category discriminator controlling how the item behaves at runtime.
• CHECKLIST_PARENT_ITEM_ID (NUMBER 15) – self-referencing "master checklist item id," enabling hierarchical groupings of items.
• CHECKLIST_PARENT_ITEM_ID combined with CHECKLIST_ITEM_ID supports item/sub-item structures for composite checklist administration.
• STATUS (VARCHAR2 30) – lifecycle state of the item.
• MANDATORY_FLAG – indicates whether the task must be defined for a checklist.
• START_DATE_ACTIVE and END_DATE_ACTIVE – effective-dating window controlling when the item is active.
• QUESTIONNAIRE_LINK (VARCHAR2 150) – URL that launches the questionnaire page associated with the item.
• TASK_LINK (VARCHAR2 150) – URL that launches the update-task page.
• VIEW_LINK (VARCHAR2 150) – URL that launches the read-only view-task page.
• TASK_LAST_MODIFIED_DATE – timestamp of the last modification to the task.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN – standard WHO audit columns (foreign keys to FND_USER and FND_LOGINS).
• ZD_EDITION_NAME (VARCHAR2 30) – Editioning column supporting 12.2.2 online patching.

Common Use Cases and Queries

Typical reporting includes listing active checklist items for a given date range, identifying mandatory tasks, or retrieving deep links used by the Collections workbench. A representative query follows:

• Active items by type: SELECT CHECKLIST_ITEM_ID, CHECKLIST_ITEM_NAME, CHECKLIST_ITEM_TYPE, STATUS FROM IEX.IEX_CHECKLIST_ITEMS_B WHERE SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE+1);
• Mandatory tasks only: filter on MANDATORY_FLAG = 'Y' and join to child items via CHECKLIST_PARENT_ITEM_ID = CHECKLIST_ITEM_ID.
• Deep-link extraction: select QUESTIONNAIRE_LINK, TASK_LINK, and VIEW_LINK where STATUS is active.
• Audit reconciliation: join LAST_UPDATED_BY to FND_USER.USER_ID and LAST_UPDATE_LOGIN to FND_LOGINS.LOGIN_ID.
• Editioning-aware lookups should constrain on ZD_EDITION_NAME to avoid returning obsolete patched editions.

Related Objects

The metadata documents the table as standalone with no outbound foreign keys beyond WHO columns, so the most significant relationships are the audit lookups and the translated ("_T") mirror of the base table.

• FND_USER – joined via LAST_UPDATED_BY and CREATED_BY to USER_ID.
• FND_LOGINS – joined via LAST_UPDATE_LOGIN.
• IEX_CHECKLIST_ITEMS_TL – translated-language companion sharing CHECKLIST_ITEM_ID.
• IEX_CHECKLIST_ITEMS_U1 – unique index enforcing the business key.
• IEX_CHECKLIST_ITEMS_B_PK – primary key constraint on CHECKLIST_ITEM_ID.
• Self-join on CHECKLIST_PARENT_ITEM_ID for hierarchy traversal.
• IEX checklist and collections task assignment tables that reference CHECKLIST_ITEM_ID when instantiating tasks for collectors.