Search Results config_func_name_desc




Overview

IGR_I_INQUIRY_TYPES_V is an Oracle E-Business Suite view owned by the APPS schema in the IGS (Student System) product family. It is documented as a Form View for the IGS_I_INQUIRY_TYPE base table, meaning it was constructed primarily to support an Oracle Forms inquiry-type maintenance screen rather than as a standalone reporting object. The view presents inquiry type definitions — the classifications used by institutions to categorize prospective-student and applicant inquiries — in a denormalized, display-ready form. Because it joins in descriptive attributes from several supporting tables, it is also a convenient read-only source for reports, extracts, and integration interfaces that must resolve coded values to their user-facing descriptions.

The user search term "configurability_func_name" corresponds directly to a column exposed by this view, indicating the view is frequently consulted when investigating how inquiry types are wired to configurable business logic.

Underlying Base Objects

The view is defined over four objects, joined largely with outer joins so that an inquiry type row survives even when optional attributes are not populated:

All three supporting joins are outer joins, so an inquiry type appears even if its source type, information type, or configurability function is null. The ETRM 12.2.2 metadata does not enumerate additional referenced base objects beyond these.

Key Columns

  • INQUIRY_TYPE_ID / INQUIRY_TYPE_CD / INQUIRY_TYPE_DESC — the surrogate identifier, unique code, and descriptive name of the inquiry type.
  • ENABLED_FLAG — indicates whether the inquiry type is active and selectable.
  • IMP_SOURCE_TYPE_ID / IMP_SOURCE_TYPE — the source type identifier and its resolved description, indicating which prospect or applicant source the inquiry type is associated with.
  • INFO_TYPE_ID / INFORMATION_TYPE / INFORMATION_TYPE_DESC — the linked information type and its code/description.
  • CONFIGURABILITY_FUNC_NAME — the Oracle Forms function name assigned to drive configurability (conditional behavior) for the inquiry type.
  • CONFIG_FUNC_NAME_DESC — the user function name derived from FND_FORM_FUNCTIONS_VL, providing a readable label for the configurability function.
  • Audit columnsCREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
  • ROW_ID — the ROWID of the underlying IGR_I_INQUIRY_TYPES row, used by the Forms block for row identification.

Common Use Cases and Queries

Typical uses include listing enabled inquiry types for a configuration or setup report, auditing which inquiry types have a configurability function attached, and joining the view to inquiry data to resolve descriptions instead of codes.

Query 1 — list enabled inquiry types with resolved descriptions:

  • SELECT inquiry_type_cd, inquiry_type_desc, imp_source_type, information_type, enabled_flag
  • FROM igr_i_inquiry_types_v
  • WHERE enabled_flag = 'Y'
  • ORDER BY inquiry_type_cd;

Query 2 — identify inquiry types wired to configurability logic:

  • SELECT inquiry_type_cd, inquiry_type_desc, configurability_func_name, config_func_name_desc
  • FROM igr_i_inquiry_types_v
  • WHERE configurability_func_name IS NOT NULL;

Query 3 — audit inquiry types missing optional attributes:

  • SELECT inquiry_type_cd, imp_source_type, information_type, configurability_func_name
  • FROM igr_i_inquiry_types_v
  • WHERE imp_source_type IS NULL OR information_type IS NULL;

Because the view is read-only and based on outer joins, it is safe for reporting and extraction. Any requirement to modify inquiry types must be performed against the IGR_I_INQUIRY_TYPES base table or through the corresponding Oracle Forms screen.