Results for “igs_ad_interface”

50+ results




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

Overview

The view IGS_AD_INTERFACE belongs to the IGS (Student System) product family within Oracle E-Business Suite. As documented in the ETRM metadata, this object is classified as Obsolete, and its stated purpose is to hold import interface run details when admissions data is imported into the system. It functions as an interface staging view, presenting the rows that have been loaded by an admissions import process and are awaiting validation, matching, or transfer into the core person and admissions tables.

From a reporting and integration standpoint, IGS_AD_INTERFACE exposes the raw inbound admission records together with the run-level and error-tracking attributes required to monitor a batch load. The metadata explicitly notes that the object is Not implemented in this database, meaning that in the referenced environment the view is not deployed. In EBS 12.1.1 and 12.2.2, IGS objects are generally associated with the Higher Education / Student System licensing, and many of these interface objects are absent from a standard installation unless that product is fully configured.

Underlying Base Objects

The documented metadata provides no referenced base objects for this view. Notably, the underlying view text does not name any base table directly; instead it selects from an alias TAB, which indicates the definition is generated or resolves internally to one or more admissions interface tables (such as the corresponding IGS_AD_INTERFACE base table). Because the ETRM record lists no confirmed base objects, the exact physical dependency cannot be verified from the metadata alone.

The view text also carries the standard EBS WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and REQUEST_ID — which confirms it is built over a table registered as an EBS concurrent-program interface target, with row-level auditing and request attribution.

Key Columns

Common Use Cases and Queries

Typical use is to inspect staged admissions records before or after the import concurrent program runs, to reconcile errors, and to verify the LEVEL_OF_QUAL value carried on each row.

  • Retrieve all rows for a specific import run.
  • Filter rows that failed validation.
  • Analyse level of qualification distribution across a batch.

Sample queries:

SELECT interface_id, person_number, surname, given_names,
       level_of_qual, status, error_code
FROM   igs_ad_interface
WHERE  interface_run_id = :p_run_id;

SELECT level_of_qual, record_status, COUNT(*)
FROM   igs_ad_interface
WHERE  batch_id = :p_batch_id
GROUP  BY level_of_qual, record_status;

Because the metadata states the view is not implemented in the reference database, these queries succeed only in environments where the IGS Student System interface is actually deployed; otherwise they return an object-not-found error.