Search Results icx_question_functions

Overview

ICX_QUESTION_FUNCTIONS is a table in the ICX schema, belonging to the Oracle iProcurement product family within Oracle E-Business Suite. Its description in the ETRM repository is recorded simply as "Retrofitted," indicating that the object was introduced or re-created to support a specific functional retrofit rather than being part of the original baseline schema. Functionally, the table serves as a mapping bridge between stored questions (typically questionnaire or survey items presented to users in iProcurement flows) and the named functions or logical actions those questions are associated with. This mapping lets the application resolve which question set applies to a given function context without hard-coding logic into the form layer.

From a data vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone. In practice, the composite primary key of the table — QUESTION_CODE combined with FUNCTION_NAME — makes it behave like a link-style association, connecting a question entity to a function entity. Because no enforced foreign keys were mined, the object is treated as a standalone lookup rather than a true hub or satellite.

Key Information Stored

The documented physical schema for ETRM 12.2.2 lists nine columns. The most important are the two business-key columns that form the primary key, ICX_QUESTION_FUNCTIONS_PK:

• QUESTION_CODE — the business identifier of the question; part of the composite primary key and the primary join value to question definition tables.
• FUNCTION_NAME — the internal name of the application function to which the question is attached; the second component of the composite primary key.
• QUESTION_ID — the surrogate identifier for the question, used for internal referential lookups against the question master table.
• FUNCTION_ID — the surrogate identifier for the function, pairing with QUESTION_ID to support surrogate-based joins.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS "Who" audit columns required on all transactional and setup tables for concurrency control and auditability.

The presence of both business-key columns (QUESTION_CODE, FUNCTION_NAME) and surrogate columns (QUESTION_ID, FUNCTION_ID) is significant: business logic and reporting should generally resolve through the surrogate IDs to the master entities, while QUESTION_CODE and FUNCTION_NAME serve as the human-readable and integrity-enforcing key pair.

Common Use Cases and Queries

The most common scenario is determining which questions are presented for a given function, or conversely which functions a question participates in. A straightforward query joins on the composite key:

• List questions for a function: SELECT QUESTION_CODE, QUESTION_ID FROM ICX.ICX_QUESTION_FUNCTIONS WHERE FUNCTION_NAME = :function_name;
• List functions for a question: SELECT FUNCTION_NAME, FUNCTION_ID FROM ICX.ICX_QUESTION_FUNCTIONS WHERE QUESTION_CODE = :question_code;
• Resolve to the question master via surrogate: join QUESTION_ID to the question definition table, and FUNCTION_ID to the function registry, to obtain full text and form metadata.
• Audit setup changes: filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to report newly added question-to-function mappings.

Reporting use cases include verifying complete question coverage across iProcurement functions, identifying orphaned questions that map to no function, and migration checks when retrofitting question sets between environments.

Related Objects

Although the mined relationship data classifies this object as standalone, its surrogate and business-key columns imply dependencies on the following iProcurement and EBS objects:

• ICX_QUESTIONS (question master) — joined via QUESTION_ID and QUESTION_CODE.
• FND_FORM_FUNCTIONS — the standard EBS function registry, joined via FUNCTION_NAME or FUNCTION_ID to resolve function metadata.
• ICX_QUESTION_FUNCTIONS_PK — the composite unique index enforcing QUESTION_CODE and FUNCTION_NAME integrity.
• ICX_QUESTION_ANSWERS / response tables — downstream of the question master, indirectly related through QUESTION_ID.
• ICX_QUESTIONNAIRES — grouping entities that reference question codes used in this mapping.
• iProcurement setup and administrative concurrent programs that maintain question-to-function assignments.

Because no enforced foreign keys exist, referential integrity is maintained at the application layer, so joins should be validated against the question and function masters when used in custom reports.