Search Results iex_checklist_items_b




Overview
Explore in AI Chat

Overview

IEX_CHECKLIST_ITEMS_B is a Collections (IEX) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the administrative definitions of checklist items. Checklist items are the discrete questions, tasks, and verification steps presented to collections agents, credit analysts, and customers during the collections workflow. Rather than storing transactional responses, this table acts as the definitional foundation for question sets, customer questionnaires, and follow-up tasks that drive credit and collection activities. Records are maintained through the Collections administration setup and are referenced when a checklist is instantiated against a specific customer, collector, or transaction.

The table carries no documented foreign-key dependencies, and the ETRM relationship metadata classifies it heuristically as a standalone Data Vault model. In modeling terms, this suggests treating IEX_CHECKLIST_ITEMS_B as a hub or reference satellite: the primary key provides the durable identity of each checklist item, while descriptive attributes such as name, type, and status behave as satellite-level descriptive context rather than relational links to other hubs.

Key Information Stored

The table is defined with 18 columns in the documented physical schema. The most significant are:

The unique index IEX_CHECKLIST_ITEMS_U1 confirms that CHECKLIST_ITEM_ID combined with ZD_EDITION_NAME is the business-key candidate, while the primary key relies on CHECKLIST_ITEM_ID alone.

Common Use Cases and Queries

Typical scenarios include reporting on active checklist items, auditing mandatory items, and generating setup listings for implementation reviews. A common query pattern selects active, non-expired items of a given type:

  • Listing mandatory items: SELECT CHECKLIST_ITEM_ID, CHECKLIST_ITEM_NAME FROM IEX_CHECKLIST_ITEMS_B WHERE MANDATORY_FLAG = 'Y' AND STATUS = 'A'.
  • Date-effectiveness filtering: WHERE TRUNC(SYSDATE) BETWEEN NVL(START_DATE_ACTIVE, SYSDATE) AND NVL(END_DATE_ACTIVE, SYSDATE).
  • Hierarchy discovery: self-join on CHECKLIST_PARENT_ITEM_ID to reveal nested checklist structures.
  • Integration checks: joining QUESTIONNAIRE_LINK, TASK_LINK, and VIEW_LINK values to their target objects to detect orphaned or incomplete setup.

Related Objects

Because the documented relationship data marks this table as standalone, related objects are inferred from its structural role rather than from enforced foreign keys.