Results for “inquiry_method_desc”

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

Overview

IGR_I_METHODS_V is a read-only view owned by the APPS schema in the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments. It resides within the IGS (Student System) product family and exposes a filtered, language-specific list of inquiry source types used by student recruitment and admissions inquiry processing. The view presents lookup values that describe how a prospect, applicant, or other inquiry party made contact with the institution—for example, telephone, walk-in, mail, or web inquiry. Although the view follows the naming convention commonly associated with the Oracle iRecruitment module, the documentation classifies this object under IGS – Student System, and it is the student system inquiry-methods window that consumes the data.

The view functions as a reporting and integration facade over the Oracle Workflow/Oracle Application Object Library lookup infrastructure. Rather than storing data of its own, it surfaces rows from the central lookup repository that match a single lookup type and a set of session- and application-scoped predicates. Its principal value is that it converts a generic, multi-purpose lookup table into a semantically named list of inquiry methods for downstream use in forms, reports, and interfaces.

The column most frequently searched for, INQUIRY_METHOD_DESC, provides the descriptive text of each inquiry method and is the field commonly rendered in inquiry source windows, drop-down lists, and operational reports.

Underlying Base Objects

The view is defined exclusively over FND_LOOKUP_VALUES, the shared lookup values entity in the APPS schema. The defining query joins no other table: it selects columns from FND_LOOKUP_VALUES where the lookup type equals ‘VEHICLE_RESPONSE_CODE’. Because it rests on a single base object, the view carries no independent storage, indexes, or constraints, and it inherits the security and language attributes of the underlying lookup rows.

Three predicates refine the result set. First, the lookup type restriction limits output to the VEHICLE_RESPONSE_CODE lookup type. Second, LANGUAGE = USERENV(‘LANG’) returns only rows translated for the language of the current session, ensuring that inquiry method text is presented in the user’s active locale. Third, the query constrains VIEW_APPLICATION_ID = 279 and SECURITY_GROUP_ID = 0, isolating the lookup values owned by the student system application and the default security group.

Key Columns

• ROW_ID – the ROWID of the underlying lookup row in FND_LOOKUP_VALUES; used internally as a unique row identifier.
• INQUIRY_METHOD_CODE – the lookup code that uniquely identifies each inquiry source type; this is the value typically stored on inquiry or prospect records.
• INQUIRY_METHOD – the short display name (MEANING) of the inquiry method.
• INQUIRY_METHOD_DESC – the longer descriptive text (DESCRIPTION) associated with the inquiry method, and the field most commonly referenced in screens and reports.
• LANGUAGE – the language code for which the row was returned.
• ENABLED_FLAG – indicates whether the lookup value is active; inactive methods should generally be excluded from selection lists.
• SOURCE_LANG, SECURITY_GROUP_ID, VIEW_APPLICATION_ID – language of origin and ownership/security context columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard WHO audit columns and the last-update login identifier.

Common Use Cases and Queries

The view is commonly queried to populate inquiry source selection lists, to validate stored inquiry method codes during data conversion, and to drive reports that summarize inquiries by source. The following query lists only active inquiry methods in the session language, ordered for display:

• SELECT inquiry_method_code, inquiry_method, inquiry_method_desc FROM igr_i_methods_v WHERE enabled_flag = ‘Y’ ORDER BY inquiry_method;
• SELECT inquiry_method_desc FROM igr_i_methods_v WHERE inquiry_method_code = :inquiry_code;

Because the view applies no additional filtering, joins, or aggregation, its performance is effectively that of a single indexed lookup on FND_LOOKUP_VALUES, and it can be safely used in concurrent programs, Oracle Reports, and BI Publisher data templates throughout Release 12.1.1 and 12.2.2.