Search Results question_code




Overview
Explore in AI Chat

Overview

ICX_QUESTIONS is a configuration table owned by the ICX schema (Oracle iProcurement) in Oracle E-Business Suite 12.1.1 and 12.2.2. The table stores the definition of individual questions used by the "Asking Oracle" plug-in, a self-service component that guides users through diagnostic or decision-support prompts within the iProcurement and iSupport framework. Each row represents a single question definition, identified by a business code and associated with an application context that scopes the question to a specific module or plug-in deployment.

Because ICX_QUESTIONS serves as the master reference for question definitions against which user responses are captured, its heuristic Data Vault classification is hub. It carries the natural business key (QUESTION_CODE) and descriptive attributes, but no foreign key dependencies were mined from the schema, reinforcing its role as a standalone reference object rather than a link or satellite.

Key Information Stored

The documented physical schema exposes 8 columns. The most significant are:

  • QUESTION_CODE — The primary key column of ICX_QUESTIONS_PK and the primary business-key candidate. Uniquely identifies each question definition referenced by the plug-in at run time.
  • APPLICATION_ID — Scopes the question to a specific Oracle application, allowing the same questions table to serve multiple products.
  • TYPE — Classifies the question (for example, by input mode or mechanism), driving how the plug-in renders and processes the prompt.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit (WHO) columns tracking creation and modification history of each question definition.

QUESTION_CODE is both the surrogate primary key and the business key, since no separate unique index beyond the PK is documented. The table is narrow by design; descriptive text and answer choices typically reside in companion ICX objects rather than being denormalized here.

Common Use Cases and Queries

Typical use cases include auditing the question set presented by the Asking Oracle plug-in, resolving questions by code during troubleshooting, and validating application scoping. A basic lookup pattern:

  • SELECT question_code, application_id, type FROM icx.icx_questions WHERE question_code = :code;
  • SELECT q.question_code, q.application_id, q.type FROM icx.icx_questions q WHERE q.application_id = :app_id ORDER BY q.question_code;
  • SELECT question_code, last_update_date, last_updated_by FROM icx.icx_questions WHERE last_update_date > SYSDATE - 30;

Reporting scenarios include generating a catalog of all questions per application, tracking configuration changes through the WHO columns, and verifying that question codes referenced by plug-in setups exist in the table. Because the object is standalone, queries do not require multi-table joins for basic lookups.

Related Objects

No foreign keys were mined, so relationships are functional rather than enforced. Objects that commonly reference or depend on ICX_QUESTIONS in iProcurement and iSupport include:

  • ICX_QUESTIONS_PK — the primary key constraint on QUESTION_CODE, enforcing uniqueness.
  • ICX_ANSWERS (or equivalent answer tables) — capture user responses keyed by QUESTION_CODE.
  • ICX_QUESTION_DEFINITIONS / question-answer mapping tables — associate questions with plug-in flows.
  • FND_APPLICATION — resolve APPLICATION_ID to an application name.
  • FND_USER — resolve CREATED_BY and LAST_UPDATED_BY to user identities.
  • iProcurement / iSupport "Asking Oracle" setup APIs and UI pages — consume question definitions at run time.

Because relationships are not enforced by the database, integrity between ICX_QUESTIONS and its consumers depends on application logic rather than constraints.