Results for “iex_questionnaire_items”

50+ results




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

Overview

IEX_QUESTIONNAIRE_ITEMS is a setup table in the IEX (Collections) schema of Oracle E-Business Suite, owned by the Advanced Collections module. It supports questionnaire administration, a feature that drives structured, question-based data capture during collections interactions. The table stores the defining attributes of questionnaire items, including the business contexts in which each item is presented and the collection stages at which it becomes relevant. In Oracle EBS 12.1.1 and 12.2.2, this object holds configuration metadata consumed by the Collections agent-facing application rather than transactional collections activity itself, which distinguishes it from operational tables such as delinquency or promise records.

From a dimensional modeling perspective, the mined foreign-key structure indicates the object is standalone. Following Data Vault heuristic conventions, IEX_QUESTIONNAIRE_ITEMS is best treated as a hub-style reference entity: it carries a single-part surrogate primary key and descriptive setup attributes, with no documented parent link table. Its role is therefore configuration-driven, defining the vocabulary and behavior of questionnaire items rather than capturing events or relationships between business entities.

Key Information Stored

The table contains 38 documented columns. The primary key is defined by the constraint IEX_QUESTIONNAIRE_ITEMS_PK on QUESTIONNAIRE_ITEM_ID, which serves as the system-generated surrogate identifier for each questionnaire item. A unique business-key candidate, IEX_QUESTIONNAIRE_ITEMS_U1, covers (QUESTIONNAIRE_ITEM_ID, ZD_EDITION_NAME), reflecting the multi-tenant edition pattern used across IEX objects. The column ZD_EDITION_NAME is therefore significant for edition-scoped configuration.

The most important functional columns include:

Numerous enabled flags define the receivable and stage contexts in which the item may be used: RECEIVABLE_ENABLED, LOAN_ENABLED, LEASING_ENABLED, CLAIM_ENABLED, PAYMENT_ENABLED, ADJUSTMENT_ENABLED, DISPUTE_ENABLED, REVERSAL_ENABLED, PROMISE_ENABLED, WRITEOFF_ENABLED, BANKRUPTCY_ENABLED, LITIGATION_ENABLED, and LATER_STAGE_DELINS. Level of use is governed by USING_CUSTOMER_LEVEL, USING_ACCOUNT_LEVEL, USING_BILLTO_LEVEL, USING_DELINQUENCY_LEVEL, DEFINE_PARTY_RUNNING_LEVEL, and DEFINE_OU_RUNNING_LEVEL. Standard EBS audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) support change tracking, and CORRESPONDENCE_ENABLED, CC_ENABLED, EFT_ENABLED, and REPOSESSION_ENABLED capture channel-specific enabling.

Common Use Cases and Queries

Typical usage centers on retrieving active questionnaire configuration and reporting which flags are enabled. A common query pattern filters by enabled status and business level:

  • List active questionnaire items by business level: SELECT QUESTIONNAIRE_ITEM_ID, BUSINESS_LEVEL, COLLECTIONS_METHODS FROM IEX.IEX_QUESTIONNAIRE_ITEMS WHERE RECEIVABLE_ENABLED = 'Y'.
  • Enumerate enabled collection capabilities: query the *_ENABLED flags to audit which features (dispute, promise, writeoff) are configured for a given collection method.
  • Edition-scoped lookups: join or filter on ZD_EDITION_NAME to isolate configuration for a specific edition.
  • Level governance reporting: aggregate USING_* and DEFINE_*_RUNNING_LEVEL columns to verify item applicability across customer, account, bill-to, and delinquency levels.

These queries support setup validation, upgrade impact analysis, and reporting on the breadth of Collections questionnaire coverage. Because the object is configuration-oriented, reporting is typically read-only, with maintenance performed through Collections setup UI rather than direct DML.

Related Objects

Given the metadata identifies this object as standalone, direct foreign-key relationships to parent tables are not documented. Meaningful related objects are those that logically depend on questionnaire setup, including:

The single-part primary key QUESTIONNAIRE_ITEM_ID is the join column expected across these dependent objects; the composite unique index IEX_QUESTIONNAIRE_ITEMS_U1 (QUESTIONNAIRE_ITEM_ID, ZD_EDITION_NAME) should be honored for edition-aware joins. Joins to transactional tables are recommended through QUESTIONNAIRE_ITEM_ID to preserve referential consistency in custom reporting.