Results for “hr_quest_fields”

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

Overview

HR_QUEST_FIELDS is a Human Resources (PER) product table in the HR schema of Oracle E-Business Suite, holding the definition of individual fields that make up a questionnaire. Each row describes one question or input element belonging to a questionnaire template, capturing its label, type, validation rules, and presentation attributes. Because questionnaire templates are used across Oracle HRMS for applicant tracking, performance management, and other seeded or custom survey flows, this table acts as the metadata backbone that controls what the end user sees and submits on a questionnaire.

From a Data Vault modeling perspective, the mined foreign-key structure classifies HR_QUEST_FIELDS as satellite-leaning. It does not function as an independent business hub; instead it hangs off the HR_QUESTIONNAIRES parent and carries descriptive attributes about each field. A satellite treatment—anchored to a questionnaire hub via QUESTIONNAIRE_TEMPLATE_ID—is the most natural heuristic fit, with FIELD_ID serving as the primary/unique identifier at the source.

Key Information Stored

The table is documented with 16 physical columns in ETRM 12.2.2. The most operationally significant columns are:

• FIELD_ID — surrogate primary key (HR_QUEST_FIELDS_PK) uniquely identifying each questionnaire field.
• QUESTIONNAIRE_TEMPLATE_ID — foreign key to HR_QUESTIONNAIRES, identifying the parent template. This is the principal join path and business-key candidate for grouping fields by questionnaire.
• NAME — the field's display label or prompt presented to respondents.
• TYPE — the field type (for example text, list, or date), controlling how responses are captured.
• SQL_REQUIRED_FLAG — indicates whether the field is mandatory, often driven by dynamic logic.
• SQL_TEXT — the SQL or lookup statement used to populate selectable values or drive dynamic behavior.
• VALIDATION_TYPE and VALIDATION_DETAIL — the validation rules applied to respondent input and the parameters controlling them.
• HTML_TEXT — rendered HTML markup or instructional content associated with the field.
• DISPLAY_SEQUENCE — the ordinal position controlling the field's order on the questionnaire.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle ADF/BC4J framework.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS who-column audit set.

The documented unique indexes are HR_QUEST_FIELDS_PK on FIELD_ID (the true business-key candidate) and a system-managed LOB index, SYS_IL0000044439C00013$$, which corresponds to the HTML_TEXT or SQL_TEXT large-object column.

Common Use Cases and Queries

Typical scenarios include listing the fields of a given questionnaire, reconstructing the questionnaire layout for reporting, and validating that mandatory or SQL-driven fields are correctly configured. A representative query retrieves the ordered field list for a template:

• SELECT f.field_id, f.name, f.type, f.display_sequence FROM hr.hr_quest_fields f WHERE f.questionnaire_template_id = :template_id ORDER BY f.display_sequence;
• Joining to HR_QUESTIONNAIRES to report all fields against their questionnaire name for administration and audit.
• Joining to HR_QUEST_ANSWER_VALUES on FIELD_ID to summarize responses per field for survey or applicant analysis.
• Filtering on SQL_REQUIRED_FLAG or VALIDATION_TYPE to identify configuration anomalies before go-live.

Related Objects

The following objects are the most significant dependencies, based on the documented foreign-key relationships:

• HR_QUESTIONNAIRES — parent table; HR_QUEST_FIELDS.QUESTIONNAIRE_TEMPLATE_ID references it, defining the questionnaire to which the field belongs.
• HR_QUEST_ANSWER_VALUES — child table; its FIELD_ID references HR_QUEST_FIELDS, storing the responses captured against each field.
• HR_QUEST_ANSWER_COLS and related questionnaire response tables in the PER schema, which consume field definitions during response capture.
• PER questionnaire APIs and OAF pages used to create and render questionnaire templates and their fields.

Together these objects form the questionnaire definition-to-response chain, with HR_QUEST_FIELDS positioned as the descriptive bridge between a questionnaire template and the answers collected against it.