Search Results inquiry_method_code




Overview
Explore in AI Chat

Overview

The view IGS_RC_I_METHODS_V belongs to the Oracle E-Business Suite IGS – Student System product family, which is the foundation of the Oracle Student System (OSS) recruitment and admissions functionality. Its documented purpose is to expose Inquiry Source Type values derived from the Oracle Student System lookup type VEHICLE_RESPONSE_CODE. Despite the "VEHICLE" prefix, this lookup is not related to fleet or transportation data; within the Student System it enumerates the media and mechanisms through which an inquiry about a student program is received — for example printed material, web forms, telephone, or referred contacts.

The view plays a supporting reporting and integration role. Rather than presenting transactional admissions data, it provides a controlled, language-aware reference list of valid inquiry method codes that ETRM components (inquiry capture forms, prospect tracking, and downstream analytical reports) rely upon. Because it is built over the Foundation FND_LOOKUP_VALUES structure, it inherits Oracle EBS features such as multilanguage (MLS) descriptions and the standard descriptive-flexfield audit columns (Who columns).

Per the ETRM documentation metadata, the view is not implemented in the supplied database. This is an important practical note: the definition exists in the ETRM metadata repository, but the object may not be deployed in every environment, and it does not appear in the standard seeded data model for all releases. The Documented view metadata (ETRM 12.2.2) confirms no documented Owner and no documented referenced base objects, meaning the only authoritative source of its definition is the stored view text itself. This behaviour is consistent across Oracle EBS 12.1.1 and 12.2.2, since the underlying Foundation architecture of lookup views is unchanged between the two releases.

Underlying Base Objects

The view is defined directly over a single Foundation base object, FND_LOOKUP_VALUES, aliased as LK. This is the standard Oracle EBS lookup values table, which stores the individual lookup codes, their translated meanings and descriptions, enabled flags, and audit attributes. The view is therefore a filtered projection of that table, not a join of multiple tables.

Three filters are applied in the WHERE clause:

  • LOOKUP_TYPE = 'VEHICLE_RESPONSE_CODE' — isolates the Student System inquiry-source lookup set from the many other lookup types in the table.
  • LANGUAGE = USERENV('LANG') — restricts rows to the language of the current database session, returning the appropriate translated meaning for the logged-in user.
  • VIEW_APPLICATION_ID = 279 AND SECURITY_GROUP_ID = 0 — scopes the rows to the owning application (Application ID 279, the Student System) and the standard Oracle security group, ensuring only the intended application's values are exposed.

Because the source is a Foundation view (FND_LOOKUP_VALUES itself is a view over FND_LOOKUP_VALUES_B and FND_LOOKUP_VALUES_TL), the effective lineage is the base table plus its translation table. The ROWID column is carried through from the lookup row, allowing stable identification of individual lookup entries.

Key Columns

The columns exposed by the view mirror the lookup structure and can be grouped as follows:

  • ROW_ID — the ROWID of the underlying lookup row, useful for uniqueness and debugging.
  • INQUIRY_METHOD_CODE — the lookup code value, i.e., the technical code identifying the inquiry source type. This is the code returned by the inquiry_method_code search term.
  • LANGUAGE — the language code of the returned row, matching the session language.
  • INQUIRY_METHOD — the translated Meaning of the lookup code; the user-facing label.
  • INQUIRY_METHOD_DESC — the long description associated with the code.
  • ENABLED_FLAG — indicates whether the inquiry method is active and selectable.
  • SOURCE_LANG — the language of the source (base) definition.
  • SECURITY_GROUP_ID, VIEW_APPLICATION_ID — application scope identifiers.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle "Who" audit columns.

Common Use Cases and Queries

The view is typically used to populate list-of-values (LOV) selections, validate user input, and drive prospect-source reporting. To list all active inquiry methods in the current session language:

  • SELECT inquiry_method_code, inquiry_method, inquiry_method_desc
  • FROM igs_rc_i_methods_v
  • WHERE enabled_flag = 'Y';

To retrieve a specific code's meaning for display or validation:

  • SELECT inquiry_method
  • FROM igs_rc_i_methods_v
  • WHERE inquiry_method_code = :p_code;

To join inquiry records against their source type, the view supplies the descriptive label for each stored code. Analysts must still confirm that the object has been deployed in the target instance, since the ETRM metadata records it as Not implemented in this database. Where unavailable, the equivalent query may be issued directly against FND_LOOKUP_VALUES using the same VEHICLE_RESPONSE_CODE filter.