Search Results other_inst_id

Overview

IGS_AD_OTHER_INST_V is a seeded Oracle E-Business Suite view owned by the APPS schema and delivered as part of the IGS — Student System product family. It is classified in the ETRM repository under the Student System module, which covers admissions, student records, curriculum, and related higher-education entities. The view presents data about "other institutions" recorded against an admission application — that is, prior or alternate educational institutions supplied by an applicant during the admissions process.

The view exposes both the surrogate primary key OTHER_INST_ID and a denormalized institution name resolved from the institution reference table. This makes it directly usable in reporting, transactional inquiries, and integration extracts without requiring the consumer to perform a join to the institution lookup themselves. Because the view carries audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and a ROW_ID pseudo-column, it can also be used by tools that require row identifier semantics, such as Oracle Forms or certain data-migration utilities.

Underlying Base Objects

The view is defined over two objects. The driving table is IGS_AD_OTHER_INST (aliased OI), which stores the other-institution records associated with an admission application. The second object is IGS_OR_INSTITUTION (aliased I), the institution reference table, joined for the purpose of resolving the institution's descriptive name.

The join condition is I.INSTITUTION_CD = OI.INSTITUTION_CODE. The view therefore returns one row for each row in IGS_AD_OTHER_INST whose INSTITUTION_CODE matches a valid institution code. Note the ETRM metadata lists "Referenced base objects: none documented" for the 12.2.2 definition; this reflects a gap in the scraped metadata rather than an absence of underlying tables. The view text itself, reproduced in the excerpt, confirms the two-source join. The ROW_ID column is derived from OI.ROWID, so uniqueness and updatability characteristics follow the underlying IGS_AD_OTHER_INST row.

Key Columns

• OTHER_INST_ID — Surrogate primary key of the underlying other-institution record. This is the identifier most commonly searched by developers and support personnel.
• ROW_ID — Row identifier derived from OI.ROWID; useful for direct row access.
• PERSON_ID — The person (applicant) to whom the other-institution record belongs. Joins to person tables in the Student System.
• ADMISSION_APPL_NUMBER — The admission application number linking the record to a specific application.
• NOMINATED_COURSE_CD — Course nominated in relation to the other institution, where applicable.
• SEQUENCE_NUMBER — Ordering sequence for the record within its application context.
• INSTITUTION_CODE — Code of the prior/other institution as stored on the transactional record.
• NAME — Descriptive name of the institution, resolved from IGS_OR_INSTITUTION.NAME.
• NEW_INSTITUTION — Indicator flag on the record.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is typically queried when investigating a specific other-institution record by its identifier, when listing all other institutions declared on an application, or when producing extracts that need the institution name alongside the code.

Retrieve a single record by primary key:

SELECT * FROM apps.igs_ad_other_inst_v WHERE other_inst_id = :p_other_inst_id;

List all other institutions for an applicant, ordered by sequence:

SELECT other_inst_id, admission_appl_number, institution_code, name, sequence_number
FROM apps.igs_ad_other_inst_v
WHERE person_id = :p_person_id
ORDER BY admission_appl_number, sequence_number;

Find applicants who named a specific institution, using the resolved name for readability:

SELECT person_id, admission_appl_number, institution_code, name
FROM apps.igs_ad_other_inst_v
WHERE institution_code = :p_institution_code;

Because the view resolves the institution name internally, reports avoid repeating the join to IGS_OR_INSTITUTION. Consumers should nonetheless be aware that the inner join means a record whose INSTITUTION_CODE does not resolve to a valid institution will not appear in the view; in such cases the base table IGS_AD_OTHER_INST must be queried directly.