Results for “answer_type_code”

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

Overview

IGF_AP_APPL_SETUP_ALL is an Oracle E-Business Suite table owned by the IGF (Financial Aid) schema, documented as VALID under ETRM for releases 12.1.1 and 12.2.2. Its documented description — "Describes the user-defined questions for each organization" — identifies it as the configuration repository that drives supplemental question sets presented to applicants during the financial aid application process. Each row defines one question, its answer type, validation bounds, and the calendar instance (term) and organization (ORG_ID) against which it is effective.

Because the table is multi-org enabled (ORG_ID), it stores setup data partitioned by operating unit, allowing institutions or scholarship bodies to present different question sets per organization. From a Data Vault modeling perspective, the metadata's heuristic classification is satellite-leaning: the table carries descriptive, historized attributes keyed by a surrogate identifier, with a dependent child table contributing application data. This classification is a modeling suggestion rather than a physical constraint.

Key Information Stored

The table exposes 27 documented columns. The most significant are:

• QUESTION_ID — the surrogate primary key (IGF_AP_APPL_SETUP_ALL_PK), uniquely identifying each configured question.
• QUESTION — the prompt text displayed to the applicant; also part of the third unique index.
• ORG_ID — the operating unit that owns the question definition, enforcing multi-org isolation.
• CI_CAL_TYPE and CI_SEQUENCE_NUMBER — the calendar type and sequence identifying the term instance the question applies to; these compose the foreign key to IGS_CA_INST_ALL.
• APPLICATION_CODE and APPLICATION_NAME — identify the application context in which the question is presented.
• ANSWER_TYPE_CODE — controls the expected response format (for example text, numeric, date, list of values).
• ENABLED and ACTIVE_FLAG — toggle whether the question is currently active.
• REQUIRED_FLAG — indicates whether an answer is mandatory.
• MINIMUM_VALUE_NUM, MAXIMUM_VALUE_NUM, MINIMUM_DATE, MAXIMIUM_DATE — numeric and date validation boundaries (note the documented spelling of MAXIMIUM_DATE).
• ALL_TERMS_FLAG and OVERRIDE_EXIST_ANT_DATA_FLAG — control whether the question applies across all terms and whether prior applicant data may be overridden.
• LD_CAL_TYPE, LD_SEQUENCE_NUMBER, LOOKUP_CODE, DESTINATION_TXT, HINT_TXT — list-of-values source, routing destination, and applicant guidance.

The business-key candidates are the unique indexes IGF_AP_APPL_SETUP_ALL_U1 (QUESTION_ID) and IGF_AP_APPL_SETUP_ALL_U3 (CI_CAL_TYPE, CI_SEQUENCE_NUMBER, QUESTION, APPLICATION_CODE).

Common Use Cases and Queries

Typical usage centres on administrative maintenance and applicant-facing rendering of question sets. Common patterns include:

• Listing active questions for a given term and organization:

SELECT question_id, question, answer_type_code, required_flag
FROM   igf_ap_appl_setup_all
WHERE  org_id = :p_org_id
AND    ci_cal_type = :p_cal_type
AND    ci_sequence_number = :p_seq
AND    active_flag = 'Y'
ORDER BY question_id;

• Identifying required questions with numeric bounds to validate submissions via MINIMUM_VALUE_NUM and MAXIMUM_VALUE_NUM.
• Joining to IGF_AP_ST_INST_APPL_ALL on QUESTION_ID to retrieve applicants' recorded answers for reporting or audit.
• Auditing configuration changes using CREATED_BY, CREATION_DATE, LAST_UPDATED_BY and LAST_UPDATE_DATE.

Related Objects

• IGS_CA_INST_ALL — referenced via the composite foreign key CI_CAL_TYPE / CI_SEQUENCE_NUMBER, supplying the term instance definition.
• IGF_AP_ST_INST_APPL_ALL — child table whose QUESTION_ID references this table, storing applicant-supplied answers per question.
• IGF_AP_APPL_SETUP_ALL_PK and IGF_AP_APPL_SETUP_ALL_UK — the primary and unique key constraints governing integrity.
• ORG_ID — resolves through the standard multi-org views (for example HR_OPERATING_UNITS) to the owning organization.

Together, these objects form the configuration-to-response chain underpinning financial aid application processing in IGF.