Results for “igf_ap_appl_setup”

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

Overview

IGF_AP_APPL_SETUP is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGF (Financial Aid) product family. It exposes the configuration rows that define the questions presented to applicants within the Financial Aid application setup flow. Each row represents a single configurable question, its presentation attributes, its validation rules, and the answer type expected from the applicant. The view is therefore the primary reference point for reporting, integration, and diagnostic work involving applicant-facing setup questions.

The view is defined over the multi-org table IGF_AP_APPL_SETUP_ALL and applies a row-level security predicate based on the session's operating unit. It is not a base table; it holds no data of its own and derives every row from the underlying _ALL table at query time. The presence of the ANSWER_TYPE_CODE column, referenced in the originating search, makes this view the natural lookup when investigating how a given question captures and validates its response.

Underlying Base Objects

The documented base object is IGF_AP_APPL_SETUP_ALL. The view text selects from this table using SELECT DISTINCT, aliasing it as IAS and projecting all significant setup columns while preserving the ROWID as ROW_ID. The DISTINCT clause together with the join-free projection suggests the view is essentially a filtered reader of the base table rather than an aggregation.

The defining predicate restricts returned rows by ORG_ID. It compares the table's ORG_ID against the operating unit derived from USERENV('CLIENT_INFO'), using NVL and DECODE logic so that a client_info value beginning with a space yields NULL, and a sentinel of -99 is used when no context is available. Multi-org security is thus enforced at the view level, meaning any query issued directly against the view returns only rows visible to the current session's operating unit. The metadata documents no additional referenced base objects and no foreign keys, so consumers should treat this view as a single-table projection with an embedded security clause.

Key Columns

• ROW_ID — the ROWID of the base table row, exposed as a stable identifier for the question configuration.
• QUESTION_ID and QUESTION — the identifier and the display text of the applicant question.
• ANSWER_TYPE_CODE — the code governing how the answer is captured (for example free text, number, date, or lookup), and the column most frequently referenced in queries against this view.
• ENABLED and ACTIVE_FLAG — flags indicating whether the question is active and available for use.
• ORG_ID — the operating unit to which the configuration row belongs; drives the view's security predicate.
• REQUIRED_FLAG — indicates whether the applicant must supply an answer.
• MINIMUM_VALUE_NUM, MAXIMUM_VALUE_NUM, MINIMUM_DATE, MAXIMIUM_DATE — numeric and date bounds applied to the answer according to its type.
• LOOKUP_CODE — the lookup value linked to the question, typically used when the answer type is a list of values.
• CI_CAL_TYPE, CI_SEQUENCE_NUMBER, LD_CAL_TYPE, LD_SEQUENCE_NUMBER — calendar type and sequence references associated with the configuration.
• ALL_TERMS_FLAG and OVERRIDE_EXIST_ANT_DATA_FLAG — behavioural switches controlling term applicability and overrides of existing antecedent data.
• DESTINATION_TXT and HINT_TXT — destination text and guidance shown to the applicant.
• Standard audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include auditing the questions presented to applicants, validating that an answer type is assigned correctly, confirming operating-unit-specific configurations, and extracting setup data for downstream reporting or migration.

To list all questions for the current operating unit:

SELECT question_id, question, answer_type_code, required_flag FROM igf_ap_appl_setup WHERE active_flag = 'Y';

To inspect answer type usage across questions:

SELECT answer_type_code, COUNT(*) FROM igf_ap_appl_setup GROUP BY answer_type_code;

To review validation bounds for numeric answers:

SELECT question_id, minimum_value_num, maximum_value_num, lookup_code FROM igf_ap_appl_setup WHERE answer_type_code = 'NUM';

Because the view enforces the operating unit from CLIENT_INFO, sessions must set the org context (for example through FND_GLOBAL or the standard MO initialization) before querying; otherwise only rows matching the default sentinel are returned. This behaviour should be accounted for in any integration or concurrent program that reads the view.