Search Results hr_quest_answer_values_fk2

Overview

The table HR.HR_QUEST_ANSWER_VALUES is a core data object within Oracle EBS Human Resources (HRMS) module, specifically designed to store the individual answer values provided for questionnaire fields. In Oracle EBS 12.1.1 and 12.2.2, the questionnaire framework allows organizations to capture structured feedback, survey responses, or custom data entry forms. Each row in this table represents a single answer to a specific field (question) within a questionnaire response. The table acts as a child to the HR_QUEST_ANSWERS table, which holds the overall response to a given questionnaire instance, and as a child to HR_QUEST_FIELDS, which defines the structure of each question. This table is essential for breaking down a completed questionnaire into its atomic answer components, enabling granular analysis and reporting.

Key Information Stored

The table contains the following primary data elements:

• QUEST_ANSWER_VAL_ID (NUMBER(15)): System-generated primary key, sourced from the sequence HR_QUEST_ANSWER_VALUES_S. Uniquely identifies each answer value row.
• QUESTIONNAIRE_ANSWER_ID (NUMBER(15)): Mandatory foreign key referencing HR_QUEST_ANSWERS. Links the answer value to a specific questionnaire response header.
• FIELD_ID (NUMBER(15)): Mandatory foreign key referencing HR_QUEST_FIELDS. Identifies the specific question or field to which this answer corresponds.
• VALUE (VARCHAR2(2000)): The actual answer content provided by the respondent. Supports up to 2000 characters of free-form or selected response data.
• OBJECT_VERSION_NUMBER (NUMBER): System-maintained version number, incremented on each update for concurrency control.
• Audit Columns: Standard Who columns (LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, LAST_UPDATE_DATE, CREATION_DATE) provide full tracking of data changes.

A critical uniqueness constraint, HR_QUEST_ANSWER_VALUES_UK1, enforces that the combination of QUESTIONNAIRE_ANSWER_ID and FIELD_ID is unique. This ensures that for any given questionnaire response, there can be only one answer per question field, preventing duplicate data entry.

Common Use Cases and Queries

The table is typically queried to retrieve or analyze questionnaire results. Common patterns include:

• Extracting all answers for a specific response: Selecting rows by QUESTIONNAIRE_ANSWER_ID to obtain a complete set of answers for a single questionnaire instance.
• Cross-referencing with question definitions: Joining with HR_QUEST_FIELDS to display question labels alongside answer values, enabling reports that present "question → answer" pairs.
• Aggregating responses for analysis: Grouping by FIELD_ID and counting distinct values to calculate frequency distributions for multiple-choice questions.
• Data validation and audit: Checking for orphaned records (where QUESTIONNAIRE_ANSWER_ID or FIELD_ID reference non-existent parent rows) or tracking updates via OBJECT_VERSION_NUMBER.

A sample query pattern for reporting might be:

SELECT qa.questionnaire_answer_id,
       qf.field_label,
       qav.value
FROM   hr.hr_quest_answer_values qav
       JOIN hr.hr_quest_fields qf ON qav.field_id = qf.field_id
       JOIN hr.hr_quest_answers qa ON qav.questionnaire_answer_id = qa.questionnaire_answer_id
WHERE  qa.questionnaire_id = :p_questionnaire_id;

Related Objects

The table has documented referential relationships with the following objects in the Oracle EBS schema:

• Parent Table: HR.HR_QUEST_ANSWERS – Represents the header of a completed questionnaire. The column QUESTIONNAIRE_ANSWER_ID in HR_QUEST_ANSWER_VALUES is a foreign key referencing this table. Joining on QUESTIONNAIRE_ANSWER_ID links individual answer values to their response header.
• Parent Table: HR.HR_QUEST_FIELDS – Defines the metadata for each question field within a questionnaire. The column FIELD_ID is a foreign key referencing this table. Joining on FIELD_ID associates answer values with their respective question definitions, including labels, data types, and ordering.
• Indexes: The table is supported by two unique indexes—HR_QUEST_ANSWER_VALUES_PK (on QUEST_ANSWER_VAL_ID) and HR_QUEST_ANSWER_VALUES_UK1 (on QUESTIONNAIRE_ANSWER_ID, FIELD_ID)—plus a non-unique index HR_QUEST_ANSWER_VALUES_FK2 (on FIELD_ID). All indexes reside in tablespace APPS_TS_TX_IDX and are of type NORMAL.
• Dependent Objects: The table is referenced by APPS-layer views (starting with HR_), though specific view names are not enumerated in the provided metadata. No bidirectional dependencies on database objects are listed.