Search Results igs_uc_adm_sys_typ

Overview

IGS_UC_ADM_SYSTEMS_V is a reporting and integration view in the Oracle E-Business Suite 12.1.1 / 12.2.2 environment, owned by the APPS schema. It belongs to the Student Systems / UK Higher Education (UCAS admissions) product family within the IGS (Intelligent Grants / Student Information) module. The view exposes administrative system configuration records used in UCAS admissions processing, joining the operational system table IGS_UC_ADM_SYSTEMS with the lookup repository so that human-readable names and descriptions are returned alongside the stored system codes.

Its primary role is to provide a denormalized, query-friendly presentation of UCAS administrative system definitions for reports, interfaces, and integration extracts. The user who searched for "igs_uc_adm_sys_typ" was likely attempting to locate the lookup type that classifies administrative systems; this view is the object through which that lookup type is consumed, since the lookup type string IGS_UC_ADM_SYS_TYP appears as a fixed predicate in the view definition.

Underlying Base Objects

The ETRM metadata documented for this view lists no separately documented base objects, but the view text itself is explicit. It is defined over two sources:

• IGS_UC_ADM_SYSTEMS ADM — the transactional table holding UCAS administrative system rows, including system identifiers, security keys, sequencing, and various flag columns.
• IGS_LOOKUPS_VIEW LV — the standard lookup view that resolves lookup codes to their meanings and descriptions.

The join condition is ADM.UCAS_SYSTEM_CODE = LV.LOOKUP_CODE restricted by LV.LOOKUP_TYPE = 'IGS_UC_ADM_SYS_TYP'. This means the view returns only those IGS_UC_ADM_SYSTEMS rows whose UCAS system code has a matching active lookup entry of the administrative-system type. Because IGS_LOOKUPS_VIEW is generally built over FND_LOOKUP_VALUES-style lookup storage, changes to lookup meanings are reflected dynamically without altering the underlying system records.

Key Columns

• ROW_ID — the ROWID of the underlying IGS_UC_ADM_SYSTEMS row, exposed for row-level identification.
• SYSTEM_ID — the primary system identifier for the administrative system record.
• NAME — the lookup MEANING, providing the display name of the administrative system.
• DESCRIPTION — the lookup description, offering expanded context.
• UCAS_SYSTEM_CODE — the lookup code, which is also the join key and the code stored on the base table.
• UCAS_SECURITY_KEY — the security key associated with the UCAS administrative system.
• MARVIN_SEQ — the sequence value used in MARVIN (UCAS data transfer) processing order.
• CLEARING_FLAG, EXTRA_FLAG, CVNAME_FLAG — operational indicator flags that govern clearing behaviour, extra processing, and CV/name handling respectively.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns for traceability.

Common Use Cases and Queries

This view is typically used to populate LOVs, validate administrative system codes during UCAS interfaces, and drive configuration reports. A representative query retrieves all active administrative systems with their descriptive names:

• SELECT system_id, ucas_system_code, name, description, clearing_flag FROM apps.igs_uc_adm_systems_v ORDER BY marvin_seq;
• SELECT system_id, name FROM apps.igs_uc_adm_systems_v WHERE clearing_flag = 'Y';
• SELECT ucas_security_key FROM apps.igs_uc_adm_systems_v WHERE ucas_system_code = :p_code;

Developers should query this view rather than joining the base tables directly, as it centralises the lookup-type restriction and guarantees consistent name resolution across reports and integrations.