Results for “hr_quest_answer_values”

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

Overview

HR_QUEST_ANSWER_VALUES is a transactional table in the Oracle Human Resources (PER) product module that stores the individual answer values captured against a questionnaire. Within Oracle EBS 12.1.1 and 12.2.2, questionnaires are widely used by HR for activities such as applicant screening, employee surveys, exit interviews, performance assessments, and benefits enrollment. Each row in this table represents one response to one question field belonging to a specific questionnaire submission.

The table resides in the HR schema and is classified in the ETRM documentation as VALID. Under the heuristic Data Vault classification mined from its foreign key structure, HR_QUEST_ANSWER_VALUES is described as a link entity, suggesting that it functions primarily as an associative object connecting questionnaire answers to individual question fields. This modeling suggestion reflects the table's role in resolving the many-to-many style relationship between a questionnaire response header and the questions it contains.

Key Information Stored

The documented physical schema for HR_QUEST_ANSWER_VALUES contains ten columns. The most significant are summarized below.

• QUEST_ANSWER_VAL_ID — The surrogate primary key (HR_QUEST_ANSWER_VALUES_PK) that uniquely identifies each answer value record.
• QUESTIONNAIRE_ANSWER_ID — Foreign key to HR_QUEST_ANSWERS, identifying the parent questionnaire submission to which this answer belongs. This column forms part of the unique business key (HR_QUEST_ANSWER_VALUES_UK1).
• FIELD_ID — Foreign key to HR_QUEST_FIELDS, identifying the specific question field being answered. Together with QUESTIONNAIRE_ANSWER_ID it completes the unique business key.
• VALUE — Holds the actual answer content supplied by the respondent, whether free-text, a coded lookup value, or a numeric score depending on the field definition.
• OBJECT_VERSION_NUMBER — Supports optimistic locking for concurrent update control, a standard feature across Oracle EBS 12.2.2 tables.
• LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — Standard audit columns capturing the user, login session, and timestamp of the most recent modification.
• CREATED_BY, CREATION_DATE — Audit columns recording the original creation context of the record.

Common Use Cases and Queries

Typical reporting scenarios include extracting interview responses for a given candidate, aggregating survey results per question, and auditing who supplied or modified a particular answer. Because answers are keyed by both questionnaire answer and field, joins to HR_QUEST_ANSWERS and HR_QUEST_FIELDS are essential in almost every query.

A representative join pattern retrieves each answer with its question text and its parent questionnaire:

SELECT a.QUESTIONNAIRE_ANSWER_ID,
       f.NAME AS question,
       v.VALUE,
       v.LAST_UPDATE_DATE
FROM   HR.HR_QUEST_ANSWER_VALUES v,
       HR.HR_QUEST_FIELDS f,
       HR.HR_QUEST_ANSWERS a
WHERE  v.FIELD_ID = f.FIELD_ID
AND    v.QUESTIONNAIRE_ANSWER_ID = a.QUESTIONNAIRE_ANSWER_ID
AND    a.QUESTIONNAIRE_ID = :p_questionnaire_id;

Aggregation queries are also common, for example grouping by FIELD_ID to produce distribution statistics for Likert-scale questions. Because VALUE may be stored as a character string, care should be taken when casting numeric responses. The OBJECT_VERSION_NUMBER column should be respected when performing data corrections outside the application to avoid conflicts.

Related Objects

The following objects are most significant in relation to HR_QUEST_ANSWER_VALUES, based on the documented foreign key relationships.

• HR_QUEST_ANSWERS — Parent table joined on QUESTIONNAIRE_ANSWER_ID; represents the questionnaire response header.
• HR_QUEST_FIELDS — Joined on FIELD_ID; defines each question, its data type, and validation rules.
• HR_QUEST_ANSWER_VALUES_PK — Unique index on QUEST_ANSWER_VAL_ID enforcing row uniqueness.
• HR_QUEST_ANSWER_VALUES_UK1 — Unique index on QUESTIONNAIRE_ANSWER_ID and FIELD_ID, ensuring one answer per question per questionnaire submission.
• HR_QUEST_QUESTIONNAIRES and HR_QUEST_QUESTION_FIELDS — Higher-level questionnaire definition tables reachable through HR_QUEST_ANSWERS and HR_QUEST_FIELDS respectively.
• PER_QUESTIONNAIRE_API family of PL/SQL interfaces — Application APIs used to insert, update, and delete answer values while maintaining the documented unique constraints and audit columns.

Together these objects form the questionnaire response data model, with HR_QUEST_ANSWER_VALUES serving as the atomic store of every captured answer.